This is pretty much my list. I'll second the salary point in particular - if I can't get the salary range from you, I'll get it from Glassdoor, and if I can't g

This is pretty much my list. I'll second the salary point in particular - if I can't get the salary range from you, I'll get it from Glassdoor, and if I can't get it from either you or Glassdoor, I probably won't apply. One other point I'll expand on a bit: > List requirements but be open-minded. An experienced-enough engineer can learn a lot very quickly. Be thoughtful and explicit about which requirements are firm and which aren't. I think of a firm requirement as one for which any resumes lacking it are automatically thrown in the trash, full stop. Or, equivalently, any requirement for which you can say f'I wouldn't hire {best_hacker_you_know} for this position if they didn't have {requirement}.' With this in mind, it may be reasonable to have 0 firm requirements for a position if you trust your interview process, and it's probably suboptimal to have more than a handful of them. Assume that there are good candidates who will treat every requirement as a firm one unless you explicitly state otherwise, and who will only apply if they meet all of them. Because there are. Chances are, you don't want to miss out on good candidates who know most of your stack like the back of their hand but decide not to apply because you "require" MySQL experience and they only know Postgres.