Should I apply?
Should I apply if the application asks for my current salary?
How you would be applying. This page answers the general case with a decision rule rather than encouragement; the specific posting on your screen is a question only your own history can settle.
Should I apply if the application asks for my current salary?
Yes, and know that in many places they are not permitted to ask — the decision turns on whether you can redirect to expectations, which is the answer to give whether or not the question is lawful where you are. A salary history field is used to anchor an offer. That is the purpose, and it is why a growing number of jurisdictions have banned the question outright. It does not tell you the field is mandatory in practice. Many forms accept a zero, a blank, or an expectations figure in its place without any consequence.
- How binding this usually is
- Usually a soft requirement. A salary history field is used to anchor an offer. That is the purpose, and it is why a growing number of jurisdictions have banned the question outright.
- What it does not tell you
- It does not tell you the field is mandatory in practice. Many forms accept a zero, a blank, or an expectations figure in its place without any consequence.
- What the decision turns on
- You can redirect to expectations, which is the answer to give whether or not the question is lawful where you are.
- What would change the answer
- Whether your jurisdiction restricts salary-history questions. Whether the field accepts a non-numeric response. What your researched expectation is, so you have something to give instead.
- Apply when
- You can supply an expectation instead of a history.
- Skip when
- It is a hard numeric field and disclosing would anchor you well below market.
Source and method
RoleSprint's published decision framework, not external research. Verified 2026-08-30. Nothing on this page is an interview rate, an application-to-offer ratio or a statistic from a study. It is a decision rule: what the signal in front of you can and cannot support, and which further evidence would settle it. The reasoning is stated so you can disagree with a specific step rather than with the conclusion. Where the honest answer depends on something only the employer knows, the page says so instead of guessing.
How binding this usually is
Usually a soft requirement
What it tells you. A salary history field is used to anchor an offer. That is the purpose, and it is why a growing number of jurisdictions have banned the question outright.
What it does not. It does not tell you the field is mandatory in practice. Many forms accept a zero, a blank, or an expectations figure in its place without any consequence.
What would change the answer
Each of these is checkable before you spend the evening, and each one moves the decision rather than decorating it.
- Whether your jurisdiction restricts salary-history questions.
- Whether the field accepts a non-numeric response.
- What your researched expectation is, so you have something to give instead.
The decision
Apply when
- You can supply an expectation instead of a history.
Skip when
- It is a hard numeric field and disclosing would anchor you well below market.
What this page cannot tell you
Stated plainly, because a decision rule that hides its own limits is just advice.
- Whether this employer treats the signal the way most do. The rule above describes the common case, and individual employers depart from it without announcing that they have.
- How your specific background reads against this specific posting. That comparison needs both documents, and it is the one thing that actually decides the application.
- Your odds. RoleSprint publishes no interview probability anywhere, and a page that offered one here would be inventing it.
What to do next
This page answers the general case. Whether this posting is worth your evening depends on what it asks for and what your history evidences, which is the comparison the analyzer makes.