I think many people write their job description's requirements, as if it were the opening stage of a negotiation. You list everything you want as if it were a requirement, and you will only get about half of that. But the problem is, it isn't a negotiation, it's a minimum spec (especially if you put the word "required" next to that line), and so many quite good candidates won't apply. However, typically, I see 20-30…
so many quite good candidates won't apply. Shame on someone for writing unrealistic or unnecessary "requirements", but also shame on the engineer who doesn't even apply because of them. I wonder how truly good a candidate is if they get discouraged so easily. Maybe a hidden requirement 1 is showing a willingness to try to punch above one's weight or displaying some self confidence during the application process. Afte…
Since it was a small-ish company, I thought maybe this was just their generic "senior software engineer" posting. Nope. I asked them. They actually expected people to be able to work on all of those things. By my count, that's about 5 different teams that should be working on those things... except that this place has ~15 engineers. I self selected out of that process because, although I could certainly do the API and integrations stuff, if I'm the best person you've got to work on ML, your company is in bad shape.
I probably could have applied and gotten an interview anyway, maybe even gotten the job, but I know it wouldn't have been someplace I could do my best work. I'm very glad I'm not there.