8 min read
Halfway through a Workday application, the form stops you: desired compensation. You don't want to price yourself out. You also don't want a low number to anchor the offer you'll see in three weeks. Most advice online treats the field like a negotiation opener. On the application, it's closer to a filter.
Before you type anything tonight, check your resume for free against the posting so the level you claim matches the range you're about to enter. A seniority mismatch raises more eyebrows than a range that's $5,000 wide.
Below: themed answers on what the field means, how it differs from desired salary, what to type when the label is vague, and copy-paste lines you can drop into Greenhouse or Lever tonight. If a cover letter field asks for salary in prose, the cover letter generator can draft one sentence without turning the letter into a comp essay.
Quick Wins
- Read whether the box wants base salary only or total compensation before you type.
- Write your floor and target on a sticky note so you don't panic-fill under pressure.
- If the posting lists a range, answer inside it unless your scope clearly exceeds the top.
What is your desired compensation on an application?
It's a band check, not your final deal. Employers set salary bands before you apply. Recruiters use your answer to see whether you're inside that band before they schedule more interview hours. That's different from offer negotiation, which happens after they decide they want you.
Does compensation mean the same thing as salary?
Usually not. Salary on a form often means base pay only. Compensation is broader: base plus bonus target, commission, equity, sign-on cash, and sometimes benefits that matter to you. When the label says compensation but the box accepts only one integer, answer base and explain total rewards in a comments field if one exists.
Read how to answer desired salary on US applications when a sibling field asks for base only on the same screen.
What do recruiters do with your number?
I've screened stacks of these in Workday and Greenhouse, and the answer that keeps you moving is a range inside the posted band with base called out clearly. Overshoot by a lot and the req may auto-close. Undershoot and some employers anchor low because you told them you'd work cheap.
Desired compensation is also not current pay on every portal. Some forms ask both. Current pay is history. Desired is what you want next. Don't copy last year's base into desired if your scope grew.
When is this field optional vs required?
Optional fields can stay blank early. Required fields in Workday, Greenhouse, Lever, or iCIMS block submit until you enter something numeric. If it's required and you have no posting range, use role level and city to set a defensible floor and target before you apply.
Answers for common form setups
When the form asks for base only
Hover the help icon. If it says annual base in USD, answer base. Don't type OTE or total comp into a base box.
Before: "$150,000" on a role posted at $95,000 base plus 10% bonus.
After: "$92,000 to $98,000 base; understand bonus is targeted at 10% and open to reviewing equity at offer stage."
When the posting shows a salary range
Answer inside the published band unless your scope clearly exceeds the title. Applying at $130,000 when they posted $90,000 to $110,000 signals you didn't read the req.
Before: "$200,000" on an AE role posted at $120,000 to $140,000 OTE with no comment.
After: "$130,000 to $140,000 OTE with 50/50 base and commission split, aligned with posted range and prior quota attainment at 112%."
When the form forces a single integer
Pick the middle of your researched range or your target if the posting range supports it. Avoid $0, $1, or joke values. Some systems flag them as incomplete.
Before: "$45/hour negotiable" on a form that asks annual salary.
After: "$78,000 to $82,000 annual base for full-time day shift, consistent with posted band and six years med-surg experience."
When a recruiter repeats the question on a phone screen
Use the same range you put on the application. Changing numbers between form and call without a scope update erodes trust. 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 structure once I see the full package."
Copy-paste block: free-text compensation answers
Desired base compensation: $88,000 to $96,000, depending on bonus structure and level. Open to discussion after learning more about scope.
Target total compensation aligned with posted range of $120,000 to $140,000 OTE for this AE role, flexible on split.
Transitioning from [field] into [target field]; targeting entry band of $X to $Y base aligned with junior [title] roles while bringing transferable [skill].
When the form also asks current compensation
Some states restrict employers from asking current pay. Answer truthfully where required, but keep desired forward-looking. If current pay is optional and you're underpaid, leave it blank when allowed and lean on a market-aligned desired range instead.
Edge case: remote role with location-based pay. Answer using your work location band, not company HQ, unless they told you they pay HQ rates nationwide. Changing location later without updating comp expectations creates offer friction.
For offer-stage moves after the screen, read how to negotiate a salary offer once they name a number in writing.
Numbers that get you filtered
Typing negotiable without any number when the field is numeric-only. Some systems reject empty or non-numeric values. Give a range when forced.
Mixing base and OTE. Calling $150,000 OTE your desired salary on a form that asks base can filter you or produce low base offers.
Answering far above band to test them. Recruiters aren't bluffing about bands on most corporate reqs. Overshooting wastes everyone's time.
Underselling to get interviews. Low anchors hurt at offer stage. Research beats fear.
Changing numbers between application and recruiter call. Keep one consistent range unless scope materially changed. Screenshot what you submitted so you don't contradict yourself weeks later.
Ignoring posted ranges when they exist. The field isn't where you reopen budget. Save hard counters for after the written offer.
Match resume proof to your range
Your desired compensation only makes sense if your resume supports the level you claim. Upload your file to HireFlow's free ATS resume checker with the posting pasted in. Fix title, scope, and metric gaps before you name a number on the form.
Run job match score on the same req to see whether your experience aligns with the seniority band you're targeting. A high comp answer on a thin match file raises recruiter eyebrows fast.
Read how salary expectations impact resume outcomes when comp fields appear before resume upload in the same portal.
What to do before you submit
What is your desired compensation on an application? It's a band-alignment answer, not your final deal. Recruiters use it to keep the pipeline efficient. You use it to stay in range without underselling your scope.
- Read whether the form wants base or total comp.
- Submit a researched range with a clear floor.
- Save hard counters for after the written offer.
Set your floor and target on paper, align your resume to that level, and run the free resume check on the posting before your next application. That's how you answer compensation fields without guessing yourself into a filter or a low anchor.
Read more
Frequently asked questions
Desired compensation is the total pay package you want from an employer, not just base salary. It can include base pay, bonus target, equity, sign-on bonus, and sometimes benefits value. Recruiters use the field to see if you fit the approved band before investing more interview time.
Not exactly. Salary usually means base pay only. Compensation is broader and often implies total rewards. When a form says compensation, read the help text. If it is ambiguous, answer with a base range and note you are open to discussing bonus and equity separately.
Use a range in most US corporate applications unless the form forces a single value. Ranges give recruiters room to match you inside the band. Make sure your floor is a number you would accept if the rest of the package is standard.
Sometimes. Optional fields can be skipped early in the process, but required fields in Workday or Greenhouse will block submission. If required and early, use a researched range or write negotiable with a base target only when the free-text box allows explanation.
Answers far above the approved band can trigger auto-rejection or recruiter pause, especially in high-volume reqs. Answers far below band can also hurt because employers may anchor low offers to your number. Aim for market-aligned ranges backed by role, city, and scope.