In-Person Interviews Are Back: How to Prepare for Onsites

If you joined the industry after 2020, there is a fair chance you have never written code on a whiteboard in front of a stranger. Every loop you passed was a video call with a shared editor, your own chair and your own coffee. In-person interviews are coming back at some employers, and for a lot of capable engineers the first one will be the real thing.
The skills are the same. The conditions are different enough to cost a level of performance if you meet them cold: no autocomplete, no running the code, five conversations in a row on your feet, and a lunch that may or may not be scored. This guide covers what has been reported about the return, what changes in the room, and a two-week plan to get ready for an onsite.
What has been reported
Most of what is public traces back to a handful of reports, so it helps to be exact about them.
- Google. In June 2025 Sundar Pichai said on the Lex Fridman podcast that Google would have "at least one round of in-person interviews for people", to make sure candidates have the fundamentals. Entrepreneur reported the remark in August 2025. Nobody has published which roles, levels or stages that covers.
- McKinsey. The same Entrepreneur article, citing the Wall Street Journal, says McKinsey asked hiring managers to schedule at least one in-person meeting with a candidate before an offer, a practice that had started about a year and a half earlier.
- Cisco. The Wall Street Journal named Cisco among US companies asking for more face-to-face interviews, as heise reported in August 2025. The coverage gives no more detail than that.
- Smaller employers. A September 2026 Wall Street Journal report, republished by Allwork.Space, describes Nominal requiring final interviews in person, with engineers taking coding tests on company-provided laptops.
How widespread is it? The numbers are soft. The Journal's 2025 piece quoted the head of a technology recruiting firm estimating that about one in three of its corporate clients were asking for in-person interviews, up from roughly 5% a year before. That is one recruiter's estimate about one firm's clients. A July 2026 summary of a Business Insider report describes "some technology employers" adding in-person rounds and cites a 2025 Greenhouse survey in which 39% of US hiring managers said they were doing more in-person interviews to verify candidates.
The fair reading as of November 2026: a hybrid is forming. Early rounds stay on video. One round, often the final or the most technical, moves into an office at some companies and for some roles. A few large employers are going the other way for part of the loop and letting candidates use AI under supervision, which is covered in the guide to AI in coding interviews. Ask your recruiter which you are getting; do not infer it from a headline.
Why companies are doing it
Two reasons appear in the reporting, and they are different problems.
The first is assistance. It became easy to run a model off camera that listens to the question and writes the answer. Pichai's remark about fundamentals is aimed at this. A room removes the second screen.
The second is identity. The heise summary of the Journal's reporting mentions North Korean IT workers placed in Western companies under false identities, and the September 2026 report describes employers checking IP addresses after finding candidates who claimed to be in the United States were abroad. An employer who has met you knows that the person who interviewed is the person who starts.
Neither reason is about you, and both mean the in-person round is unlikely to be a formality. It exists to produce evidence the company trusts more than the video rounds.
What changes in the room
Whiteboard coding has no undo. You cannot insert a line above the one you just wrote. Start in the top left corner, write smaller than feels natural, and leave a blank line between statements so you can add a condition later. Decide your function signature and the main loop before the marker touches the board.
Nothing runs. In a shared editor you find the off-by-one by pressing a button. On a board you find it by tracing a small input by hand, aloud, updating the variables in a corner of the board. Interviewers have always valued the trace. In a room it is the only test you have, so do it without being asked.
No autocomplete and no documentation. You will forget the exact name of a library method. Say so and write what you mean: "I'll assume a heap with push and pop; the Python name escapes me." Interviewers at a whiteboard generally care that the algorithm is right and the code is plausible. Check with yours at the start whether they want syntax that would compile.
Design is drawn by hand. A system design diagram on a whiteboard takes longer than in a drawing tool and cannot be rearranged. Draw the request path left to right, leave room around the data stores, and stand to the side so the interviewer can see. Handwriting a diagram is slower than you remember.
Your body is part of the interview. Back-to-back rounds on a video call let you slump between them. An onsite of four or five rounds means hours of standing, talking and writing with little privacy. The last round is where tiredness shows. The remedies are dull: sleep, food, water, and treating each new room as a fresh start instead of carrying the previous round into it.
Lunch. Some companies schedule a lunch with an engineer and describe it as unscored. Whether it is depends on the company and you will not be told with certainty. Behave as a colleague would: ask about their work, eat something, do not unload your frustrations about the morning.
Small talk carries weight. Walking between rooms you will chat with the interviewer. It is not a test, but someone who has had a pleasant two minutes with you starts the hour inclined to help.
Practising aloud and by hand
The gap between knowing an algorithm and producing it by hand while talking is wide, and it closes quickly with the right repetitions.
- Write by hand. Paper works; a cheap whiteboard on a wall is better because you stand. Do one problem a day this way for two weeks. Time it. Your first attempts will be noticeably slower than typing.
- Trace every solution. Pick an input of three or four elements and walk it through, writing variable values as they change. Aim to finish coding with ten minutes left for this.
- Talk to an empty room. Record audio on your phone. Listen for silences longer than fifteen seconds and for the moments you started writing before saying what you were about to do.
- Draw three designs. Take systems you know well and draw each on one board in under ten minutes: clients, entry point, services, stores, queues. Then explain it standing up.
- Rehearse the day's length once. Do three sessions back to back on a weekend with ten-minute breaks. You are training the fourth hour.
What you cannot rehearse alone is a person in the room. Someone watching changes how you write, and someone interrupting changes how you think. Ask a colleague to sit in, or book a session from the mock interview coaches page and ask the coach to run it whiteboard-style: camera on your board or paper, no editor, no running code. It is the closest thing to the room that you can do from home.
Logistics that cost people offers
None of this is intellectually hard. It gets skipped anyway, and it decides how you feel at 9am.
- Travel. Arrive the day before if the flight is longer than a couple of hours. A same-day flight that slips makes you late or rattled.
- Time zones. If you cross more than two, ask for a late-morning start. Recruiters can usually arrange it and would prefer you awake.
- Expenses. Ask in writing, before you book anything, whether the company books travel itself or reimburses, what the limits are, and how long reimbursement takes. Policies differ, and there is no public source worth quoting. If paying up front is a problem, say so; recruiters deal with this routinely.
- The schedule. Ask for the list of rounds, their order and who you meet. Ask whether coding is on a whiteboard or a laptop, and whose laptop. Per the Journal's report, at least one employer supplies the machine.
- What to bring. Photo ID, water, a snack, a layer for an over-cooled meeting room, and your own whiteboard markers if you are particular. Office markers are often half dead.
- The building. Find the entrance and reception the evening before if you can. Campuses are large and badly signed.
Identity checks
Expect to be asked for government photo ID at reception, and bring the document that carries the name on your application. Given the fraud cases above, assume the company will want to see that the person who arrives is the person from the video rounds.
Remote rounds in the same loop may come with checks too. The September 2026 Journal report lists requests to remove virtual backgrounds, pan the camera around the room, share the screen or wave a hand in front of your face. These are irritating and reasonable. Comply without comment and move on. If a request seems excessive, such as installing monitoring software on a personal machine, ask the recruiter what it does and whether there is an alternative.
A two-week onsite plan
This assumes you already prepared for the video rounds and passed them. It is about converting what you know to the room.
| Days | Coding | Design and behavioural | Logistics |
|---|---|---|---|
| 1 to 3 | One problem a day by hand, untimed, with a full trace | Draw one familiar design by hand | Confirm schedule, format, travel and expenses in writing |
| 4 to 6 | One a day, timed at 35 minutes, aloud and recorded | Tell your five main stories aloud, standing | Book travel to arrive the day before |
| 7 | Live mock on a board with another person | Review the recording or notes | Rest in the afternoon |
| 8 to 10 | Two a day by hand, timed; redo the mock's weak spots | One full design round by hand, 45 minutes | Check ID, route and building entrance |
| 11 to 12 | Three sessions back to back, once | Second live mock, design or behavioural | Pack; shift sleep toward the interview time zone |
| 13 | One easy problem to stay warm | Read your story notes once | Travel |
| 14 | The onsite |
Two notes on it. The day-7 mock is placed early on purpose, so there is a week to fix what it shows. And day 13 is nearly empty on purpose. Nothing learned the night before survives the adrenaline, and tiredness costs more than a missed problem.
Where coaching fits
A live mock is the closest rehearsal for an onsite because it supplies the one condition you cannot create alone: a person watching and interrupting in real time. As of November 2026, 34 of the 40 coaches on techinterview.coach offer a mock interview, and the mock interview page lists them; tell the coach the round type and that you want it run by hand. For repetitions of speaking under questioning between mocks, the practice interview runs a voice round with an AI interviewer and sends a written recap. It is free; sign in to start.
Related guides
- AI in coding interviews: which companies allow assistants, which forbid them and what to ask the recruiter.
- Mock interviews guide: how to set up a rehearsal that resembles the real round.
- Google system design interview: includes what guides say about Google's onsite location.
- System design interview questions by level: what to practise drawing for your level.
- STAR method: structure for the stories you will tell standing up.