That little box asking for your salary expectations on an application can feel like a trap. Go too high and you worry the resume gets tossed before a human ever reads it. Go too low and you leave real money on the table for years. The good news: with a bit of research and a clear strategy, you can answer this question in a way that keeps you in the running and protects your worth.
Why applications ask for salary expectations
Employers ask about salary expectations for a few practical reasons, and none of them are personal. Most often it is a budget filter. The role has an approved pay band, and recruiters use your number to sort candidates who fit from candidates who are out of range. Sometimes it is a screening tool to see how you think about your own value, and occasionally it is just a required field in an applicant tracking system that HR never customized.
Knowing the intent helps you relax. Your goal is not to win a negotiation inside a form field. Your goal is to stay in the conversation long enough to make your case in an interview, where you have far more leverage.
Do your homework before you type a number
Never answer the salary expectations question off the top of your head. Spend fifteen minutes gathering real data so your number is grounded, not a guess.
- Check the job posting itself. Thanks to pay transparency laws in states like California, Colorado, New York, and Washington, many listings now include a range. If it is there, you already have your answer band.
- Use free salary data. Glassdoor, Levels.fyi (especially for tech), Payscale, LinkedIn Salary, and the U.S. Bureau of Labor Statistics all give you market rates by title and location.
- Adjust for your city and level. A "senior analyst" in Austin and one in San Francisco can differ by tens of thousands of dollars. Match the data to where the job actually sits.
- Factor in remote pay. Some companies pay by your location, others by a national band. If it is remote, aim for the middle of the national range.
Write down three numbers: the floor you would genuinely accept, a comfortable target, and a stretch number the market can support. These three anchors drive every answer below.
The safest answer is a researched range
When the field accepts text, a range is almost always your best move. It signals flexibility while protecting your floor. The key rule: the bottom of your range should be a number you would actually say yes to, because employers tend to hear the lowest figure you give.
A clean format looks like this: "Based on my experience and market rates for this role, I am targeting $75,000 to $85,000, and I am open to discussing the full compensation package." That last clause matters. It reminds them that base salary is only one part of the picture, alongside bonus, equity, and benefits.
Keep the spread reasonable, usually around 10 to 15 percent. A range of $60,000 to $110,000 reads as if you have no idea what the job pays.
What to do when the field forces a single number
Some online forms demand a numeric entry and reject text, ranges, or the word "negotiable." You have a few honest options here.
First, if the form allows it, enter the middle of your target range as a whole number. This is the cleanest approach and rarely hurts you, because there is almost always room to discuss it later.
Second, if you truly want to defer, some applicants enter a placeholder like 0 or a very high number such as 999999 to signal "let us talk about this." Be careful with this. Automated systems sometimes filter on that value, and a recruiter may read it as evasive. If you use a placeholder at all, only do it when the field is clearly required and you plan to address pay directly in your cover letter.
Third, when the question sits inside a cover letter or free response box rather than a strict field, you can write: "I would prefer to learn more about the role and its full scope before naming a specific figure, though I am confident we can find a fair number." That is a legitimate answer for many roles.
When you can defer the conversation
You do not always have to commit to a number on the application. If the posting does not require it, leaving a thoughtful "open" or "negotiable" note is fine, especially for senior or specialized roles where the scope is still fuzzy. Deferring works best when you have unusual skills, when the job description is vague, or when you are early in the funnel and want the interview to establish your value first.
That said, ignoring a clearly required field can get your application auto-rejected. Read the form carefully and answer what is genuinely mandatory.
A quick real-world example
Maria is applying for a marketing manager role. The posting lists no range. Her research shows the position pays $70,000 to $90,000 in her metro area, and comparable roles at her level cluster around $80,000. Her floor is $72,000.
The application has an optional salary expectations field that accepts text. She enters: "$78,000 to $88,000, open to discussing the total package." Her floor sits safely below her stated bottom, her target is inside the range, and she has invited a conversation instead of drawing a hard line. If the field had demanded a single number, she would have entered $82,000 and addressed flexibility in the interview.
Make sure the rest of your application earns the number
Here is the part people forget. Your salary expectations only land if the recruiter believes you are worth them, and that belief starts with a resume that actually gets read. Many resumes never reach a human because the applicant tracking system garbles the formatting or misses key terms from the job description. If the parser cannot cleanly pull your title, dates, and skills, your carefully chosen salary number never gets a fair look.
Before you submit, it is worth seeing exactly what a parser extracts from your resume. Bounce offers a free "Beat the Bots" scan at careerbounce.io that shows you the literal text a machine reads from your file, so you can catch problems a human eye would miss. And when you want your resume tailored to a specific posting using only your real experience, Bounce Studio builds a version you can defend line by line in the interview. A resume you can stand behind is what turns your salary expectation from a hopeful guess into a number you can justify.
Common mistakes to avoid
- Lowballing to seem safe. A number set too low can anchor every future raise and even make you look junior. Trust your research.
- Giving a wild range. Spreads of $40,000 or more signal uncertainty. Keep it tight.
- Forgetting total compensation. Base salary is one lever. Bonus, equity, PTO, and remote flexibility all count, so leave room to weigh them.
- Skipping required fields. Do not let a blank box auto-reject you when a simple, researched number would keep you in.
Answering salary expectations well is really about preparation. Do the research, pick a range you can defend, and let the interview do the heavy lifting. Everyone bounces back, and knowing your worth on paper is a solid place to start.