MongoDB
About this role
This role owns the reliability architecture of a MongoDB platform across regions and cloud providers, which is a broader remit than keeping one service healthy. You would collaborate with the teams building the platform, advising on operability, capacity and practice, and set the operational standards for the SRE team itself: on call quality, incident response and service level objective discipline. Mentoring and technically developing the SRE team is stated as part of the job, and so is participating in a 24 by 7 on call rotation, which is worth deciding about before applying rather than after. The technical requirement is 10 or more years operating distributed systems with deep Kubernetes expertise, specifically including designing or evolving multi cluster platforms. One requirement stands out as unusual and interesting: understanding workload isolation at the systems level, and the tradeoffs between containers and virtual machines for running untrusted code.
Who this is for
What the posting requires:
- 10+ years of experience working on software and operating distributed systems, with deep Kubernetes expertise including designing or evolving multi cluster platforms.
- Proficiency in Python, Go or a similar programming language.
- Understanding of workload isolation at the systems level: containers, virtual machines, and the tradeoffs between them for running untrusted code.
- A customer focused mindset.
- Valuing efficiency in processes and operations, with a strong preference for automation over manual processes.
What the posting sets as position expectations:
- Own the reliability architecture of the platform across regions and cloud providers.
- Collaborate with the teams building the platform, providing internal support and guidance on operability, capacity and best practices.
- Set operational standards for the team: on call quality, incident response and service level objective discipline.
- Mentor and technically develop the SRE team.
- Participate in a 24 by 7 on call rotation to resolve issues involving platform infrastructure.
⚠️ The on call commitment is stated plainly as a 24 by 7 rotation. At staff level that usually means you are also the escalation point for others' incidents. Weigh it honestly against the seniority and scope on offer.
The detail worth noticing: the requirement about running untrusted code tells you something about the platform. Isolation tradeoffs between containers and virtual machines only become a live question when you are executing code you did not write, which makes this a more interesting systems problem than standard service reliability work.
Location and working pattern: the posting states MongoDB is looking for candidates based in Bengaluru for its hybrid working model.
Honest fit guidance: ten years plus deep multi cluster Kubernetes is a high and specific bar. The distinguishing experience is having designed or evolved multi cluster platforms rather than operated a single one, and being able to talk about isolation tradeoffs concretely. If you have that, the scope here, reliability architecture across regions and clouds, is genuinely staff level rather than a retitled senior role.
- 10+ years of experience working on software and operating distributed systems, with deep Kubernetes expertise including designing or evolving multi cluster platforms.
- Proficiency in Python, Go or a similar programming language.
- Understanding of workload isolation at the systems level: containers, virtual machines, and the tradeoffs between them for running untrusted code.
- A customer focused mindset.
- Valuing efficiency in processes and operations, with a strong preference for automation over manual processes.
What the posting sets as position expectations:
- Own the reliability architecture of the platform across regions and cloud providers.
- Collaborate with the teams building the platform, providing internal support and guidance on operability, capacity and best practices.
- Set operational standards for the team: on call quality, incident response and service level objective discipline.
- Mentor and technically develop the SRE team.
- Participate in a 24 by 7 on call rotation to resolve issues involving platform infrastructure.
⚠️ The on call commitment is stated plainly as a 24 by 7 rotation. At staff level that usually means you are also the escalation point for others' incidents. Weigh it honestly against the seniority and scope on offer.
The detail worth noticing: the requirement about running untrusted code tells you something about the platform. Isolation tradeoffs between containers and virtual machines only become a live question when you are executing code you did not write, which makes this a more interesting systems problem than standard service reliability work.
Location and working pattern: the posting states MongoDB is looking for candidates based in Bengaluru for its hybrid working model.
Honest fit guidance: ten years plus deep multi cluster Kubernetes is a high and specific bar. The distinguishing experience is having designed or evolved multi cluster platforms rather than operated a single one, and being able to talk about isolation tradeoffs concretely. If you have that, the scope here, reliability architecture across regions and clouds, is genuinely staff level rather than a retitled senior role.
Apply on company site
Opens www.mongodb.com, the employer's own application page. Applying is always free.