Drimva

JPMorgan Chase

Software Engineer III - Asset Management Research Engineer

$138K–$185K

Jersey City, NJ · Full-time · Posted Aug 21, 2026

Experience
3+ years of applied experience.
Education
Formal training or certification on software engineering concepts.

About the job

Builds and maintains secure, scalable software for Asset Management Fundamental Research Technology, including applications and systems that support the firm’s business objectives.

What you'll do

  • Designs, develops, troubleshoots, and maintains production software and algorithms; creates architecture and design artifacts for complex applications.
  • Uses authorized AI coding tools to assist with coding, testing, refactoring, and documentation, validating outputs for correctness, security, and performance.
  • Analyzes and visualizes data to identify patterns and improve software applications, coding practices, and system architecture.

What they ask for

  • Formal training or certification in software engineering concepts and 3+ years of applied experience.
  • Hands-on system design, application development, testing, and operational stability experience; experience maintaining code in a large corporate environment.
  • Java fluency; practical experience with React and modern JavaScript/TypeScript; working experience with Kafka and event-driven patterns.
  • Experience with authorized AI-assisted software development tools, responsible AI practices, SDLC, agile methods, CI/CD, resiliency, security, and AWS.

Nice to have

  • UX/UI design experience, including user-centered interfaces, UI standards, and accessibility.
  • Financial Services experience.

Pay

USD 137,750.00-$185,000.00 base salary

Tools

Java, React, JavaScript/TypeScript, Kafka, AWS, CI/CD

AI focus

Uses enterprise-authorized AI-assisted development tools for coding, refactoring, tests, troubleshooting, and documentation; evaluates outputs and follows responsible-use, data-sensitivity, security, and resiliency practices.

Model-written summary · the original posting is authoritative

First seen Oct 28, 2026 · Last verified Nov 5, 2026 (UTC)