Not sure whether to list a single number or a salary range? Learn how to choose the right approach for desired salary and avoid common application mistakes.

If a job application asks, “What is your desired salary?” you’re not alone—this question can decide whether you get screened in or out. The real challenge with should you put a number or a range for desired salary is that you’re trying to balance two competing goals: staying credible to recruiters and keeping enough flexibility for negotiation later.
In this guide, you’ll learn when a single number works best, when a salary range is smarter, how to calculate a range that doesn’t look arbitrary, and what to write when forms don’t let you enter both.
Here’s the simplest way to decide:
Most candidates should not pick a number “because it feels right.” They should pick the number (or range) they can defend with market research and that still keeps them open to the employer’s level and budget.
When employers ask for desired salary, they’re usually doing one (or more) of the following:
This is why your answer matters. It’s not just a negotiation move—it’s a signal.
If the posting is explicit about level (for example, “Senior,” “Manager,” “Level 3/5”), and the role is consistent with your experience, a number communicates confidence and reduces ambiguity.
Some application systems only accept a single salary figure. If that’s the case, you don’t have to guess wildly—use research and pick the number you’d be satisfied with if the offer is structured normally (base pay, expected bonus mechanics, typical benefits).
For example:
Some postings are vague: they say “will consider candidates at multiple levels,” or they list broad requirements that can map to more than one career tier. A range helps you avoid being dismissed because your number is slightly above (or below) what they initially budgeted.
If you’re early in the process and tasks might evolve—especially in fast-moving teams—a range can be more realistic than a single number. It also creates room to negotiate scope (“If I’m expected to lead X vs. contribute to X, how does compensation adjust?”).
A range is also a negotiation posture. It suggests you understand compensation isn’t one-size-fits-all and you’re willing to align on an offer that matches your impact.
A credible salary range is grounded in data and aligned to your constraints. Here’s a straightforward method:
In many cases, candidates choose a range that spans roughly 5–15% between low and high. That’s not a rule, but it’s a common way to stay credible. If the role is highly standardized and pay bands are tight, narrower ranges often read as more professional. If the role can flex significantly, slightly wider ranges may be appropriate.
If your number is far from the likely band, you might fail screening before you ever get a chance to discuss fit. A range can help—but only if the low end is plausible.
Extremely broad ranges can reduce credibility. You want to appear flexible, not uncertain.
Most application forms implicitly mean base salary. If you switch to total compensation without clarity, you can create confusion for recruiters who are comparing apples to apples.
Even if you’re open to negotiation, your answer is still used for routing. Treat it like a decision input, not a casual preference.
Not all systems handle ranges the same way. Here are practical approaches based on the input field:
If the form doesn’t ask, you can still prepare. When you do get asked later, use the same principles: market data, role level, and flexibility anchored to real constraints.
Instead of treating desired salary like one-time trivia, think of it as a stage-based strategy:
| Stage | Goal | Best approach |
|---|---|---|
| Application (first pass) | Pass screening and maintain credibility | Number if the level is clear; range if level/band is uncertain |
| Early recruiter conversation | Confirm fit and align on level | Be consistent; reiterate flexibility with boundaries |
| Interview / offer stage | Negotiate scope and total compensation | Discuss base + bonus/equity/benefits and tie to impact |
Salary expectations don’t exist in a vacuum. Even the best-number strategy can fail if the rest of your application isn’t aligned. Focus on:
If you’re applying across many systems, you’ll also want to reduce avoidable friction. A free way to streamline repetitive data entry is JobWizard, a Chrome extension that autofills applications on major platforms (including Workday, Greenhouse, iCIMS, Lever, Ashby, SmartRecruiters, Taleo, and 500+ others). It does not auto-submit without your review—so you can still make sure your salary answer and custom questions are exactly right before you send anything. (It also helps reduce repeated typing across long application forms.)
If you want to strengthen other application answers that often come up alongside compensation questions, these guides help:
It depends on how much flexibility you have and how the employer frames the question. If you’re confident in your target and want to be direct, use a number. If you’re open to negotiating or the job has a broad pay band, a range usually reads as reasonable flexibility—especially early in the process.
On many job applications, a range can work well because it signals flexibility without locking you in. However, if the form requires one value, choosing a well-researched number closer to your ideal (not your absolute minimum) is often safer than guessing low.
Start with your market research (job title, level, location, and years of experience), then set a range that reflects your walk-away floor and your ideal target. Many candidates choose a span wide enough to show flexibility but narrow enough to avoid looking vague—often a difference of roughly 5–15% between the low and high, depending on how standardized the role is.
If the form only allows a single number, enter the number you’d realistically accept while still staying aligned with your research. If you later get asked to discuss specifics, you can explain that you’re flexible within a band based on scope, level, and benefits.
If your number is significantly above the likely band, it can reduce callbacks. To protect yourself, use a range that includes your ideal but also a realistic lower bound, or choose a number that matches your best estimate of the role’s market value. You can also emphasize overall compensation (benefits, growth, impact) in later conversations rather than only focusing on base pay.
If the application doesn’t specify, base salary is usually the clearest anchor. In later interviews, you can broaden the discussion to total compensation—bonus, equity, health benefits, and other perks—especially if those components drive your true decision. Avoid mixing formats in a way that confuses screening systems.
JobWizard auto-fills applications, suggests resume improvements, and tracks every submission — so you can focus on landing interviews.