EY Forward Deployed · recruiter practice
Training Feed
Recruiter screen · practice transcripts

Three recruiter calls, written out

Read them out loud, in character. Your lines are editable: click any of them, change the words to yours, and the page remembers the edit in this browser. The number under each line is how long it takes to say at a normal pace. Anything over 60 seconds turns red.

How to use this page
  1. Read A once straight through, both parts, out loud. Fix any line that does not sound like you.
  2. Switch on Practice mode. Read the recruiter's line, answer from memory, then tap to compare.
  3. Do B when A is smooth. B is the same call with a recruiter who pushes.
  4. C is the drill for a rushed call: the two-minute version of everything.
  5. Fill every [bracket] before the real call. Those are facts only you know.
$151K–$262KNYC band, Manager
$250K · $290Kyour base anchor · total cash
$225Kyour floor on base
~$206Kband midpoint, where HR starts
40–60%in person; NYC, Charlotte, Dallas, Tampa
SR 26-2replaced SR 11-7, 17 Apr 2026
Transcript A · about 30 minutes

The standard screen

A friendly recruiter from EY's financial services technology recruiting team, working from a script: the pitch, your background, motivation, the posting's must-haves, logistics, your questions. The recruiter's job is to decide whether you are clear, senior, and closeable. Nothing here is about architecture.

R
Johnny, thanks for making the time. I'm with the financial services technology recruiting team here at EY. Quick agenda: I'll tell you a bit about the team and the role, I'd love to hear your background, we'll cover logistics, and then I'll leave time for your questions. Sound good?
J
Sounds good. Let me say what I think I know, and you can correct me. This sits in FSO's Consulting practice, in FS Technology Consulting, under the AI practice Mudit Gupta leads. You're hiring Forward Deployed Engineers at three levels at once: Senior, Manager and Senior Manager. I applied for the Manager seat.
Why this works. Thirty seconds in, the level is settled and the recruiter knows you did the homework. Say it once. Do not repeat it, and do not explain it unless you are asked.
R
That's right, and you've clearly read up. The short version from our side: FSO is EY's dedicated financial services business, and this team embeds engineers with banks, insurers and asset managers to take AI from pilot into production. We're hiring at three levels because we're standing up small pods. It's hybrid, roughly forty to sixty percent in person, out of New York, Charlotte, Dallas or Tampa. So, walk me through your background.
J
Twenty years in data and AI, in three chapters. Twelve years client-facing, at Accenture and two agencies, leading onshore and offshore analytics teams for Fortune 20 clients. Then eight years inside bank risk, at MUFG and US Bank, building the platforms, getting them through model validation and presenting to a board risk committee. At US Bank there was no budget for a vendor, so I made the build-versus-buy case and built it in-house on open source. Three teams share it now. And this year, hands-on agentic engineering through the Gauntlet program, shipping with Claude Code every day. The forward deployed role is those three chapters combined.
Demonstrates: communicator, commercial acumen. Watch: stop at "combined". The recruiter will ask for more if they want it.
R
Tell me more about the US Bank platform. What did you actually build?
J
A climate scenario analysis platform for the credit portfolio. There was no budget for a vendor, so I made the case to build it in-house on an open-source stack. It simulates physical hazard across more than thirty-six building types and a portfolio above two hundred fifty billion dollars, and it feeds credit loss estimates. The hard part wasn't the modeling. It was getting it through model risk management and in front of the board risk committee, with the documentation and the evidence trail that implies. I'll say it plainly: it's a quantitative simulation platform, not an AI-agent system. The agent work is what I've done this year.
Demonstrates: integrity, regulated judgment. Volunteering that the platform is not an agent system builds trust before the hiring manager can poke at it.
R
Great. So why EY, why this role, and why now?
J
The posting describes work I've done from the client's side: taking AI into production inside a bank's governance. EY has what a single bank can't give me: client access across many institutions, a dedicated FS unit, the Microsoft and NVIDIA platform, and a team being built at three levels right now. Why now is simple. I spent this year retooling as an engineer on purpose, and I want the seat where that combination is the job rather than a side project.
Demonstrates: innovation mindset, lifelong learner. The sentence "I'd rather do it across many institutions than one" is the line recruiters repeat to hiring managers.
R
And what's your current situation? Are you still at US Bank?
J
I'm at US Bank, leading climate scenario analysis. Earlier this year I made the case internally that applied AI was becoming central to that work, and my manager backed it with a combination of time off and remote work. That's how I did the Gauntlet engineering program properly rather than around the edges. [GT School: confirm title, scope and whether it's current.] So there's no gap on the timeline. The retooling was deliberate, and my employer agreed with it.
The point of this answer is that there is no gap. You were employed throughout. Time off plus approved remote work is a normal arrangement, and saying your manager backed it removes any suggestion you were doing it quietly.
Say it in one breath, without hedging. The recruiter is only checking for a gap or something irregular. "I made the case, my manager backed it" answers both at once. LinkedIn must show continuous US Bank employment or this unravels.
R
You've been inside banks for eight years. Why consulting again? And just so you know, even at Manager there's a utilization target and some business development expected.
J
I spent twelve years client-side before banking, so the rhythm is familiar: scoping, delivery, the client relationship, developing people. On business development, I've run a P&L before, at Havas, and inside US Bank I sold a build-versus-buy decision with no budget behind it, which is the hardest version of that because you're asking for belief before money. And the practical reason: a forward deployed engineer sees ten banks' problems in the time someone inside one bank sees one.
Demonstrates: commercial acumen. Do not apologize for the bank years. They are the credential.
R
How hands-on are you today? This is an engineering role, not a program lead.
J
Daily. Python, Claude Code and Codex, LangGraph, local and frontier models. This year I shipped a multi-agent red-teaming platform with an evaluation harness and a tested cost invariant, and a clinical copilot with an eighty-case regression suite. I'm happy to screen-share the pipeline in the technical round.
Demonstrates: analytics mindset, ownership. Offering the screen-share closes the "is he really hands-on" question without arguing it.
R
Let me run the must-haves on the posting. Ten-plus years, production AI systems in financial services, experience with model risk and regulatory expectations, the posting mentions SR 11-7, and familiarity with agentic frameworks and evaluation. Anything there you'd flag?
J
All covered, with one small update you may want for the posting. SR 11-7 was replaced by SR 26-2 in April. I've worked under both: my platforms went through model validation at two banks, and SR 26-2 is what I'd design to now. On agentic frameworks and evaluation, that's this year's work, and I can show it.
Demonstrates: regulated judgment, courage to lead, gently. Correct the posting once, kindly, and move on. Never make the recruiter feel caught out.
R
On level: you applied at Manager, but your background reads Senior Manager or above. Help me understand that. Are you targeting Manager deliberately?
J
Manager, and that's deliberate, not a fallback. I spent this year retooling as a hands-on engineer, and the Manager seat is where the build time is. On a consulting team, Senior Manager is roughly where you stop building and start running the people who do. I'd rather come in and do the work than negotiate for a level and then spend a year proving the calibration. Twenty years means I'll contribute quickly. It doesn't mean I need the title to.
Say it positively, once. The recruiter's worry is that Manager is your consolation prize. "Deliberate rather than a fallback" kills that in six words. Never justify it twice; repetition sounds like regret.
R
Understood. Compensation: what are your expectations?
J
The Manager band for New York runs one fifty-one to two sixty-two. Where does a Manager with twenty years and two banks' worth of model-risk depth usually land in that, and what's the bonus target at this level?
Turn it first. You learn their number before you give yours. NYC's salary history ban means they cannot ask what you earn now; give expectations only.
R
Honestly, most Manager offers land in the upper one hundreds, call it one eighty to two ten on base, with a bonus target in the mid to high teens. Where are you?
J
Upper part of the band. Around two fifty on base, with total cash near two ninety. That reflects twenty years, the FS regulatory depth and New York. I'm flexible on structure, so if base is capped, the bonus target and a sign-on are the levers. I'd also want to understand the promotion cycle, because at this level that matters more to me than the first number.
Anchor inside the band, not above it. $300K was the Senior Manager number; the Manager ceiling is $261,600, and asking past it reads as someone who did not read the posting. Realistic landing is $175–210K base, so $250K is an ambitious ask you must justify with the twenty years. Your floor is $225K: do not say it.
R
Noted. Location and travel: you're in New York? And how do you feel about forty to sixty percent in person, plus client travel?
J
New York City. Hybrid is how I've worked for years, and client-site time is the point of a forward deployed role. Travel to Charlotte, Dallas or Tampa for engagements is fine [confirm any constraints before the call].
R
Work authorization, notice period, and when could you start?
J
[Authorized to work in the US without sponsorship, confirm.] Notice is [two to four weeks, confirm]. I could start [a date, or "within a month of an offer"].
Have exact answers. Vagueness on these three reads as a flight risk.
R
Are you interviewing elsewhere, and what's your timeline?
J
I'm in a couple of conversations, and this one is a priority because it matches the work most closely. I can move at your pace. If your loop runs two or three weeks, that works.
No firm names, no stages. "A priority" is the phrase; "my first choice" sounds like a negotiating position.
R
How did you hear about the role, and do you know anyone at EY?
J
Jing Huang referred me through the employee referral program at the end of October. The connection is at one remove: my wife is ex-EY, she was in the QAS quant team in FSO doing CECL work, and Jing worked with her there. So I have a fair picture of how FSO runs and how model work gets reviewed. The referral opened the door. I'd rather be judged on the work.
Say the referral out loud. It is logged in EY's system against req 1708794, so the recruiter can already see it. Claiming you have no referral would read as evasive. One sentence of connection, one of independence from it.
R
Last one from me: anything we should know before the hiring manager sees your resume?
J
Two things worth saying plainly. My delivery experience is credit and market risk rather than fraud or wealth, and my platform work has been Snowflake rather than Databricks. Both transfer, and I'd rather the hiring manager hear it from me than discover it. One more for your process: I know EY audits U.S. Bancorp, so I expect independence disclosures around my US Bank employment and any holdings. I'll complete whatever you need.
Demonstrates: integrity. Raising independence yourself saves the recruiter an awkward call later and marks you as someone who knows how a Big Four firm works.
R
That's helpful, and yes, independence is part of onboarding for everyone. What questions do you have for me?
J
Four, and I'll keep them short. First: who is the hiring manager, and who else is on the loop?
R
Mudit Gupta is the hiring leader. You'd likely meet one of his Managing Directors or Senior Managers, there's usually an architecture conversation, and a Partner round at the end.
Listen for: a named Partner or MD in the AI practice and a defined technical conversation. Both are signs the practice is real, not a bench.
J
Second: how many rounds, and is there a technical exercise, a case or a presentation I should prepare for?
R
Typically three to four rounds after this call. No formal case. The technical round is a conversation about a client scenario, sometimes from your own resume. Occasionally a short written exercise.
Listen for: "from your own resume" means the US Bank platform and this year's agent work will be the material. "Written exercise" means a 48-hour deck is possible.
J
Third: is this requisition one seat or several, and is it tied to a specific client engagement or building the bench? And a related one: Jing Huang referred me to the Senior Manager requisition, and I've also been looking at the Manager seat. How do you think about calibrating someone with twenty years but one year of hands-on agentic engineering?
Put the level question to them rather than deciding it alone. The Senior Manager req (1708794) is live and you hold a referral into it, so pretending you only want Manager is a story the recruiter can check. Asking how they calibrate lets them place you without you talking yourself down.
R
Several seats across the levels, and a mix. Some pods are tied to engagements already sold, some are capacity for demand we're seeing. The posting may have been refreshed; the requisition is open.
Listen for: "sold" versus "capacity". A seat tied to a sold engagement starts faster and is harder to down-level. If the answer is vague, ask who the first client would be.
J
Last: what's the timeline to a decision, and when do you need someone to start?
R
We're moving quickly. If the hiring team wants to proceed, you'd hear from me within a few days, and the loop usually wraps in two to three weeks. Start dates are flexible, ideally within the quarter.
J
Thank you, this was useful. I'll send a short note tonight confirming my interest in the Manager seat and my availability. Who should I expect to hear from next, and roughly when?
Close. Then send the note the same day: two sentences, no attachments unless asked. It is the only follow-up most candidates skip.
R
You'll hear from me. I'll share your profile with Mudit's team today and come back with next steps. Thanks, Johnny.
Transcript B · about 30 minutes

The skeptical screen

Same call, different recruiter. This one has been burned by senior hires who could not do the work, and by candidates who would not close. Every question is a probe. Your job is the same: stay clear, stay senior, stay closeable, and never get defensive.

R
Johnny, I'll be direct because it saves us both time. Your resume reads data scientist and risk leader. This is an engineering role. Convince me.
J
Fair challenge, and I'd rather you ask it now than the hiring manager later. The data and risk years are why I can be trusted inside a bank. The engineering is what I've been doing daily this year. Concretely: a multi-agent red-teaming platform with an eval harness and a tested cost invariant, a clinical copilot with an eighty-case regression suite, and production agents for an education company. I write and ship the code with Claude Code and Codex. I'm not going to claim I'm a twenty-year software engineer. What I'll claim is that I'm the engineer who already knows how a bank's second line will read the code.
Rule: never say "I'm not a SWE". Say what you are. The last sentence is the whole pitch for this role.
R
Your last three titles are VP at banks. Consulting is a different pace, and frankly a different ego structure. Why would you go back, and why would you last?
J
I did twelve years of it first, at Accenture and two agencies, running onshore and offshore teams, so I know the pace and I know who the client is. I went into banking to understand the buyer from the inside, and I did. I've sat in the model validation meeting and in front of the board risk committee. On lasting: what burns people out in consulting is not knowing whether the work matters. A forward deployed engineer embedded in a bank sees it matter every week. That's the version of consulting I want.
Demonstrates: resilience, self-awareness. Answer "why would you last" directly; dodging it confirms the worry.
R
You've got twenty years and two VP titles. Manager is a seven-year role. What's going on, and are you going to be bored in six months?
J
Fair question, and the honest answer is that I optimized for the work, not the level. I spent 2026 retooling as a hands-on engineer, and on a consulting team Senior Manager is roughly where you stop building. If the worry is that I resent it in six months, the real test is whether the seat is genuinely hands-on, and that's the question I'd put back to you. If the worry is that I leave the moment a bigger title shows up, I'd point out I've already left two VP titles to get closer to the build.
Demonstrates: self-awareness, resilience. Turn the flight-risk worry into a question about the work. Do not promise to stay. Say what would make you stay.
R
The posting asks for SR 11-7 experience. Do you have it?
J
Yes, at two banks, and it's moved on: the Fed replaced SR 11-7 with SR 26-2 in April. The practical change is that it scopes out the generative and agentic systems this team builds, which means the bank's own governance has to carry them. That's exactly the gap a forward deployed engineer fills. I can go deeper in the technical round, but the short answer is yes, and current.
Demonstrates: regulated judgment. One sentence of substance, then an offer to go deeper. The recruiter does not need the detail; the hiring manager will.
R
Our platform work in this practice leans Databricks. Your background is Snowflake. Problem?
J
A gap I'd name myself. Snowflake is where my platform work has been. The lakehouse concepts, lineage, retrieval and governance are the same problems with different names, and I'd expect to be fluent on Databricks inside the first engagement. If it helps the hiring manager, I'll come to the technical round with something built on it.
Name the gap, size it, and offer evidence. Never claim fluency you do not have; Mudit leads EY's FS Databricks business and will know.
R
Two fifty is near the top of the Manager band. We rarely go there, and almost never for someone coming in from outside consulting. Is that a deal-breaker for you?
J
Not a deal-breaker, a starting point. The band tops out at two sixty-two, so two fifty is inside it, not above it. If base has to sit nearer the midpoint, then structure matters: a sign-on, the bonus target, and a promotion cycle with named criteria. Tell me where the team can get to and I'll tell you quickly whether it works.
Closeable, not cheap. You moved from base to structure without lowering your number. Your floor stays unspoken. Manager bonus targets run roughly 15–20%, so the bonus is worth real money to negotiate.
R
There's a stretch in 2026 where you were part-time, or between things. What were you doing?
J
Retooling on purpose, and with my employer's agreement. I made the case at US Bank that applied AI was becoming central to my role, and my manager approved a combination of time off and remote work so I could do the Gauntlet program properly. I shipped weekly rather than read about it. [GT School: confirm title and whether current.] I'd rather be judged on what I built this year than on how I arranged the time. Both are on the resume and in GitHub.
Must match Transcript A and LinkedIn exactly. If LinkedIn shows a US Bank end date, fix LinkedIn before the call.
R
You worked at US Bank. EY audits U.S. Bancorp. Are you aware of what the independence rules mean for you?
J
Yes. I expect to disclose my US Bank employment and any U.S. Bancorp holdings, and I understand restricted securities have to be divested at Manager and above. I'd note that EY is also Anthropic's auditor, so I'll disclose anything relevant there as well. Send me the questionnaire whenever it's useful. It won't slow anything down.
Demonstrates: integrity. Knowing about the Anthropic engagement before they mention it is a quiet signal of how closely you read.
R
Do you know anyone at EY? Any referral?
J
Yes, and formally. Jing Huang referred me through the employee referral program in late October. My wife is ex-EY, she was in the QAS quant team in FSO doing CECL work, and Jing worked with her there, so I know how FSO runs from the inside and how model work gets reviewed. I'll say plainly that a referral is a door, not an argument. I'd rather be judged on what I've built.
Also available: Ken Chen, who works closely with your wife at EY, is a second connection if one is ever useful. Do not list connections; one is enough.
Demonstrates: integrity, cultural fit. Say "QAS" and "CECL" as she would. Jing Huang is confirmed: the referral landed 29 Oct through the EY Employee Referral Program, so naming her is safe and checkable.
R
Last from me. If I put you forward and the hiring team passes, what would the reason most likely be?
J
Probably that they wanted a career consultant with a Databricks resume. If so, that's a fair call, and we'd have found out in two conversations instead of six. What I'd ask is that the technical round happens before that judgment, because the work is the best argument I have.
Demonstrates: self-awareness, confidence without arrogance. Naming the likely objection disarms it and asks for the one round that favors you.
R
Appreciated. Questions for me?
J
Two. What does a Manager on this team own end to end, and what does the path to Senior Manager actually look like here in practice? And is this seat tied to a sold engagement or building the bench?
Ask the promotion question at Manager. Typical Manager to Senior Manager is three to four years, about two for strong performers. Their answer tells you whether they see you as a fast-track hire.
R
Senior Managers own the client relationship and the architecture decisions; Managers run the delivery under them. Mix of both on seats. Some pods are sold, some are capacity.
Listen for: if the recruiter describes your experience back to you as Manager scope, correct it immediately and specifically. If the seat is "capacity", ask for the expected start.
J
Then the Manager seat is the right conversation. Thank you for being direct. It made this a better call. I'll confirm in writing tonight. What happens next, and when?
Transcript C · fifteen minutes

The rushed screen

The recruiter is late from another call and has fifteen minutes. There is no room for the full story. The drill: land the pitch in ninety seconds, give logistics in one breath, secure level and comp, ask two questions, close. Everything you say is shorter than in A.

R
Johnny, apologies, I'm running behind and I have about fifteen minutes. Can you give me the two-minute version of your background and why this role?
J
Of course. Twenty years in data and AI: twelve client-facing at Accenture and two agencies, then eight inside bank risk at MUFG and US Bank, where I built the climate platform in-house on open source with no budget for it, took it through model validation and presented it to a board risk committee. This year I retooled as a hands-on agentic engineer through Gauntlet, shipping with Claude Code daily. The forward deployed role is those three things in one seat: build inside the bank's governance, across many banks instead of one. That's why EY, and why now.
Ninety seconds, one breath. Practice this one until you can say it while walking.
R
Perfect. Level, location, authorization, notice, comp. Go.
J
Manager, deliberately. New York City, fine with forty to sixty percent in person and travel to the other three cities. [Authorized without sponsorship.] Notice [two to four weeks], start [within a month of an offer]. On comp, the Manager band is one fifty-one to two sixty-two. Given twenty years and the FS depth I'd expect around two fifty on base, and I'm flexible on structure.
Five facts, no hedging. Say the comp line exactly as written, then stop.
R
That's at the top of what I usually see for SM, but I'll carry it. Anything the hiring manager should know up front?
J
Two things, plainly: my delivery depth is credit and market risk rather than fraud or wealth, and my platform work is Snowflake rather than Databricks. Both transfer. And I know EY audits U.S. Bancorp, so I'll do the independence disclosures whenever you send them.
R
Good. Two minutes for questions.
J
Two. Who is the hiring manager and what does the loop look like, including any technical exercise? And is this seat tied to a sold engagement or building the bench?
R
Mudit Gupta's team. Three or four rounds, one of them an architecture conversation, Partner at the end. Mix of sold and capacity.
Listen for: the architecture conversation. If it is missing, offer the screen-share anyway; it is the round that favors you.
J
Thanks. I'll send a two-line note tonight confirming the Manager seat and my availability. Who do I hear from next, and when?
R
Me, by end of week. Thanks for being efficient, Johnny.
Drill

Hard moments, two ways each

Read the recruiter's line, answer out loud, then compare. Pick the version that sounds like you and delete the other.

"Honestly, you look overqualified for this level. Why are you applying at Manager?"

1 "Deliberate, not a fallback. I optimized for build time rather than title: on a consulting team Senior Manager is roughly where you stop shipping, and I spent this year becoming someone who ships. I'd rather be the most useful engineer on a Manager pod than a miscalibrated Senior Manager."

2 "Twenty years of context, and seven years of the specific thing you're hiring for. The posting wants someone who can build inside a bank's governance. That overlap is a Manager-shaped job, and the title can catch up."

"Given your background, we might look at the Senior Manager requisition instead."

1 "I'd want that conversation. The bands overlap, so this isn't only about money; it's whether the seat still has build time in it. If Senior Manager here is genuinely hands-on, I'm interested."

2 "Yes. I came in at Manager because that was the live requisition. If Senior Manager reopens, I'd want to understand what changes day to day before I say yes to the title."

"Would you be comfortable reporting to a Senior Manager with less experience than you?"

1 "Yes, and I have. The two people who most changed how I work this year were both younger than me. I care whether someone is good, not whether they are senior."

2 "Twelve years in consulting; the pyramid doesn't bother me. What I'd want is a manager who tells me plainly when the work isn't good enough."

"What are you earning now?"

1 "I'd rather talk expectations than history. For the Manager band, given twenty years and the FS regulatory depth, I'd expect the upper part of it: around two fifty base."

2 "New York doesn't let you ask that, and honestly it wouldn't help you: the roles aren't comparable. Where does a Manager with this profile land inside the one fifty-one to two sixty-two band?"

"The role is mostly embedded at one client."

1 "That's the model, and it's the part I want. How much of a forward deployed engineer's year goes back into reusable platform work, so the second client starts faster than the first?"

2 "Your UK release described FDEs as embedded in client delivery teams; I'm trying to understand how the US FSO version balances embedded time against platform time."

"There's no technical round for this level."

1 "Then I'll bring one. I'd like twenty minutes with whoever owns the architecture to screen-share the eval harness; it answers the hands-on question faster than I can."

2 "Understood. May I send a short architecture note with my follow-up instead? One page, the six layers and where the evidence trail lives."

"You were at US Bank while doing a full-time program? How did that work?"

1 "I made the case internally that applied AI was becoming central to my role, and my manager agreed. It was a combination of time off and remote work, arranged up front. Nothing informal about it."

2 "With my manager's approval. I argued that the bank's climate platform was going to need agentic tooling and that I should be the one who could build it. He gave me the room: some time off, some remote. I used it to ship."

"Why did you leave MUFG?" or "Why leave US Bank?"

1 "At MUFG I'd built the climate risk reporting function; US Bank offered the chance to build the platform itself. I'd leave US Bank for the same reason: the platform is built, validated and shared, and the next thing I want to build sits in many banks, not one."

2 "Each move has been toward building the thing rather than reporting on it. This is the next step in that line."

"What do you know about EY's AI work in financial services?"

1 "The Agentic Platform built with NVIDIA, the Microsoft commitment in May that names forward deployed engineers, your FS leaders' published view that governance is what makes agents deployable, and the three FDE levels posted last month. From the banking survey, the number that stuck is forty percent of use cases missing expectations."

2 "Enough to know the thesis: governance first, then autonomy. Sameer Gupta's point about fifteen versions of the same AI function inside one bank is the problem I've lived."

"You seem very prepared. Is this a bit rehearsed?"

1 "Prepared, yes. I read how EY says it hires and I'd rather respect your time than improvise. Ask me anything that isn't on the posting."

2 "I prepare for clients the same way. It's a habit from twelve years of being the consultant."

"Is there anything that would make you say no to an offer?"

1 "A seat with no real build time in it. I took the Manager level to be hands-on; if the job is coordinating other people who build, the trade stops making sense."

2 "A base near the floor of the band with no structure around it and no named promotion criteria. Otherwise I'm here to find the yes."

After each run

The recruiter's scorecard, and yours

The recruiter is scoring three things: clear, senior, closeable. Tick what you did; the rest is the next rehearsal.

Still to decide

Edits live only in this browser. Print to keep a copy.
Recruiter lines are plausible, not transcripts of real EY calls. Facts quoted match the feed as of 1 Nov 2026: NYC base bands $128–201K Senior, $150.7–261.6K Manager, $172.8–374K Senior Manager; SR 26-2 effective 17 Apr 2026; EY audits U.S. Bancorp and Anthropic.