The Post-Offer Approver Interview, Carried to a Written Yes

You have a verbal offer, and then the recruiter says a senior leader wants one more conversation before the letter goes out. This guide is for the candidate in that gap: verbally yes, not yet signed, and facing a VP or skip-level who never interviewed you and can still veto. I carry one case all the way through that approver call so you can recognize it for what it is, run it, and convert it into a written yes.

Most offer-stage advice treats the verbal offer as won and moves on to paperwork. That advice is wrong for this situation. The extra conversation is not a formality. It is the last unrestricted evaluation, and the person running it is often the one selling you and the one who can kill it.

Why there is an extra interview after a verbal offer

The extra conversation exists because the sign-off chain is real and deep, and a senior approver who never met you often wants their own read before committing the letter. Recruiters frame it as a "sell." It functions as a live evaluation.

Here is the mechanism. An offer does not clear one person. The interview team signs off, then the hiring manager, then a director, and only then does it reach a VP who can still reject you. In Refolk's index of professional profiles, the US has 20,597 director-tier and 2,100 VP-tier engineering approvers, which works out to roughly 9.8 directors for every VP. That ratio is the shape of the problem: an offer commonly passes several people before it reaches an executive, and any of them can add days or say no.

This is why "the director signed off" is not the same as "you are safe." The documented cases bear it out: a Coinbase verbal offer revoked by the VP, an Apple hardware role where the verbal was accepted and then executive approval rejected the acceptance, a Waymo verbal offer not approved after three days for a local candidate who never negotiated. In each, lower approvers had already cleared it. The last gate held the veto.

The case: verbal yes, then "meet the VP"

Follow one candidate through the whole arc. The pattern generalizes even though the names do not.

The candidate, call them the applicant, cleared a full loop for a senior engineering role. The hiring manager and recruiter both signaled strong intent. Two days later the recruiter called with a verbal offer: base, equity, a target start date, and the sentence that defines this guide - "One more thing, our VP wants a quick conversation with you before we send the letter. It's really just a chance for you to hear about the org."

That framing is the trap. Because both candidates and interviewers describe these post-offer meetings as standard and reasonable, the applicant's first instinct was to treat it as a lap of honor. That instinct is the single most expensive mistake available here, and I will show where it nearly cost the offer.

The verbal-to-written window matters because it tells you how much runway the approver step has to consume. Here is the timeline by employer type, which is the backdrop the whole case plays out against.

The applicant's employer ran multi-level approval, so the honest expectation was weeks, not days. One reported Apple candidate got the letter about two weeks after the verbal offer; the reported range at that scale runs from three days to four months, with one position requiring SVP-level sign-off that overlapped holidays. The lesson from the timeline table: match your follow-up cadence to the employer type, and do not read a slow multi-level approval as a rejection.

Read the recruiter's framing correctly

The recruiter's exact words are a signal, and the honest read is that any conversation whose sign-off is required for the letter is an interview regardless of how it is described. Decode the framing before you decide how hard to prep.

Two phrases tell you what you are walking into. When a recruiter says something like "she has gotten VP approval and you just wait a few days for the system," the evaluation is behind you and the delay is administrative. When the recruiter says "the VP wants to talk to you first," the evaluation is still live and in front of you. The applicant's recruiter said the second thing. That is a live interview.

Do not try to infer this from tone. Ask directly.

"Happy to make time for the conversation with [leader's name]. So I can prepare well - is their sign-off required before the written offer goes out, or is this more of an intro to the org? And do you have a target date for the letter itself?"

The answer tells you two things at once: whether to prep as an interview, and what date to anchor your follow-up cadence to. If the answer is yes, sign-off is required, you prepare for a live evaluation. If the recruiter dodges the sign-off question, assume yes.

Map the approver and the approval chain

Before the call, name every gate between the verbal yes and the signature, because the veto usually sits with someone who never saw your loop. You cannot prep for an evaluator you cannot name.

In the case, the applicant reconstructed the chain from the recruiter and from public records: interview panel, then the hiring manager, then a director, then the VP taking the call. Four gates. Three had cleared. The one that had not was the one that had never met the applicant, which is exactly the configuration that produces late rejections.

The depth of that chain is not uniform across markets. It changes how many gates sit before an executive and how you should read a stall.

The UK numbers look thin, but the ratio inside a company is what bites. In Refolk's index there are 17.4 directors per VP in the UK versus 9.8 in the US, implying more director-level gates before you reach an executive in a UK org. That is consistent with the UK's lower 19% withdrawal rate but points to potentially slower sign-off. Read your own chain accordingly: more gates means more days and more places the offer can stall for reasons that have nothing to do with you.

Mapping the chain by hand means reading org charts and guessing at reporting lines. This is one place where a search that already knows the approver population removes real friction. Refolk can name the VP and directors above your hiring manager so you know who signs and who you are actually talking to.

Prep substance, not charm

Prepare to re-justify your impact and your ceiling, because the objection that kills these calls is rarely "we don't like them" and usually "I met them but I'm not sure they raise the bar." The approver is checking whether the lower gates were right, not restarting from zero.

The applicant's first prep pass was a mistake worth naming: rehearsing enthusiasm, reading the company blog, preparing to sound excited. That is charm. Charm does not survive a skeptical skip-level who has three other offers on their desk. The second pass was substance: two or three stories where the applicant did not just do the job but changed how the team worked, sized so they could be told cold in ninety seconds.

The distinction is concrete. "Met the bar" means you can do the role. "Raised the bar" means the team is better because you joined. The approver is testing the second claim, so lead every impact story with the change you caused, not the task you completed.

Build each story to survive a follow-up question. A story that collapses on "what would you have done differently" reads as rehearsed, and rehearsed reads as met-the-bar. If your stories are thin, that is a prep problem you can fix before the call, not a reason to walk in hoping.

Run the approver conversation

Answer every strategy and fit question as if it is scored, and keep all compensation with the recruiter, never the VP. The call is won by leaving no new objection open and by not creating one.

Here is the ordered shape of the whole procedure, from the moment you hear "one more conversation" to the signature.

In the case, the call ran about forty minutes. The VP asked how the applicant thought about a hard architectural tradeoff, what the applicant would change about how the team shipped, and one pointed question about a competing approach. The applicant answered with the impact stories, named a real gap without flinching, and did not once mention money.

That last part matters. Midway through, the VP asked casually whether the offer was "landing where you hoped." This is the fork where the case nearly turned. The instinct is to negotiate - the VP asked, the VP has authority, why not. The applicant said, "The recruiter and I are still finalizing the details, but I'm excited about the role itself." That deflection saved the offer.

Here is why the deflection was right. Late negotiation is the highest-cost wrong turn in this whole process, because a counter re-triggers approval at the exact moment sign-off is pending. Documented cases lost the entire offer over a match request: a candidate negotiated, the recruiter said they would not match, and then either ghosted or would not proceed. Reopening comp with the person holding the veto compounds that risk. Keep money with the recruiter, always, and never on the approver call.

Hold the follow-up cadence

Send exactly one professional check-in at about five business days if the letter has not arrived, and escalate only after two unanswered follow-ups over ten-plus days. Cadence here is diagnostic, not just polite.

The reasoning is precise. A single five-day check-in maximizes information while avoiding the anxiety read. Two unanswered follow-ups over ten-plus business days is the recognized stall flag, so silence after your check-ins tells you something the recruiter will not say directly. Over-pinging tells the employer something too, and none of it is good.

The applicant's employer ran multi-level approval, so five business days passed with no letter, which was fully expected at that scale. The check-in was framed as planning, not pressure.

Subject: Quick status check on the written offer

Hi [recruiter name],

Thanks again for the conversation with [leader] earlier this week - I enjoyed it and I'm still very excited about the role. I wanted to check on the status of the written offer, and whether there's anything you need from me to keep things moving. I'm lining up my start-date logistics and want to make sure I have everything I need to review promptly on my end.

Thanks,
[name]

Match the trigger to the employer type. For a startup or a typical company, five business days is the mark. For enterprise, government, or multi-level VP or SVP approval, hold to eight-plus business days before the first nudge, because the window itself is three to six weeks or more. Nudging a slow-but-normal approval at day five reads as anxious and buys you nothing.

How this goes wrong

The failure modes here are specific and each one has cost people the whole offer. This is the part to read twice, because recognizing the trap is most of avoiding it.

Two of these deserve extra weight because they are counterintuitive.

Misdiagnosing the stall. A budget or headcount freeze looks identical to a slow approver from the outside: same silence, same "still working through approvals." The tell is external. If the role gets reopened or reposted on the company careers page, the stall is structural, not about you. Check the careers page when a stall runs long, because it distinguishes "the VP is busy" from "the headcount is gone."

The competing-offer disclosure. The false positive is thinking a higher offer adds urgency. In practice it can read as flight risk before sign-off, and one Apple candidate had executive approval reject the acceptance while unsure whether the competing offer factored in. If you genuinely need a decision by a date, state the timeline to the recruiter as a scheduling fact, not to the approver as leverage.

What "done" looks like

Before you treat this as won, verify every gate below. The applicant's case ended with a signed letter about two and a half weeks after the verbal offer, inside the multi-level window, with no wrong turns left uncorrected.

The one rule that outranks all the others: do not resign until the letter is signed. Roughly one in four job seekers have declined an offer after verbally accepting it, and employer-side withdrawal runs about 31% in the US and 19% in the UK, so reversals in both directions are ordinary. The candidate who resigns on a verbal yes and then hits a VP veto has no offer and no job. Keep interviewing, keep your current role, and let the signature be the thing that ends the search.

Keep the read current

The mechanism in this guide is stable, but two of its inputs move, so re-check them per situation rather than trusting a remembered number. Timelines and approval depth are the two to verify each time.

First, re-confirm the letter window against the employer type on the day you get the verbal offer, because a startup's one-to-two days and a multi-level enterprise's three-to-six weeks demand completely different cadences. Ask the recruiter for a target date and hold them to their own type, not to a generic average.

Second, re-map the approval chain for each new company, because the number of gates before an executive varies by market and org. The 9.8 directors per VP in the US and 17.4 in the UK from Refolk's index are averages; your specific company may be deeper or flatter, and the depth tells you how many places the offer can quietly stall. When the stall runs long, the careers page is your ground truth: a reposted role means the problem is structural, and a silent-but-unposted role means you are still in the queue.