Software Engineer 3

MongoDB MongoDB · Enterprise · Toronto, ON · PTO Billing

Software Engineer 3 role focused on designing, building, and operating backend services for Cloud Payments at MongoDB. The role involves ingesting and processing large volumes of usage and billing data, collaborating with various teams, and ensuring system reliability and scalability. Experience with Java, distributed systems, and databases is required, with a preference for financial systems experience.

What you'd actually do

  1. Design, implement, and operate backend services that ingest, process, and reconcile large volumes of usage and billing data from internal and external systems
  2. Collaborate with product, Finance, Revenue, and other engineering teams to evolve our billing and payments capabilities and improve customer experience
  3. Own features end‑to‑end: requirements, design, implementation, testing, rollout, monitoring, and iterative improvement
  4. Help scale and harden our systems as Atlas and our broader Cloud business continue to grow rapidly
  5. Contribute to improving our tooling, observability, and development workflows so the whole team can move faster and safer

Skills

Required

  • 3+ years of experience building and maintaining backend systems in a compiled language, ideally Java
  • Understand core object‑oriented design principles and how to apply them to complex, evolving systems
  • Experience with distributed systems and services that need to be highly available, observable, and correct at scale
  • Are comfortable working with databases (relational and/or non‑relational such as MongoDB) in production environments
  • Communicate clearly and enjoy working with both technical and non‑technical stakeholders across multiple teams

Nice to have

  • Experience with billing, payments, or other financial systems where correctness, auditability, and compliance really matter
  • Experience with cloud platforms (AWS, GCP, Azure) and modern communication protocols like gRPC
  • Familiarity with data-intensive applications, data pipelines, or data lakes
  • Exposure to working with I/O frameworks like Reactor
  • Experience with containerization and orchestration (e.g., Docker, Kubernetes)
  • Prior exposure to MongoDB as a developer or operator

What the JD emphasized

  • correctness
  • auditability
  • compliance