Senior Lead SRE - Platform Standards, Observability & Production Readiness in Glasgow

Senior Lead SRE - Platform Standards, Observability & Production Readiness in Glasgow

Glasgow Full-Time 63000 - 77000 £ / year (est.) On-site
JPMorganChase

At a Glance

  • Tasks: Lead the charge in site reliability engineering, ensuring top-notch service availability and observability.
  • Company: Join JPMorgan Chase, a leader in tech innovation and reliability.
  • Benefits: Competitive salary, career growth, and opportunities to work with cutting-edge technology.
  • Other info: Collaborative environment with mentorship opportunities and a focus on continuous improvement.
  • Why this job: Make a real impact by setting reliability standards across multiple platforms.
  • Qualifications: Advanced SRE knowledge and experience in observability and AI capabilities.

The predicted salary is between 63000 - 77000 £ per year.

Elevate your engineering expertise to new heights by joining a team of exceptionally talented professionals and position yourself among the top tier in site reliability.

As a Senior Lead Site Reliability Engineer at JPMorgan Chase within the Chief Technology Office, SRE Enablement, you work with your fellow stakeholders to define non-functional requirements and availability targets for the services in your application and product lines. You will ensure those requirements are accounted for in your products' design and test phases, that your service level indicators are effectively measuring customer experience, and that service level objectives are defined with stakeholders and implemented in production.

What makes this role different from most site reliability engineering roles in the firm: our team does not run a single application. We set the reliability and observability standards that whole platform organisations are held to, and then we get them adopted across engineering teams we do not own. The estate runs to many dozens of applications across several technology towers. You will spend as much time persuading engineers of a standard as implementing one, and the standards you set are enforced at the production gate rather than suggested in a document.

Our core method is the observability assessment, and you will run them end to end. That is one process with four outputs, and you produce all of them: the user journeys as the customer would describe them, the map of which alerts actually cover each step of those journeys, the service level indicators for the service level objectives that matter to the journey rather than to a component, and a failure modes and effects analysis derived from that journey work. Each step surfaces the gaps for the thing it just produced. You then design and run a chaos gameday to test whether the failure modes and effects analysis was right, because such an analysis is a hypothesis until something breaks on purpose.

Job responsibilities

  • Creates and delivers high-quality designs, roadmaps, and programme charters alongside the engineering team.
  • Runs observability assessments end to end: user journeys, alert coverage mapping, journey-level service level indicators and service level objectives, and a design-phase failure modes and effects analysis; then designs and runs the chaos gameday that tests it.
  • Scores applications against the production-readiness bar and holds the line at the gate — a completed failure modes and effects analysis and a passed gameday are conditions of go-live in our organisation, not recommendations, so your assessment is the thing standing between an application and production.
  • Acts as a key resource and mentor for technologists in your area seeking advice on technical and business issues, and serves as a culture carrier and site reliability adoption champion for your team.
  • Collaborates with others to create and implement observability and reliability designs for complex systems that are robust, stable, and do not incur additional toil or technical debt.
  • Replaces whole-service and component-health measurement with journey-level indicators, working out which alerts and service level indicators an application should actually have and proving the indicator moves when the thing it measures breaks.
  • Proves an indicator can report a breach before trusting it — querying equations against the metrics store rather than reading them, because plenty of definitions look correct and return nothing.
  • Uses enterprise-authorized AI capabilities within the work environment to accelerate reliability design and operational decisioning (e.g., incident and post-incident analysis and requirements traceability), validating outputs and handling operational data according to sensitivity and security requirements.
  • Applies those capabilities at estate scale rather than one service at a time, helping design and run automated screening across the estate and validating what it returns.
  • Drives evolution and debugging of critical components by understanding application and platform interdependencies and limitations.
  • Contributes across the breadth of what the team does — which in any given quarter has included reliability assessments and production-readiness reviews, chaos gameday design and delivery, service level objective quality analysis at scale, migrating and rationalising service level objective estates between platforms, defining alerting standards, resiliency and recovery evidence for audit, and building the small internal tools that make all of the above repeatable.

Required qualifications, capabilities, and skills

  • Formal training or certification on site reliability engineering concepts and advanced applied experience.
  • Brings an advanced understanding of site reliability culture and principles and a track record of demonstrating how to implement site reliability within an application or platform.
  • Advanced knowledge and experience in observability such as white and black box monitoring, service level objectives, alerting, and telemetry collection.
  • Hands-on fluency writing and debugging queries against a time-series metrics store — PromQL or equivalent — as a daily activity rather than an occasional one.
  • Practical experience defining service level indicators and service level objectives from user journeys, and the judgement to distinguish a customer-facing indicator from a component health check.
  • Demonstrated experience using enterprise-authorized AI capabilities within the work environment to improve reliability engineering workflows, with strong validation habits and awareness of data sensitivity.
  • Ability to set team practices for safe AI usage in operations (e.g., review and approval expectations and escalation paths) while maintaining resiliency, security, and auditability outcomes.
  • Advanced knowledge of software applications and technical processes with considerable depth in one or more technical disciplines.
  • Strong communication skills and a desire to mentor and educate others on site reliability engineering principles and practices.
  • The ability to communicate findings an engineering team may not want to hear — with evidence — while maintaining productive working relationships.

Preferred qualifications, capabilities, and skills

  • Experience with failure modes and effects analysis or an equivalent structured failure-analysis method, and the ability to run the exercise with an application team rather than write it for them.
  • Experience designing and running chaos or fault-injection experiments, with tooling such as Gremlin or AWS Fault Injection Simulator, and specifically designing experiments to test whether anyone notices — not only whether something breaks.
  • Hands-on experience with Dynatrace, Prometheus or Cortex-based metrics platforms, and Grafana.
  • Experience with error budgets as an input to delivery decisions, including what happens when one is exhausted.
  • Familiarity with resiliency and recovery governance: recovery time and recovery point objectives, application recovery plans, and the evidence an internal audit expects to see.
  • Experience working across lines of business or legal entities where you have influence but no direct authority, and comfort operating in a globally distributed team with the autonomy that implies.

Senior Lead SRE - Platform Standards, Observability & Production Readiness in Glasgow employer: JPMorganChase

J.P. Morgan Europe Limited is an exceptional employer, offering a dynamic work culture that fosters collaboration and innovation in the heart of the financial sector. Employees benefit from comprehensive growth opportunities, competitive compensation, and a commitment to professional development, all while contributing to impactful consumer banking initiatives. Working here means being part of a prestigious institution that values insights and empowers its team members to drive meaningful change.

JPMorganChase

Contact Details:

JPMorganChase Recruitment Team

StudySmarter Expert Advice🤫

We think this is how you could land Senior Lead SRE - Platform Standards, Observability & Production Readiness in Glasgow

✨Join Local Tech Meetups

Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at JPMorganChase or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!

✨Contribute to Open Source Projects

Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to JPMorganChase.

✨Tap into Online Developer Communities

Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like JPMorganChase.

✨Explore Job Boards Specifically for Tech Roles

Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like JPMorganChase that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!

We think you need these skills to ace Senior Lead SRE - Platform Standards, Observability & Production Readiness in Glasgow

Site Reliability Engineering
Observability
Service Level Objectives
Alerting
Telemetry Collection
PromQL
Failure Modes and Effects Analysis

Some tips for your application 🫡

Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.

Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at JPMorganChase.

Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at JPMorganChase and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!

Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!

How to prepare for a job interview at JPMorganChase

✨Brush Up on Your Coding Skills

For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.

✨Know Your Tools and Frameworks

Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If JPMorganChase uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.

✨Showcase Your Projects

Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.

✨Prepare for Behavioural Questions

While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.