Backend Tech Lead

Quantum Machines is a global leader in control systems for quantum computing, a field on the verge of exponential growth. Our innovative hardware and software mark a groundbreaking approach in quantum computer control, scaling from individual qubits to expansive arrays of thousands. At the core of QM lies a passionate and ambitious team committed to reshaping the construction and operation of quantum computers. Our work is fueled by a deep understanding of customer needs, driving us to deliver unparalleled solutions in this revolutionary field. We are looking for a hands-on Tech Lead to drive the technical direction of the core backend layer over the company's flagship product — and to lead the engineers building it.

The systems you'll own handle bursty, high-throughput workloads — thousands of requests per second with strict latency requirements, distributed coordination, and hard concurrency problems. Your job is to make sure we solve them right: through architecture you shape, designs you review, and code you still write.

It is a unique opportunity to lead a team of top-notch engineers working on cutting-edge technologies in a fast-paced environment of quantum computation.

What Makes This Role Different

Our backend team sits in the middle of everything — we're the orchestration layer between:

• Hardware control systems (C++)

• Client exposed SDK (Python)

• Reporting and managing system (Go)

• Our business logic (Java/Kotlin + Spring)

As Tech Lead, you're the technical anchor of that layer. When teams disagree on where a boundary belongs, you drive the decision. When a design has a flaw nobody's spotted, you're the one expected to catch it. And when the hardest problem lands, you're still close enough to the code to pick it up yourself.

What You'll Own

• Technical direction — architecture of the backend layer: concurrency models, resource pooling, distributed coordination, API boundaries. You set the direction and defend it with reasoning, not authority.

• Design quality — you lead design reviews, raise the bar on what "good" means, and know when to insist and when "good enough to ship" wins.

• The team's growth — mentoring engineers through design conversations and code reviews, growing seniors into people who can own systems end-to-end.

• Cross-team alignment — you're the backend voice in decisions spanning C++, Python, and Go teams: API contracts, integration points, performance budgets.

• Production — when something breaks at 2 AM levels of urgency, you lead the dig-in, drive the root cause, and make sure the class of bug dies, not just the instance.

• Delivery trade-offs — balancing tech debt against roadmap, with the judgment to know which shortcuts are loans and which are landmines.