Overview
Models write backend code that passes the happy-path test and falls over on everything else: the race condition under load, the N+1 that melts the database, the API contract that breaks every client the day you change it. Someone has to reason about the system, not just the snippet, and that someone is you.
As a Backend Engineer you'll stress-test how models design services, data models, and APIs, expose where their reasoning breaks under real load, and write the answers a strong backend engineer would stand behind.
What you’ll actually do
- Probe backend reasoning across service design, data modeling, and API contracts, and see where the model's design falls apart.
- Find the failures that matter: race conditions, N+1 queries, bad indexes, and breaking changes hiding in a clean-looking diff.
- Write the correct design when the model falls short, with the scaling and consistency trade-offs made explicit.
Roles this fits
Common backgrounds: Backend Engineer, API Engineer, Platform Engineer.
What we look for
- Professional or serious open-source experience building backend services.
- Comfort with databases, APIs, and concurrency; most tasks assume a language like Python, Go, Java, or Rust.
- Clear written English: your explanations are the training signal.
- No degree required. We care about what you can do, not where you learned it.