MongoDB
Software Engineer 3, Networking & Observability
About this role
MongoDB is hiring a Software Engineer 3 to enhance the networking and observability capabilities of their distributed database. You'll work on low-level system components that affect database performance, reliability, and diagnostics, collaborating with teams across the company.
What you'll do
- Improve and maintain MongoDB's networking and observability codebase
- Lead medium-sized projects from technical design through delivery
- Collaborate with cross-functional teams throughout the project lifecycle
- Conduct code reviews and participate in design discussions
- Contribute to development of new features for major releases
- Debug and fix issues in production-level code
What they're looking for
- C++ (required)
- Distributed systems design
- Networking protocols and architecture
- Observability frameworks and OpenTelemetry
- Data structures and algorithms
- Software design and architecture
- System performance optimization
- Cross-team communication
Benefits
- Employee affinity groups and community
- Fertility assistance
- Generous parental leave policy
- Flexible work arrangements (NYC office or remote within US/Canada)
- Professional development and career growth opportunities
- Support for employees with disabilities
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
- Describe your experience building and maintaining distributed systems at scale. What was your role and what did you accomplish?
- Walk us through a complex networking or observability issue you debugged. How did you approach it and what was the outcome?