|
Not OP, but we do the same thing. We basically keep job listings limited to "we're writing cloud software using Angular, Spring, and relational data". We're a large company, so other teams do it differently, but my team tries hard to not put ceilings or floors on experience or skills. We've hired everything from summer intern to Principal (Staff) Engineer using the same job req. We also don't limit the listings to a specific functional area - we might hire Ops, Front or Back End, Full Stack, Test, Autimation, etc, using the same req. We also actively look for skills we don't currently "need", on the hope they will widen the practical experience of the team. Honestly, truly, does all that extra detail around experience, "job duties", micromanaged required skills, etc, actually add any value to the listing? Does "Agile experience preferred" even mean anything? |
Nope, but the "x years of experience" does. IME teams that have the wrong balance of experience tend to go way off course. I worked on a team with a lot of juniors that put out a similar advert (HR snafu) and we were flooded with even more. It was a struggle to mentor those we had let alone do actual work.
I probably would apply to such jobs if I were really desperate but if salary is left out I assume it's a lowball negotiating ploy and ignore them. I believe absolutely that in spite of all protests to the contrary that it absolutely is in all cases. No shame in that either. You might score somebody senior for cheap.
There are plenty of roles these days that are up-front about what they are, though.