What are the responsibilities and job description for the Lead eSoftware Engineer - DevOps position at JPMorgan Chase?
We have an opportunity to impact your career and provide an adventure where you can push the limits of what's possible.
As a Lead eSoftware Engineer at JPMorgan Chase within the Commercial and Investment Banking - Electronic Trading Technology (ETT) team, you are an integral part of an agile team that works to enhance, build, and deliver trusted market-leading technology products in a secure, stable, and scalable way. As a core technical contributor, you are responsible for conducting critical technology solutions across multiple technical areas within various business functions in support of the firm’s business objectives. You will help build and run latency-sensitive services that operate under real-time constraints, and bring strong engineering discipline and attention to detail to design, implementation, testing, and production readiness—delivering changes that are correct, predictable, and resilient during market hours.
Job responsibilities
- Manage and coordinate releases across environments (UAT → production), ensuring readiness checks, clear change documentation, stakeholder communication, and reliable rollback plans
- Own production reliability and latency for algo/execution services (including post trading hours releases, operational readiness, and market-hours support posture)
- Executes creative software solutions, design, development, and technical troubleshooting with ability to think beyond routine or conventional approaches to build solutions or break down technical problems
- Manage and own UAT environment provisioning and configuration for on‑prem hosts—supporting uptime, deployments, environment triage, and release readiness in coordination with partner teams
- Build and improve CI/CD and release engineering for Java services with automated builds, artifact/versioning discipline, promotion across environments, gated releases, and fast rollback
- Partner with infrastructure/networking teams on Linux and network performance considerations that impact latency, jitter, and stability
- Drive incident management excellence in knowing rapid triage, root-cause analysis, and permanent remediation to reduce recurrence and MTTR
- Engineer for resiliency with HA/DR design, failover testing, dependency isolation, and capacity
- Identify opportunities to eliminate or automate remediation of recurring issues to improve overall operational stability of software applications and systems
- Leads communities of practice across Software Engineering to drive awareness and use of new and leading-edge technologies
- Adds to team culture of diversity, opportunity, inclusion, and respect
Required qualifications, capabilities, and skills
- Formal training or certification on software engineering concepts and 5 years applied experience
- Hands-on practical experience delivering system design, application development, testing, and operational stability
Advanced development experience in one or more programming language(s) (i.e., Python, Java, or equivalent)
- Proficient in all aspects of the Software Development Life Cycle
- Familiar with AI-assisted development tools in the development lifecycle (and ability to evaluate outputs critically)
- Advanced understanding of agile methodologies such as CI/CD, Application Resiliency, and Security
Demonstrated proficiency in software applications and technical processes within a technical discipline (e.g., cloud, artificial intelligence, machine learning, mobile, etc.)
- Proven track record with observability (metrics/logs/traces), alert design, and SLO-driven reliability practices
- In-depth knowledge of the financial services industry and their IT systems
- Strong troubleshooting across app OS network layers being comfortable with incident response and postmortems
Practical cloud native experience
Preferred qualifications, capabilities, and skills
- Experience with high-throughput and/or low-latency systems
- Proven track record with observability (metrics/logs/traces), alert design, and SLO-driven reliability practices
- Experience designing for non-functional requirements (resiliency, scalability, supportability) and driving those into implementation