1. LandOffer
  2. Blog
  3. All articles
  4. Desired Salary on an Application: Handle Ranges, Single Numbers, and Required Fields

Job search

Desired Salary on an Application: Handle Ranges, Single Numbers, and Required Fields

Answer desired salary fields with clear currency, pay period and compensation scope. See worked range, single-number and hourly examples before submitting.

9 min readLandOffer team

For a desired salary question, give an expectation you can explain for this role, in the requested currency, pay period and compensation component. Use a meaningful range when the form permits it. If it requires one number, choose a real target you are willing to discuss. Zero, one and an arbitrary high figure are not reliable substitutes for an answer you mean.

Start with the employer's current posting, rather than a salary answer saved for another job. You can find a relevant opening among recent roles on LandOffer.ai, then read its compensation wording and application instructions together. LandOffer publishes this guide. Sources were checked October 13, 2026; every candidate, role, pay amount and completed answer below is fictional, not a current market benchmark or tested application result.

A candidate aligns a salary expectation with a ruler marked by currency, pay period and compensation scope before writing an application answer. Editorial illustration.

Define the question before choosing an amount

“Desired annual base salary” asks about future recurring base pay. “Minimum acceptable hourly rate” asks for a lower boundary. “Expected total compensation” asks about a package whose components need definition. These are different questions, even if a browser or extension offers the same saved number for all three.

Write down the currency, period and component beside the label. A dollar symbol alone may leave the currency unclear. A monthly salary and an annual salary differ even when both refer to base pay. Total compensation might include variable pay or equity. Keep those components separate so the employer does not read a package target as the recurring base salary you expect.

Desired pay and your private minimum can also differ. Your desired amount is the expectation you communicate; your private minimum helps you decide whether an opportunity is feasible under stated conditions. If the question asks for the least pay you would accept, enter a lower boundary you could actually consider under the stated conditions. A range’s lower bound and a question about your firm minimum need separate reading.

Salary history is another category. A question about current or previous earnings is not answered accurately by copying a new-role expectation. This guide addresses desired pay; questions about whether an employer may request history require the relevant jurisdiction's guidance. Do not infer that legal answer from a numeric box.

Build an expectation from the actual opportunity

Read any posted band with its location, level and employment arrangement. The upper endpoint is not an individual offer. If several locations or levels share one posting, establish which band applies before treating the full interval as available to you. The separate guide to reading salary ranges covers that posting-level comparison.

Use comparable public wage information as context. CareerOneStop's wages tools describe occupation and location comparisons. Match the work performed, geography and pay definition; a national occupation figure does not establish the right expectation for one senior platform role. Note the data reference period as well as the day you looked it up.

The BLS OEWS FAQ defines its wage measures and median. Its wage estimates exclude nonproduction bonuses and employer costs of nonwage benefits, while including some items beyond base rates, such as commissions and production bonuses. They are not a total-compensation estimate. The occupational median separates the higher-paid half of workers from the lower-paid half in the measured population. It does not determine this employer's budget or your individual target.

Use that context alongside the responsibilities you can demonstrate, the employer's stated band and your own requirements. Keep your private affordability calculation separate from the professional explanation of your contribution. Neither an aggregate statistic nor a percentage increase over your last job automatically produces a defensible desired salary.

Translate the same expectation into the available field

Read the complete question and adjacent help before typing. Greenhouse's employer documentation shows that employers can configure custom questions, descriptions and required responses. A familiar ATS brand does not guarantee identical question wording across companies. That documentation does not establish a universal salary-screening rule.

Form you encounter A usable approach Check before proceeding
Optional free text State a defined range, or use a truthful discussion response if permitted Does the question nevertheless request a specific amount?
Required free text Give an expectation with currency, period and component Can the full wording fit without losing its meaning?
Separate minimum and maximum Enter the bounds you intend to communicate Are both boxes asking about expectations, or is one a firm minimum?
One required numeric field Enter one real expectation in the stated unit Is it annual, monthly or hourly; base or total?
Fixed salary bands in a dropdown Choose a band consistent with your expectation Does selecting it imply willingness to accept its lower end?
Required field with unclear units Resolve the missing definition before inventing an amount Is there employer guidance or an official support channel?

If text is allowed, a concise answer can say: “Targeting $140,000–$150,000 USD in annual base salary, depending on confirmed responsibilities. Bonus and equity would be discussed separately.” Use that structure only with your own researched numbers and actual conditions.

“Open to discussion” can honestly describe flexibility, but it leaves the amount unknown. It is not a universal solution for a prompt explicitly requiring a range. If the employer requests one number, decide whether you can provide one you mean; do not assume the text response will be accepted or interpreted favorably.

Worked example: one role, three completed answers

Priya is a fictional backend engineer considering a fictional opening with a $125,000–$155,000 USD annual base band for her location. The work concerns API ownership and production reliability. She has evidence for those responsibilities and, for this exercise, would communicate a $140,000–$150,000 desired base range. Her private floor under the stated conditions is $132,000. All figures are invented.

She keeps the floor private because the question asks for desired pay, not the least she would accept. The band overlaps her desired range; that establishes possible alignment, not an offer or evidence that the maximum is available to her.

Fictional form variant Priya's completed draft Meaning retained
Desired annual base salary, USD; text allowed $140,000–$150,000 USD annual base, depending on confirmed responsibilities; bonus and equity separate A defined range with a scope condition
Desired annual base range, USD; two number boxes Minimum: 140000; maximum: 150000 Bounds of the communicated desired range, not her private floor
Desired annual base salary, USD; one number required 145000 One target she genuinely wants to communicate

Priya chooses $145,000 because it represents her target in this example. Its position at the range's midpoint is incidental; there is no general rule to average the endpoints. She would need a different answer if the prompt asked for her minimum, total compensation or an hourly rate.

Her private record says: “Role BE-42; local annual USD base band $125,000–$155,000; unsubmitted answer draft 145000; target range $140,000–$150,000; bonus/equity separate; responsibilities still to confirm.” The record makes the number interpretable later. It does not say the employer accepted her conditions, and this example does not submit any application.

Check hourly and annual assumptions separately

An hourly rate needs hours and paid weeks before it becomes an annual estimate. Record those assumptions explicitly, especially for fixed-term, part-time or contract work. A larger annualized headline can conceal fewer paid weeks or a different benefits arrangement.

Consider Ellis, another fictional engineer. A posting describes $60 USD per hour for a planned 40-hour week over 46 paid weeks. For the exercise, all planned hours are paid at that rate. His planning estimate is $60 × 40 × 46 = $110,400. Multiplying by 52 weeks instead gives $124,800, which adds six weeks not included in this scenario. Neither calculation guarantees actual earnings.

The next application field says only “Desired compensation” and accepts one number. Ellis does not enter 110400 merely because he just calculated it. The posting uses an hourly rate, while the field does not say whether it wants hourly or annual compensation. An accepted numeric entry would not resolve that ambiguity.

A fictional hourly-pay example separates forty hours across forty-six paid weeks from an unsupported fifty-two-week assumption, leaving an ambiguous salary field awaiting clarification.

Ellis saves the application draft if that function exists and prepares this question for the employer's listed recruiting contact: “For role CT-18, the posting states an hourly USD rate, but the required ‘Desired compensation’ field has no pay-period label. Should this field contain an hourly rate or an annual amount?” No message is sent in the example, and no employer reply is invented.

The completed decision is to hold that field pending clarification. If confirmed hourly, he would enter 60 only if that is his actual desired rate. If confirmed annual, he would reconsider what annual commitment is being requested; his arithmetic estimate should not automatically become a salary expectation for a different arrangement.

Handle validation without changing the answer's meaning

A form may reject currency symbols, commas, decimals or a range. Follow its visible instructions and validation message. Removing separators from 145,000 to enter 145000 can preserve meaning when the currency and annual-base unit are already clear. Changing 145000 to 145, or entering 0 to bypass the question, changes the record.

For a dropdown, check both the selected label and surrounding explanation. If a band straddles your target, selection may communicate less precision than you intend. Use an available clarification field or recruiting conversation to explain the actual expectation. Do not select a knowingly unsuitable band solely to continue.

If a required field remains ambiguous or cannot express an answer you can support, save the question, restriction and job identifier. Use the employer's designated application-help route. Keep any employer-specific placeholder instruction with that role's record rather than reusing it everywhere. If a deadline arrives first, clarification does not guarantee an extension; decide whether to pause or use another officially offered route.

You cannot determine a hidden filter's behavior from whether the form accepts your entry. This review did not test employer screening, recruiter interpretation or offer outcomes. Treat syntax validation as evidence that the field accepted the format, not that your pay expectation passed a hiring decision.

Save the context for the next conversation

Before submission, reread the final answer on any review page. Check for an older autofilled amount, a changed currency selector or a pay-period mismatch. Record the exact question and entry alongside the job ID, location, level, posting date checked and any material unresolved condition. Retain a private copy without collecting unrelated personal information.

An initial expectation is not a substitute for reviewing an eventual written offer. CareerOneStop's negotiation guidance concerns the offer stage and recommends evaluating responsibilities, benefits, working conditions and personal needs. Its suggestion to wait for an offer before asking about salary does not solve an earlier mandatory form field; the field-handling method here is our editorial recommendation.

If the role changes, compare its revised responsibilities, location and pay definition with your saved record, then explain any changed expectation. For example, a newly required on-call schedule or a different location may justify reconsideration. If you entered the wrong unit, identify the mistake and ask for the available correction route; avoid a duplicate application created just to replace the number. Save the correction request and keep the revised answer distinct from the original record.

Choose one opening from recent tech jobs on LandOffer.ai, record its pay question verbatim, and prepare a defined range or single target in the requested format. Leave the draft unsubmitted until its currency, period, component and number all express the expectation you intend.

Sources and Further Reading