Most developer job specs read like a list of every technology the company has ever touched. Good developers skim them and move on. A short, specific spec gets more of the replies you want.
Start with the work
Say what the person will build in their first six months. “Rebuild the billing service in Laravel and move it to queues” tells a candidate more than “dynamic, fast-paced environment”.
Be exact about the stack
Separate what you use every day from what you are moving towards, and from what you merely have lying around. If the role is 80 percent PHP and 20 percent DevOps, say so.
Show the salary range
Developers compare offers. A range saves both sides a call that was never going to work out. If you cannot share one, expect fewer applicants.
Describe the process
List the steps and roughly how long they take: a screening call, a practical task, a team conversation, an offer. Candidates drop out of processes that feel open-ended.
Leave out
- Years of experience as a proxy for skill.
- Wish lists of ten technologies.
- Slogans about rockstars and ninjas.
A tight spec is also easier for a recruiter to work from, which means a better shortlist.