To prepare for an onsite interview, start about two weeks out: get the agenda from your recruiter, map each round to the skills it tests, and practice every round type out loud under time pressure. In the final days, shift from learning new material to rehearsal, logistics and rest, because an onsite is four to six interviews in a row and your last session counts as much as your first.
An onsite (also called the final loop or full loop) is the stage where most hiring decisions are made. Many companies now run it over video, but the preparation is the same. This guide gives you a timeline, what each typical round tests, a day-of checklist, and links to a dedicated guide for every part of the onsite. If you want the definition and the debrief process first, read our explainer on the full loop interview; for a general one-week plan that works for any interview, see how to prepare for an interview.
How do I prepare for an onsite interview in 2 weeks?
Use the table below as your plan. The hours are estimates for someone with a full-time job; a senior role, a new domain or a rusty skill needs more time in the first week.
| When | Round-by-round prep | Logistics | Energy and mindset | Questions to ask |
|---|---|---|---|---|
| 14 to 10 days out | Get the agenda. List every round and the skill it tests. Do a diagnostic: one timed practice per round type to find your weakest area. | Confirm date, time zone, format (in person or video), and travel if it applies. | Block prep time in your calendar now: 60 to 90 minutes on weekdays, longer on weekends. | Hold a prep call with the recruiter and ask what each round covers. |
| 9 to 5 days out | Spend most time on the weakest round. Build or refresh 6 to 8 STAR stories. Rehearse your role-specific rounds (coding, design, case, portfolio). | Book travel or confirm the video platform and any tools you will use, such as a shared code editor or online whiteboard. | Do at least one long practice block so you learn how your focus holds up over three or four hours. | Research each interviewer you have names for. Draft two questions per person. |
| 4 to 2 days out | Run a full mock loop: back-to-back sessions with short breaks. Fix the two answers that scored lowest. | Test your setup or plan your route. Prepare your bag or desk. | Keep normal sleep and exercise. Stop learning new topics after this point. | Finalize your questions and your closing statement. |
| Day before | Light review only: your one-page brief, your story list, a few warm-up problems. | Lay out clothes, ID, chargers, water, snacks. Save the recruiter's phone number. | Early night. Plan your breakfast and lunch. | Reread the job description and your notes on the team. |
| Day of | Ten-minute warm-up: say your introduction out loud, solve one easy problem or walk through one story. | Arrive or log in 10 to 15 minutes early. | Reset between rounds: water, a short walk, three slow breaths. | Ask each interviewer at least one question. |
If you have less than two weeks, keep the order and compress it: diagnostic on day one, weakest round next, a full mock loop two days before. Our guide to the recruiter prep call before an onsite lists the 15 questions that get you the agenda you need for step one.
What does each onsite round test?
Onsite structures vary by company, team and level, and your recruiter's agenda is the only reliable source for yours. Commonly, though, an onsite is built from some mix of the rounds below, with each interviewer assigned one area so that together they cover the whole job.
| Round | What it usually tests | How to prepare |
|---|---|---|
| Behavioral or values | Ownership, collaboration, conflict, handling failure, alignment with the company's stated values | 6 to 8 STAR stories mapped to the job description and the company's values; practice follow-up questions |
| Coding or technical | Problem solving, code quality, testing, communication while you work | Timed problems in the tool you will use; say your approach before you code |
| System or product design | Scoping, trade-offs, scale, judgement under ambiguity | A repeatable structure; practice drawing and explaining at the same time |
| Role deep dive | Depth in your own past work: decisions, metrics, what you would change | Pick one or two projects and prepare the architecture, numbers and trade-offs |
| Case, analytics or portfolio | Structured thinking, metrics, communication of your work | Practice a framework and a timed presentation |
| Hiring manager | Motivation, fit with the team's problems, how you work, early impact | Know the team's top problems and how your stories map to them |
Amazon, for example, describes its interview loop as meeting current employees individually, with each person assessing different aspects of your skills and experience (as of October 2026, Amazon's interview loop page). That division of labor is why a strong onsite answer stays on the topic of the round you are in. For the questions themselves, see our list of onsite interview questions by round.
How to prepare round by round
- Start with a diagnostic, not a study plan. One timed attempt at each round type shows you where the time should go. Most people over-prepare their strongest area because it feels productive.
- Prepare stories once and reuse them. A good story about a project that went wrong can answer failure, conflict and ambiguity questions. The free STAR story builder turns rough notes into a structured outline.
- Practice in the format you will face. If the technical round uses a plain shared editor without autocomplete, practice there. If you will draw on a whiteboard, stand up and draw.
- Say everything out loud. An answer you have only thought through is usually twice as long and half as clear when spoken. Time yourself: most behavioral answers land well at around two minutes.
- Rehearse the transitions. Practice the first 60 seconds of each round: greeting, a short introduction, and confirming what the interviewer wants to cover.
- Know your numbers. Write down the metrics behind each story and project: users, revenue, latency, time saved. Interviewers in different rounds often ask for them.
Logistics and energy: the part most people skip
An onsite is a long day, and fatigue shows up in the third and fourth sessions as slower thinking and longer answers. Plan for it the way you plan for the content.
- Know the schedule. Ask for the order of rounds, the length of each, and where the breaks are. Our guide on how long an onsite interview lasts covers typical schedules.
- Eat on purpose. Have a real breakfast and bring a snack. If lunch is part of the day, treat it as part of the interview; our lunch interview etiquette guide covers what to order and talk about.
- Plan travel early. If the employer books or reimburses travel, keep every receipt. See whether companies pay for onsite interview travel.
- Protect your setup for remote loops. A video onsite has its own failure points: a dead battery, a frozen call, a long day staring at a screen. Our virtual onsite interview tips include a run sheet.
- Ask for what you need. If you need an accommodation, such as extra time or a specific format, ask the recruiter as early as you can.
Day-of checklist
- Agenda printed or open, with every interviewer's name and round
- One-page brief, résumé and the job description
- Water, a snack, and for in-person loops a phone charger and photo ID
- For video loops: laptop on power, headphones tested, a backup internet option, the recruiter's phone number
- A notebook and pen for names and questions
- A reset routine for each break: stand, drink water, breathe, look at your brief
- One question ready for every interviewer, plus your closing statement for the last round
If a round goes badly, close it out and reset before the next one. Interviewers usually write feedback independently, so one weak session often does not decide the result on its own. Our guide on what to do if you bombed one round of an onsite interview explains how to recover, and how onsite interviews are scored explains why.
Guides for onsite interviews
Every guide in this series covers one part of the onsite in depth.
- Onsite interview questions: 40 questions grouped by round, with what a strong answer shows
- How long is an onsite interview? Typical lengths, breaks and split-day schedules
- What to ask the recruiter before an onsite: 15 questions and a prep-email template
- Virtual onsite interview tips: running a remote loop of four to six sessions
- Software engineer onsite interview questions, round by round
- Senior software engineer onsite interview: how the senior loop differs
- Engineering manager onsite interview: people, delivery and architecture rounds
- Machine learning engineer onsite interview: ML fundamentals, ML design and deep dives
- How onsite interviews are scored: feedback, rating scales and the debrief
- Product manager onsite interview questions by round
- Data scientist onsite interview questions: SQL, stats, product cases and ML
- Data analyst onsite interview questions: live SQL, cases and take-home presentations
- Product designer onsite interview: portfolio talk and design challenge
- What is a superday interview? The finance and consulting final day
- Lunch interview etiquette: what to order and what to talk about
- Do companies pay for onsite interview travel?
- I bombed one round of my onsite interview: what to do next
- Team matching after an onsite interview: how it works and what to ask
- Mock onsite interview with AI: simulate a full loop in one day
Practice it
The single best predictor of how you will sound on the day is how many times you have said your answers out loud. You can rehearse with a free AI mock interview: the CoPilot Interview desktop app's Mock Interview builds questions from your résumé and the job description, reads each one aloud, and scores your spoken answer out of 10 with what to fix and a model answer. Choose the question mix to match your agenda, for example behavioral plus system design, and run several sessions back to back to rehearse the stamina an onsite needs. It is free for 15 minutes a day with no account. Follow each employer's rules on AI tools, and use AI to prepare beforehand.
Rehearse your onsite before the real one
Answer real interview questions out loud, get each answer scored out of 10 with what to fix, and see which round needs the most work. Free for 15 minutes every day, no account needed.
Try a free AI mock interviewFAQ
How far in advance should I start preparing for an onsite interview?
About two weeks is a comfortable window for most candidates: one week to fix your weakest round and build stories, and one week for full mock loops, logistics and rest. With less time, keep the same order and compress it.
What should I bring to an onsite interview?
Bring photo ID, copies of your résumé, the agenda with interviewer names, a notebook and pen, water, a snack and a phone charger. For a video onsite, keep your laptop on power and have the recruiter's phone number ready in case the call drops.
Is an onsite interview the final round?
Usually, yes. For many companies the onsite is the last interview stage before the hiring decision, although some add a hiring manager call, a team-matching step or reference checks afterward.
Do I need to prepare differently for a virtual onsite?
The content is the same, but plan for tech failures, longer screen time and breaks spent alone at your desk. Test your setup, keep a backup internet option and step away from the screen between sessions.
Can I ask the recruiter what each onsite round will cover?
Yes. Asking for the agenda, the focus of each round and the tools you will use is normal, and most recruiters expect it. The answers decide how you spend your prep time.
What if I do badly in one onsite round?
Reset and give the next round your full attention. Interviewers commonly write feedback independently and the decision is made after reviewing all of it, so one weak round is often not decisive on its own.