Lead Software Engineer

JPMorgan Chase JPMorgan Chase · Banking · Wilmington, DE +1 · Consumer & Community Banking

Lead Software Engineer at JPMorgan Chase in Consumer and Community Banking Operations Dispute technology. Responsible for designing, developing, and deploying highly scalable, fault-tolerant, mission-critical distributed systems and cloud modernization initiatives. Drives technical design decisions, serves as technical lead for full-stack development, and ensures code quality and security. Collaborates with cross-functional teams and provides L3 production support.

What you'd actually do

  1. Lead the design, development, and deployment of highly scalable, fault-tolerant, mission-critical distributed systems and cloud modernization initiatives that process high-volume financial transactions with zero-downtime
  2. Drive technical design decisions and long-term architecture strategy, making critical choices on technology stack, architectural patterns, and infrastructure solutions while evaluating and introducing emerging technologies that improve team productivity and system capabilities
  3. Serve as technical lead for full-stack development, providing hands-on guidance to engineers on complex technical challenges, driving code review excellence, and championing engineering best practices across the team
  4. Ensure code quality and security through comprehensive automated testing strategies (unit, integration, end-to-end), static code analysis, and vulnerability scanning
  5. Mentor and develop engineering talent within the team, conducting technical coaching sessions and fostering a culture of continuous learning and technical excellence

Skills

Required

  • Java
  • Spring Boot
  • RESTful API design
  • microservices architecture
  • AWS cloud services (EC2, ECS/EKS, Lambda, S3, RDS, SQS/SNS, API Gateway, CloudWatch)
  • Terraform
  • React JS
  • PostgreSQL
  • Oracle databases
  • event-driven architectures
  • message queues (SQS/SNS)
  • streaming platforms (Kafka, AWS MSK)
  • application security principles
  • OAuth2/JWT authentication
  • CI/CD pipelines
  • test-driven development (TDD)
  • application resiliency patterns
  • observability
  • production monitoring (Splunk, Dynatrace, CloudWatch)

Nice to have

  • financial services industry
  • regulatory requirements
  • Agentic AI solutions
  • machine learning model integration
  • AI-powered automation frameworks
  • Camunda BPMN
  • workflow orchestration engines
  • GraphQL API design

What the JD emphasized

  • highly scalable
  • zero-downtime
  • critical technology solutions
  • highly scalable distributed systems
  • high-availability production environments
  • high-throughput systems
  • operational stability
  • continuous improvement