The unusual one: the technical rounds are normal, but the general round is mostly not about engineering. It is about sitting with a customer, scoping a vague problem, and defending a trade-off out loud to someone non-technical.
Engineering loops are the most structured of any discipline, and the most predictable. Expect a recruiter screen, one or two technical rounds, a system design conversation at mid-level and above, and a behavioral round that is usually underestimated.
The technical rounds are rarely won on the answer. They are won on narration — whether the interviewer can follow your reasoning while you work, and whether you say the trade-off out loud instead of silently picking one.
Each round is run by the interviewer built for it, with its own scoring axes — not one generic interviewer asked to change subject.
Customer insight, prioritization, product judgment, and execution trade-offs.
Scored on User-first framing · Prioritization & execution · Product judgment & influence
Customer insight, prioritization, product judgment, and execution trade-offs.
Scored on User-first framing · Prioritization & execution · Product judgment & influence
Hands-on problem solving, code quality, debugging, and engineering judgment.
Scored on Problem-solving communication · Engineering correctness · Adaptability & craft
System design, trade-offs, and war stories from production.
Scored on Technical communication · Engineering depth · Ownership & collaboration
Hands-on problem solving, code quality, debugging, and engineering judgment.
Scored on Problem-solving communication · Engineering correctness · Adaptability & craft
Six you can expect, in the register interviewers actually use. Answer them out loud before you read the next section — reading a question and answering one are different skills, and only the second is marked.
The gap between these two is most of your score, and it is easier to see than to be told.
“Tell me about a time you told a customer they were the wrong thing.”
Either capitulating — 'the customer is always right, we built it' — or bulldozing them with technical reasons. Both fail the same rubric.
Find the need under the request, name it back to them, and offer the thing that actually serves it. Then say what you did when they still wanted the original. This round is testing whether you can disagree and keep the relationship.
The post-mortem nobody sends you. These are specific to this loop rather than general interview advice.
For Forward Deployed Engineer, a general round runs with Leila — customer insight, prioritization, product judgment, and execution trade-offs. It is the fastest way to find out which round you actually need to work on. The first session is free.
Practise a Forward Deployed Engineer interview →Before you practise, it is worth reading how the common rounds are marked: tell me about yourself, behavioral questions and STAR, and system design.