Stupid Job Posts Don't Matter!

Kirsten Renner opens by saying poorly written job postings frustrate many people, and that a large share of the hacking community reports trouble finding work. She frames the search as an engineering problem: gather requirements, identify blockers, and design solutions. Her first step is to read a posting as a signal of what a company needs, then look past its marketing. Checking who holds the same title on LinkedIn and what employees publicly say about growth and daily work can show whether a role offers room to develop.

She then walks through typical problems: contradictory entry-level requirements, vague terms like "strong," long tool lists lumped together, and postings written for one specific person. Offensive postings, she says, are a reason to walk away. Candidates should turn their doubts into written questions, ask recruiters to answer them, and raise topics such as training, certification costs, and growth plans. When a requirement is missing, describe equivalent experience instead.

The question-and-answer segment covered reaching hiring managers when recruiters go silent, following up after interviews, and asking for feedback that companies may be unable to give. Tailored resumes matter because many employers filter applications by keywords, and a short opening note explaining the goal helps a reader. The takeaway: a weak posting may still point to a good employer, so review it before skipping, and invest in relationships with recruiters.