I've always read requirements for tech jobs to be a laundry list of things that are "nice to haves". Read "requirements" as "skills we're interested in," even i

I've always read requirements for tech jobs to be a laundry list of things that are "nice to haves". Read "requirements" as "skills we're interested in," even if they have an explicit section for bonus talents. This is especially true for junior and/or entry level roles. Every place I've seen just has an eternally published "opening" on theirs careers section. They keep it there so that when they finally decide that they're ready to hire, they'll have a ready-made pool to of résumés from which to draw. If you're not experienced enough, you'll be able to tell from a specific, well written job description. If it's full of buzz words and meaningless fluff, they're not looking for someone specific and you should apply.