Stage 4 · Interviews · 6 min read
Final Round Guide: Panels, Onsite Loops, Presentations and Take-Homes
Four interviewers in one day hear one candidate. How to stay consistent across the loop, run a panel, deliver a 60-day plan, and scope a take-home without doing free work.
The final round is where the questions stop being new and the format starts mattering. Four to six interviewers, back to back, each with their own scorecard; a presentation; sometimes a take-home with a weekend attached. Then a debrief you are not in, where the hiring manager asks each of them one question: "hire or no hire, and why?"
Candidates who were strong in the screen lose here for reasons that have little to do with ability: a story told four different ways to four people, energy gone by the third session, a presentation that answered the wrong question. All of it is preparable.
1. What Changes in the Final Round
Three things, and they shape everything below:
- Consistency is now a signal. Interviewers compare notes. The numbers in your ERP story need to match across the hiring manager's session and the peer's. Say your story bank leads the same way each time; the practised version is the consistent one.
- Each interviewer has one job. The loop is designed so that different people test different things. Guessing which is which tells you which stories to lead with.
- The decision is made without you in the room. Your last ten minutes with each person are what they carry into the debrief. The reverse-interview guide has the closing question that surfaces a doubt while you can still answer it.
2. Map the Loop Before You Walk In
Ask the recruiter for the names and roles of everyone on the schedule. Then map it:
| Session | What they are testing | Lead with |
|---|---|---|
| Hiring manager | Can you do the job, and will they enjoy managing you | The two stories closest to the posting's first bullets; your 60-day view of their problem |
| Peer or technical | Depth, honesty under follow-up, whether you would make their week harder or easier | The deep dive with the trade-off and the "what broke" answer ready (the deep-dive guide) |
| Cross-functional partner | Whether you can work with people who do not report to you | The persuasion story; the time you cut scope and told a stakeholder why |
| Skip-level or executive | Judgment, and whether you think about the business rather than the task | Impact first: the before-and-after numbers, then how you chose what to work on |
| Values, culture or bar raiser | Ownership and honesty; they will push on your weakest story | The failure story, told plainly, with the change it made in how you work |
The same story may serve two sessions. That is fine as long as you tell it from the angle that session cares about, and the facts do not move.
Try a question
Try it on this guide’s questionFree · no account · 5 questions
Five questions free here, no account. Sign in with your email to keep your best answers and get your full plan.
Welcome back. Sign in to your questions ›
Your field:
“Tell me about a time you led an effort without formal authority: getting people moving when nobody reported to you.”
Say it or type it; about a minute and a half is enough.
When is the interview?
Sign in to answer it in the room: free, an email link, no password.
Your first five.
These five stay in this browser for seven days, and for good once you sign in.
Keep these five and get tomorrow's question. Where should we send the link?
Send it at
Continue with GoogleNothing after a minute? Check spam.
One sign-in link, no password; it works once and lasts 15 minutes. Open it and your five scores are saved, and tomorrow's question comes the next morning.
- Tell me about a time you led an effort without formal authority: getting people moving when nobody reported to you.
3. Running a Panel
Two or more interviewers at once is a format of its own. A few mechanics keep it from running you:
- Answer the person who asked, then widen. Start on the asker, finish the answer with a glance across the panel. Everyone feels addressed; nobody feels ignored.
- Pull in the quiet one. One panelist usually says little. Their scorecard counts the same. When you close, aim one question at them by name.
- When one interrupts, finish the sentence and yield. Panels have an interrupter. Let them in; the rest of the panel notices who stayed calm.
- Keep your answers 60 seconds in a panel, not 90. With three people waiting their turn, the long answer costs more.
4. The Presentation Round
Many loops ask for a 20–30 minute presentation: a 60- or 90-day plan, a case, a lesson, a teach-back. The question is never really the topic. It is "can this person structure a problem and hold a room?" Build it this way:
| Part | Time | What it does |
|---|---|---|
| The problem as you understand it | 2 min | Shows you read the posting and listened in the earlier rounds; invites a correction early |
| What you would look at first | 5 min | The audit: the queue, the codebase, the unit's handoffs, the cohort's data; the baseline you would measure |
| Two or three options and the trade-off | 8 min | The fork in the road; why you lean one way; what it would cost |
| The first quick win | 5 min | One low-risk change you have made before, with the number it moved |
| What you would need, and the risks | 3 min | Shows judgment; sets up the questions |
| Questions | The rest | Where the hire is decided; leave at least a third of the slot |
Three rules. One idea per slide and about one slide per minute. Rehearse it out loud, standing, twice, with a clock: a 20-minute deck read silently takes 12 minutes aloud, and a nervous one takes 30. And decide in advance what you will cut if the earlier session runs long, because one will.
5. The Take-Home Assignment
A take-home is a real signal of how you work, and sometimes a weekend of unpaid labour. Scope it before you start, with three questions to the recruiter or the hiring manager:
- "How long do you expect this to take?" Then take that long, within a half, and say so in the write-up.
- "What are you most looking for: a working solution, the reasoning, or how I'd handle the edge cases?"
- "Can I make assumptions where the brief is unclear, and list them?"
Then build the thing that the answer asked for:
- A README before the solution. What you built, what you assumed, what you left out and why, and what you would do with another day. For most reviewers this page is the assignment.
- The trade-off, named. "I chose the simpler schema; it costs a join on reads but keeps the migration reversible." That one sentence is the senior signal.
- Timebox and stop. A polished half beats an unfinished whole. Gold-plating reads as poor judgment, not generosity.
- Expect to walk through it live. The deep-dive session will be about this. Rehearse the five layers on it as you would any project.
If the assignment is a real piece of the company's current work with no scoping and no limit, it is a yellow flag, and a fair question to ask about.
6. The Day Itself
Energy management is the overlooked skill of a loop. Four sessions over five hours and the fourth interviewer meets a different candidate from the first:
- Eat before, and between. Say yes to the break. Use it to drink water and look at the sticky note with your three leads, not your phone.
- Reset between sessions with one sentence. "New person, same stories, same numbers." The last session's wobble does not come into this one.
- Keep a page of every question asked. Within two hours of the loop, write them all down and run the shaky ones through Bashmo. The follow-up guide has the same-day note that repairs an answer you fumbled.
- Ask every interviewer the closing question. "Is there anything in my background or an answer I gave that leaves you with a question mark I can clear up now?" Ninety percent say no and remember you for asking. The other ten tell you what would have cost you the offer.
7. Rehearse the Loop as a Loop
A final round is a mock interview with the stakes on. Run one without them first:
- Two days out, run the timed mock on Bashmo in the "tough (bar raiser)" style, three to eight questions back to back. It interrupts, it pokes at the numbers, and the debrief says ready or not and what to fix.
- Then run it once more in "neutral". Consistency across two styles is consistency across four interviewers.
- Check the one number. Each position in Bashmo shows one % ready, built from your best answers to the core questions and the ones written from this posting and your resume. If the number is not where you want it on the day before, the fix is to say the weakest two answers again, not to read more.