What are you worth? Researching developer salaries
Salary is not a number you guess, it is a number you research. A practical method for working out your range before anyone asks.
2 min read · Updated Oct 2026
The fastest way to be underpaid is to answer "what are your salary expectations?" with a number you invented on the spot. Spend an hour with data first, then see how to answer the question.
Build a range, not a number
You are looking for three figures:
- Your floor, below which you would rather keep looking.
- Your target, fair for your experience and the role's scope.
- Your stretch, what you quote when you know you are a strong fit.
Where the data comes from
- Listings that state pay. Filter for roles that publish a range; they anchor everyone else.
- Company size and funding stage, these move pay more than the stack does.
- Your own history. Your last total compensation is a floor, not a ceiling.
Adjust for the realities of remote
Remote roles often pay by location band, which is why the same title varies so much between companies. Read remote pay bands before you decide a number is "too low", or accept one that is too low.
Answer with a target, not a floor
Try: "I'm targeting [target] for a role with this scope, is that in range?" You have moved to facts without naming your floor. When an offer lands, go to negotiating your offer, and remember that equity and bonuses count; see total compensation explained.
Related guides
Find a role that's actually remote
Search fresh, genuinely-remote developer jobs - free.
Browse jobs