The Onsite Round Run, From Written Travel Terms to a Paid Expense Claim

This is the run for a candidate whose whole loop has been on video and who has now been asked to come to the office for one round. It takes the invite through a dated sequence: travel terms in writing before you book, the agenda, ID and AI rules confirmed, practice moved from screen to paper, the day run block by block, and an expense claim filed inside the employer's deadline. Keep it open from the invite email until the reimbursement lands.

Why does a video loop add one in-person round?

Mostly to confirm that you are the person who did the earlier rounds. It is usually one round added to an otherwise remote process, so bringing the right ID and following the room's rules count as part of passing it.

The pressure behind this is interview fraud, which here means impersonation: someone other than the candidate doing the interview, or being fed answers during it. The evidence:

• A Gartner survey of 3,000 job candidates found 6% admitted to taking part in interview fraud.
• Computerworld, reporting on Google, Cisco and McKinsey bringing back in-person interviews, cited a Gartner figure that 72.4% of recruiting leaders were interviewing in person to combat fraud. That figure is not in Gartner's own release, so treat it as reported, not confirmed.
• Greenhouse surveyed 4,136 people across the US, UK, Ireland and Germany and found 39% of US hiring managers were running more in-person interviews to verify authenticity.
• GetReal surveyed 668 IT, cybersecurity, risk and fraud leaders at organizations with at least 1,000 employees, and 41% said their company had hired and onboarded a fraudulent candidate.

Candidates mostly don't mind. In the same Gartner survey, 62% said they were more likely to apply if the organization required in-person interviews.

Here is what nobody has established. No public dataset shows what share of technical interviews now include an in-person round, and nothing breaks the trend down by role or company size. Specific percentages for the rise appear only on secondary blogs. Don't plan around a base rate. Plan around the invite you actually have.

Do companies pay for onsite interview travel?

Often they do, under one of three models, and the model sets your risks. In published policies, the employer either books and pays vendors directly, has you pay and claim it back with receipts, or mixes agency booking with reimbursement for some costs.

• Employer books and pays directly. Richmond books through a travel agency. Princeton uses World Travel, which arranges travel "with little or no out-of-pocket expenses to the candidate". You have little or nothing to claim, so the risk moves to whatever the policy leaves out. Richmond, for example, does not reimburse candidates for meals.
• Candidate pays and claims it back. Bath and Mt. SAC work this way. The risks are the deadline and the type of receipt.
• Mixed. St. Lawrence books through an agency and pays meals at $30 a day without receipts or $40 with receipts.

A note on what this table is. Nearly all of these are universities, because universities publish their policies. Most private employers don't. Use the table to learn which questions to ask, not to predict your own employer's answer. The only terms that apply to you are the ones your employer puts in writing.

Three details in these policies catch people out:

• Local exclusions differ a lot. A candidate 40 miles away is refused at Princeton (50-mile threshold) and accepted at Bath (30-mile radius).
• Some travel modes are excluded. Princeton says rental cars are normally not covered.
• Internal candidates may not qualify. Leeds says expenses will not usually be reimbursed to candidates already employed by the university.

Who books the travel decides which mistake you can make.

Who should I ask about travel reimbursement, and what should I say?

Ask whoever administers the policy, usually an in-house recruiting or interview coordinator, and ask in writing before you book. The recruiter who invited you may not control the travel policy, especially if they work for an agency.

The numbers explain why. A recruiting coordinator schedules interview loops and handles candidate logistics. A technical recruiter sources and screens candidates. There are far more of the second than the first.

In Refolk's index of professional profiles, a staffing firm, Experis, accounts for 6 of the top 25 technical recruiter profiles sampled. Agency recruiters place candidates with client companies and may not control or even know the client's travel policy. I am inferring this from the data, not quoting a published rule. In practice it means: if your contact is an agency recruiter, ask them to connect you with the client's coordinator, or to get the policy in writing from that coordinator.

Don't read the UK figure of 56 as the size of the UK market. It most likely reflects gaps in coverage or title matching, so don't compare the US and UK counts as if they described real markets. US coordinator employers in the sample include Salesforce, Toyota North America and Simpplr. UK employers include AWS, Apple, PwC and the NHS.

Lead time matters if you need to fly. Vassar strongly suggests 14 or more days of advance notice when airfare is involved. Send this email the day the invite arrives.

Subject: Travel and logistics for the in-person round on [date]

Hi [Name],

Thanks for the invite to the in-person round. Before I book anything, could you confirm a few things in writing?

1. Will you book travel, or should I book and claim it back?
2. Are there caps on airfare, lodging, mileage or meals, and is a rental car covered?
3. Is there a distance threshold for reimbursement? I'm travelling from [city], about [X] miles away.
4. Which claim form should I use, where do I send it, and what is the deadline?
5. What receipt format do you need (itemized, in my name, originals or scans)?
6. Could you share the agenda: the rounds, their length, and whether lunch or a tour is included? If there is a lunch, does the host submit feedback?
7. What ID should I bring to check in? May I mask everything except my name and photo?
8. What are the rules on AI tools, devices and notes for each round?

If travel is handled by another team or by your client, could you put me in touch with the coordinator who manages it?

Thanks,
[Your name]
[Phone]

You're done when you have a reply that names the booking model, the caps, the form and the deadline. "We'll sort it out on the day" doesn't count. If that's the answer you get, reply and ask for the policy document.

The in-person round, start to finish

The run has eight steps, dated from the day the invite arrives. Steps 1 to 3 settle money and rules in the first week, step 4 covers the last two weeks of practice, and steps 5 to 8 run from the day before through to payment.

The order changes in one case. Richmond asks for rental-car receipts on the day of the scheduled interview, so for an employer like that, part of step 8 happens during step 6. Look in the terms email for any same-day requirement and move it into your plan for the day.

Step 2 in detail: ID, AI and device rules

ID. Equinix's published rule is the clearest one available: at the start of the interview, candidates present a valid government-issued photo ID, and may mask everything on it except name and photo. In the UK, Bath Spa says candidates may be asked to show reception an original document proving their right to work in the UK. Some employers also run a pre-onsite identity check, and one verification checklist notes that a CLEAR identity check is offered through Greenhouse. Comparing your face against recordings of earlier video rounds is not a published practice at any employer I can find, so don't assume it happens or that it doesn't.

AI and devices. Employers' rules point in opposite directions. Amazon's guidance tells candidates not to use generative AI tools during interviews unless explicitly permitted, and breaking that rule can lead to disqualification. Meta, Canva and Shopify allow or expect AI tools in technical rounds. Google is doing both at once, piloting an AI-assisted round while bringing back an in-person one. I have found no employer page that sets separate device or notes rules for onsite rounds alongside its rules for virtual rounds. So get the rule round by round. If the invite says nothing, email the recruiter and ask plainly whether AI tools are allowed.

How do I switch from screen practice to whiteboard practice?

For the last two weeks, do every review session on paper or a whiteboard, with a 30 to 45 minute timer, at two to three problems a week, and with someone watching at least once. Practice in an IDE does not carry over to writing code by hand while explaining it.

The published protocols are close to one another:

All of these are practitioner blogs, not benchmarks. Nobody has tested whether two problems a week beats three. Treat the numbers as a sensible minimum.

How to run the switch:

1. Ask what surface you'll use. Whiteboard, paper or a provided laptop changes the drill. Add the question to your step 2 email if the agenda doesn't say.
2. Week two out: move all practice to the surface you'll use. Get a cheap whiteboard or a pad of plain paper. Set the timer to match the round, about 45 minutes if your agenda follows the common pattern.
3. Drill what the IDE was doing for you. That means syntax from memory, legible layout with room to insert lines, and tracing your code by hand on a small input before you call it done.
4. Talk the whole time. The round assesses your reasoning as much as the code. Practise narrating while you write, because that's the skill a screen let you skip.
5. Week one out: do at least one timed solve with someone watching, in person if you can. That is the check that practice has actually moved off the screen.

Here is what a result looks like when it misleads you: you finish a hand-written problem in 30 minutes, but silently, alone, and with notes in reach. That proves you know the material. It does not prove you can perform in the room. Only the observed, timed drill tests that.

For drill topics, start with the posting's requirements where your evidence is thinnest. Refolk scores how well your history fits each posting you apply to, and its weakest requirements are the ones most likely to come up at the whiteboard.

I found no published equivalent of these protocols for case interviews. If your in-person round is a case, the protocol isn't established. Ask the coordinator what format it uses and rehearse in that format with the same timer-and-observer setup.

Onsite interview day schedule: what to expect

Expect most of a day. Aggregated reports of Google's onsite describe four to six interviews of about 45 minutes each, typically two or three, then a lunch break, then two or three more. No employer publishes its own structure, so take your actual schedule from the coordinator's agenda.

The sources split on lunch. Don't settle it by guessing. Ask the coordinator whether the lunch host submits feedback, and until you have an answer, behave as if they do.

What to bring to an in-person final round

• Valid government-issued photo ID. Mask everything except name and photo if the employer allows it, as Equinix does.
• In the UK, an original right-to-work document if the employer has asked for one.
• The written agenda and the coordinator's phone number.
• The travel-terms email, so you can answer any question at the desk.
• Printed copies of the exact resume version you applied with. Interviewers will be reading that version. Refolk keeps the tailored resume for each posting, so you print the one this employer has, not your latest edit.
• A phone with space for receipt photos and an envelope for paper originals.

Between blocks

Use the gap to reset, not to replay the last round. Check the time, drink water, and read the next block's line on the agenda. If a block overruns, tell the coordinator rather than cutting into the next one yourself.

How the in-person round goes wrong

Most failures happen before or after the interviews themselves, and nearly all of them come from assuming instead of checking. Each failure mode below has its own check, and most of the checks belong in step 1 or step 2.

1. Lunch is treated as off the record. It shows up as a candidate who relaxes over lunch and says things they'd never say in a scored round. Levels.fyi says lunch is not evaluated. LockedIn AI says it is. Check: ask the coordinator whether the lunch host submits feedback.
2. A bank statement is used as the receipt. The claim gets rejected or sent back weeks later. Bath refuses bank and credit card statements outright, citing tax authority guidelines. Check: get the itemized vendor receipt before you leave the counter.
3. The candidate falls under the local exclusion. Someone 40 miles away files a claim that fails at Princeton's 50-mile threshold, though it would pass at Bath's 30-mile radius. Check: confirm the threshold in step 1, and give your distance in the email.
4. A scam ID request looks legitimate. Collecting identity documents before an interview is a known tactic of fraudulent operations, and a request for a passport scan by email can look like normal onboarding. Check: show your ID only in person or on live video, never send it to a personal email address, and mask everything except name and photo where the employer allows it.
5. The AI rule is assumed to carry over. A candidate who was allowed AI tools in one round assumes the onsite works the same way. Rules are set round by round, and at Amazon the penalty for breaking one is disqualification. Check: get the AI, device and notes rule in writing for each round.
6. Practice stays in the IDE. It shows up as fluent screen solves followed by a stalled whiteboard, with forgotten syntax and silence while writing. Check: do one timed paper solve with someone watching before the day.
7. Internal candidates assume they qualify. An employee applying internally books travel expecting to be reimbursed. Leeds says it will not usually reimburse candidates it already employs. Check: if you already work there, ask specifically whether the policy covers you.
8. The name on the ID differs from the name on the application. This is my own inference; no public guidance covers it. A married name, a preferred name or a transliteration could stall check-in at an identity-focused round. Check: raise it with the recruiter in step 2 and ask which document they'll accept.

Two of these failures look like success at first. A claim with card statements gets submitted without error and then bounces. An onsite where the candidate relaxed at lunch feels like it went well until the feedback comes back. In both cases the confidence comes from not having checked.

Filing the expense claim and keeping the record

Log every receipt the day you get it, as an itemized vendor receipt in your name, and file the named form well inside the deadline. Published deadlines run from 15 business days to 60 days, so a candidate who assumes "about a month" misses St. Lawrence's window.

Receipt rules vary as much as deadlines do:

Payment timing varies too. At Leeds, forms received by the 10th of the month are normally paid by the end of that month. At Bath Spa, successful candidates get their expenses back in their monthly salary. Use the terms email to work out when to expect the money, and set a reminder for the day after.

Employer:
Coordinator and email:
Booking model (direct / claim-back / mixed):
Local exclusion and my distance:
Claim form name and where to send it:
Claim deadline (exact date):
Receipt format required:
Expected payment date:

Date | Vendor | Category | Amount | Paid by | Itemized? | In my name? | Photo file | Claimable?
[date] | [vendor] | [travel / lodging / meal / parking] | [amount] | [card / cash] | [Y/N] | [Y/N] | [file name] | [Y/N per terms]

Submitted on: [date]  Confirmation: [reference]
Chase on: [date]

After filing, keep the terms email, the submitted form and the receipt photos together until the money arrives. If the expected date passes, reply on the same thread with your submission date and confirmation reference. If you're likely to get more onsite invites, save this log as a template. Each new employer only needs a new header.