[susodapop]

I try to answer two questions quickly: Am I competent enough for this position? And can I see myself working there? Both are easier to answer if the posting gives solid examples, like a description of a recent project or the markets you serve. I want to understand your desired outcomes, not "required" skills.

More often than not, some "required" skills in the description become negotiable during the interview. But outcomes aren't negotiable because outcomes drive revenue.

I wouldn't abandon a job description for including the phrase "relentlessly positive attitude". But it's pure fluff and I would skim it looking for a concrete description of the work.

Recently I was impressed by this job posting from a small outfit in Kentucky [1]. It's a little long for my taste. But it was easy for me to answer my own questions.

[1]: https://www.level12.io/careers/full-stack-web-app-developer-...

[Falling3]

That's really helpful; thank you! I'm going to borrow a few phrases and ideas from your post. Your "two questions" approach is a really good insight for the kind of information that needs to be present and obvious in whatever we go with. I appreciate the feedback.