Backend Engineer Interview — APIs, Databases, Distributed Systems
Backend interviews lean heavier on system design, persistence, and operational concerns than the generalist SWE loop. Expect to spend a full round on one or two database/queue/cache topics, plus deeper questions about availability, consistency, and observability than a frontend or full-stack candidate would see.
Technical screen (60 min). One coding problem with a backend flavour — concurrency, retry/idempotency, parsing structured data, or implementing a small server endpoint.
API / service design (60 min). Design a REST or gRPC API for a real product feature. Interviewer cares about resource modelling, idempotency, error handling, versioning, and pagination.
System design — distributed (60 min). Larger system: chat, ride-hailing, ticketing, payment ledger. Focus on partitioning, replication, consistency model, hot-spot mitigation, and failure modes.
Data & storage round (45–60 min). SQL-vs-NoSQL trade-offs, indexing, query plans, cache-invalidation strategy, schema migration in production, sharding.
Behavioural (45 min). Operational ownership stories: post-mortems, on-call pages, debugging in production, working with SRE/security/data teams.
Top Backend Engineer technical questions
These are pulled from interview-debrief patterns we see most often across Engineering roles. They are not memorization fodder — interviewers reword them constantly. Practice the underlying skill, not the wording.
Design a distributed counter that survives node failures. What consistency guarantees can you offer?
When would you choose Postgres over MongoDB? Give a concrete example where you'd pick each.
Explain CAP, then PACELC. When have you actually had to choose?
How does a B-tree index differ from a hash index? When does one beat the other?
Walk through what happens during a cross-region database failover. What can go wrong silently?
Design an idempotent payment API. Discuss request keys, retries, and replay attacks.
How would you implement at-least-once delivery on top of Kafka? Where do duplicates come from?
Optimize a slow query: SELECT * FROM orders WHERE customer_id = ? ORDER BY created_at DESC LIMIT 10 over 200M rows.
Design rate limiting for an API gateway. Token bucket vs leaky bucket vs sliding window — pick one and defend it.
How do you migrate a column from VARCHAR to JSONB on a 50M-row table without downtime?
Explain isolation levels (READ COMMITTED → SERIALIZABLE). Give a concrete bug each one prevents.
How would you audit which microservice depends on which database/topic?
Behavioural questions
Tell me about the worst production incident you've debugged. What was the root cause and what changed afterward?
Describe a service you owned that you'd architect differently in hindsight.
When have you said no to a feature request because of a backend constraint? How did the conversation go?
Walk me through a tricky data-migration you ran. How did you de-risk it?
Preparation tips for Backend Engineer candidates
**Always state your consistency model explicitly.** Strong, eventual, read-your-writes, monotonic — interviewers want the vocabulary, not just hand-waving.
**Treat retries as a first-class part of the design.** Idempotency keys, dedup windows, and side-effect ordering separate senior backend candidates from juniors.
**Memorize the storage-engine cheat sheet.** Postgres MVCC, MySQL InnoDB pages, Cassandra LSM trees, Redis single-threaded event loop — one-line summaries are enough.
**Bring a real war story.** Backend rounds often pivot from textbook to 'tell me about a time' — have a 5-minute incident narrative ready.
Practice with the AI mock interviewer
Panor's AI Job Assistant runs voice-based mock interviews tuned to the Backend Engineer role. It ad-libs follow-up questions, calls out red flags in your answers, and produces a transcript with rubric-graded feedback. Resume × JD matching is also included — paste a target job description and the assistant rewrites your bullets in STAR format with keyword alignment scoring.
Strong candidates with relevant experience generally need 4–6 weeks of focused prep for a competitive Backend Engineer loop. Career switchers should plan on 8–12 weeks, weighted heavily toward the engineering fundamentals.
Do I need to grind LeetCode?
For most Backend Engineer loops in 2026, depth on a curated set of 60–80 problems beats grinding 400. Focus on the patterns the questions above test, not problem volume.
Is the format the same at startups vs Big Tech?
No. Big Tech tends to over-index on coding and system design; startups put more weight on judgement, speed, and 'will this person carry the team'. Read the JD and ask the recruiter for the explicit loop structure — they will tell you.