Onsite Interview Day Logistics and What to Bring

Logistics are the part you can fully control

You cannot control which questions an interviewer asks, but you can control whether you arrive calm, on time, and with everything you need. Onsite days are long and tiring, and small avoidable problems, a late train, a forgotten ID, a dead phone, drain the energy you should be spending on the interviews themselves. Treating the logistics as their own task, planned the day before, removes a whole category of stress.

The reason this matters is more than comfort. Interview performance is heavily affected by working memory, and working memory is fragile. Every open loop in your head, "did I bring the right adaptor", "will I make the connection", "what was that interviewer's name", competes for the same mental resource you need to reason about a system design or trace through a tricky bug. The goal of good logistics is to close every one of those loops before you walk in, so that when the hard question lands you have your full attention available for it.

This guide assumes a traditional onsite loop where you visit an office for several back-to-back sessions. Plenty of the same thinking applies to a half-day visit, a single in-person round, or even the in-person final stage of a mostly remote process, and a later section covers what changes when the whole loop is virtual or split across two days.

A useful mental model: treat the logistics as the warm-up you have already won. Everything in this guide is a problem you can solve in advance for free. Spend the cheap effort here so you arrive with nothing left to spend it on but the conversations.

Plan the journey before the day

Work out the route and timing the night before, not on the morning. Know the exact address, the nearest station or car park, and how long the journey takes with a sensible buffer. The buffer is not optional padding, it is insurance against the one delay you cannot predict. A reasonable rule is to add roughly fifty per cent to the door-to-door estimate the maps app gives you, then aim to arrive in the area early and wait nearby rather than walking in twenty minutes ahead, which can be awkward for the host. Most interview guidance lands on the same window: walk into reception ten to fifteen minutes before the scheduled time and plan the route in advance rather than on the morning.

A few things to confirm in advance:

• The full address, including building, floor, and any specific entrance. Large offices and shared buildings often have a side entrance for visitors that is not the one the map pin points to.
• Who to ask for at reception, and a contact number in case you are delayed.
• Whether you need to be added to a visitor list or bring photo ID for building security. Corporate and finance offices in particular can refuse entry without ID on the visitor list.
• Parking or transport details if you are driving or the office is awkward to reach.

It is worth doing a quick reconnaissance of the last hundred metres too. Street view will tell you whether the entrance is obvious or tucked down a side road, and whether there is a café nearby where you can sit, use the bathroom, and settle for ten minutes before you go in. That café is the single most useful piece of local knowledge you can gather, because it gives you somewhere to land early without hovering in the lobby.

If anything goes wrong on the day, a late train or a closed road, message your recruiter or contact straight away. Things happen, and a quick, calm heads-up is handled far better than a silent late arrival. Recruiters move loops around all the time, and a fifteen-minute warning usually means they can shuffle the first session rather than cancel anything. The mistake is going quiet and arriving flustered with no explanation.

What good versus weak preparation looks like

What to bring

Pack a small bag the night before so you are not scrambling. The aim is to be self-sufficient for a long day without carrying half your flat.

A sensible kit:

• Photo ID, in case building security needs it.
• A few printed copies of your CV, even in a paperless office, because someone may not have it to hand. Interview checklists put three to five copies at about the right number. This sounds old-fashioned, but interviewers are often pulled in at short notice and have not read it, and handing over a clean copy is far better than watching them squint at a phone.
• A notebook and a pen, plus a spare pen, for jotting names, questions, and things you want to follow up on. Paper is also the only note-taking medium nobody will read as you being distracted or disengaged.
• Your phone, fully charged, plus a small power bank if it is a long day.
• A bottle of water and a small snack, since loops can run through normal meal times.
• Any take-home or portfolio material the company specifically asked you to bring.

If the role is technical and you have been told you will use your own laptop, bring it charged with the right adaptors and make sure your environment is set up. Test it the night before on the actual network conditions you can, and confirm the basics: your editor opens, your toolchain runs, you can compile and execute a trivial program, and you are not one OS update away from an hour of waiting. If you are unsure whether to bring a laptop, ask the recruiter rather than guess.

There is a small set of comfort items that punch above their weight on a long day: a pack of mints or gum, a spare pen, a tissue or two, and if you wear them, a spare pair of contact lenses or your glasses. None of these are interview kit in the obvious sense, but each one removes a small distraction that would otherwise sit in the back of your mind.

What not to bring matters too. Leave the bulky bag, the visible energy drinks, and anything you would be anxious about losing. You want to walk in light, with a single bag you can keep with you between rooms without thinking about it.

Dress to match the place

When in doubt, dress slightly smarter than the team's everyday norm, but do not turn up in a way that feels out of place for the company. Most tech offices are casual, so smart-casual is a safe default for engineering roles. If you genuinely cannot tell, it is a fine question to ask your recruiter, and asking signals care rather than uncertainty. The goal is to feel comfortable and unremarkable, so that nobody is thinking about your clothes either way.

How this differs by company is worth knowing. An early-stage startup will read a suit as a slight misread of the culture, while a bank, a law-adjacent fintech, or a large enterprise client-facing team may expect something closer to business attire. When the role involves meeting customers or presenting, lean smarter. When it is a pure engineering team building internal systems, lean comfortable. If you have seen the team's photos on the company site or social media, use that as your calibration. The safest single choice across almost all software roles is a clean, plain shirt or top with smart trousers, and shoes you can comfortably walk and stand in for a whole day.

Handle the multi-stage loop

An onsite loop is usually several sessions in a row, often with different interviewers, sometimes including lunch with the team. The challenge is stamina and consistency rather than any single hard question. A typical onsite runs three to six interviews in several formats across three to five hours, and the people you see in the afternoon are scoring you against the same bar as the people you saw in the morning, even though you are far more tired by then.

Some things that help across a long day:

• Treat each session as a fresh start. A weak round does not have to colour the next one, and interviewers rarely compare notes mid-loop. The debrief usually happens after you have left, so the person in front of you almost certainly does not know how the last hour went.
• Note each interviewer's name and role as you go, which helps with questions and with any follow-up afterward.
• Use the short gaps between sessions to drink water, reset, and glance at your notes rather than replaying the last hour.
• Keep your energy steady. Interviewers in later sessions deserve the same focus as the first, even when you are tired.

A small reframing technique helps with the worst-round problem. If a session goes badly, give yourself a fixed, short window to feel annoyed about it, the length of one walk to the next room, then deliberately close it. The candidates who lose loops are rarely the ones who had one weak round, they are the ones who let that round bleed into the next two. Interviewers expect a spread of performance across a loop, and a single soft session against four solid ones is a normal, passing pattern.

If there is a lunch or an informal walk-around, remember it still counts. It is usually a softer assessment of whether people enjoy talking to you, so be friendly and curious, but assume it is part of the process rather than entirely off the record. A safe stance is to be warm and ask genuine questions about the team and the work, while keeping anything you would not want repeated in the debrief to yourself. Avoid complaining about a previous employer, avoid strong opinions on office politics, and do not treat the lunch host as a confidant just because the setting feels casual.

A short worked example: the gap between sessions

Here is how a strong candidate spends a ten-minute break between a system design round that went well and a behavioural round they are nervous about.

Round three wrapped a couple of minutes early. I thank the interviewer, note "Priya, staff eng, payments" in my notebook, and ask the coordinator where the bathroom is. I use it, refill my water, and sit down. I do not reopen my laptop or rehearse. I read the one line I wrote for the behavioural round, "lead with the situation, keep the result concrete, name the trade-off", take three slow breaths, and let the system design round go. When the next interviewer arrives, I am present rather than still in the previous room.

The point is not the specific routine. It is that the break is used to reset and reset only, not to relitigate the last hour or cram for the next one.

During the sessions

The logistics carry into the room. Keep your notebook visible so you can capture a question that occurs to you rather than interrupting. It is fine to take a moment before answering a hard question, and it is fine to ask for clarification. If you are working on a whiteboard or a shared screen, narrate your thinking so the interviewer can follow you even when your final answer is imperfect. Most technical interviewers are scoring how you reason far more than whether you reach the perfect solution, and a clearly explained partial answer routinely beats a silent correct one.

When you are coding, a simple narration pattern keeps the interviewer with you and buys you thinking time at the same time:

1. Restate the problem in your own words and confirm it.
2. State your assumptions and ask about edge cases out loud.
3. Describe the approach before you write, and name its complexity.
4. Write the code, narrating the non-obvious decisions only.
5. Walk one example through it, then call out what you would test.

Look after yourself physically too. Accept the offered water, ask for a short break if you need one between sessions, and do not be afraid to step out to the bathroom. None of this counts against you, and arriving at the final session frazzled because you pushed through helps nobody. If your energy is dropping, the snack you packed earns its place here, even a quick bite in a gap can be the difference between a sharp final round and a foggy one.

When the onsite is virtual, split, or half a day

Not every onsite is a full day in one building, and the logistics shift with the format.

A virtual onsite moves the whole loop to video, so the logistics turn technical. What you plan for is a quiet room you control for three to five hours, a wired connection or a tested backup, a camera and microphone checked in advance, and a charger plugged in rather than a battery you are watching. Close the browser tabs and notifications you do not need, keep a glass of water and your printed notes to one side, and save the coordinator's number in case a link drops mid-session. The remote-interview setup guide covers the environment in more depth.

Some companies now split the loop across two days rather than run it back to back. If you are offered the choice, a split loop is usually the easier one to perform in: you arrive fresh for each half and have an evening to reset, which matters more the longer the loop. A half-day or single in-person round compresses everything into two or three sessions instead. The buffer, the kit, and the reset between rounds all still apply, but the stakes per session are higher, because with fewer rounds to average across, one weak session carries more weight than it would in a six-round day.

One question is worth asking whatever the format: find out from your recruiter which way the loop leans before the day. A backend or platform loop usually centres on a system design round and questions about reliability and scale, a frontend loop often includes a live build or a UI debugging session, and a product-leaning role weights user impact and working with non-engineers. Knowing the shape tells you what to keep sharpest, and asking is a fair, welcome question when they send the schedule.

Common mistakes that quietly cost loops

• Arriving with no buffer. A single delayed train turns into a flustered first round, which is the round that sets the interviewer's first impression.
• Treating lunch as off the record. It is part of the assessment. Friendly and curious, not unguarded.
• Letting one weak round spread. The biggest avoidable failure mode across a full loop.
• Going silent when delayed. A calm early message is handled far better than a quiet late arrival.
• Under-testing your own laptop. If you bring it, prove it works the night before, including the boring parts.
• Forgetting names. Write them down as you go. A follow-up that names the right person about the right topic lands far harder than a generic one.
• Pushing through exhaustion. Skipping water, food, and breaks to seem keen leaves you foggy for the rounds that matter most.

Ending the day well

The last impression sticks. When the loop wraps up, thank the people who hosted you and ask about next steps and rough timing if it has not already been covered. Make a quick note while it is fresh of who you met and anything specific you want to mention in a follow-up message. A short, genuine thank-you note afterward, referencing something real from the day, rounds things off without being excessive.

A good follow-up note is specific and brief. Here is the difference.

Weak: "Thank you for your time today. I really enjoyed meeting the team and would love the opportunity to work with you."

Strong: "Thanks for the time today. I enjoyed the system design discussion with Priya, especially digging into how you handle idempotency in the payments flow, it is the kind of problem I would like to spend more time on. Looking forward to hearing about next steps."

The strong version proves you were present, names a real person and a real topic, and signals genuine interest in the actual work. It takes two extra minutes to write and it is the version the team remembers.

Before you leave the building, do a quick mental check that you have your ID, phone, notebook, and anything you brought to show. Leaving your laptop in a meeting room is a memorable way to end an otherwise strong day.

A simple day-before checklist

- Route, timing, and a fifty per cent buffer confirmed
- Address, contact name, and phone number saved
- Nearby café or waiting spot identified
- Visitor list and ID requirement checked
- ID, printed CVs, notebook, pen packed
- Phone charged, power bank in bag
- Laptop and adaptors ready and tested, if needed
- Water and a snack
- Mints, spare pen, glasses or spare lenses
- Outfit decided and laid out

Run through it once the night before and you remove almost every avoidable problem, leaving you free to focus on the only part that actually matters: the conversations.

Frequently asked questions

How early should I actually arrive? Aim to be in the area ten to fifteen minutes early, then walk into reception around five minutes before the start. Much earlier and you create an awkward wait for the host, much later and you risk a flustered start.

What if a round goes badly? Assume it does not sink the loop. Reset in the break, treat the next round as a clean slate, and remember that interviewers expect a spread of performance and rarely compare notes until after you have gone.

Is lunch really part of the assessment? Usually, yes. Be warm and curious, ask genuine questions, and avoid anything you would not want repeated in the debrief. Treat it as a softer round rather than a break.

Should I bring my own laptop? Only if the company has told you to. If they have, bring it charged with the right adaptors and test the full setup the night before. If you are unsure, ask the recruiter rather than guess.

Do thank-you notes matter? A short, specific one helps and is never held against you. Reference a real person and a real topic from the day. A generic note adds little, so either make it specific or keep it to a brief line on next steps.

Where to take this next

The day itself is one piece. These cover what sits on either side of it:

• Managing interview anxiety for the stamina and nerves a long loop tests.
• How to research a company before the interview so the harder preparation is done well before the buffer starts.
• Post-interview follow-up etiquette for the thank-you note the ending section describes.

Sources

• Career.io, how early to arrive and planning your route
• 4 Corner Resources, what to bring to an interview checklist
• Randstad, the must-have job interview checklist
• The Holloway Guide to Technical Recruiting and Hiring, the interview loop