Skip to main content

MongoDB

Software Engineer 3, Atlas Search Systems

San FranciscoFrom $209kmidAdded 1 month ago

About this role

Join MongoDB as a Software Engineer 3 for Atlas Search Systems, where you'll design and enhance scalable solutions for their innovative search platform. In this role, you'll collaborate with a talented team to develop robust software and contribute to projects that streamline data retrieval for users across multiple cloud environments.

What you'll do

  • Improve scalability and user experience of Atlas Search
  • Collaborate with team members on technical decisions
  • Lead projects and manage subsystems
  • Contribute to the architecture and roadmap of the system
  • Support existing projects and implement improvements

What they're looking for

  • 2+ years backend software experience
  • Expertise in distributed systems
  • Familiarity with public cloud platforms
  • Proficiency in a modern statically typed language, preferably Java
  • Strong technical communication skills
  • Ownership mindset and ability to learn quickly

Benefits

  • Employee affinity groups
  • Fertility assistance
  • Generous parental leave policy
  • Supportive and enriching culture
  • Opportunities for personal growth
Apply on the employer's site

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.

View all jobs at MongoDB

Likely interview questions

  • Can you walk us through a distributed system you've designed or maintained? What challenges did you face around scalability and observability?
  • Tell us about your experience with multithreaded applications. How have you approached concurrency issues and testing in complex codebases?