Drimva

JPMorgan Chase

Lead Software Engineer - Java, AI, Spring Boot and Kafka

$138K–$185K

Chicago, IL · Full-time · Posted Oct 6, 2026

Experience
8+ years of applied experience, including hands-on delivery of system design, application development, testing, and operational stability.
Education
Formal training or certification in software engineering concepts.

About the job

Leads engineering for a next-generation equipment and asset finance platform, delivering secure, scalable lease origination, asset valuation, and lifecycle management capabilities.

What you'll do

  • Designs, develops, tests, troubleshoots, and maintains production software to architectural and quality standards.
  • Sets technical direction for a global feature team, mentoring engineers and partnering with Product Owners, Operations, and Technology teams.
  • Promotes approved AI-assisted engineering practices and improves application stability, observability, code quality, and deployment reliability.

What they ask for

  • Formal training or certification in software engineering concepts.
  • Advanced Java development, including Java 21+ and system design, concurrency, and modern language features.
  • Advanced Spring Boot 3.x / Spring Framework 6.x experience, including microservices, RESTful APIs, and Kafka.
  • Hands-on experience with React 18+, TypeScript, relational databases, and Hibernate / JPA; experience leading approved AI-assisted development and validating outputs.

Nice to have

  • Experience with Next.js 14+, cloud platforms, Kubernetes, Helm, or infrastructure-as-code tools.
  • Experience with testing and observability tools, Redis, GraphQL, data pipelines, or relevant financial-services and asset-finance domains.

Pay

$137,750.00-$185,000.00 USD base salary

Tools

Java 21+, Spring Boot 3.x / Spring Framework 6.x, Kafka, React 18+, TypeScript, Oracle SQL / PostgreSQL, Hibernate / JPA, OpenAPI 3.x

AI focus

Leads adoption of enterprise-authorized AI-assisted software development and automation, validating outputs for correctness, performance, security, and responsible handling of sensitive data.

Model-written summary · the original posting is authoritative

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