Skip to main content

Match Group

Software Engineer II, Backend

Los Angeles, California$145k–$150kfull-timemidAdded yesterday

About this role

Join Tinder's backend engineering team to build and maintain systems powering a massive global dating platform handling billions of daily interactions. You'll own critical backend infrastructure serving tens of millions of users across 190+ countries while having significant autonomy and measurable impact on core product features.

What you'll do

  • Design and implement scalable backend systems handling billions of daily swipes and millions of matches
  • Develop APIs and services supporting the Tinder mobile app across global markets
  • Collaborate on architecture improvements and technology innovation initiatives
  • Contribute to safety, performance, and reliability of production systems
  • Participate in code reviews and mentor junior engineers on the team
  • Explore and evaluate emerging technologies to enhance platform capabilities

What they're looking for

  • Backend development and API design
  • Distributed systems and scalability
  • Database design and optimization
  • Cloud infrastructure (AWS, GCP, or Azure)
  • Strong problem-solving and system design
  • Proficiency in Java, Go, Python, or similar languages
  • Experience with high-scale systems
  • Collaborative communication and teamwork
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Match Group

Match Group builds dating and relationship platforms including Tinder and Hinge, using technology to connect people. The company is hiring Machine Learning Engineers to develop AI-driven user experiences and Android Engineers to build and improve mobile applications.

View all jobs at Match Group

Likely interview questions

  • Describe your experience designing systems that handle high traffic and scale. How did you approach performance optimization?
  • Tell us about a complex backend architecture decision you made. What trade-offs did you consider?