What makes a developer who's happy where they are reply to an offer
Short answer: a message that already answers the questions in their head. That means a gross annual salary with a narrow band, the work mode with the number of days, the role in one sentence, and a short process. That is what comes out of an r/devpt discussion in October 2026, with more than 150 comments from more than 40 developers, answering a simple question: what would make you even reply to an offer?
These are the opinions of the people who commented, not a study. But they repeat often enough to work as a list.
1. Gross annual salary in the first message
The most agreed-on point. A band is fine if it is narrow. One participant put the benchmark at 10 to 15% between the minimum and the maximum: 50-60k is fine, 60-80k is borderline, 40-70k is too much. Another gave 30-60k as an example of bait: that is how a wide band reads. And anyone offering good terms loses nothing by showing them.
2. Moving has a cost, and that cost weighs as much as the offer
One of the most upvoted comments was about processes with endless stages. The most concrete limit came from one participant: three stages (HR, technical and fit), closed in three weeks to a month. Anyone who needs more, they said, doesn't know what they are looking for. Stability has a price too: some asked for considerably more to accept a probation period.
3. The work mode without asterisks
The problem isn't on-site work. It's calling four days in the office hybrid, or "one week a quarter here" remote. Say how many days, and how flexible.
4. The role in one sentence, and the problem before the tools
"Design and build the backend of product X" says more than a list of technologies from different areas, which reads as "does everything, meaning nothing". The clearest example in the discussion compared two ads:
- Good: "we're building a computer-vision system to detect breast cancer; we're looking for experience in X, Y, Z or similar".
- Bad: "Python, MongoDB, Docker, CI/CD and testing".
Interviews are the same. A good interview asks what problems you solved and how you designed the solution. A bad one asks trivia about a library.
5. A lot is decided by exclusion
Sectors (weapons, alcohol, casinos), kinds of project (maintaining old technology with no migration plan), roles that mix code and infrastructure, consultancies. Almost no ad says what is out of scope, and for many people that is what decides it. An unusually high salary in one of those sectors doesn't persuade: it reads as a warning sign.
6. Time is worth money
Some would take up to 10% less for a four-day week, and some would take half for fully remote work. For some, above a certain salary, hours and benefits come before money.
7. Trust
People who value stability want to be able to check: the history of layoffs, how many clients the company has, talking to people who work there. A referral from someone they know is worth more than any anonymous review, especially for those who already moved for a good salary and found a bad environment or constant crunch.
On ads that don't name the company up front, opinions split. For some, with everything else written down, it makes no difference. The one risk they pointed out was the ad being from the company the person already works for. For others, without the name there is no way to check anything.
8. Small things that annoy
Being asked for a CV when the LinkedIn profile is there and more up to date. "We'd like to talk to you" with nothing else. Half an hour of small talk with someone who hasn't read the profile. A final offer with numbers different from the ones agreed.
What it comes down to
Almost nothing on this list depends on a platform. It depends on the company writing these things in the ad, wherever the ad is.
Next step
If you're hiring: How to write a tech job ad that people who aren't looking will answer, and the free job ad checker.
If you're the one who's happy where you are: on Radarfox you don't apply or send a CV. Every role shows the salary and the work mode, and your identity stays sealed until an interview is confirmed. For candidates
Source: a public r/devpt discussion opened on 4 October 2026, with more than 150 comments from more than 40 people. Where a number comes from a single participant, the text says so. Summary and paraphrases by Radarfox, with no usernames.