The Salary Expectations Answer, Staged From Form Field to Final Round

A recruiter, an application form, or a hiring manager has just asked your salary expectations, and you have no offer in hand. This guide is for the candidate who has already researched their number and now has to deploy it in conversation, before they hold any leverage. It treats each pre-offer touchpoint as a separate decision, tells you whether to deflect, give a range, or give a firm number, and hands you the wording for that exact stage.

Most comp advice covers two other jobs: researching your market number, and negotiating an offer you already hold. The gap between them is where candidates get screened out. Naming a number under uncertainty is a judgment call that changes shape depending on where the question lands, and a single generic script cannot cover a text form field, an AI knockout, a live recruiter, and a hiring-manager repeat all at once.

Where the question lands, and why the stage decides the move

The salary question is not one question. It appears at four pre-offer touchpoints, and the correct move flips depending on which one you are facing. The order also matters: whatever number you name first becomes the anchor the offer gets built around.

The four stages, earliest to latest:

• Application form field. A box on the form: free text, a range picker, or a strict numeric input.
• AI knockout screen. An automated screen, often over SMS, where salary can be a hard filter checked before a human reads you.
• Recruiter phone screen. A live call where a recruiter confirms your expectations align with the budget.
• Hiring-manager round. The question repeated in an interview, testing consistency and fit to scope.

The single most useful thing to understand up front is that the rule protecting you at a live call actively harms you at a bot. On a phone screen you can fence: ask their range before naming yours. At an automated knockout there is no one to fence with, and a dodge is logged as a non-answer. This is a documented reversal, not a nuance, and it is the reason a one-size script fails.

Why anchoring is load-bearing here: Kahneman and Tversky showed that under uncertainty we are easily swayed by the first figure introduced, and that number becomes an anchor that is almost impossible to forget. In practice, companies rarely climb above the figure a candidate volunteers. The mechanism, selective accessibility, means the low end of your range is what lands in the recruiter's notes. That is why the decision is not the midpoint of your range. It is the bottom.

How to answer the application form field

Read the field type first, then match your entry to it. A free-text box, a range picker, and a strict numeric input are three different questions wearing the same label, and the right answer differs for each.

Treat an application salary box as an input field, not a final negotiation. Most applications use one of three fields: "salary expectations," "minimum salary," or "desired compensation," and they are often used to screen for fit. If a post asks you to state an expected salary, give a range you are comfortable with. If the form forces a single number, enter a base figure that reflects the center of your likely deal, not your dream outcome.

The minimum salary prompt is not the same as expectations. A "minimum" is a literal floor, and some candidates use it deliberately: enter the lowest number you would entertain to auto-filter employers you do not want to talk to, and make clear it is the minimum to entertain an offer, not to accept one. That turns the screening mechanic against the employer. Just do not answer a "minimum" prompt with your total compensation, because folding equity and bonus into a floor inflates your own floor and can create a mismatch. Give base only where you can.

I'm targeting the market range for this role, which I estimate at $128,000 to $150,000 base for this level in this metro, based on public benchmarks and comparable offers. I'm flexible on the total package depending on scope, equity, and bonus structure.

One caution on placeholders. Some older advice says enter "negotiable" or "000" if the form allows it. The newer AI-parsing sources contradict this directly: parsers may read those as evasion or auto-reject the entry. If the field is a strict numeric box feeding an automated screen, do not gamble on a placeholder. Enter a real number.

Clearing the AI knockout screen

At an automated screen, give a real, tight band and answer in short, parseable phrases. This is the one stage where "never name a number first" is the wrong instinct.

Many applicant tracking systems let recruiters set acceptable salary bands. If your stated expectation falls outside that range, the system can filter you out before any human reviews your resume, and this happens more often than candidates realize, especially for roles with strict budget constraints. High-volume hiring increasingly runs these knockouts over SMS through assistants like Paradox's "Olivia," where salary is a field the bot has to check before you reach a person.

The failure here is cleverness. Bots log a dodge as a non-answer, and some pipelines penalize it. So give a real number or a tight band you would actually accept, not "negotiable."

That said, a salary question is not automatically a knockout. Whether it filters you is "sometimes, but not by default." It becomes a hard filter only when the employer configures it as one. You cannot see the configuration from the outside, so the safe assumption is to answer as if it is a knockout: concise, numeric, and inside a band you would sign for.

Working the recruiter phone screen

On a live call, take your one deflection: ask the recruiter's range before you name yours. If they push, give your researched range and emphasize flexibility. Recruiters are trying to confirm that your expectations align with the employer's budget, and a range leaves room for more discussion later.

The deflection is not evasion, it is a fair request for the information you both need. The cleanest opening acknowledges what they are doing and offers a trade:

It sounds like you're trying to qualify me for a salary range. If you want to tell me what that range is, I'm happy to tell you if it's in the ballpark.

If they decline to share a range, acknowledge it professionally and offer your own, based on market research. When you name your band, keep it tight. The recommended width in a recruiter screen is roughly $20,000 to $25,000, or you can use plus or minus 10 percent around your target. A $50,000 spread reads as guessing and signals you have not researched.

There is a detail worth exploiting: precise numbers beat round ones. Research on anchoring found that precise figures like 287 rather than 300 produce better outcomes and read as more competent for the anchoring party. So "$142,500" lands as more informed than "$140k or $150k" and shifts concessions your way.

A single number hands them a bullseye, and the bottom of your range is the number that lands in their notes.