Lead Software Engineer - API Gateway, AWS
JPMorgan Chase & Co. (company site, opens in a new tab)7+ yrsMumbaiOn-siteDirect career pageEst. 30–45 LPA
Posted 21h ago
Reach people at JPMorgan Chase & Co.
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at JPMorgan Chase & Co. you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Design, build, and enhance microservices frameworks and platform services including API gateways and management for external APIs.
- Implement scalable, secure API, microservices, and event-driven application patterns across cloud (AWS) and edge platforms.
- Drive engineering excellence via automation, CI/CD, operational ownership, AI-assisted development practices, and coding standards adoption.
Minimum Requirements
- 5+ years applied software engineering experience with formal training or certification.
- 7+ years programming experience in Java, Python, and/or Golang.
- 3+ years hands-on experience with AWS (including EKS), Infrastructure as Code (Terraform), and API gateway/management (e.g., Kong).
- Advanced knowledge of cloud platforms, containerization (Docker, Kubernetes), and engineering fundamentals (architecture, design, code review).
Ideal Candidate Profile
- Experienced in leading and embedding AI-assisted software development tools and practices, with focus on validation standards and responsible AI use.
- Comfortable working across multiple teams in Agile/Lean/Continuous Delivery environments with strong collaboration.
- Strong expertise in AWS platform engineering including networking, security, and observability; familiarity with event-driven architectures and messaging/streaming patterns.