Software engineer video interviews
On a call the interviewer cannot see your whiteboard or your head. The answer has to carry the diagram. Here is one answer, taken apart a sentence at a time.
The question, from the practice set
“Walk me through a technically challenging project you've owned end to end.”
The project below is invented for illustration. Use your own, with your own numbers.
I owned moving our notification service from a nightly batch job to an event queue.
Scope first, in one sentence. The interviewer now knows what the whole answer is about and can stop you early if it is the wrong project.
The batch job was the problem. When a run was late, users got yesterday’s alerts and we had no way to see why it was late.
The cost of the old design in terms a user would feel. The detail about not being able to see why plants the observability point you come back to at the end.
The decision I spent longest on was delivery guarantees. At-least-once was easy to build but could send the same alert twice, so I made every handler idempotent and stored a message ID for each delivery.
The trade-off, the choice and its price, all in one breath. This is the sentence a design interviewer will probe, so say it slowly and keep the terms exact.
I rolled it out behind a flag, one customer segment at a time and ran both paths for two weeks, comparing what each would have sent.
How you handled risk. “Ran both paths” and “comparing” tell the listener you checked instead of hoped.
Median delay went from hours to under a minute and the on-call pages for late alerts stopped.
The result, with a before and after. One number, one consequence people felt. Stop here for a beat; do not rush to the next sentence.
What I would change is the dead-letter dashboard. I built it three weeks after launch and the failures in the first two weeks were invisible to everyone but me.
One specific regret. Interviewers often ask “what would you do differently” and answering it before they do saves a turn and shows you review your own work.
Read aloud at a normal pace, this takes about a minute. Interviews rarely stop there; the next question is usually about the sentence in the middle.
What the call changes
Say the diagram before you describe it
In a room you can point. On a call, the other person is looking at your face or a shared tab. Name the parts in order, then the connections: “Three boxes: the API, a queue and a pool of workers. Requests go in on the left and results come back through the same API.” Then add detail. If you do share a whiteboard, keep narrating; people lose the thread when they have to work out what you are drawing.
Silence reads differently
Five seconds of quiet thought is normal across a table. On a call it can sound like a dropped connection. Fill the gap with the thinking itself: “I am working out what happens to in-flight messages when a worker dies.” That is also the thing the interviewer wants to hear.
Read before you type
In a live coding round, say what the next block will do before you write it, then write it. Narrating every keystroke is too much and silent typing for two minutes leaves the interviewer guessing whether you are stuck.
Leave a beat after they finish
Video has a small delay and people talk over each other more than they would in person. Wait a moment after the question ends. It also gives you time to pick the first sentence, which is the one that sets up the rest.
Talking is not most of the job
In the occupational data behind our role speaking index, software developers fall in the bottom quarter of 905 occupations for how much speaking the work asks for. Nothing is wrong with that. It does mean the interview may be the one place in your week where you explain your reasoning out loud, so it is worth hearing yourself do it before the day.
Record the same answer about your own project
Pick the project you would least like to be asked about and answer the question above in one take. The report shows your pace, the filler words you lean on and any silence long enough to sound like a lost connection. Paid reports also suggest the follow-up question an interviewer would ask next, which you can record straight away.