HR, Screening & the Offer Stage

What this area actually covers

This area covers everything in a hiring process that is not a technical assessment: the recruiter's first call, the motivation and fit questions, the awkward explanations about a gap or a nine-month job, the logistics of notice and location and background checks, and then the offer — reading it, comparing it, negotiating it, accepting or declining it. Two of those points carry nearly all the consequence. The recruiter screen decides whether the technical loop happens at all, and the offer conversation decides what the whole exercise was worth.

The reason to treat this as one subject rather than six is that the counterparty is the same throughout, and the information you volunteer at the beginning constrains what you can ask for at the end. A number given casually in minute four of the first call is quoted back to you six weeks later as your expectation. That is the through-line: early conversations are cheap to have and expensive to have badly. Nothing you say to a recruiter is off the record, not because recruiters are duplicitous but because they take notes and those notes travel with your file.

What people wrongly bundle in is the behavioural round. A competency interview about a conflict you handled is a scored technical-adjacent assessment run by engineers against a rubric; it belongs with behavioural preparation. What happens here is commercial and procedural, conducted by people whose incentives are different from the panel's, and the skills do not transfer. The other misplacement is treating offer evaluation as arithmetic. Comparing two offers is mostly about which unknowns you are prepared to carry, and arithmetic is the easy part.

A third thing worth separating out is the reference and background check. Candidates treat it as a formality and occasionally it is not: an employment history that does not match what you said, a title inflated on your profile, or a referee who was never asked and is surprised to be called can all unwind an accepted offer late. It costs you nothing to keep your stated dates and titles exactly matching what a payroll record would show, and to warn your referees before they are contacted.

The six conversations underneath

This section is divided the way the process is divided, because each of these moments has a different counterparty, a different failure mode and a different thing worth rehearsing. Read them in order the first time; after that, go straight to whichever one is next in your own process.

Recruiter Screening covers the first call: the ninety-second positioning statement, the closed must-have questions, and the filter criteria you are being checked against without being told. It exists as its own subsection because it is the highest-leverage half hour in the whole process and the one candidates prepare for least, on the mistaken assumption that a recruiter cannot reject them. Open it and you will find the shape of the call, the questions that are really pass-fail, and how to make the summary the recruiter writes about you accurate rather than approximate.

Motivation & Fit is the family of questions about why this company, why you are leaving, and where you expect to be in a few years. It is separate from the screen because the same words mean different things depending on who is asking: a recruiter is checking coherence, a hiring manager is estimating how long you will stay. The material here is about answering with a reason that is specific to this employer and true, since the failure mode is a fluent answer that would apply to any company in the sector.

Gaps & Job Changes handles the awkward parts of a history — a short tenure, a redundancy, a career break, a run of contracts, a switch out of and back into engineering. It is its own subsection because the technique is unusual and counterintuitive: the content matters far less than the length and the tone, and almost everyone over-explains. You will find worked phrasings for each of the common cases, and guidance on where to stop talking.

Compensation & Negotiation is the commercial core: deflecting the early number question, deciding what to anchor on, valuing a full package rather than a base salary, and making a counter that gets approved rather than one that irritates. It is separated out because it has genuine mechanics — bands, levels, approval chains — that reward being understood rather than improvised. Expect scripts, and expect the emphasis to be on asking once and well.

Logistics & Policy is the unglamorous set: notice periods and garden leave, relocation and its repayment terms, hybrid attendance expectations, background and reference checks, probation, and any bond or clawback attached to money you receive early. These are grouped because they share a property — none of them feels negotiable, several of them are, and all of them are cheaper to raise before you sign than after.

Offer Evaluation is what you do once something is in writing: comparing two offers when one has illiquid equity, reading a counter-offer from your current employer for what it really signals, deciding under a deadline, and declining in a way that leaves the door open. It is last because it is the only part of the process where you hold all the authority, and the questions here are about judgement rather than technique.

Where it sits in a real business

Recruitment sits between a hiring manager who has been given approval for a headcount and a finance function that has attached a band to it. The manager wants the seat filled by someone good; finance wants the band respected; the recruiter is measured on filling roles, on time-to-hire, and — in agency and some in-house models — on the offer actually being accepted. Understanding that last incentive explains most recruiter behaviour that candidates read as manipulation. A recruiter who has invested five weeks in you does not want you to decline, and that is leverage you already have without doing anything adversarial.

The offer itself is usually not the recruiter's to invent. There is a band for the level, the level was decided during or just after the loop, and any figure outside the band needs someone senior to sign it. That is why "let me check" is a real answer rather than a stall, and why asking for a level review is sometimes a larger move than asking for more money at the level you were given.

It helps to see the whole thing as a funnel with two narrow points, because your preparation should be weighted towards them rather than spread evenly.

flowchart TD
    A[Application or inbound approach] --> B[Recruiter screen]
    B -->|Forwarded with a summary| C[Hiring manager call]
    B -->|Filtered on a must-have| X[Out of process]
    C --> D[Technical loop]
    D --> E[Debrief and levelling]
    E -->|Hire at a level| F[Offer conversation]
    E -->|No hire| X
    F --> G[Accept, counter or decline]

The edge worth studying is the one from the debrief into the offer. Everything before it is about whether you are hired; that single arrow is where your level is fixed, and level sets the band, and the band sets the ceiling on every later conversation about money. By the time you are talking to the recruiter about a figure, the most consequential decision has already been made in a room you were not in.

The last row is not a joke. Once you have accepted, every term you did not raise is settled, and raising it afterwards costs goodwill at exactly the moment you have none banked.

The vocabulary you will be quoted at

Most of the confusion in an offer conversation is lexical rather than adversarial. Someone uses a term of art, you nod, and you have agreed to something you have not understood. These are the words that carry money.

Learn these before the call rather than during it. The commonest own goal in this whole area is agreeing enthusiastically to a number that turns out to be OTE when you heard base.

Who does this work

On the other side of these conversations are technical recruiters, either in-house or at an agency, who spend the day sourcing, screening, scheduling and chasing. In-house recruiters know the team, the manager's tolerances, and the band; agency recruiters know the market and are paid on placement, which makes them better at pushing your number and worse at answering questions about the team. An HR business partner appears for policy questions, notice negotiation and anything to do with a probation period or a bond. At larger employers a compensation analyst you will never meet sets the bands that shape everything.

A recruiter's day is not mysterious and it is worth picturing: a dozen calls, a shortlist to defend to a manager who is unimpressed, and candidates who go quiet. Being easy to schedule, unambiguous about what you want and prompt in replying is not politeness, it is a genuine advantage, because it makes you the candidate whose process is not painful. Recruiters are managing thirty processes in parallel, and the one that moves is the one where nobody has to chase.

The distinction between in-house and agency deserves a moment because it changes what you should ask. An in-house recruiter can tell you what the team is like, why the last person left, what the levelling criteria are and roughly where in the band the offer will land, and they cannot tell you what a competitor would pay. An agency recruiter is the reverse: strong on comparative market information, weak on anything inside the company, and structurally motivated to get you to accept because their fee depends on it. Ask each of them what they can actually answer.

There is one more party you rarely meet and should keep in mind: the hiring manager's own manager, or a finance approver, who signs anything unusual. When a recruiter says an exception has to go up, that is who it goes to, and the approval takes days rather than minutes. Building a deadline into your own side of the conversation without allowing for that is how candidates accidentally force a no.

The recruiter screen, minute by minute

This call runs about half an hour and follows a stable shape. Knowing the shape is most of the preparation, because the failures are structural rather than substantive: talking for nine minutes when ninety seconds was wanted, or being unable to say why you are looking without sounding aggrieved.

The recruiter is working from a short list of must-haves supplied by the hiring manager. Those are usually a technology or domain, a seniority band, a location or attendance expectation, a notice or availability window, and a salary range. They are checking each one and writing a two-paragraph summary that the manager will read instead of your resume. Your goal is that the summary is accurate and makes the manager curious.

A RECRUITER SCREEN, AS IT ACTUALLY RUNS

0-3 min    Their pitch. Company, team, role. Listen for the words they
           repeat - those are the must-haves. Take one note.

3-8 min    "Tell me about your background." They want a ninety-second
           arc, not a chronology. Where you are now, one thing you own,
           why the shape of this role follows from it. Stop talking.

8-15 min   Must-have probing. Specific and closed. Have you used X. How
           big was the team. Did you own the deployment or watch it.
           Answer the question asked, then one sentence of evidence.

15-20 min  Logistics. Notice period. Location and days on site. Work
           authorisation. Any other processes running. These are facts;
           give the true ones and do not improvise a start date.

20-24 min  Compensation. See the section below. This is the only part
           of the call that is worth rehearsing word for word.

24-30 min  Your questions, and next steps. Ask two that only they can
           answer, then ask directly what the process looks like and
           when you will hear.

Two lines in that script do more work than the rest. The first is the ninety-second arc, because a recruiter who cannot summarise you will forward you weakly or not at all, and the summary they write is the one you gave them. The second is the closing question about process, since it converts a vague "we will be in touch" into a date you can follow up against without seeming pushy.

On the awkward explanations — a redundancy, a gap, a short tenure, a non-technical detour — the working rule is that length signals discomfort. Two or three sentences delivered evenly reads as a fact. The same content across five minutes reads as a wound. Say what happened, say what you did, and stop; if the recruiter wants more they will ask, and answering a follow-up is far better than pre-empting it.

Demand, adoption and how that is changing

This is steady rather than surging, and it is steady for a structural reason: as long as hiring is intermediated by a recruitment function, every candidate passes through these conversations regardless of discipline or seniority. There is no technology cycle here to raise or lower the ceiling.

Two shifts have changed the texture rather than the volume. Pay-transparency legislation in several jurisdictions — including a number of US states and the EU's pay transparency directive, which member states are required to transpose into national law by June 2026 — has pushed advertised ranges into job postings. Where that applies, the early salary question is less of a trap and the negotiation moves towards where in a published band you land, which is a different conversation requiring different evidence. The other shift is remote and hybrid policy becoming an explicit, contested term of the offer rather than an assumption, which is why location and attendance expectations now belong in the same conversation as money. An attendance expectation is a compensation term in disguise, because commuting three days a week has a cost you can calculate.

A third change is worth naming because it affects how you should behave in the screen. Application volume per posting has risen sharply as applying became frictionless and assisted by tooling, which means the screen has become a harder filter rather than an easier one, and generic material is discarded faster. Specificity is the only defence: a recruiter reading a hundred summaries remembers the one with a concrete system, a number and a scope, and forgets every adjective.

What has not changed is that most engineers still arrive at the offer stage having prepared nothing. That is the honest reason this area is worth an hour: not because it is in demand as a skill to sell, but because the return on a small amount of preparation is larger here than anywhere else in the process.

What makes it hard

The difficulty is not intellectual. It is that these conversations arrive when your judgement is at its worst — you are being liked, an offer is in front of you after weeks of interviews, and the instinct to protect the good feeling in the room is overwhelming. That instinct is what produces the two classic losses: a number given before you had to give one, and an offer accepted the day it arrived.

Second, silence is genuinely uncomfortable and it is where the value sits. "That is a bit below what I was expecting" followed by nothing is more effective than any argument, and most people cannot do it without training themselves, because the pause feels like rudeness rather than the ordinary rhythm of a commercial conversation. Recruiters are used to silence and are not offended by it. You will be the only person in the conversation who finds it excruciating.

Third, you are negotiating with almost no information. You do not know the band, the other candidates, how badly the manager needs the seat filled, or whether the recruiter has already used their discretion. Experienced negotiators are not better at guessing those things; they are better at asking questions that reveal them and at being comfortable while they remain unknown.

Fourth, and least discussed, is that the whole exchange is asymmetric in repetition. Your counterpart has had this conversation several hundred times and you have had it perhaps six. They are not smarter than you and they are not lying to you, but they know the shape of it, and a shape you have never seen before feels like pressure when it is only routine. Most of what reads as a tactic is simply someone doing their job in the way they always do it.

The compensation question and four ways to answer it

There is one moment in the screen worth rehearsing until it is automatic: "what are you looking for?". You do not have to answer it, you should not answer it badly, and the four sensible responses have different costs. Which one is right depends entirely on whether a range has already been published.

Two rules sit underneath all four. Never state a number you would resent, since it will become the offer. And never inflate your current package, because in several jurisdictions the employer may see a payslip or a P60 during onboarding, and being caught having lied about a fact is a category of problem that no negotiation recovers from.

Researching your number is a separate exercise from stating it, and it is the one people skip. Do it from at least three kinds of source rather than one: published ranges on live postings for the same level in the same location, which are the strongest evidence because they are what the employer has already committed to advertise; what agency recruiters covering your niche tell you they are placing people at, discounted for their interest in a high number; and people you actually know doing the job, asked specifically rather than generally. Aggregated public data sets are worth a glance and no more, because they mix levels, locations and years. Do not quote a figure to a recruiter that you cannot say where you got.

The negotiation, as it really runs

Most engineers imagine negotiation as a confrontation and it is nothing of the kind. It is a short, bounded exchange in which you ask once, clearly, and then let an approval process run. The important structural fact is that the person you are talking to usually cannot say yes on their own.

sequenceDiagram
    participant C as Candidate
    participant R as Recruiter
    participant M as Hiring manager
    participant F as Compensation
    R->>C: Verbal offer, near the band midpoint
    C->>R: Thank you. I would like a few days to consider
    C->>R: One counter, with a reason attached
    R->>M: Candidate is asking above midpoint
    M->>F: Requests approval to move up the band
    F-->>M: Approved to a stated ceiling
    M-->>R: Go to the ceiling and no further
    R->>C: Revised offer, described as final

Look at the two dashed replies in the middle. That is where the delay comes from, and it is why an answer arriving on Thursday rather than Monday is not evidence of anything. It is also why a second counter usually fails: the ceiling was set once, and asking again forces your counterpart to go back to the same approver having already told them the matter was settled. Ask well, ask once, and take the answer.

What a good counter looks like in practice is unremarkable. It is one message, it names one or two specific things, it gives a reason that is about the market or the role rather than about your needs, and it ends with a clear signal that you want to accept.

A COUNTER THAT WORKS, IN FULL

  Thank you for this - I am genuinely keen and I would like to make it
  work. Two things I would ask you to look at.

  On base, the offer is at 78k. Based on the ranges advertised for
  senior roles at this level in the same location, and the fact that
  I will be taking on the on-call rotation from the start, I was
  expecting something closer to 86k.

  On the start date, my notice is eight weeks rather than four, so
  the realistic date is 3 November.

  If you can get to 86k I will accept today. If the band does not
  reach that, I would be glad to talk about a joining bonus instead.

WHY IT WORKS

  - One number, not a range. A range concedes the bottom of it.
  - A reason external to you. "I need more" invites sympathy;
    "the market is here" invites a band check.
  - Two asks, not six. Six reads as a list of grievances.
  - An explicit close. The recruiter can now go to their manager
    with "she will sign today at 86", which is a much easier
    argument than "she wants more".
  - A named fallback. Sign-on bonuses often sit outside the band and
    are the easiest thing for a manager to approve.

On exploding offers, the answer is neither to capitulate nor to bristle. Say plainly that you want to accept, that you have one process concluding on a specific date, and ask whether the deadline can move to accommodate it. A real employer will move it. An employer who will not has told you something useful about how they treat people, and you have learned it for free.

Reading the offer before you read the number

When the written offer arrives, the instinct is to check the base salary and skip to the signature. The base is the part you already discussed; everything that will surprise you later is in the rest of the document. Read it once with this list beside you.

OFFER LETTER CHECKLIST

  Money
  [ ] Base, and the date of the first review
  [ ] Variable - target percentage, what it depends on, discretionary
      or contractual, what was paid last cycle at your level
  [ ] Equity - number of units not a currency value, vesting schedule,
      cliff, what happens to unvested units if you leave or are let go
  [ ] Sign-on bonus - amount, payment date, clawback trigger and period
  [ ] Pension or retirement contribution, and whether it is matched

  Terms that cost money later
  [ ] Probation period, and notice during it in both directions
  [ ] Notice period after probation, and any garden leave clause
  [ ] Non-compete or non-solicit, its duration and geography
  [ ] Intellectual property assignment, and any carve-out for
      personal projects
  [ ] Relocation support and its repayment terms

  Terms that decide your week
  [ ] Attendance expectation - days, which days, and who can change it
  [ ] On-call - frequency, compensation, and whether it is in the letter
  [ ] Working hours, overtime treatment, holiday entitlement and carry-over
  [ ] Reporting line and job title, spelled exactly

  The one people forget
  [ ] Which internal level you have been placed at, and the criteria
      for the next one

Ask about anything unclear in writing and keep the reply. A recruiter's email saying that the sign-on clawback lapses at twelve months is not a contract, but it is extremely awkward for an employer to contradict, and it costs you one sentence to obtain.

Comparing two offers is where the arithmetic tempts you into false precision. Private-company equity in particular cannot be compared with cash, because its value depends on an event that may not happen; the defensible way to treat it is to value it at zero, decide which offer you prefer on that basis, and then treat the equity as the upside that breaks a genuine tie. Beyond the money, the questions that actually predict how the next two years feel are who you report to, what the team ships and how often, and whether the role exists because someone left. It is worth asking why the position is open, and listening to how readily the answer comes.

Why study it

Because the size of the effect is out of proportion to the effort. A single unrehearsed sentence about your expectations can move the offer by an amount you would not recover with a year of good performance reviews, and an unasked question about a clawback or a variable component can cost you real money eighteen months later. Nothing else in interview preparation has that ratio.

Be clear that this is not a subject you study. There is no body of knowledge here, no depth to build, and reading more than a few pages about negotiation tactics is a way of avoiding the actual work. It is a set of situations, perhaps eight of them, that reward having thought about each one exactly once before you are sitting in it. Do that and you are ahead of nearly everyone.

There is a second, quieter reason. Doing this well requires you to state what you are worth and then be still while someone considers it, and most people find that harder than any technical question they have ever been asked. Practising it in a low-stakes setting — a role you are lukewarm about, a process you would not mind losing — is genuinely useful rehearsal for every later conversation about a raise, a promotion or a rate.

Who should skip it: if you are being rejected in technical loops, this changes nothing, because you will not reach the stage where it matters. And if you are in a jurisdiction or a structure where the offer is genuinely fixed — some graduate programmes, many public-sector roles, most standardised campus hiring — read the logistics material and ignore the negotiation material entirely. In those settings the only lever is level, and the only time to pull it is during the loop.

Your first hour

Write two things, on one page, and keep the page.

1. YOUR NUMBER (before any call happens)
   Current total:   base + variable + equity + benefits you would lose
   Walk-away:       the figure below which you stay where you are
   Target:          what you would say yes to immediately
   The sentence:    what you say when asked in minute four

2. YOUR SITUATIONS (one honest paragraph each, spoken aloud once)
   Why you are leaving        - true reason, said without complaint
   The gap or short tenure    - what happened, what you did, then stop
   Notice and start date      - the real date, not the optimistic one
   Location and attendance    - what you will actually do every week

The test of the number page is that you can say the walk-away figure out loud without your voice changing. The test of the situations page is length: if the paragraph about a short tenure runs past four sentences, it reads as a defence, and shortening it is the whole exercise. An hour is enough for both, and this artefact is the input to every question in this section.

If you have a spare fifteen minutes after that, add a third block: the three questions you will ask at the end of every screen. Not the polite ones. Ask what the last person in this role went on to do, ask what would make the manager say at six months that the hire had worked, and ask what the team is worst at. The answers are informative, and asking them changes how you are described in the summary the recruiter writes.

What this is not

It is not adversarial. The recruiter is a filter and an advocate at the same time — the same person who screens you out on a must-have will argue your case to a hesitant manager and push your number upwards, because they want the placement. Treating that person as an opponent costs you an ally who is on your side more often than not.

It is not a test of toughness. Negotiation here is a short, polite, factual exchange between two professionals about a price, closer to agreeing a delivery date than to a confrontation. Candidates who arrive braced for a fight tend to overreach and then apologise, which is worse than asking plainly once. The tactics literature written for one-off transactions between strangers is actively misleading here, because you are about to work with these people.

It is not a values assessment, however similar some of the questions sound to the behavioural round. "Why do you want to work here?" asked by a recruiter is a screening question about coherence and motivation; the same words from a hiring manager are about whether you will stay. Answering both as though they were a values assessment is why the answers come out sounding rehearsed.

And it is not permanent. Almost everything settled here can be revisited later from inside the company, with the significant exception of level, which is sticky in a way salary is not. If you are going to spend your one unit of persistence on something, spend it there.

Decide your number and rehearse your four awkward paragraphs before the first call, because every one of these conversations happens when you are least able to improvise well.