SRE II: Reliability Engineer, Observability & AI-Driven Ops
JPMorganChase
Get a reply from this employer — a resume and cover letter tailored to exactly what they’re hiring for.
Benefits offered by this job
Job summary
JPMorgan Chase is seeking a Site Reliability Engineer II to help ensure reliable operations across our enterprise systems. You will work within the Corporate and Investment Bank Payments Technology Team, leveraging software engineering best practices and AI-enabled tooling to accelerate incident triage and post-incident analysis.
The role involves cross-functional collaboration, ownership of incident and change management, and building observability so production services stay healthy with
Qualifications
- 2+ years of software engineering experience with formal training or certification.
- Experience with AI-assisted tooling in production reliability work.
- Strong understanding of networking (DNS, TCP/IP, VPN, load balancing).
- Experience across on-prem and public cloud environments.
- Hands-on observability with production monitoring and tracing.
Responsibilities
- Deliver end-to-end service delivery to ensure reliable operations.
- Define and maintain SLOs/SLIs and error budgets with cross-functional teams.
- Use enterprise AI capabilities to speed incident triage and post-incident analysis while ensuring data sensitivity.
- Own incident, problem (RCA), and change/event management.
- Monitor production environments and build alerting to minimize downtime.
- Design Dynatrace instrumentation to monitor performance and user experience.
- Apply AI insights to identify toil and reliability risks and drive improvements.
Skills
Tools
Job description
JPMorgan Chase is seeking a Site Reliability Engineer II to help ensure reliable operations across our enterprise systems. You will work within the Corporate and Investment Bank Payments Technology Team, leveraging software engineering best practices and AI-enabled tooling to accelerate incident triage and post-incident analysis.
The role involves cross-functional collaboration, ownership of incident and change management, and building observability so production services stay healthy with
'/%3e%3cpath%20d='M101.744%2012.4726L102.894%2016.1947L99.0021%2013.2201L101.744%2012.4726ZM105.3%208.40937H100.488L99.0026%203.59473L97.5116%208.41047L92.7%208.40385L96.5965%2011.3834L95.1055%2016.1942L99.0021%2013.2196L101.408%2011.3834L105.3%208.40992V8.40937Z'%20fill='white'/%3e%3cdefs%3e%3clinearGradient%20id='paint0_linear_5593_1381'%20x1='90'%20y1='9.44471'%20x2='99'%20y2='9.44471'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%2300AD70'/%3e%3cstop%20offset='0.998594'%20stop-color='%2300B67A'/%3e%3cstop%20offset='1'%20stop-color='%23DCDCE6'/%3e%3c/linearGradient%3e%3c/defs%3e%3c/svg%3e){kind=small}
