Read a sample: 1. Start With the Decision, Not a Guess
The salary question often arrives before you feel ready for it. An application asks for your expected pay. A recruiter wants to know whether you are in the right range. An interviewer mentions that the role has grown since the job description was written. Each situation can make you feel as though you need one perfect number immediately.
You do not. You need a decision that fits the information available at that stage.
A useful salary request is not a guess dressed up as confidence. It is a conclusion you can trace back to a particular job, a set of imperfect comparisons, and your own priorities. It can change when the job changes or when better information becomes available.
This book will help you move from evidence to a range you can explain. First, though, you need to identify what you are deciding. Are you choosing a number for an application field? Preparing for a first conversation? Comparing an actual offer with your current position? These are related decisions, but they do not require the same level of detail or the same response.
Starting with the decision also helps you avoid a common trap: treating the first number that comes to mind as if it were the answer. Your current pay, a figure a friend mentioned, and a salary you saw online may all be useful pieces of context. None is automatically the right request for a different job.
Before researching pay, describe the opportunity in ordinary language. The job title is a starting point, not a complete definition. Two employers can use the same title for positions with different responsibilities, authority, and expectations.
Write down what you know about:
- The main work the person will perform.
- The level of experience and judgment the employer appears to expect.
- Whether the role manages people, projects, budgets, or specialized work.
- The industry and type of organization.
- The location and expected work arrangement.
- What remains unclear.
You do not need a perfect job description. You do need enough detail to recognize when a comparison is weak. If you are considering a project manager position, for example, a salary figure for someone coordinating schedules may be less relevant than one for someone responsible for delivery, budgets, and senior stakeholder decisions—even if both people have the same title.
A career changer should pay particular attention to the work rather than the label. Your previous title may not look similar to the new one, but some responsibilities may transfer directly. At the same time, relevant experience does not make every comparison to an established specialist equally strong. The goal is to make an honest match, not to find the highest figure that can be attached to a familiar keyword.
If details are missing, record the gaps instead of filling them with assumptions. “May supervise a team” is different from “manages six people.” A range built on the first statement may need to change when you learn which is true.
Next, describe the immediate compensation decision in one sentence. Keep it specific enough that you can tell when you have made it.
You might be deciding:
- Whether to enter a figure in an application.
- How to respond when a recruiter asks about expectations.
- Whether a posted pay band is worth discussing.
- What range to share after learning more about the role.
- Whether to negotiate, accept, or decline a written offer.
Also note when the decision is due and what information you can reasonably obtain before then. A required application field may give you little time. An offer with a stated response date may allow you to request benefits details and ask questions, but not conduct an unlimited search.
The stage of the process affects how much confidence you can place in your conclusion. Early on, you may know the title, location, and a few duties. Later, you may know the reporting line, scope, performance expectations, and structure of the offer. Your early response can acknowledge that difference:
> “Based on what I know so far, I’m looking for a base salary in a range that reflects the role’s scope and the overall package. Could you share the budgeted range and tell me more about the responsibilities?”
That response asks for useful information without pretending you have already evaluated the whole opportunity. It may not be possible in a required numeric field, and an employer may still ask you to provide a number first. Later chapters address those situations. For now, recognize that a question about pay is often also a question about what you know—and what you still need to learn.
Two figures deserve separate places in your preparation: what you would like to earn and the least acceptable offer for the opportunity.
Your desired salary is a goal. It reflects the compensation you would be pleased to receive for the work, informed by evidence about comparable roles and your assessment of what you bring. It is not necessarily the highest figure you can find, and it need not be the first number you share.
Your minimum acceptable offer is a private decision boundary: the point below which you would not accept the job on the terms you understand. It depends on more than a salary database. Your financial needs, alternatives, benefits, work arrangement, risk tolerance, and career priorities can all matter.
These figures answer different…