The Recruiter Screen: The Complete Guide

What it is

The recruiter screen is the first conversation with a human being in a hiring process. It runs twenty to thirty minutes, usually by phone or a video call with cameras optional, and it is booked by somebody whose job is to decide whether you should meet anybody else at the company. It rejects more candidates than any other stage in the loop, and it is the stage almost nobody prepares for, because it does not feel like an interview. There is no whiteboard, no panel, no problem to solve. Somebody friendly asks about your background, mentions the role, asks what you are looking for, and thanks you for your time.

That framing is the reason the stage is dangerous. A candidate who has spent four weekends on system design and none on the twenty minutes that decide whether they get to use it has optimised the wrong part of the process. The screen is not a warm-up for the real assessment. It is a gate with its own criteria, and failing it produces exactly the same outcome as failing the technical loop, arrived at four weeks earlier and with less information about why.

What makes it hard to prepare for is that its criteria are not skills. Nobody is going to ask you to demonstrate anything. They are going to check a short list of facts about you against a short list of requirements they were given, form an impression of whether you can hold a conversation, and decide whether forwarding you to the hiring manager is a good use of that manager's time. Those checks are quick, they are largely binary, and several of them can end the call in the first ten minutes regardless of how good you are at the job.

The shape of the conversation is remarkably consistent across companies, industries and seniorities, and knowing the shape is half of the preparation.

flowchart TD
  accDescr: The shape of the screen from opening and rapport through the CV walkthrough, motivation and why this role, and logistics notice and location, to the salary alignment branch, where being outside the band ends the process there and being aligned moves on to your questions, the handover decision and being forwarded to the hiring manager.
  OPEN[Opening and rapport] --> CV[CV walkthrough]
  CV --> MOT[Motivation and why this role]
  MOT --> LOG[Logistics notice and location]
  LOG --> PAY{Salary alignment}
  PAY -->|outside the band| STOP[Process ends here]
  PAY -->|aligned| ASK[Your questions]
  ASK --> HAND[Handover decision]
  HAND --> FWD[Forwarded to the hiring manager]

Look at the branch that leaves the process entirely. Salary is the only node in that flow that can terminate the conversation on a single sentence, it is usually reached with ten minutes left, and it is the one thing on the list that neither party can fix later by trying harder. Everything else on the path is a conversation; that one is an arithmetic comparison against a number the recruiter already knows.

The gates, and what they are

There are six things a recruiter is genuinely checking, and it is worth being precise about them because the list is shorter and duller than candidates imagine. None of them is about how good an engineer, analyst or manager you are. All of them are about whether you are a viable candidate for this specific requisition, which is a different question and a much cheaper one to answer.

That you are real and that you are interested in this role rather than any role. A large fraction of applications are volume applications, and a recruiter working a shortlist can usually tell within four minutes whether you know what you applied to. This is not a test of enthusiasm. It is a test of specificity: whether you can name the role, connect one thing on your CV to one thing in the description, and give a reason for the application that is not "I am looking at opportunities".

Salary alignment against a band they already hold. They have a range. They know it before the call starts. Their job at this gate is to find out whether your expectation sits inside it, near it, or so far outside it that continuing wastes four people's time. This is the single most common reason a screen ends without a next stage, and it is the reason the salary section of this page is as long as it is.

Notice period and start date. Roles have dates attached. A requisition that needs somebody in six weeks and a candidate on a three-month notice period is a mismatch the recruiter has to surface now, not at offer, and there is very little either of you can do about it in the moment except state it accurately.

Location and work authorisation. How many days in the office, which office, whether you are within commuting distance, whether you need visa sponsorship and whether the company sponsors. These are yes-or-no facts. They are asked flatly, they are recorded flatly, and evasion on them is far more damaging than an inconvenient answer.

A career story that holds together. Not an impressive one. A coherent one. The recruiter is reading your CV while you speak and checking that what you say matches what is written, that the moves have reasons, and that there is nothing that will make the hiring manager ask a question the recruiter cannot answer. Gaps, short tenures and unexplained sideways moves surface here first, which is why explaining an employment gap or short tenure is a recruiter-screen skill before it is an interview skill.

Whether you can hold a conversation. This is the softest gate and the one candidates most underestimate. The recruiter is going to put their name on you. If you are hard to follow, defensive about a previous employer, unable to answer a direct question directly, or so terse that the call is work to conduct, they will hesitate, because the person they forward you to is somebody whose opinion of their judgement matters more than your CV does.

The pattern in that table is worth stating plainly. Almost every failure mode in the right-hand column is a failure of preparation or of directness, not a failure of capability. That is what makes the stage both frustrating and unusually winnable.

Who is on the other end

"Recruiter" covers at least four jobs with materially different incentives, and the differences change what you should tell them, how much they can answer, and how to read the pressure you feel. Working out which one you are speaking to takes one question at the start of the call and is worth the ten seconds.

An internal or in-house recruiter works for the company. They are salaried, they are measured on quality of hire and on the hiring manager's satisfaction as much as on volume, and their central constraint is the manager's time. Every candidate they forward who turns out to be a waste of an hour costs them credibility with a colleague they will work with for years. They will not push you towards an offer you do not want, because a decline after five stages is a bad outcome for them. They can usually tell you the band, the panel, the number of stages and why the role is open, and they are the recruiter most worth asking.

An agency or external recruiter is paid a fee when you start, typically a percentage of your first-year salary, and paid nothing otherwise. That single fact explains most of the behaviour candidates find frustrating and most of the behaviour they find helpful. It makes them motivated: they will chase the company for feedback in a way an internal recruiter will not, they will prepare you, and they will advocate. It also makes them push. A higher salary for you is a higher fee for them, which aligns your interests, but a placement at any salary beats no placement, which does not. They frequently do not know the panel, may be working from a job description rather than a conversation with the manager, and may be one of three agencies on the same role. Treat their information as second-hand unless they demonstrate otherwise, and be careful about giving permission to submit your CV to companies you have not named, because a duplicate submission can disqualify you from a process you were already in.

An embedded or RPO recruiter sits inside the company's process but is employed by a supplier. They use the company's systems, they attend the company's meetings, and to you the call feels internal. What differs is depth of context: they may have joined the account eight weeks ago and may be running roles across three teams. They will know the process and the band and are less likely to know why this particular team is hiring or what the manager cares about. It is a reasonable thing to ask about directly, and no reasonable embedded recruiter is offended by "how close are you to the team on this one".

An executive search consultant works on retained assignments at senior levels and is paid regardless of placement, in stages. Their incentive is to present a credible shortlist and to protect a long-term client relationship, which makes them the least transactional and the most probing. A search screen is longer, closer to a real interview, and will go into your commercial impact, your leadership record and your motivation in more depth than any other kind of screening call. They will also be far more careful with confidentiality in both directions, and are often the only recruiter who will genuinely discuss the politics of the role.

None of this makes any category the enemy. Most recruiters of every type are competent people running more requisitions than they would like, and a candidate who treats the call as an obstacle to be got past performs measurably worse than one who treats it as the first genuine conversation about the job. The reason to know the categories is not suspicion; it is that you get better answers when you ask the right person the right question.

Why we need it

The stage exists because of arithmetic. A moderately visible role attracts more applicants than anybody can interview, the ones who pass automated filtering are still more than a hiring manager can meet, and the manager's time is the scarcest resource in the entire process. Somebody has to convert a long list into a short one, and the cheapest reliable instrument for doing that is a short conversation that checks facts.

It also exists because a large proportion of hiring failures are not capability failures. They are mismatches on things nobody discussed early: a candidate who was never going to accept the salary, one who cannot start for five months, one who needs sponsorship the company does not offer, one who wanted a different job than the one advertised. Every one of those is discoverable in ten minutes and, when not discovered, is discovered instead after five rounds and a written offer. The screen is the cheapest place in the process to find out that this was never going to work, and finding that out is a service to both parties even when it does not feel like one.

There is a third reason, less often stated, which is that the recruiter is a filter on the hiring manager's experience of hiring. Managers who receive three well-matched candidates engage with the process. Managers who receive twelve random ones stop reading. The recruiter's professional standing inside the company rests on the hit rate of the people they forward, and that is the single most useful thing to understand about their behaviour. When a recruiter seems to be probing something that feels irrelevant to whether you can do the job, they are usually checking whether the hiring manager will ask them a question they cannot answer.

For the candidate, the stage has a value that is easy to miss while resenting it. It is the only conversation in the whole process where somebody is both willing and able to tell you the band, the number of stages, who is on the panel, why the role is open and how long it has been open. None of those questions will be answered as candidly by anybody you meet later. The recruiter is on your side in a narrow but real sense: they want you to succeed at the stages that follow, because your success is their result. That makes the screen the best-value information-gathering opportunity in the process, and most candidates spend it entirely on being assessed.

What is not being assessed, and why that matters

Nothing technical is being assessed. Not your architecture, not your algorithms, not the depth of your knowledge of the framework the job advert mentions. The recruiter is generally not qualified to assess it, is not asked to, and in most processes is explicitly instructed not to try.

This is the point at which a specific, expensive and extremely common mistake happens. A candidate is asked "tell me about your current role", hears an invitation to demonstrate expertise, and delivers six minutes on the event-driven architecture they built, the partitioning strategy, why they chose one message broker over another, and how they handled exactly-once semantics. It is accurate, it is impressive to the right audience, and to this audience it lands as a communication failure.

Understand what the recruiter experiences during those six minutes. They cannot evaluate any of it, so it provides no signal on the thing they can evaluate. They have a structured list of items to get through in twenty minutes and you have consumed a third of the call on the one topic they will not be reporting on. They are now wondering how you will handle a conversation with a non-technical stakeholder, because they have just been one. And when they write you up for the hiring manager, they will have three lines about a broker choice and nothing about your motivation, your availability or your expectation, which means the write-up is thin and the forward is weaker.

Depth to a recruiter is not a display of strength. It is a failure to read the room, performed at length, in the one round where reading the room is the assessment. The correct register is the one you would use with a smart colleague from a different department: what the system does, who it serves, roughly how big it is, what your part in it was, and why it mattered. Two or three sentences, in plain language, with the jargon stripped out. If they want more they will ask, and if they ask, they are almost always checking that a keyword on your CV corresponds to real experience rather than trying to evaluate the work.

The same logic applies to the questions the recruiter cannot answer. Asking a recruiter about the team's approach to trunk-based development, or how the platform handles multi-region failover, is not a mark against you but it is a wasted question, and you only get a few. Save those for the hiring manager, who will have them, and spend your recruiter questions on the things only a recruiter knows.

What the recruiter writes down

It is useful to picture the artefact this call produces, because it is what the hiring manager reads and it is much smaller than the conversation. In most applicant tracking systems the recruiter fills a short form: current role and company, relevant experience against two or three must-haves, salary expectation, notice period, location and work status, and a free-text summary running to roughly a paragraph. That paragraph is your entire representation to the person deciding whether to interview you.

Everything about how you should behave on the call follows from that. Your goal is not to impress; it is to make that paragraph easy to write and strong when written. A candidate who can be summarised in two sentences gets summarised well. A candidate who was interesting but rambling gets summarised as "seems capable, hard to pin down", which is not a recommendation. When you finish an answer, it is worth privately asking whether you have just handed over a sentence somebody could type, and the discipline of the ninety-second self-introduction in tell me about yourself is exactly this discipline applied to the opening question.

The CV walkthrough

"Walk me through your background" is the most common opener in the world and the most commonly botched answer in the entire process. It is asked in some form on nearly every screening call, it consumes the largest single block of the call, and it sets the frame through which everything afterwards is heard. Candidates who prepare for the technical loop and not for this have prepared for a stage they will not reach.

The reason it is botched is that it sounds like an invitation to talk about yourself, and it is not. It is a request for a structured summary aimed at a specific requisition, delivered in a length that leaves room for the rest of the agenda. Almost every failure is a failure of selection or of length rather than of content.

How long it should be

Two minutes. Ninety seconds if the recruiter sounds rushed or the call is fifteen minutes rather than thirty. Three minutes at the very outside for a twenty-year career with a genuine change of discipline in it, and even then the extra minute has to be earning something.

Two minutes feels short while you are speaking and is not. Read aloud at a normal pace it is around two hundred and fifty to three hundred words, which is enough for your current role, two or three prior moves with reasons, one concrete proof point, and a landing. What it is not enough for is every employer you have had, and that is the constraint doing the useful work.

The failure at the long end is more common and more damaging. A seven-minute walkthrough does four things at once: it eats the salary and logistics conversation, which then gets rushed and goes badly; it demonstrates that you cannot judge how much detail a listener needs; it forces the recruiter to interrupt you, which nobody enjoys doing; and it buries whatever was relevant under things that were not. Recruiters rarely stop you. They wait, they stop taking notes, and they mark you down for something they will never name.

The failure at the short end is real but rarer. "It is all on my CV, really" is heard as either disengagement or an unwillingness to sell yourself, and it hands the recruiter the job of interviewing you, which they will do less well than you would.

The shape

A good walkthrough is not a chronology. It is a short argument, and the argument is: here is what I do, here is how I came to be good at it, here is the piece of it that matches your role, and here is why I am talking to you.

flowchart LR
  accDescr: The walkthrough as a short argument rather than a chronology, running from where you are now, through two or three moves and their reasons, to the one thing closest to this role, why this role and why now, and handing back with a question.
  NOW[Where you are now] --> ROUTE[Two or three moves and their reasons]
  ROUTE --> PROOF[The one thing closest to this role]
  PROOF --> WHY[Why this role and why now]
  WHY --> BACK[Hand back with a question]

The interesting element is the last node, which almost nobody includes. Ending on a question hands the conversation back deliberately instead of trailing off, and it lets you check that you aimed at the right thing before the call moves on.

Take the elements in turn.

Start where you are now, not where you started. The single highest-leverage change most candidates can make is to invert the order. A recruiter's attention is highest in the first fifteen seconds and your most relevant experience is almost always your most recent. Opening with "I graduated in 2009 and joined a small consultancy" spends that attention on the least relevant thing you will say. Opening with "I am a backend engineer at a payments company, and for the last three years I have owned the settlement service" spends it on the thing the requisition is about.

Give two or three prior moves with reasons, not a list of employers. The reason is the content. "I moved from consultancy into product because I wanted to see what happened to things after they shipped" tells the recruiter something. "Then I was at Acme for two years, then at Beta for three" tells them what the CV already told them. Three reasons that form a consistent direction turn a work history into a career, and this is the same discipline that makes walk me through your career answerable at greater length in front of a hiring manager.

Land one concrete proof point, chosen for this role. One. Specific enough to be a real thing and short enough to fit in two sentences, and picked because it maps onto something in the job description. If the role emphasises scale, the proof point is about scale. If it emphasises working with regulators, the proof point is about that. The mapping is what makes the walkthrough feel tailored, and tailoring is largely what the recruiter is listening for.

End on why you are talking to them specifically. This is the part that is nearly always missing and the part that converts a decent answer into a strong one. It closes the loop between your history and their requisition, it pre-empts the "why this role" question by answering it before it is asked, and it gives the recruiter the sentence they need for their write-up. It has to be specific to this company or this role. "Because I am looking for a new challenge" is worse than saying nothing, because it advertises that you have not looked.

Why chronological narration fails

Chronology is the natural order and the wrong one, for a reason that has nothing to do with interest.

A chronological walkthrough allocates time by when things happened rather than by how much they matter. It gives your 2011 graduate scheme the same weight as the work you did last quarter, and it front-loads the least relevant material into the part of the call where the recruiter is most receptive. By the time you reach the thing that would have made them sit up, they have been listening for four minutes and have started skimming your CV instead.

It also has no argument in it. A chronology is a sequence of facts with an implied "and then", and an implied "and then" is not a reason. The recruiter is trying to establish whether your history points at this role, and a list does not point anywhere. When a hiring manager later asks the recruiter "why did you send me this one", the recruiter needs an answer, and a chronology does not supply one.

And it invites the wrong questions. Every employer you name is a hook, and a listener with a list of names in front of them tends to ask about the interesting-sounding one rather than the relevant one. Twelve minutes later you are discussing a company you left in 2015 because you mentioned it in passing.

The fix is not to hide your history. It is to compress the early part into a single clause and let the recent part breathe. "I started in consultancy and moved into product engineering about eight years ago" covers a decade in one line and buys you ninety seconds for the work that matters.

The two-minute version, in literal words

Here is a complete walkthrough for a senior backend engineer applying to a payments company. The point is the structure rather than the details, and the structure transfers to any discipline.

I am a senior backend engineer at Northgate, where I have been for four years. Day to day I own the settlement service, which is the thing that takes the day's transactions, reconciles them against what the banks say happened, and produces the files the finance team works from. It handles a few hundred thousand transactions a day and it is the system that has to be right, because when it is wrong somebody's money is in the wrong place.

The route there was fairly direct. I started in consultancy, mostly integration work, and moved into product engineering about eight years ago because I wanted to see what happened to things after they shipped rather than handing them over and leaving. I joined Northgate as a mid-level engineer on the core ledger and moved onto settlement when we took reconciliation back in-house from a vendor.

The piece I would point at for this role is that migration. We were on a third-party reconciliation product that could not handle a new scheme we were joining, and I led the work to replace it. About nine months, three engineers, running old and new side by side and comparing outputs daily until we trusted it enough to cut over. What I took from it was less about the code and more about how you retire something that finance depends on without anybody having a bad month-end.

Why I am talking to you: your advert says the team is bringing scheme integrations in-house over the next year, and that is very close to the work I have just finished, on the same side of the business. I am not unhappy at Northgate, but the settlement rebuild is done and the next twelve months there look like maintenance. Does that sound like the part of the role you are hiring for, or is the emphasis somewhere else?

Notice what that does. Two hundred and ninety words, roughly two minutes read aloud. It opens on the present. It explains a technical system in language a non-technical listener can repeat, with no broker names, no framework names and no architecture vocabulary. It compresses six years into one clause. It gives one proof point chosen to match the advert. It states a reason for leaving that is about the work rather than about a grievance. And it ends with a question that both hands back control and checks the aim.

Notice also what it does not do. It does not mention every employer. It does not quantify anything it cannot defend. It does not apologise for anything. And it does not go anywhere near how the reconciliation engine works, even though that is the most interesting part of the job, because the person listening cannot use it.

The thirty-second version

You need a second one. Some screens open with "give me the two-minute version", some with "just briefly, what do you do", and some recruiters are on a fifteen-minute call with four candidates that afternoon. Reading the room and delivering the short version when the short version was wanted is itself a positive signal.

I am a senior backend engineer at Northgate, working on payment settlement and reconciliation. For the last three years I have owned that service, including a nine-month project to replace a third-party reconciliation product with something we built, which is the closest thing on my CV to what your advert describes. I have been there four years, the rebuild is finished, and I am looking for the next version of that problem rather than maintaining this one.

Sixty-five words, about thirty seconds. It is the two-minute version with the reasons removed and the proof point compressed to one clause. Both versions end in the same place, which is the point of having them: whichever length you deliver, the last thing the recruiter hears is why you are on the call.

The technique for building the short one is to write the long one first and then delete every sentence that is not doing one of the four jobs. What remains is almost always the thirty-second version.

When the role is one you are lukewarm about

Most people in an active search are interested in about a third of the processes they are in, and interested in one of them a great deal. The problem is that a lukewarm walkthrough sounds lukewarm, recruiters hear it clearly, and "did not seem very engaged" is a note that ends processes you might later have wanted.

The answer is not to manufacture enthusiasm you do not have, which is worse: performed enthusiasm is transparent, it collapses under one follow-up question, and it commits you to a story you will have to keep telling. The answer is to find the true thing and lead with it, and there is always a true thing. The scale is bigger than where you are now. The domain is one you have wanted to move into. The stack matches what you want to do more of. The role is a level up, or has ownership you do not currently have, or is in a company whose product you have used. Any of those is honest, specific and sufficient.

Honestly, I am not in a rush to leave, so I am being fairly selective. What made me reply to this one is the ownership. Where I am, the settlement service is shared across two teams and every change is a negotiation. Your advert describes one team owning the whole flow, and that is the difference I am looking for. I do not know enough about the rest of it yet to say more than that, which is partly why I wanted the call.

That is a lukewarm candidate performing well. It is candid about the temperature, gives a real and specific reason, and openly treats the call as information gathering, which is exactly what it is. Recruiters respond well to it, partly because it is credible and partly because a selective candidate is a more attractive candidate. What it avoids is the version that kills processes: enthusiasm with no content behind it, followed by an inability to name a single thing about the company.

The one thing not to do with a lukewarm role is to let the temperature show as vagueness rather than as candour. "I am open to hearing about anything at the moment" is heard as a volume applicant, and volume applicants do not get forwarded.

The red flags the recruiter raises here

Gaps, short tenures, a redundancy, an unexplained sideways move: these surface at the screen more often than anywhere else, because the recruiter is reading the CV as you talk and their job is to make sure the hiring manager is not surprised. The full treatment of these belongs to career gaps, layoffs and short tenures, but two points are specific to this stage.

The first is that pre-empting inside the walkthrough is usually better than waiting to be asked. A gap addressed in one clause as you pass it — "I took eight months out in 2023 for a family situation, and came back into the same kind of work" — is a fact. The same gap raised by the recruiter after you have narrated around it is a question, and questions get written down. The cost of pre-empting is one sentence; the cost of being asked is that the topic now has weight.

The second is that the recruiter is not the person who will judge it. They are the person who has to be able to answer it on your behalf. That reframes what a good answer looks like: you are giving them a line they can repeat, not making a case. Short, factual, unapologetic, and finished. The same applies to the awkward version of experience mismatch, where the advert asks for more years than you have and the honest answer is a reframe rather than a defence, which is the argument in the role wants five years and you barely have it.

The salary conversation

This is the other centre of the call and the one with the most at stake per sentence. It usually arrives with five to ten minutes left, it is often introduced apologetically, and the answer you give will be written into a field in a system and carried through the entire process. It is worth thinking about properly in advance, because there is no version of this conversation you can improvise well.

Why they ask, and what they do with the answer

They ask early for a reason that is genuinely legitimate: the band exists, it is usually not very flexible, and a candidate whose expectation is well outside it will decline the offer after everybody has spent six hours interviewing them. Finding that out at the start is the correct thing to do and is in your interest too, since your time is the thing being spent as well.

What happens to the number is more consequential than the asking. It is recorded. It travels with your file. It is visible to the hiring manager and, at offer time, it is visible to whoever approves the offer. In many processes the offer is constructed from the intersection of the band, the level you interviewed at, and the number you gave at the screen, and that third input is doing real work. A number given carelessly in minute eighteen of a twenty-minute call can quietly become the ceiling of an offer made two months later.

That is why the strategic goal at this stage is narrow: stay in the process, avoid setting a ceiling below what the role would have paid, and, if possible, extract the band. It is not to negotiate. Negotiation happens when there is an offer and leverage; at the screen you have neither, and behaving as though you do reads badly.

Current salary against expectation

These are two different questions and they deserve different treatment.

Your expectation is a forward-looking statement about what it would take for you to move. It is legitimate for them to ask, it is your own judgement, and it is answerable.

Your current salary is a fact about a different employment relationship with a different scope, a different location and a different set of circumstances. Its only use in the conversation is as an anchor to price you against your past rather than against the role. Asking for it is restricted in some jurisdictions and discouraged by policy at many companies that operate across several; the shape of those rules is that employers may not require disclosure of pay history and must sometimes disclose the range for the role instead. Whether any of that applies to your call depends entirely on where you and the employer are, and it varies, so the practical stance is not to argue law but simply to redirect. Most recruiters will accept the redirect immediately, because many of them are not permitted to press.

I would rather talk about what I am looking for than what I am on now, if that is all right. My current salary reflects a role I took four years ago at a different scope, so it is not a great guide to either of us. For this role I am looking at something in the region of eighty-five to ninety-five.

That handles both questions in one move: it declines the backward-looking one with a reason that is about relevance rather than about rights, and it immediately supplies the forward-looking one so the redirect does not read as obstruction.

The path through the conversation

flowchart TD
  accDescr: The salary exchange, deflecting once and asking for the band, then either being given the band and judging whether it fits, confirming and moving on if it does and saying so now rather than at offer if it does not, or being pressed again and giving a researched range anchored on the market rather than on current pay.
  ASK[Recruiter asks expectations] --> DEF[Deflect once and ask for the band]
  DEF -->|band given| FIT{Does the band fit}
  DEF -->|pressed again| RANGE[Give a researched range]
  FIT -->|yes| CONF[Confirm and move on]
  FIT -->|no| SAY[Say so now rather than at offer]
  RANGE --> ANCH[Anchor on market not on current pay]
  ANCH --> CONF

The node worth dwelling on is the deflect, because it is exactly one move long. Deflecting once is professional; deflecting twice is evasive, and the second refusal costs more goodwill than the number would have cost you.

Deflecting once, gracefully

The first ask is the one to answer with a question, and the way to do it without friction is to give a reason and to make it easy for them to say yes.

Before I give you a number, is there a range budgeted for the role? I ask because levels vary a lot between companies and I would rather calibrate against your band than guess at it. If it helps, I am not going to be difficult about this — I just do not want either of us to find out in six weeks that we were a long way apart.

That does four things. It asks the question directly rather than hinting. It gives a reason that is about accuracy rather than about tactics. It signals cooperativeness explicitly, which removes the main risk of the deflect, which is being read as adversarial. And it frames the shared interest, which is true and which most recruiters recognise immediately.

In an increasing number of processes the answer is simply the range, either because the company publishes it or because the recruiter has been told to lead with it. When you get it, the conversation is almost over: confirm that it works, or say clearly that it does not.

When they press a second time

Some recruiters cannot give the band, some are instructed to obtain a number first, and some will simply repeat the question. When the question comes back, answer it. The cost of a second deflection is out of proportion to what you gain.

That is fair. Based on what I have seen for comparable roles at this level and in this market, I am looking at eighty-five to ninety-five thousand, and where I land in that depends on the rest of the package and the level. If your band is different from that, tell me now and we can work out whether it is worth continuing — I would rather know.

The construction matters. It gives a range rather than a point. It attaches the range to the market and to the level rather than to your current pay. It makes the top of the range conditional on things not yet known, which keeps the door open. And it closes by inviting the correction, which converts your number from a demand into a proposal and very often prompts the recruiter to tell you the band after all.

Giving a range that does not cap you

Ranges are conventional and are read in a specific way that candidates often do not expect: the bottom of your range is the number that gets recorded. Recruiters hear "eighty to ninety-five" and write eighty, because eighty is the figure at which you said you would move. Assume this and construct accordingly.

Three rules follow. Put your genuine target at or near the bottom of the range, not in the middle. Keep the range narrow, roughly ten to fifteen per cent wide, because a range spanning thirty per cent reads as not knowing your own value and invites the lowest number in it. And attach the top of the range to something concrete, so that it is a condition rather than a wish.

Eighty-eight to ninety-five on base. Eighty-eight is where it makes sense to move for the scope as I understand it; the upper end would be if the role turns out to be the senior level with the on-call rotation, or if the bonus is discretionary rather than guaranteed.

That is a range with a mechanism inside it. It gives the recruiter a usable number, it explains what would move it, and it means that discovering the role is a level higher than you thought does not require you to reopen a number you have already given.

Two ancillary points. Be explicit about whether you are quoting base or total, because a recruiter who assumes one while you mean the other produces an offer that disappoints everybody. And if a substantial part of your current package is equity, bonus or allowances, say so as part of the same sentence rather than raising it later, since a base-only comparison will otherwise make your expectation look like a large jump.

When you genuinely do not know the market rate

This is a common and uncomfortable position, particularly for people who have not changed employers in several years, who are moving country, who are moving discipline, or who are early enough in their career to have no reference points. Guessing badly in either direction is costly: too high can end the call, and too low sets a ceiling you will never recover in that process.

The honest version is a legitimate answer and works better than most candidates expect.

I will be straight with you: I have been at the same company for six years, so my sense of the current market is not good. I would rather not pull a number out of the air and have it follow me around. What I can tell you is my current package and what would make the move worthwhile in principle, and if you can tell me the band we can check quickly whether this is realistic. I am not trying to be cagey — I genuinely do not want to misprice this in either direction.

That is candid, it is disarming, and in practice it produces the band more often than any tactical approach does, because the recruiter now has a reason to supply it that is about getting a usable answer rather than about conceding ground.

Before the call, do the twenty minutes of work that makes this unnecessary. Look at how the same role is advertised elsewhere in the same city, particularly where ranges are published. Ask two people who do your job at a similar level, phrased as a range for the role rather than as what they earn. And check whether the company publishes bands or whether the advert itself has one, since a surprising number do and candidates do not look.

Asking for the band, and what the answer tells you

Asking is normal, it is increasingly expected, and it is now the default in a growing number of markets. Ask once, ask plainly, and pay close attention to the answer, because the answer is diagnostic well beyond the number.

A specific range — "the band for this level is eighty-two to ninety-six, and we usually offer in the middle unless somebody comes in above the bar" — is a good sign in three ways. It tells you the number, it tells you the company has levels with defined bands, and it tells you the recruiter is trusted with them.

A range with a caveat — "the band goes to ninety-five but I should say we have not gone above ninety on this team" — is more useful still, because it is the real ceiling rather than the theoretical one, and a recruiter who volunteers it is being straight with you.

A vague answer is the one to read carefully. "It is competitive", "it depends on experience", "we benchmark against market" and "I would need to check with the hiring manager" are all non-answers, and they usually mean one of four things. The band is genuinely wide because the level has not been settled, which means the level will be decided by how you interview and you should ask what the levels are. The recruiter does not have it, which is common with agency and newer embedded recruiters and is worth establishing directly. The company's policy is to obtain your number first, which tells you something about how the offer conversation will go. Or the band is below what the role should pay and disclosing it early loses candidates, which is the least charitable reading and the one that becomes visible if the vagueness persists after you have given your number.

The follow-up that resolves most of this is simple and low-friction: "That is fine — can you tell me whether eighty-eight to ninety-five is in the right area, without giving me the exact band?" Almost anybody will answer that, because it asks for a direction rather than a figure.

When you must give a number first

Sometimes there is no way round it. The application form had a mandatory field, the recruiter opens with the question and will not proceed, or the process genuinely requires a figure before a conversation. This is the hard case, and the technique is to make the number conditional and reversible rather than to refuse.

If you need a figure to put in the system, put ninety. I want to flag that it is a working number rather than a final one, because I do not yet know the level, what the bonus structure is, or how the on-call is compensated, and any of those could move it. I am telling you that now rather than surprising you later.

Three things are happening there. You have supplied the number, so the process continues and you have not been difficult. You have stated the conditions under which it changes, which is what preserves your position later: revisiting a number you explicitly flagged as provisional is a continuation, whereas revisiting a number you gave flatly is a renegotiation. And you have signalled good faith by pre-announcing the possibility, which is precisely how the later conversation is kept clean if the written offer comes in under what you expected, the situation dissected in the written offer is below the number you gave.

For the mandatory application field, the same principle applies in fewer words. Put a real number rather than zero or a placeholder, since placeholders get filtered, and raise the conditionality at the first live conversation.

The row worth reading twice is the one where the band is below your floor. Ending a process at the screen because the money does not work is a success of the stage, not a failure of yours, and how you end it matters. A candidate who says "that is below what I can move for, but thank you for being straight with me — if something at the next level up comes through, I would be glad to hear about it" is a candidate the recruiter calls again. Recruiters keep long memories and short lists, and the second call from the same recruiter is frequently the better role.

Notice, availability and where else you are

The logistics block is short, feels administrative, and contains two questions that are more consequential than they sound.

Notice period should be answered exactly, in weeks or months, with any nuance attached in the same breath. "Three months, though my contract allows it to be shortened by agreement and my manager has been reasonable with others" is a better answer than "three months" because it tells the recruiter what to write for a role with a date on it. If you are on gardening leave, between roles, or on a fixed-term contract with a known end date, say the actual date. Vagueness on notice is read as either not knowing your own contract or hedging, and both are avoidable. The wider question of when to raise relocation and remote expectations alongside it is treated in when to raise notice period, relocation and remote expectations.

Start date follows from notice but is not identical to it. If you have a holiday booked, a handover you have committed to, or a bonus vesting on a known date, mention it now in one clause rather than at offer stage. Nobody minds a two-week gap declared in advance; everybody minds one discovered during contract preparation.

Location and office pattern should be answered with your genuine constraint stated once, clearly, and without either apology or negotiation. If the role is three days in an office ninety minutes away and that will not work, saying so at the screen is the correct time. Agreeing on the call and renegotiating after the offer is the single most reliable way to burn a relationship with a company you had just persuaded to hire you.

Work authorisation is a factual question with a factual answer. State your status, state what you would need, and if you are unsure of the detail, say what you know and offer to confirm. This is not a question to be clever about; discovering a sponsorship requirement late is one of the few things that can unwind a signed offer.

Competing processes, and how honest to be

"Are you interviewing anywhere else?" is asked on most screens and answered badly on most screens. Two instincts pull in opposite directions: the fear that admitting to other processes makes you look uncommitted, and the belief that claiming other processes creates urgency.

The honest middle is both true and strategically correct. Say that you are in other processes, do not name the companies, and give the stage in general terms. That answer tells the recruiter you are a live candidate in a market that agrees with their assessment, which raises rather than lowers your standing, and it gives them a real timeline to work with, which is genuinely useful to them.

I am, yes. Two other processes, both at a similar kind of company, and one of them is fairly advanced — I would expect to know where it lands in about three weeks. I am not trying to create a deadline, but you asked and that is where things are. Nothing is signed and nothing is decided.

What to avoid at both extremes. Inventing a competing offer is a bad idea, not because it is caught often but because it commits you to a timeline you then have to manage, and because a recruiter who accelerates a process on the strength of a fiction will remember when it evaporates. And naming the companies costs you information for nothing: recruiters talk to each other more than candidates assume, and there is no benefit to you in the disclosure. "Similar companies, similar roles" is complete enough. The fuller treatment of the question and its follow-ups is in are you interviewing elsewhere.

One nuance for agency recruiters specifically: they will ask where else you have been submitted, and here the honesty is operationally necessary rather than tactical. If another agency has already put you forward to the same client, a second submission creates an ownership dispute that can remove you from consideration entirely. Keep a list of where you have been submitted and by whom, and say so.

The questions worth asking

The recruiter can answer things nobody else in the process will, and the window closes after this call. Hiring managers will not discuss the band. Panel interviewers do not know how long the role has been open. Nobody in a later round is going to tell you there is an internal candidate. Six questions carry most of the value, and they take four minutes in total.

The band is covered above. Ask it, and if it is not forthcoming, ask for a direction rather than a number.

How many stages, over what period. This is the question that lets you plan and the one that most often produces a surprise. Four stages sounds fine until it is four stages plus a take-home plus a final with a director, spread over seven weeks. Ask for the count, the formats and the expected elapsed time, and ask whether any of them is a take-home, because that changes the arithmetic considerably — the trade-off in accepting one is the subject of take-home assignments and case studies, and the fatigue arithmetic of a long loop belongs to surviving a multi-stage interview process.

Who is on the panel and what each will focus on. This is the highest-value preparation question available anywhere in the process, and recruiters answer it readily because answering it makes their candidates perform better. Names let you read what those people work on. Focus areas tell you what to prepare. And a recruiter who can tell you that the second interviewer always goes deep on testing has handed you an hour of targeted preparation for free.

Why is the role open. Three answers with three different meanings. Growth means a new headcount and usually an optimistic, slightly undefined role where you will have room and less structure. Backfill means somebody left, and the useful follow-up is where they went and whether it was internal, because a series of internal transfers out of one team is informative. A new function or a problem to fix means you are being hired to change something, which is often the most interesting version and the one where you most need to know who wanted it and who did not.

How long has it been open. A role open two weeks is a fresh requisition. A role open five months has a reason, and there are only a few: the band is below the market for the requirement, the bar is unclear so offers are not being made, the specification is unrealistic, or something about the team is putting people off at the final stage. Asking the follow-up gently — "what has been the sticking point?" — produces a genuinely useful answer surprisingly often.

Is there an internal candidate. Uncomfortable to ask and worth asking, in a form that makes it easy to answer. "Is there anyone internal in the running for this?" is neutral and factual. Some processes run an external slate for governance reasons while an internal appointment is expected, and knowing that changes how much of your life you spend on it. Most recruiters will tell you, because most of them dislike wasting your time as much as you dislike having it wasted.

Two more worth adding when the answers to the above are good. What does success look like in the first six months, which the recruiter will have from the manager and which is the closest thing to a real job description you will get. And what the last person who was hired into this team did well in the interviews, which is a question about their bar phrased as a question about somebody else, and which recruiters answer far more freely than the direct version.

Reading the answers

The content of the answers matters. So does their texture, and the texture is often the more reliable signal.

Precision is the strongest positive. A recruiter who names the band, names the four panel members and their focus areas, says the role has been open three weeks and explains that it is a backfill for somebody who moved to the platform team is describing an organised process run by somebody with access. Everything about that call is more likely to be true, including the timelines.

Vagueness about the band most often means one of the four things listed earlier, and the way to distinguish them is what happens after you give your own number. A recruiter who could not give the band but immediately confirms that your range is in the right area was constrained by policy. One who stays vague after you have gone first is either uninformed or managing you, and in both cases you should assume the offer conversation will be harder than average.

Vagueness about the process — not knowing how many stages there are, or how long they take — is a stronger negative signal than vagueness about money, because it usually means the loop has not been designed. Processes that are improvised as they go are the ones that add a stage after you thought you were finished, go quiet for three weeks, and produce inconsistent feedback because the interviewers were never told what each was assessing.

Enthusiasm without specifics is worth noticing. A recruiter who is warm and complimentary but cannot say what the team does, why the role exists or who you would meet has not spoken to the hiring manager. That does not mean the role is bad; it means their information is thin, and you should discount their reassurances accordingly and get your questions answered by the manager.

Speed of response afterwards is the final tell and the most predictive of all. A process that comes back within the window they promised is a process where the manager is engaged and hiring is a priority. One that goes quiet for two weeks after an enthusiastic call is a process where something is competing with it, and that something will keep competing with it right up to the offer.

When the screening call is the hiring manager

A meaningful minority of first calls are with the hiring manager rather than a recruiter, either because the company is small enough not to have a recruiting function, because the manager prefers to screen their own pipeline, or because you arrived through a referral or a direct approach. The invitation frequently does not say which, and the difference changes almost everything about how the conversation should go.

Establish which it is in the first minute. It is usually obvious from the introduction, and if it is not, "before we start — are you on the team, or are you on the recruiting side?" is a perfectly normal question that nobody minds.

Four things change when it is the manager.

Depth becomes appropriate. The register that fails with a recruiter is the register the manager wants. They can evaluate technical content, they are interested in it, and the conversation will go there. You should still not open with it — the walkthrough is still a walkthrough — but when they ask how the reconciliation worked, they want the real answer, and the two-sentence non-technical version now reads as evasive or thin.

It is a real interview even when it is called a chat. Managers form views quickly and those views are hard to reverse later in the loop. A conversation described as informal is still producing an assessment, and the fact that it was described as informal is the reason candidates underprepare for it.

The salary conversation is different in kind. The manager may not know the band precisely and may be less constrained by policy about discussing it, but they are also the person who will approve the offer. A number given to the manager is given to the decision maker rather than to an intermediary, which makes both the deflection and the conditionality more important, not less. The graceful ask still works and is often answered more candidly.

Your questions should change entirely. You now have the person who can tell you what the first six months looks like, what the team is struggling with, how decisions get made, how they handle disagreement, and what happened to the last person in the role. Spend the question time on those and not on process mechanics, which is the one place where a manager conversation is less informative than a recruiter one.

There is a hybrid worth naming: the call that begins with a recruiter and has the manager join halfway. The register has to shift mid-call, and the shift is itself observed. The safe approach is to keep the plain-language framing for anything the recruiter needs to be able to repeat, and to go deep only in direct response to a technical question.

Following up, and being ghosted

The call ends, you are told you will hear back, and then the process either moves or it does not. Handling the aftermath well is a small skill that costs nothing and occasionally recovers a process that had stalled for reasons unrelated to you.

flowchart LR
  accDescr: The aftermath of the screen, a short note the same day, waiting the stated window, then one nudge, which either brings a reply and a booked next stage or leads to a second nudge a week later and then closing the loop and stopping.
  CALL[Screen ends] --> NOTE[Short note the same day]
  NOTE --> WAIT[Wait the stated window]
  WAIT --> N1[One nudge after the window]
  N1 -->|reply| NEXT[Next stage booked]
  N1 --> N2[Second nudge a week later]
  N2 --> CLOSE[Close the loop and stop]

The branch that matters is the one that stops. Two nudges is the whole budget, and the value of a third is negative.

The note on the day

Short, sent within a few hours, and doing one job that thank-you notes usually do not: reinforcing the sentence you want in the write-up.

Thanks for the call — useful, and the scheme integration work sounds like the closest thing to what I have just spent a year on, so I am keen. As discussed, three months' notice, potentially shorter by agreement, and I am comfortable with the two days in the office.

Anything you need from me before you speak to Marcus, just say.

Four sentences. It restates the fit in the recruiter's own words, it repeats the two logistics facts they will need for their form, and it offers to help rather than asking for anything. It is also short enough to be forwarded, which is the ideal outcome.

Waiting, and the two nudges

Ask before the call ends when you should expect to hear and by what channel. That single question converts the entire waiting period from anxiety into arithmetic, because you now have a date and can stop refreshing your inbox before it.

Wait the stated window plus a couple of working days, then send the first nudge. If no window was given, a week to ten working days is the norm for a screen. Keep it brief, keep it warm, and give a reason to reply.

Hello Sarah — following up on our call on the fourth. Is there any news on whether it is going forward to the next stage? No rush if things are still moving; it would just help me plan, as I have another process running to a timeline.

The mention of another process is honest if it is true and gives the recruiter something to act on internally. It should never be an ultimatum.

If that gets nothing, send one more a week later, and make it a closing message rather than a chase.

Hello Sarah — one last note from me on this one. If it has not gone forward, that is absolutely fine and I would rather know than wonder. If it has and things are just slow, I am still interested. Either way, thanks for the conversation, and do keep me in mind if something else comes up that fits.

That message works because it makes silence an acceptable answer, which paradoxically increases the reply rate, and because it leaves the relationship intact. Recruiters change companies frequently and remember the candidates who were easy to deal with when things went wrong.

Then stop. A third and fourth message convert a neutral non-outcome into a memorable negative one, and the reasons for the silence are usually structural rather than about you: the role was paused, the requisition was moved to another team, the manager went on leave, an internal candidate emerged, the recruiter left. None of those is fixable by another email, and none of them is feedback about your performance. The wider question of what to do with a process that ends in silence, and how to diagnose yourself when there is nothing to go on, is the subject of interview rejection and self-diagnosis.

One thing worth doing when you stop: write down what happened while you remember it. Which recruiter, which company, what the band was, what the process was, what you said your expectation was. Six months later, when the same recruiter calls about a different role, that record is worth a great deal — and reusing your own number from a previous process without remembering it is one of the easier ways to undercut yourself.

What interviewers ask

Recruiter-screen questions differ in kind from panel questions, and the difference is worth naming because it changes how you should answer. A panel question is usually an invitation to demonstrate something: reasoning, depth, judgement under pressure. A screen question is usually a check against a field. It has a right length, a right register, and frequently a right answer that is simply the true one stated plainly.

That is why the answers in the next section are shorter and flatter than they would be in a technical round. Elaboration is not rewarded here; precision, brevity and directness are. The most common way to fail a screen question is not to give a wrong answer but to give a four-minute answer to a fifteen-second question.

There is one cross-cutting signal that appears in every screen and is never written on a form: whether the recruiter finishes the call believing they can predict what you will do. Predictability sounds like faint praise and is in fact the highest compliment at this stage. A candidate whose expectation is clear, whose notice is known, whose motivation is specific and whose answers do not shift is a candidate a recruiter can confidently place in front of a colleague. A candidate who was impressive but ambiguous on three of those four is a risk, and risks get held back in favour of the ones the recruiter can describe in a sentence.

Questions

These are phrased the way recruiters put them. The answers name the signal being read, because on this stage what the question appears to be about and what it is checking are frequently different.

Tell me a bit about yourself.

Give the two-minute walkthrough: where you are now and what you own, two or three moves with reasons, one proof point chosen for this role, and why you are talking to them. Then stop and hand back with a question — "does that line up with what you are hiring for, or is the emphasis elsewhere?"

Three things are graded. Length, because a two-minute answer where four minutes were available leaves room for their agenda and a six-minute answer eats it. Selection, because what you leave out shows what you think matters. And whether you land somewhere, since an answer that trails off into "and yeah, that is me" leaves the recruiter to work out the relevance themselves, and under time pressure they will not.

Walk me through your CV.

Treat this as the same question with one addition: they are reading the document while you speak, so the narration has to match what is on the page. Follow the same shape, and as you pass anything on the CV that would prompt a question — a gap, a nine-month tenure, a job title that does not describe what you did — address it in one clause and keep moving.

What is being checked here that is not checked by "tell me about yourself" is consistency between your account and the document. A discrepancy in dates, a role you describe as leading a team that the CV lists as an individual contributor, or an employer you skip entirely will all be noticed, because the CV is open in front of them. None of those is fatal when explained; all of them are damaging when discovered.

In one sentence, what do you do?

Answer in one sentence, in plain language, with no jargon. "I build and run the systems that reconcile payments at the end of each day and make sure the money that moved matches what everyone says moved."

This is a compression test and a register test at once. Recruiters ask it when they need something to type or when a previous answer was too long, and the ability to produce a single clean sentence is read as clarity of thought. Answering with a job title, or with a sentence containing three pieces of technical vocabulary, both fail — the first because it says nothing and the second because it demonstrates you cannot adjust for the listener.

Why are you looking to leave your current role?

Give a reason about the work, forward-looking, and finish it. "The settlement rebuild I was hired to lead is done, and the next year there is maintenance and incremental change. I would rather be building the next one than looking after this one."

What is graded is whether the reason is about what you are moving towards rather than what you are escaping, and whether you can say it without criticising anybody. A candidate who talks about a difficult manager has given the recruiter a risk to write down, even when the difficulty was real, because the recruiter cannot verify it and the hiring manager will hear a pattern. Keep it short: a long answer to this question sounds like justification. The fuller version, and how it pairs with the "why this company" half, is worked through in why this company and why are you leaving.

Why this company?

Name something specific and true, and connect it to your own history. "Two things. The advert says the team is taking scheme integrations in-house this year, and that is the work I have just finished elsewhere. And you are at a size where I would still be close to the product, which is what I lost when my last company grew."

The signal is whether you have read anything, and the bar is lower than candidates fear: one specific, accurate observation clears it. What fails is the generic answer, and it fails hard, because a recruiter hears twenty of them a week and the phrase "great culture and exciting products" is functionally identical to saying nothing. If you genuinely do not know much about them yet, say that and give the one thing that made you reply — candour beats a hollow answer every time.

What do you know about us?

Give a short, accurate summary and then declare the edge of your knowledge. "You process payments for mid-market retailers, you have been going about eight years, and I know you moved into the European market recently because it was in the news. I do not know much about how the engineering side is organised, which is one of the things I wanted to ask."

Two things are read: whether you did fifteen minutes of preparation, and whether you overclaim. Confidently stating something inaccurate about the company is worse than knowing little, because it is checkable in real time. Naming the boundary of what you know and converting it into a question turns a weak position into a good one.

What are you looking for in your next role?

Answer with two or three concrete things rather than adjectives, and make at least one of them checkable against this role. "Ownership of a service end to end rather than shared across teams. A domain with real constraints — payments, or something with the same seriousness. And a team small enough that I know what everyone is working on."

This is graded on whether your answer describes a job or a mood. "Growth, challenge and a good culture" is a mood and tells the recruiter nothing about whether this requisition fits. It is also, quietly, a fit check in the other direction: if what you describe is not what the role offers, a good recruiter will tell you now, which is a service. Where you want to be in the longer term is a related but separate question, treated in where do you see yourself in five years.

What are your salary expectations?

Deflect once with a reason and an offer to cooperate: "Is there a band budgeted? I would rather calibrate to your range than guess, and I am not going to be awkward about it." If they give the band, confirm whether it works. If they press, give a narrow researched range with your target at the bottom, anchored to the market and the level rather than to your current pay, and invite the correction.

What is graded is not the number but the handling. Recruiters are reading whether you can be asked a direct financial question without becoming either evasive or aggressive, because the same trait will show up at offer stage and in your dealings with the business afterwards. The two failures are a flat refusal to engage, which reads as difficult, and a number blurted out with no basis, which reads as unprepared and sets a ceiling. The tactical detail behind all of this is in what are your salary expectations.

What are you on at the moment?

Redirect once, with a reason about relevance rather than about rights, and supply the forward-looking number in the same breath so the redirect does not read as obstruction. "I would rather talk about what I am looking for — my current number reflects a role I took four years ago at a different scope. For this one I am looking at eighty-eight to ninety-five."

Almost every recruiter accepts this without a second attempt, and a number of them are not permitted to press. The signal being read is whether you can decline a question gracefully. Refusing with a lecture about pay-history rules is technically defensible and lands poorly, because the recruiter asking is usually following a script rather than making a decision. If they press anyway and you judge the process worth continuing, giving the figure with context attached — what it excludes, when it was set — is a reasonable choice, not a defeat.

That is above the band for this role. How flexible are you?

Answer with a real position rather than either collapsing or refusing. "How far above? If it is a few thousand, that is a conversation and the rest of the package matters. If it is fifteen or twenty per cent, then honestly it probably does not work, and I would rather say that now than take up four people's afternoons. Is the level fixed, or is there a version of this at the next grade?"

The graded content is whether you hold a position without becoming rigid, and whether you can talk about money without discomfort. Instantly dropping to their number tells them the first figure was invented and that the offer can be set anywhere. Refusing to move at all, before you know anything about the role or the package, reads as inflexible. The question about the level is the strongest element, because it is frequently the actual solution: bands are attached to levels, and levels are more negotiable than the bands inside them.

What is your notice period?

Say the exact figure and add the nuance in the same sentence. "Three months contractually. It can be shortened by agreement and my manager has let people go earlier before, so realistically eight to ten weeks, but I would not want you to plan on it."

Precision is the whole answer. What is being read is whether you know your own contract and whether you distinguish what you can promise from what you hope. A candidate who says "three months, but I can probably get out in four weeks" and then cannot has created a problem for a start date somebody is planning around. Understating notice to seem more available is a bad trade: it is discovered immediately and it converts a scheduling constraint into a credibility question.

When could you realistically start?

Work forwards from the offer rather than from today, and declare anything that would delay it. "If an offer landed at the end of next month, three months' notice takes me to early December. I have a week booked in October which is inside the notice period, so it does not move anything. Nothing else in the way."

The signal is whether you can think about a date practically and whether you volunteer complications. Holidays, a bonus payment date, a handover you have committed to, a visa timeline: all of these are neutral facts declared now and awkward surprises declared later. Recruiters plan against these dates and pass them to the manager, so an answer that shifts twice in one process is remembered.

Are you interviewing anywhere else?

Be honest, be unspecific about names, and give a real timeline. "Yes — two other processes at similar companies, one of them fairly advanced. I would expect that one to resolve in about three weeks. Nothing signed, nothing decided."

Being in other processes is a positive signal rather than a negative one: it means the market agrees you are hireable, and it gives the recruiter a genuine reason to move. What is graded is whether you are straight about it and whether you inflate. Claiming an offer you do not have is the main failure, because it forces a timeline you cannot control, and because if the process accelerates and the offer never appears, the whole account collapses at the point where you most need credibility.

Where are you in those processes, and would you take one of them?

Give the stage without the name, and answer the second half honestly rather than protectively. "One is at final stage, the other has had a first call. Would I take the first one? Probably, if the offer is right, but it is a bigger company and I am less sure about the ownership question, which is the thing I am here to ask you about."

This is a stronger question than it looks because it tests whether your stated priorities survive contact with a real alternative. A candidate who says the ownership matters and then admits they would take a role without it has revealed the priority was decoration. Consistency between what you say you want and how you rank actual options is the signal, and it is read carefully. Whether you would stay if your current employer matched is a variant of the same test, and it is dissected in if your employer matched the offer, would you stay.

The role is three days a week in the office. Does that work for you?

Answer once, clearly, and do not negotiate. Either "yes, that is fine, I am forty minutes away" or "three is more than I want to commit to. Two would work well. Is there any flexibility, or is three firm?"

What is being checked is whether your answer now will be your answer at offer stage. The expensive failure is agreeing on the call while privately intending to renegotiate, because the renegotiation arrives after the company has chosen you and reads as a bait and switch, which damages a relationship you would then have to work inside. Raising the constraint at the screen costs you a small number of processes and protects every other one.

Do you have the right to work here, or would you need sponsorship?

State the position factually and completely, including any timing that matters. "I am on a visa tied to my current employer, so I would need the new employer to sponsor a transfer. I have done it before and it took about six weeks. Happy to send the details of exactly what is involved."

This is pure fact-checking and there is nothing to gain from managing it. Offering to supply the detail is the strong move, because recruiters frequently do not know the mechanics and a candidate who makes it easy is a candidate whose case is easier to argue internally. Evasion here is uniquely damaging: it is the one topic where a late discovery can unwind an offer that has already been made.

I see a gap here between these two roles — what happened?

State it in one or two sentences, factually, and finish. "I was made redundant in March 2023 when the team was cut, and I took four months before starting the search properly because my father was ill. I came back into the same kind of work in the August."

Graded on whether it is a fact or a defence. Length is the tell: a two-sentence answer sounds like something that happened, and a two-minute answer sounds like something that needs explaining. The recruiter is not judging the gap; they are checking that they can answer the manager's question about it, so give them a line they can repeat. Volunteering it before it is asked, inside the walkthrough, is better still. The longer treatment, including layoffs and short tenures, is in career gaps, layoffs and short tenures and in there is a year gap on your CV.

You have had three roles in four years. What is going on there?

Give the reason for each in a clause and then say what makes this one different, without protesting too much. "The first was a fixed-term contract that ended. The second, the company was acquired and my team was closed nine months in. The third I chose, and I have been there two years. So one ending, one closure and one decision — but I understand how the pattern reads, and what I am looking for now is somewhere I can stay through a full cycle of building and running something."

The signal is whether the pattern has an explanation that a manager would find rational, and whether you can acknowledge how it looks without becoming defensive. Refusing to concede that it is a fair question is worse than the tenure record itself. The specific version of this and its follow-ups are covered in frequent job changes — why will this one be different, and the related and more delicate question of whether a departure was your choice in was leaving your last role your decision.

The role asks for eight years and you have four. Convince me.

Do not argue with the number. Reframe onto what the number was standing in for, and offer a concrete substitute. "Four years by date, yes. What I would put against the eight is that I have owned a production payments service end to end for three of them, including a migration and the on-call for it, which is usually what a longer number is a proxy for. If the concern is something specific — leading a team, or a particular scale — tell me which and I will tell you straight whether I have it."

Graded on whether you can handle a direct challenge without either deflating or overclaiming, and on whether you understand that years are a proxy rather than a requirement. Offering to be told the specific concern is the strong move, because it converts a rejection criterion into a conversation. Claiming the years anyway, or saying that years do not matter, both fail.

Is there anything on your CV I should know about before I put you forward?

Treat this as the gift it is. If there is something — a gap, a dismissal, a role you left after two months, a title inflation — this is the cheapest possible moment to say it, in one or two sentences, with no drama. If there genuinely is nothing, say so plainly and offer the one thing that most often prompts a question anyway: "Nothing awkward. The only thing people ask about is the two-month role in 2022, which was a contract that was cancelled after the client pulled the project."

The question is asked because the recruiter does not want to be surprised in front of the hiring manager. Whether you make their job safe is what is being graded. Anything you conceal here and that emerges later is doubly damaging, because it becomes a question about candour rather than about the fact, and the same logic applies to anything a screening process would surface, which is the subject of anything a background check will turn up.

How did you come across this role?

Answer factually and use it to say something specific. "Your careers page — I was looking at a couple of payments companies specifically after the settlement project finished, and this one had the scheme integration line in it, which is what made me apply rather than bookmark it."

Two things are read: whether you applied deliberately or in bulk, and, for the recruiter's own reporting, which channel worked. A referral is worth naming explicitly, because referred candidates are handled differently in most processes. The weak answer is "I think a recruiter sent it to me, or maybe I saw it somewhere", which is honest and unhelpful; if that is the truth, add the reason you responded to it.

Are you currently employed?

Answer plainly, and if you are not, state the situation without apology and say what you have been doing. "No — I was made redundant in April, so I am available immediately. I have been doing a couple of small contract pieces and finishing a certification while I look."

Being out of work is common and is not, in itself, a negative in most processes. What is read is your relationship to it. Defensiveness, over-explanation or a hint of desperation all register; a flat statement plus availability does not. Availability is genuinely valuable to a recruiter with a date to hit, so it is worth stating as the fact it is rather than burying it.

Tell me about the most recent thing you worked on.

Give the non-technical version, in three or four sentences, and offer to go deeper rather than going deeper unprompted. "We replaced a third-party reconciliation product with something we built, because the vendor could not support a new payment scheme we were joining. Nine months, three of us, and the tricky part was running both systems side by side and comparing them daily until finance trusted the new one enough to switch. I can go into the technical side if it is useful, but that is the shape of it."

The graded quality is calibration to the listener. This is the question where most technically strong candidates lose ground at a screen, by hearing an invitation to demonstrate depth. Explaining a complex piece of work to somebody who cannot evaluate it, clearly and without condescension, is a genuine and rare skill, and it is the thing this question measures. The offer to go deeper is what protects you if the recruiter did want more.

What would make you turn this down?

Answer honestly with one or two real conditions, because a candidate with no conditions is not credible. "Two things would. If the ownership turns out to be shared across teams the way it is now, that removes the main reason I am here. And if the compensation lands below the range we discussed, I would have to weigh it against where I am, since I am not unhappy."

This is a due-diligence question and the signal is whether you have thought about the decision as a decision. "Nothing, I would definitely take it" is read as either desperation or as an answer that has not been considered, and it also removes the recruiter's ability to solve for you. Naming a specific, addressable condition is genuinely useful to them: a good recruiter will go and check the thing you named. What fails at the other end is a list of six conditions, which reads as somebody looking for reasons to decline.

Is there anything that would stop you accepting an offer if we made one?

Answer with the practical blockers rather than the emotional ones: notice, a competing process with a timeline, a bonus date, a relocation question, sponsorship. "Nothing structural. Three months' notice, and the other process I mentioned resolves in about three weeks — if that one lands first I would want to be able to compare, and I would tell you rather than go quiet."

The recruiter is doing risk assessment for the manager, and what is graded is whether you volunteer the friction. The last clause is the strongest part: promising to communicate rather than disappear is exactly the reassurance they are looking for, and it is one of the few things you can say at a screen that meaningfully differentiates you, because a significant proportion of candidates do go quiet.

Do you have any questions for me?

Ask the ones only they can answer, and make it four or five rather than one. The band. The number of stages, their formats and the elapsed time. Who is on the panel and what each one focuses on. Why the role is open and how long it has been open. And, if it fits, what success in the first six months looks like.

Graded on whether you know what a recruiter is for. Asking a recruiter about the team's testing strategy is a wasted question; asking about the panel is worth an hour of targeted preparation. Having no questions is the common failure and reads as either disengagement or as not having thought about the process as a decision you are also making. The general principle — that this is never a formality — is set out in do you have any questions for us, and the sharper version of it in what do you still not know about this role.

Are you happy for me to put you forward?

Say yes explicitly, or say what you need first. "Yes, please do. One thing before you do — you mentioned the band goes to ninety-five; if the level here is the mid grade rather than senior, I would want to know that before it goes further, because it changes the arithmetic. Otherwise, go ahead."

For an agency recruiter this question has an additional weight and should always be answered with a named company. Blanket permission to submit your CV is how duplicate submissions happen, and a duplicate submission can remove you from a process you were already progressing in. "Yes, for this specific role at this specific company — and please check with me before sending it anywhere else" is a normal, professional thing to say and any reputable recruiter expects it.

One last thing — how does this compare to the other roles you are looking at?

Answer comparatively and honestly, which means being willing to say something is not the strongest thing on the list. "It is the closest on the actual work — the scheme integration piece is a better match than anything else I am looking at. The one I mentioned at final stage is a bigger company and pays more, so if I am being straight with you, this one wins on the job and probably not on the money. Which is why I asked about the band."

The signal is whether you can hold a nuanced position rather than flattering them, and whether your comparison is consistent with the priorities you stated earlier in the call. A candidate who tells every recruiter their role is the favourite is either lying to some of them or has no criteria, and experienced recruiters test for this. Being candid about where this role loses is what makes your statement about where it wins believable, and it hands the recruiter a specific thing to go and fix internally, which is the outcome you want from the last thirty seconds of the call.