How to Negotiate a Job Offer Without Guessing Your Number
Most people guess a salary number because they feel put on the spot. They name the lowest figure they would accept, or they repeat their current pay and hope it sounds reasonable. Both habits give away leverage before the conversation starts.
You do not need a script that sounds tough. You need a number you can explain, based on the role, your proof, and the full package. Build that before any recruiter asks.
Build your number from three inputs
The role as actually scoped. Read the posting again and list the real scope: team size, systems you will own, on call or travel duties, and whether the role manages people or budgets. A coordinator role that also trains new hires and owns scheduling is not the same job as a coordinator role that only processes requests. Scope is what you are pricing.
Your proof. Pull two or three results from your resume that match that scope directly. If the role needs escalation handling, your proof is the escalation work you already do, with scale stated honestly. This is the same work as writing strong bullets. See how to write resume bullets that prove your impact for how to turn duties into proof you can also say out loud in a negotiation.
The total package, not just base pay. List base pay, bonus if any, paid time off, schedule flexibility, training or certification support, and start date. Two offers with the same base pay can be very different once you count time off and schedule. Decide in advance which parts matter most to you, so you know what to ask for if base pay does not move.
Write your target as a range with a reason attached to each end. The low end is the smallest package that still fits the scope and your needs. The high end is what the scope plus your strongest proof supports. If you cannot explain a number, do not use it.
What to say when they ask for your range early
Early in the process, you often know the least about the role. It is reasonable to learn more before you commit to a figure.
Practical reply: I want to give you an accurate range. Can you share the approved range for this role and what the full package includes? Once I understand the scope fully, I can confirm where I fit in that range.
That is not evasive. You are asking for the information any careful candidate would need, and you are keeping the conversation on scope and fit.
If you are pressed to name a number first, give the range you built, name the scope it assumes, and keep the door open. For example: Based on the scope you described, including training new hires and owning the schedule, I am looking in the range I shared, depending on the full package including time off and bonus. If the scope changes, I am open to revisiting it.
Notice what that reply does. It ties pay to work, not to your last job or your personal bills.
A weak reply and a stronger reply
Situation: The offer comes in below your target.
Weak reply: That is lower than I wanted. Can you do more?
That gives the hiring team nothing to work with. More is vague, and there is no reason attached that a manager can take to an approver.
Stronger reply: Thank you for the offer. I am excited about the role and the team. Based on the scope we discussed, including owning scheduling for the full team and training new hires in my first quarter, I was expecting a base closer to the top of the range we discussed. If we can get the base there, I am ready to accept and agree on a start date. If base is fixed, could we look at a signing adjustment or an extra week of paid time off instead?
The stronger reply is specific, it restates the scope, it names a clear yes condition, and it offers a second path if base pay is fixed. That makes it easy for the other side to say yes to something.
Use LinkedIn and your network before the offer, not after
The best time to check whether your range is realistic is before the final interview. Talk to people who do the same work in the same market, look at current postings that list a range, and make sure your own profile supports the level you are asking for. If your profile still reads like your last role, fix that first. See fix your LinkedIn headline and About section in 30 minutes for a fast way to align your headline and proof with the role you want next.
Do not use a single posting or a single conversation as your only data point. Look for a pattern across several sources, then test it against the actual scope in front of you.
Mistakes that cost you leverage
Naming your current pay as your target. Your last salary reflects your last scope, not this one. Price the role in front of you.
Apologizing for negotiating. A short, polite ask tied to scope is normal professional work. Long apologies signal that you do not believe your own number.
Negotiating one item at a time over many days. Gather your full ask, make it once, and state what would make you say yes. Piecemeal asks frustrate hiring teams and weaken each later ask.
Accepting verbally before you see it in writing. Confirm the final base, title, start date, and any agreed extras in the written offer before you resign or decline other options.
Threatening to walk away when you would not. Only name a walk away condition you actually mean. Credibility is part of your leverage.
A checklist for today
Write the scope of your target role in five bullet points, from the posting and your interview notes.
Pick two or three proof points from your resume that match that scope exactly.
List the full package parts that matter to you, in priority order.
Set a range where you can explain both ends in one sentence each.
Practice the early range reply and the offer reply out loud once, so neither sounds rushed.
Bottom line
Negotiation is not about winning an argument. It is about pricing a clear scope with proof you can defend, and giving the hiring team a specific, reasonable way to say yes. Build your number before you need it, tie it to the work, and make one clean ask.
If you want help building that proof on your resume and LinkedIn profile before you negotiate, our team at Elite Resume Solutions can review both so they support the level you are asking for.


