MongoDB
Site Reliability Engineer 3
About this role
MongoDB is seeking a Site Reliability Engineer in New York City to design and optimize global infrastructure for its MongoDB Atlas platform. The role emphasizes building resilient systems and automation while reducing operational burden and enhancing system health visibility.
What you'll do
- Design and build infrastructure for a global cloud service with MongoDB clusters
- Implement and troubleshoot service automation and monitoring
- Optimize infrastructure performance from application to firmware
- Participate in a weekly on-call rotation
- Improve infrastructure capabilities for cost and maintainability
What they're looking for
- 3+ years in Linux environments
- Proficiency in modern programming languages
- Familiarity with web/network protocols (HTTP, TLS, DNS)
- Experience with automation tools
- Knowledge of cloud platforms (AWS, GCP, Azure)
- Networking and security experience
Benefits
- Supportive corporate culture
- Affinity groups and professional development
- Fertility assistance
- Generous parental leave policy
- Commitment to diversity and inclusion
Opens the official application on the employer’s site. No login required.
MongoDB
MongoDB builds a cloud database platform (Atlas) and related tools that help enterprises operate MongoDB at scale, along with AI-powered migration and infrastructure management solutions. The company is hiring technical services engineers to support enterprise customers with complex database troubleshooting and infrastructure challenges, and software engineers to develop AI-powered code generation tools, Atlas management systems, and cloud product capabilities.
- Website
- mongodb.com
Likely interview questions
- Tell us about your experience running mission-critical services at scale in Linux environments. What was the largest infrastructure you've managed, and what metrics defined success?
- Describe your approach to designing automation for a globally distributed system spanning multiple cloud providers. How would you handle different cloud APIs and provider-specific constraints?