What Is Your Desired Salary? | HireFlow

11 min read

You're staring at a Greenhouse field that says "What is your desired salary?" and you're not sure whether to type your current pay, a round number you hope sounds reasonable, or negotiable and run. You don't want to get filtered out before someone reads your resume. You also don't want to anchor a low offer because you panicked and typed $75,000 when the band starts at $90,000.

I've screened thousands of applications where this field decided the next step before I opened the PDF. Desired salary means base pay you want going forward, not a confession of what you earn today. It's a band check, not a final contract. Before you submit tonight's batch, check your resume for free against the posting so the level you claim matches the salary range you're about to enter.

This guide explains what is your desired salary on US applications, how it differs from total compensation, when to use a range versus one number, hourly versus annual answers, copy-paste responses, and mistakes that get you filtered or underpaid.

What is your desired salary on applications?

Desired salary is the base pay you want if you accept the role. In most US corporate Workday and Greenhouse forms that means annual base in dollars before bonus, commission, or equity. It is forward-looking: what you need and want next, not a copy of last year's W-2 unless the form explicitly asks for current pay in a separate box.

Recruiters use your answer to see if you fit the approved salary band for the req. Bands are set before you apply. If your number sits far above the max, you may get filtered in high-volume pipelines. If it sits far below the min, some employers anchor offers low because you told them you would work cheap.

Application salary answers are alignment checks. Hard negotiation belongs after they decide they want you and name an offer number. Read how to negotiate a salary offer for that stage.

Recruiter filter: When you type $200,000 base on a role posted at $95,000 to $110,000, I know you did not read the req. That is a self-filter, not a power move.

Desired salary is narrower than desired compensation. Salary is base only. Compensation adds bonus, equity, sign-on, and sometimes benefits value. When a form says compensation, read what is your desired compensation for total rewards answers. This page covers base salary fields specifically.

Read how does salary pay work when you need to convert hourly, biweekly, or annual figures before you type into the portal.

Some employers publish salary only in the posting and ask desired salary to confirm you read it. Others hide the band and use your answer to sort reqs before human review. Either way, the field is not a personality test. It is data entry that must match role level, geography, and the proof on your resume.

Commission-heavy roles still often have a base salary field separate from OTE. Answer the base box with base. Mention OTE in comments only when the form provides a free-text notes field and the posting centers on variable pay.

How to answer what is your desired salary

Step 1: Read the field label and unit

Check whether the box wants annual base salary, hourly rate, or monthly pay. Workday and Greenhouse wordings vary. Hover help icons. Search the posting for published ranges like $85,000 to $95,000 per year.

If the posting shows a range, your answer should usually sit inside it unless your scope clearly exceeds the title level. Applying at $120,000 base when they posted $80,000 to $90,000 signals you skipped the req.

Step 2: Set a floor and target before you apply

Floor is the minimum base you would accept with a standard package. Target is what you want when scope and bonus match the posting. Research using role title, city, company size, and your proof points, not a round number from a friend in a different field.

Before: typing $100,000 because it feels round.
After: "$92,000 to $98,000 base, aligned with posted range and six years in this stack."

Step 3: Default to a range in free-text fields

Ranges reduce filter risk and give recruiters room inside the band. When the form accepts only one integer, use the middle of your range or your target if the posting supports it.

Copy-paste answers for salary fields:
"Desired base salary: $88,000 to $96,000, depending on level and scope. Open to discussion after learning more about the role."
"Targeting $72,000 to $78,000 annual base for this analyst title in Austin, consistent with posted band."
"Hourly equivalent: $38 to $40 per hour for full-time day shift, based on 2,080 hours annually."

Step 4: Convert hourly and annual correctly

Full-time hourly to annual: hourly rate times 2,080 hours for a standard 40-hour week. Annual to hourly: divide by 2,080. Do not guess. A $45 hourly answer on a form asking annual salary is $93,600, not $45.

Before: "$45/hour negotiable" in an annual salary box.
After: "$93,600 to $97,500 annual base for full-time RN day shift, aligned with posted band."

Step 5: Keep application and phone screen answers consistent

Recruiters repeat the salary question on intake calls. Use the same range you typed on the form. Changing numbers without a scope update erodes trust.

Phone script: "Based on the scope we discussed and market for this title in [city], I'm targeting $X to $Y base. I'm flexible on bonus structure once I see the full package."

Step 6: Separate current pay from desired salary

Some portals ask both. Current pay is history. Desired salary is what you want next. Do not copy last year's base into desired if your scope grew. Some states restrict current pay questions. Answer truthfully where required, but keep desired market-aligned.

When current pay is optional and below market, leave it blank when allowed and submit a researched desired range instead of anchoring to a low past number.

Step 7: Save what you submitted

Screenshot or log company, req ID, date, and range before submit. Recruiters reference it weeks later on phone screens. Track posting band when shown so you can compare offers to your documented floor.

A simple spreadsheet beats memory: Company, Req ID, Date applied, Desired range submitted, Posting band if visible, Recruiter name, Phone screen date. When an offer arrives, compare base to your floor before you counter or accept. Five minutes per application prevents accepting a number you already decided was too low.

Composite example: operations analyst

Before: "$130,000" with no context on a role posted at $85,000 base plus 10% bonus.
After: "$88,000 to $94,000 base; understand bonus targets 10% and open to reviewing equity at offer."

Composite example: new grad underselling

Before: "$55,000" on a posting that lists $70,000 to $78,000 for entry analysts.
After: "$72,000 to $76,000 base, aligned with posted entry band and relevant internship proof."

Edge case: required field, no posted range

Use role level defaults for your city and stay flexible. "Targeting mid-market base for [Title] in [City]; range $X to $Y depending on level." Avoid $0, $1, or joke answers. Some systems flag them as unserious.

Edge case: remote role with location-based pay

Answer using your work location band, not company HQ, unless they pay national rates. If the form asks expected location, align salary with that city before submit.

Edge case: career change into lower band

State intent without underselling: "Transitioning into [target field]; targeting entry band $X to $Y base aligned with junior [title] roles while bringing transferable [skill]." That signals realism without inviting a rock-bottom anchor.

Edge case: internal transfer

Reference level and scope: "Targeting mid-point of published L4 band given current responsibilities leading [project]." HR may require a number for system compliance even when outcome is mostly predetermined.

Edge case: multiple similar reqs at one employer

Large companies run parallel reqs with different bands for the same title family. Match your desired salary to the specific req ID you applied for, not a number you used on a different posting last week. Wrong-band answers on the wrong req are a common self-filter mistake.

Edge case: nonprofit or public sector posted steps

Some government and nonprofit postings list fixed steps or grades. Answer inside the published step range when shown. Adding ten percent above the top step without scope justification usually pauses the req rather than opening negotiation early.

Edge case: salary asked in cover letter

One sentence with base range only. Keep proof in the resume. Use the cover letter generator to draft that line without turning the letter into a salary essay.

Desired salary mistakes on applications

Typing negotiable in a numeric-only field. Some systems reject non-numeric values. Give a range when forced.

Mixing OTE with base salary. Calling $150,000 OTE your desired salary on a base field filters you or produces low base offers.

Underselling to get interviews. Low anchors hurt at offer stage. Research beats fear.

Overshooting to test the employer. Bands on corporate reqs are usually real. Waste everyone's time and you still get a no.

Changing numbers between form and recruiter call. Keep one consistent range unless scope materially changed.

Ignoring posted salary ranges. Applying outside the band signals you did not read the req.

Wrong hourly or annual unit. Double-check the form before you submit.

Copying current pay into desired when you are underpaid. Desired should reflect market and scope, not history alone.

Answering before reading the posting band. Skim the req for salary language first. Many postings now include ranges required by pay transparency laws in several US states.

Using gross OTE as base on sales roles. Split base and variable in your notes when comments allow. Recruiters need base for band checks.

Align salary answers with resume proof

Your desired salary only holds up if your resume supports the level you claim. Upload to HireFlow's free ATS resume checker with the posting pasted in before you name a number.

Use job match score to see whether experience aligns with the band you target. High salary on a thin match file raises eyebrows fast.

Build scope proof in the free resume builder before you apply at senior bands.

When salary belongs in a cover letter, use the cover letter generator for one clean base range sentence.

Base range in the band, negotiate after the offer

What is your desired salary on applications? Base pay you want next, usually as an annual range inside the posting band when one exists. Set floor and target before you type, match the field unit, keep form and phone answers consistent, and save what you submitted.

• Answer salary when the label says salary, not total comp.
• Use copy-paste ranges tied to title, city, and posting band.
• Negotiate hard only after they name an offer number.

Open your tracker tonight, set floor and target for tomorrow's applications, and run the free resume check on each req before you submit the salary field.