For most applications, leave the desired salary field blank when that option exists, or enter "Negotiable" in a free-text box. This protects your negotiating leverage and keeps applicant tracking systems from screening you out before a human sees your resume. When a number is required, give a researched range tied to the role and location rather than a single figure, and if you must pick one number, state your target, not your minimum.
TL;DR:
- Leaving salary fields blank or marking them "Negotiable" preserves negotiation leverage and avoids early screening by applicant tracking systems.
- Providing a researched salary range based on median and 75th percentile wage data from the Bureau of Labor Statistics offers a defensible and flexible figure for employers.
- When forced to choose a single number, stating your target near the midpoint of your range prevents undervaluing yourself and offers room for negotiation.
- During early interviews, deflect early salary questions politely and redirect the conversation to role fit or the employer's budget range.
- Wait until receiving a formal job offer before negotiating salary, and support your counter with market data and specific value examples.
Table of Contents
- What to enter on an application: blank, negotiable, a range, or one number
- Handling required numeric fields and ATS workarounds
- How to answer during phone screens and interviews
- How to research and pick defensible numbers
- When to negotiate and how to reopen pay after an offer
- Updating desired salary in later communications
- Common mistakes to avoid when stating desired salary
- Examples of well-crafted desired salary statements
- Primary sources and tools to build your salary range
- Setting your range is easier when your job search is already organized
- Sources
- FAQ
What to enter on an application: blank, negotiable, a range, or one number
Your best move depends on the field itself. Some applications let you skip the question, some accept text, and some demand digits only.
- Leave it blank whenever the form allows it. An empty field can't be used to screen you out on price before the employer has met you, which preserves your leverage for later negotiation.
- Write "Negotiable," "Open," or "Market rate" in free-text fields. This signals flexibility without anchoring the conversation to a number you might regret.
- Give a range when a range is requested. Format it clearly: "$48,000–$57,000" for salaried roles or "$15–$18/hr" for hourly ones, with your low end set at the minimum you'd accept and your high end near what a strong candidate could realistically get.
- If forced to name one number, name your target, not your floor. Recruiters tend to treat a single figure as a starting point for their own math, so a target near the midpoint of your range gives you room to move without underselling yourself.
An entry-level candidate applying for an hourly warehouse job might write "$16–$18/hr." A mid-career marketing manager applying for a salaried role might write "$72,000–$85,000." Both formats tell the employer you've done your homework without boxing yourself into a single number too early.
Handling required numeric fields and ATS workarounds
Many applicant tracking systems reject blank or text answers in salary fields, and some employers set automatic cutoffs that filter out anyone above or below a threshold. That's a real risk if you enter something extreme.
- Try a placeholder pattern like "000" or "99999" only if the system's help text explicitly allows a placeholder or non-numeric entry; otherwise this can trigger an outright rejection.
- When placeholders are blocked and a real number is required, enter a conservative, market-based figure near the low to middle of your researched range instead of your ideal number.
- Convert pay periods accurately so the figure matches the field's format: divide annual salary by 2,080 hours for a rough hourly rate, multiply an hourly rate by 40 for a weekly figure, and multiply weekly pay by 52 for an annual estimate.
Pro Tip: Never enter a number you can't stand behind in an interview. A placeholder is a workaround for a rigid form, not a chance to misrepresent your expectations.
How to answer during phone screens and interviews
Recruiters often ask about salary early to filter candidates before investing more time, but you don't have to be the first to name a number.
- Deflect once, politely: "I'd love to understand the budget you have in mind for this role before we discuss numbers."
- Redirect toward fit: "I'm focused on finding the right role first. What range has the team budgeted for this position?"
- For hourly roles: "What's the pay range you're working with for this position?" works just as well and sounds natural for shift or contract work.
Once you have their range, respond with confidence: "Based on my research and experience, $65,000 to $72,000 would work well for me, and I'm glad to discuss specifics once we're further along." If a recruiter pushes for a firm number in an early screen, repeat your deflection once, and if they push again, state your target from your researched range rather than staying silent, since refusing outright can end the conversation.
How to research and pick defensible numbers
A believable range starts with real wage data, not guesswork.
- Look up the role and location. Use the Bureau of Labor Statistics Occupational Outlook to find median pay and percentile breakdowns for your occupation.
- Extract the median and 75th percentile. These two numbers frame a realistic low and high for your range.
- Set your low, mid, and high, then adjust. Add a premium for extra years of experience, in-demand skills, or a higher cost of living, and factor in benefits like healthcare or retirement matching when comparing offers.
BLS occupational wage data breaks down median and higher-percentile pay by role and region, which lets you build defensible salary numbers instead of relying on a single average. Anchoring your range near the median and 75th percentile gives you room to negotiate upward while staying within what most employers have budgeted for the role.
When to negotiate and how to reopen pay after an offer
Wait until you have a formal offer before negotiating hard. CareerOneStop's negotiation guidance recommends postponing salary talks until that point, partly because future raises and bonuses are often calculated as a percentage of your starting pay, so a stronger opening number compounds over time.
- Ask for 24 to 48 hours to review the offer before responding.
- Use that time to pull your BLS-based range and prepare one or two concrete examples of the value you bring, such as a project outcome or a specific skill the role requires.
- Present a counteroffer tied to your research: "Based on market data for this role, I was hoping for something closer to $78,000. Is there flexibility there?"
- If the base salary is fixed, ask about alternatives like extra vacation days, a sign-on bonus, or an early performance review tied to a raise.
Pro Tip: A counteroffer grounded in a specific number and a specific reason lands better than a vague request for "more."
Updating desired salary in later communications
Your stated expectations aren't locked in once you submit an application. If your research turns up a stronger range after you've submitted, mention it early in a follow-up email or during your next conversation rather than waiting until an offer is on the table, since a late change can look inconsistent. If a recruiter asks you to confirm your range again during a later stage, restate it exactly as you gave it before unless new information, like a broader job scope or a location change, justifies an update.
When a role's responsibilities shift during the interview process, such as an added direct report or expanded scope, it's reasonable to revisit your number and say so plainly: "Given the expanded responsibilities we discussed, I'd like to revisit my range to reflect that." Keep any written record, like an application portal or an email thread, consistent with your verbal statements so nothing looks like a contradiction later. If you're applying to multiple roles with Oink's curated matches, it helps to settle on one baseline range for your profile and adjust it per role only when the job level or location genuinely differs; our guide on describing the job you want to an AI covers how to phrase those preferences so your matches reflect them accurately.
Common mistakes to avoid when stating desired salary
A few recurring errors cost candidates leverage before negotiations even start.
Giving a single low number too early is the most common one. Once you've said $50,000, an employer has little reason to offer more, even if the role's budget goes higher. Entering wildly inflated numbers to "leave room to negotiate down" backfires just as often, since it can trigger an ATS cutoff or make you look out of touch with the role's actual pay band. Skipping research entirely and guessing is another frequent misstep. A number pulled from memory or a friend's experience rarely matches what the BLS wage data shows for your specific role and region.
Ignoring total compensation is a subtler mistake. Comparing only base salaries across offers overlooks benefits, bonuses, and retirement contributions that can shift the real value significantly. Finally, changing your number inconsistently across an application, a phone screen, and a final interview raises doubts about your judgment. Keep your figures aligned unless the role itself has changed.
Examples of well-crafted desired salary statements
The strongest statements tie a number or range to research and stay flexible enough to invite discussion.
For a free-text field: "Negotiable, open to discussing based on role scope and total compensation." For a required range: "$62,000–$70,000, based on market data for this role and region." For an hourly position: "$22–$26/hr, depending on schedule and benefits." In an interview, once you have the employer's range: "Based on what you've shared and my research, $75,000 feels right, and I'm happy to discuss the full package." Each version does the same job: it shows you've thought about the number without locking yourself into the lowest one you'd accept.
Primary sources and tools to build your salary range
The Bureau of Labor Statistics Occupational Outlook is the strongest source for median and percentile wage data by occupation. The EEOC's guidance on pre-employment inquiries clarifies that there's no federal ban on salary-history questions, though many states and localities restrict them. CareerOneStop's negotiation resource offers a practical workflow for timing your ask and building a counteroffer. Use BLS for numbers, EEOC for legal context, and CareerOneStop for the negotiation steps themselves.
Setting your range is easier when your job search is already organized
Once you've settled on a defensible salary range, the next challenge is finding roles that actually match it without combing through dozens of listings by hand. Oink pulls job postings from multiple boards, filters them against your profile, including your target salary, location, and seniority, and explains why each match fits before sending it to you on Telegram. That means you spend less time filtering out roles that don't meet your range and more time on applications worth your effort. Oink does not submit applications or guarantee interviews, and it won't write your resume for you, but it does keep your shortlist focused so the salary research you just did actually pays off. If low response rates have been a problem, our guide on what to do after applying to 200 jobs with no response covers other signals worth checking beyond salary entries.
Create a free Oink profile at Oinkjobsearch to start receiving curated Telegram job matches built around the range you just set.
Sources
- Bureau of Labor Statistics — Occupational Outlook / Occupation finder
- CareerOneStop — Negotiate your salary
- U.S. Equal Employment Opportunity Commission — Pre-employment inquiries and financial information
FAQ
What is a desired salary for $20 an hour?
A defensible answer starts with a range rather than a flat $20, such as "$18–$22/hr," based on your researched market rate for the role and location using BLS wage data. If a form requires one number, use your target within that range rather than the lowest figure you'd accept.
What is a desired salary for a 17 year old?
For a first job or entry-level role, it's reasonable to reference local entry-level or minimum wage rates as a floor and build a small range from there, since career-center guidance recommends prioritizing flexibility for first-time job seekers. Writing "Negotiable" or a modest range like "$13–$15/hr" both work when the application allows text.
Should I put 0 for desired salary?
No, entering zero can look like an error or a lack of preparation, and some applicant tracking systems may auto-reject or flag it. A better option is leaving the field blank if possible, writing "Negotiable," or entering a conservative market-based range instead.
What is the best answer to expected salary?
The strongest answer ties your number to research: a range based on median and 75th-percentile wage data for your role and location, adjusted for your experience. If pressed for a single figure, state your target near the midpoint of that range rather than your minimum acceptable pay.