Which tech salary negotiation scripts actually work?

A good salary negotiation does not sound clever. It makes the recruiter carry a clear, defensible request back to the people who can approve it. The words matter because a vague counter creates work for the recruiter, while a precise counter gives them a case they can repeat almost verbatim.

I have hired engineers, built compensation plans, and sat on both sides of the call. The candidates who improve an offer rarely deliver a dramatic speech. They slow the conversation down, separate facts from pressure, and ask for one decision at a time. These tech salary negotiation scripts give you the exact language, but their value comes from the reasoning underneath them.

Your first answer should buy information, not name a number

The recruiter call is for learning the role's level, band, and process before you anchor yourself. A recruiter may ask for your expectations in the first five minutes because the answer helps them screen for fit. You do not owe a number before you know what the job includes, and you do not need to make the exchange adversarial.

When the recruiter asks, "What compensation are you targeting?" use this:

I would like to understand the level, scope, and full package before I set a target. What salary band has been approved for this role?

Then stop. Do not rescue the silence. The recruiter may answer with a range, ask about your current pay, or say the company has flexibility. Each response contains different information.

If they press for a target, stay cooperative:

I am looking for a package that matches the market for this scope. If you can share the approved band and the level the team is considering, I can tell you quickly whether we are in the same area.

If a form or a person forces a number, use a conditional range rather than a naked demand:

Based on what I know so far, I would expect a base salary between $X and $Y, assuming the role is at level L and the equity, bonus, and benefits are competitive. I can be more precise once I understand the scope.

Replace every placeholder before the call. Your lower number must still be a number you would accept. Recruiters often hear the bottom of a candidate's range as permission, not as a midpoint. A range of $180,000 to $210,000 does not communicate a $195,000 target. It communicates that $180,000 may close the deal.

Questions about current salary deserve a shorter answer. Laws on salary history vary by location, so do not pretend one rule applies everywhere. You can redirect without giving a legal lecture:

I keep my current compensation private. I am happy to discuss the value and market range of this role. What range did the company approve?

If the recruiter will not disclose any range, decide whether the interview is worth the time. One refusal may reflect policy or poor training. Repeated refusal after several rounds tells you the company expects the candidate to price the role with less information than the employer has. That imbalance rarely improves later.

A range is useful only when both ends are acceptable

Your target needs three numbers: the result you will ask for, the result you would accept, and the point at which you walk away. Mixing them together is how candidates accept an offer and regret it before their first day.

Build the numbers from comparable roles, not from the raise you want over your current salary. Use recent compensation data for the same location, company stage, technical specialty, and level. Separate base salary, target bonus, equity, signing money, retirement contributions, insurance, paid leave, and any recurring allowances. A senior backend engineer at a public company and a first engineering hire at a seed startup may share a title while carrying completely different risk and compensation.

The U.S. Bureau of Labor Statistics treats wages and benefits as separate parts of employer compensation. That sounds obvious, yet candidates routinely compare one offer's base salary with another offer's total value. The BLS method is useful as a discipline, not as a calculator for your particular offer: list each component, identify who bears the risk, and compare like with like.

Make a decision sheet before you negotiate. Give base salary, annual cash bonus, equity, signing payment, start date, and leave their own rows. For each row, record the offer, your target, your minimum, and your confidence in the value.

Confidence describes how much you trust the value, not how much you want it. Cash already stated in a written offer has high confidence. Private-company options with no current preferred price, strike price, share count, or dilution context have low confidence. Do not turn a speculative equity number into guaranteed annual income in your spreadsheet.

There are also two ranges that candidates often blur. The approved compensation band is the employer's formal interval for a level. The recruiter budget range may be the portion they expect to use for this hire. Ask which one you are hearing:

Is that the full approved band for the level, or the range the team expects to use for this opening?

That question can expose room without accusing anyone of hiding it. If the recruiter says the offer is already at the top, ask whether the constraint is the base salary, the level, or total compensation. A cap in one category does not prove every category is fixed.

Make the counter about scope and level

A strong counter links your evidence to the work the company wants done and ends with a specific number. Personal expenses, a desired percentage raise, and the fact that you worked hard through the interviews do not help an approver justify an exception.

Wait until you have the full written offer unless the recruiter explicitly runs the process verbally. Thank them, confirm your interest, and ask for time to review. Enthusiasm and negotiation can coexist. The recruiter is trying to learn whether an improved offer can close you, so give a truthful conditional commitment only if you mean it.

Use this on the offer call:

I am excited about the role and the team. After reviewing the scope, especially ownership of X and responsibility for Y, I would be ready to sign at a base salary of $205,000. Can you take that request to the compensation team?

The last sentence matters. "Is there any flexibility?" invites a small concession or a polite no. "Can you take $205,000 to the compensation team?" creates a decision. The recruiter can answer yes, no, or explain the constraint.

If you have a competing offer, state only facts you can document:

I have another written offer with a $215,000 base and a decision date of Friday. I prefer this role because of the product ownership, and a base of $205,000 would make the decision straightforward for me.

Do not invent an offer or imply one exists. A bluff creates the exact problem you do not want: the recruiter may ask for timing, the company may decline to compete, or an approval may depend on a claim you cannot support. You can negotiate without a competing offer by using scope, level, rare experience, interview evidence, and market comparables.

When the offer is below your minimum, do not reveal the minimum and hope they land above it. Counter at your reasoned target:

Thank you for laying out the package. The current base is below the range I can accept for this scope. Based on the staff-level responsibilities we discussed, I am asking for $225,000 base. If the base band cannot reach that number, I would like to discuss the level and the mix of signing payment and equity.

A counter should make one coherent case. Five unrelated reasons sound like you are collecting arguments. Pick the two facts an internal approver can verify: the role owns a larger domain than the original description, your experience removes a stated execution risk, the interviews calibrated you at a higher level, or another written offer prices comparable work differently.

The written counter should be boring and precise

A written counter works best when the recruiter can forward it without editing. Keep it short enough to read on a phone and specific enough that nobody has to guess which term you want changed.

This is a complete counter email you can adapt:

Subject: Offer for [role]

Hi [name],

Thank you for the offer and for answering my questions about the team. I am enthusiastic about the role, especially the opportunity to own [specific responsibility].

Based on the scope we discussed, my [relevant experience], and compensation for comparable [level] roles, I am asking for a base salary of $X and [specific equity or signing term]. If the team can approve those terms, I am prepared to accept the offer by [date].

Please tell me whether you can take this counter to the compensation team. I am available [two windows] if a call would help.

Best, [name]

Only include the acceptance sentence when approval really would close the deal. If you still need to review a noncompete, understand equity, meet a leader, or compare another offer, write this instead:

If the team can approve those terms, the package would be much closer to what I need to make a decision.

That wording is less powerful because it gives the employer less certainty, but it is honest. Never trade certainty you do not have.

A common failed counter reads like this: "I was hoping for something closer to market, and I would appreciate anything you can do." The recruiter cannot tell whether the candidate wants $5,000 or $50,000, which market applies, or whether any change will produce an acceptance. They may request a token increase because that is the easiest internal action. The candidate then counters again, and the recruiter feels that the target is moving.

Repair it by naming the gap once:

The $175,000 offer is $20,000 below the base I am targeting. I am asking for $195,000 because the role includes technical leadership for two product areas and on-call ownership. If $195,000 is outside the band, please share the highest base the level permits and whether the team can add a signing payment.

Do not send an essay describing your career. The interview loop already evaluated you. The counter should connect the evaluated evidence to the compensation decision. Also keep negotiation out of chat fragments when several terms are moving. Email creates a clean record and reduces the chance that a number loses its conditions as people relay it.

An exploding offer is a deadline, not evidence

An exploding offer gives you a short acceptance window and threatens to disappear afterward. The deadline may reflect a real business constraint, another finalist, a compensation approval window, or an attempt to stop comparison. You do not need to guess which one. Ask what drives it and request the time you actually need.

Start with this response:

I am pleased to receive the offer, and I am taking it seriously. The current deadline gives me [number] business days to review the written terms and complete conversations already in progress. I can give you a firm answer by [date]. Can the company keep the offer open until then?

Use a date, not "more time." A defined extension is easier to approve. If you need a week, ask for a week. Asking for two days and returning for a second extension makes your process look unmanaged.

If the recruiter says the deadline cannot move, ask one clean follow-up:

What specific constraint makes [current date] necessary, and what happens to the role if I have not accepted by then?

The answer matters. "We need to close payroll" may be negotiable. "The team has another candidate waiting" may be real. "It is our policy" tells you the pressure is designed into the hiring process. None of those answers requires anger. They require a decision based on your alternatives.

Do not accept merely to hold the offer while continuing to interview unless you are willing to break your word. Circumstances do change, and employment rules differ across jurisdictions, but tactical acceptance transfers the time pressure to your reputation and to a manager planning around your start. Ask for the extension first. If the company refuses, decide with the information you have.

You can also accelerate another process without disclosing confidential details:

I have received an offer that requires a decision on Thursday. Your role remains a serious option for me. Is it possible to complete the remaining interviews and reach a decision before then?

Some companies cannot move. That is information, not rejection. An offer that expires before you can inspect its terms may still be attractive, but the forced speed belongs in your assessment of how the company makes consequential decisions.

Trade salary against compensation components deliberately

When base salary is capped, negotiate the items that solve your actual problem instead of collecting concessions. A signing payment can close a first-year cash gap. More equity changes upside and risk. A guaranteed first-year bonus removes performance uncertainty. A later start date protects time. Extra leave changes your working year. These terms are not interchangeable.

Ask which constraints are independent:

I understand that $190,000 is the maximum base for this level. Can the company increase the signing payment to $30,000 or move the equity grant to [number] units? Which of those has more approval room?

This gives the recruiter two routes instead of an open request to "improve the package." Still, do not negotiate ten terms because they exist. Rank the terms before the call, then spend political capital on the first one or two.

Equity needs its own questions. For public shares, ask about the grant value, number of units, vesting schedule, and the price or averaging method used to calculate the grant. For private options, ask for the number of options, total fully diluted shares or your percentage ownership, strike price, latest preferred price, vesting, exercise window, and what happens after termination or acquisition. A large option count without a denominator tells you very little.

Use this when details are missing:

I cannot evaluate the equity portion from the grant count alone. Please provide the percentage on a fully diluted basis, the strike price, the latest preferred price, the vesting schedule, and the post-termination exercise window.

Do not call private equity worthless, and do not count it as cash. Model at least three outcomes: no liquidity, a modest outcome after dilution and exercise cost, and a strong outcome. Your counter can then reflect the risk rather than a headline valuation.

Benefits can affect the comparison, but confirm them before assigning a dollar value. Ask for employee premiums, deductibles, retirement matching rules, paid leave, parental leave, remote-work expectations, and any geographic pay policy that could change your salary after a move. The EEOC's compensation guidance treats bonuses, insurance, leave, and other benefits as forms of compensation in its discrimination analysis. That is a useful correction to the habit of treating base salary as the whole deal, though laws and protections depend on jurisdiction.

If the company cannot change money, you may negotiate role terms that have real value: a six-month compensation review with written criteria, a defined title, remote status, a start date, or a reporting line. Do not accept "we can revisit this later" as compensation. Ask who will decide, on what date, against which goals, and whether the commitment can appear in the offer. A future conversation has no guaranteed value.

Negotiate the level before squeezing the package

A level mismatch can cost more than a small salary gap because the level sets the band, scope, equity, promotion path, and future comparables. If the interviews evaluated you for senior work but the offer says mid-level, arguing only about base salary leaves the structural mistake intact.

Ask for the evidence behind the level:

The responsibilities we discussed include leading architecture across two teams and mentoring senior engineers. Those expectations sound consistent with your staff scope. Which interview evidence led the committee to place the role at senior, and what responsibilities differ between the two levels?

This question is firm without claiming that titles mean the same thing everywhere. It asks the company to reconcile stated work with its own framework. If the recruiter cannot explain, request a conversation with the hiring manager.

Sometimes the lower level is correct. Your prior title may not map to the new company's scale, or the interviews may not demonstrate the required breadth. Ask what evidence was missing. A credible answer names behaviors and scope. A weak answer repeats that the committee felt more comfortable at the lower level. You can accept a down-level when the work, pay, and growth case still make sense, but do it knowingly.

Be wary of a high title attached to a low band at an early startup. A "VP of Engineering" offer can mean executive authority, or it can mean the only engineer who also recruits. Clarify headcount authority, budget, hiring plan, decision rights, on-call expectations, and who owns product delivery. Negotiate the job that will exist on Monday morning, not the status implied by the title.

For a startup executive role, use this:

Before we settle compensation, I want the mandate in writing. I understand that I will own engineering hiring, delivery commitments, architecture decisions, and the infrastructure budget, reporting to the CEO. Please correct anything that is wrong. Once we agree on that scope, we can price the role and equity against it.

Founders should welcome this precision. If the mandate cannot survive a paragraph in an email, salary negotiation is not the largest risk in the offer.

Know when to accept, pause, or walk

Your walk-away point comes from your best alternative, not from winning the last exchange. Roger Fisher, William Ury, and Bruce Patton defined BATNA in Getting to Yes as the best alternative to a negotiated agreement. The Harvard Program on Negotiation emphasizes the practical question: what will you actually do if this deal fails? For a candidate, the answer might be another offer, staying in the current job, contracting, taking time off, or continuing the search.

A BATNA is not your aspiration. "I can probably find something better" is a forecast. "I will remain in my current role at known compensation while I interview" is an alternative. Price its income, risk, timing, learning, workload, and personal cost. Then compare the offer with that alternative.

Use this decision sequence after the final counter:

1. Write the final terms and unresolved conditions in one place.
2. Compare them with your actual alternative, using the same time horizon.
3. Check whether any deal breaker changed during negotiation.
4. Decide once, then communicate the decision without reopening settled points.

Accept plainly:

Thank you for working through the package. I accept the [role] offer under the terms in the written offer dated [date]. Please send the final documents and next steps.

Decline without prosecuting the company:

Thank you for the offer and the time the team invested. I have decided not to accept because the final compensation and scope do not fit what I need for my next role. I appreciate the direct conversations and wish the team well.

Pause when a material term remains unclear. Do not sign and hope the document means what someone said on a call. Ask for a corrected offer or an addendum. Equity class, vesting, location, remote status, title, start date, and contingencies belong in the final record if they influenced your decision.

A recruiter who answers a reasonable counter with shame, threats, or a sudden change in role scope has given you information about the employer. A company can say no without behaving badly. You can also hear no without treating it as disrespect. Walk when the deal is below your minimum, when material claims will not be put in writing, or when the process reveals conduct you would not accept as an employee.

Managers need a salary process that can survive daylight

Employers get better negotiations when they define the level, approved band, and decision authority before the first recruiter call. A candidate should not need theatrical confidence to discover information the company already uses internally. Publish the range where law or policy requires it, train recruiters to explain what it covers, and document why an offer sits at a particular point.

The EEOC advises employers to set compensation criteria, apply them consistently, and avoid basing pay solely on prior salary. That guidance makes operational sense beyond legal compliance. Prior salary imports another employer's decisions into yours. Price the work, the level, and the evidence your own interview produced.

Founders often create inequity by handling every counter as a special contest. The confident candidate gets an exception, the quiet candidate accepts the first number, and six months later two people doing comparable work have a gap nobody can explain. A written band does not remove judgment. It forces the company to name the judgment and keep a record of it.

Use four checks before approving an exception:

• Does the interview evidence support a different level or position in the band?
• Would we make the same decision for an existing employee with comparable scope?
• Which compensation component can change, and who owns that budget?
• Can we explain the decision later without referring to the candidate's negotiating style?

A Team & AI Audit from oleg.is examines roles, delivery work, and engineering cost over five business days, with a fixed $5,000 price and a guarantee of at least $50,000 in identified annual savings or the audit is free. Salary bands are only one part of that review, but unclear roles and unclear pay usually point to the same missing operating discipline.

Candidates notice that discipline during negotiation. A company that can explain its band, level, equity, and approval path can still hold a firm line. The difference is that both sides know what the no means. Make the offer defensible before asking a candidate to decide quickly.