How interview courses differ by the goal you have

Interview courses are organized by goal, and the goals do not overlap much. Passing a coding screen, answering a competency question, closing a pay conversation and landing a first hourly job reward different kinds of preparation.

Most interview training spends a disproportionate amount of time on one moment: the question about salary expectations. It is treated as the hinge on which the whole outcome turns, and it is usually taught as a contest over who says a number first.

That framing is wrong often enough to be worth correcting. The correction is also what separates a course worth taking from one recycling folklore.

What to take away

How interview courses differ by the goal you have

Compare them on four things: who gives the feedback, which situations get rehearsed, what the price covers, and whether the program teaches you to research a range or supplies a number.

To pass a coding or technical screen. These programs sell drilling plus mock interviews with working engineers, and they cost the most.

To answer behavioral and competency questions. The method here is a structure for stories, not algorithms, and the courses are cheaper.

To negotiate pay once you have an offer. These courses are priced for people with a number on the table, not for people still answering screening questions.

To get a first job, an hourly role, or a return after time out. Price and format change again: free public services and courses under $150, not $5,000 cohorts.

To pass a consulting case interview. Case and fit interviews need their own rehearsal, and this market is small.

To switch fields with unrelated experience. Here the course looks more like coaching, and one model takes payment from your future salary.

• Pathrise works on an income share agreement, typically around 9% of first-year salary up to a cap, with nothing owed below a salary floor.

The price list settles the argument about whether one program fits every goal. Negotiation runs from a $15 book to a $1,750 course, while a coding screen starts in the thousands.

Why the first number matters less than the folklore says

Anchoring is a real effect. It is also a much weaker force than the machinery on the other side of the table.

By the time anyone asks what you want, several things are usually already decided. The role has been scoped and tied to a level. That level has a pay range set before you applied. The recruiter knows it, and someone approved the budget.

Your number does not create the range. It can move you within it, or start a discussion about whether you belong at a different level.

The number you say is one input into a process with pre-set boundaries. A figure a little low will not usually get you the bottom of the range if the process levels you in the middle. A figure far above the range will not raise it; it will more often end the conversation.

What moves the outcome, in rough order: the level you are placed at, whether there is a competing offer, how the employer's structure handles exceptions, and where in their cycle you arrive. Your opening figure sits well below those.

Three different questions that sound the same

The same words mean different things depending on when they arrive.

On an application form. This is usually a filter, and often a required field. It is asked before anyone has assessed you, and it is the least informed moment in the entire process.

In a recruiter screen. Here the question is genuinely mostly logistical. The recruiter is checking whether you are within reach of an approved range, so that nobody wastes four rounds discovering otherwise. Treating this as an adversarial moment misreads it.

At or near offer stage. Now the question is about closing. The level has been decided, an internal case has been made, and the range is known to everyone but you.

Asking for their range first

The most useful habit is to ask for the employer's range before offering yours. Ask it as a practical question rather than a challenge: what range has been approved for this level, and how many levels does the role span?

This works more often than people expect. Recruiters are usually allowed to say. In a growing number of places, employers must publish a range or face limits on asking about your pay history.

Rules differ by jurisdiction and change, so check what applies where you are. A question phrased around their constraints is easier to answer than a demand.

If they decline, that is information too. It tells you something about how the process is run.

Answers that do not corner you

When you do have to say something, three properties make an answer safe. It should be a range rather than a point. It should be tied to the level rather than to you personally. And it should leave the door open to revision once you know more about the role.

What that sounds like in practice is short. Say you are looking for a range consistent with the level as described, that you have researched it and can share your reasoning, and that you would rather understand the scope before committing to a figure. Then say the range if pressed.

What to avoid: a precise single figure early, a justification based on your personal expenses, a threat, and, most damaging, a number you have not researched, because you will either be embarrassed by it or bound to it.

What a course can teach about the pay conversation, and what it cannot

Interview training earns its money on the parts that are genuinely skills: structuring an answer, describing your work at the right altitude, handling a question you cannot answer, and rehearsing under mild pressure. These improve with practice and with feedback from someone competent, which is exactly what a course provides.

What a course cannot do is give you the range. That range depends on the role, the employer, the level, and the place, and it changes.

Be suspicious of any program that gives a general figure for a kind of job as a fact, or teaches a scripted number. The script ages fastest and transfers worst.

Judging a program, then, comes down to a few questions:

Doing the research the course cannot do for you

Before any conversation, build a range from more than one kind of source, and know what each measures. National statistics give you a defensible baseline for a broad occupational category. Posted ranges in current advertisements give you the specific market. People doing the job give you the level detail neither of the others carries.

In the United States the statistical baseline comes from the Bureau of Labor Statistics. Its wage program states what its estimates include and exclude on its questions and answers page; read that before the figure. The site refuses an automated request while serving the page normally in a browser. Other countries have an equivalent national statistics office.

At a small employer, structured bands may simply not exist. Small businesses often set pay case by case, within whatever the business can carry. General guidance on how they operate is published by the relevant national small-business body, such as the SBA business guide in the United States.

If you take one thing

Ask what level the role is, and what range that level carries, before you say a number. The level decision is worth far more than the anchoring contest everyone is preparing for.

Related on this site: interviews generally, common questions and how to structure answers, and how a level becomes a range in the first place.

Common questions

Should I really refuse to name a number first?

You should ask for theirs first, which is not the same as refusing. The person asking has a range written down. If they will not give it and you have a well-founded range of your own, naming yours is reasonable.

What if I name a range and they offer the bottom of it?

That is the normal result, which is why the bottom of your stated range should be a number you would accept. Stating a range whose floor you would decline is the most common self-inflicted wound in this conversation.

Is the first number really an anchor?

It matters less than the folklore claims, because the band was decided before you arrived. Anchoring moves your position inside a range; it does not move the range.

Can a course teach me to handle the silence?

It can give you rehearsal, which is the only thing that works. The skill is entirely about having practiced with another person rather than about knowing that silence is a technique.

What should I do if I have no competing offer?

Argue from scope instead of from pressure: what you would decide, commit and affect, and which level that corresponds to. That argument is available to everyone and it is the one the employer's own system is built to answer.