Recruiter Prep Call Before Your Onsite? Ask the Questions That Can Still Change Your Loop

A recruiter prep call before your onsite is a short call after the loop is booked. Most candidates spend it asking what to study. That gets a generic topic list. Asking for the actual questions gets a polite no. Use the call for answers that can still change your week. First, find out which version of each round you are slotted for. At some companies the recruiter picks it from your background. That choice can still move. Second, pin down the tools. That means the editor, the language, whether your code runs and the rules on AI. Third, get the date you will hear back and the person who will tell you. Each answer should change one thing about how you practice before the loop. If an answer would change nothing, skip that question. Below is one Android engineer’s call, a full script to adapt and the prep change each answer caused.

A recruiter prep call is your last chance to change the loop

Here is the running example. Karim is an Android engineer with five years on one Kotlin app. His onsite at a large company is booked for ten days out. The recruiter emails the agenda and offers a 20-minute prep call. The agenda lists two coding rounds, one design round and one behavioral round.

Karim’s first draft of questions is the common one. What topics come up? Is it LeetCode medium or hard? Any tips? None of those answers would change his plan. He already practices coding every day. A recruiter’s tip list will not tell him anything his own prep missed.

So he rewrites the list around decisions. Each question has to settle something he would otherwise guess. He ends up with four. They cover the design round, the coding setup, AI rules and the decision date.

Some recruiters still choose which design round you get

The design slot is the question most likely to change the loop itself. At Meta, the recruiter assigns it, according to interviewing.io’s guide to Meta’s hiring process. The guide shows no publish date. Its AI-round section describes late 2025. interviewing.io sells mock interviews. So read it as a coaching company’s account. It says the recruiter picks product design or system design. The pick depends on your experience. Feature work points to product design. Work on high-scale distributed systems points to system design.

Karim’s five years were mostly product features. That includes offline sync, a checkout flow and the API contract behind it. A product design round fits that history. A backend-heavy system design round fits it less well. If his file says “system design,” he wants to know now. Ten days is enough to shift his practice. It is also early enough to tell the recruiter what he built. Then he can ask whether the other round fits better.

Other companies may not offer that choice. The question still costs ten seconds. If the answer is fixed, you at least know which round to drill. See our post on the Meta product architecture interview for Android engineers. It covers how that round differs from backend design.

Tool questions decide which editor you should practice in this week

The second group of questions is about the environment. Three companies show how far apart the setups can be.

Amazon’s own SDE II prep page shows no date. It says the loop has four interviews of 55 minutes each. It asks for syntactically correct code and rules out pseudo code. It also suggests practicing in Livecode if you are rusty coding without an IDE. A candidate who only practices in Android Studio will feel that gap on the day.

Stripe works differently, in interviewing.io’s account of Stripe’s process. That page is also undated. It lists a second 30-minute recruiter call to help you prepare for the onsite. For coding, it says you choose between your own IDE over screen share and CoderPad. It also says AI use in Stripe interviews is strictly prohibited.

Meta adds a third case. The same Meta guide says an AI-enabled coding round randomly replaces one of the two onsite coding rounds. The guide called that round a pilot as of the fourth quarter of 2025. It said Meta planned to roll it out to all software engineering roles in 2026. It adds that your recruiter should send a practice environment link. If they don’t, ask for it.

So one company suggests practicing without an IDE. Another lets you bring your own. The third may hand you an AI assistant. That is why the setup questions belong on every prep call. Ask about the editor, running code, the language and AI. Two of our posts cover what to do with the answers. One is on using Android Studio in a coding interview. The other is on the AI-assisted coding round.

A sample script: Karim’s four questions in the order he asked them

Karim reads this from a note. It takes about two minutes before the recruiter answers. Adapt the details to your own background.

Thanks for setting this up. I have four quick questions. Then I’ll let you go.

First, the design round. Is it product design or system design? Most of my last five years was feature work in our Android app. That means offline sync, the checkout flow and the API contract behind it. If there’s any flexibility, product design matches that better.

Second, the coding setup. Which editor will I use? Will my code run, or is it read only? And is Kotlin fine for both coding rounds?

Third, is either coding round AI-assisted? If it could be, is there a practice environment I can try this week?

Last, after the loop, when should I expect to hear back? Will that come from you?

The recruiter’s answers, in this example, are specific. The design round is product design. Coding happens in a shared editor, the code runs and Kotlin is fine. One coding round may be AI-enabled. A practice link follows by email. A decision usually comes within a week, from the recruiter.

Each answer in the script changes one part of the next ten days

The opener sets a limit. “Four quick questions” tells the recruiter the call will stay short. It also keeps Karim from drifting into small talk he did not plan.

The design question comes with evidence. Karim names three things he built. If the recruiter has any say, those details support the change. The answer moves his design practice to client-server contracts and away from sharding drills.

The coding question has three parts because each part changes practice. A shared editor means he stops leaning on autocomplete this week. Running code means he practices writing small tests as he goes. Confirming Kotlin removes a last-minute language switch.

The AI question asks for a practice link as well as a yes or no. The link turns a vague worry into an hour of hands-on time. He tries the editor and the assistant before the real round.

The last question gets a date and a name. If a week passes with no word, he knows whom to email and when. Our post on no response after the final interview covers that follow-up.

After the call, Karim rewrites his plan in one line per answer. Product design gets two practice sessions. Coding moves to a plain editor with tests. One evening goes to the AI practice environment. Before the call, each of those three choices was a guess.

Leave the actual questions and your salary out of the call

Two kinds of questions waste the slot. The first is asking what the interview questions will be. A recruiter is unlikely to share them. The ask can also sound like you want a shortcut. Ask about format, tools and round types instead.

The second is pay. The prep call is about the loop. interviewing.io’s Stripe page has advice on pay. It says not to reveal salary expectations in the first recruiter call. Keep this call on the loop for the same reason. If the recruiter raises pay, say you’d like to focus on the interviews first and talk numbers later.

Leave a Comment