How to read a job description like a hiring manager
By Kyle Shaddox 7 min read The job search
Most job descriptions are written by committee. A first draft by the hiring manager, edits by HR, leftover language from the last person who held the role, and a paragraph of marketing pasted from the careers page. The result reads less like a job and more like a wishlist someone hopes the universe will deliver.
Hiring managers know this. They wrote it. When they read your application, they are not checking against the full list. They are checking against a much shorter version of the list that lives in their head — the version of the role they actually need filled. Reading the job description well means finding that shorter version before applying.
The two questions a job description actually answers
Strip the marketing language away and a job description is trying to answer two real questions for the reader.
- What will this person do day to day?
- What must they already be able to do on day one for that to work?
The first answer lives in the “responsibilities” or “what you’ll do” section. The second lives in the first two or three bullets of the “requirements” section. Everything else is context, wishlist, or HR template. Those four to six lines are the whole posting, for practical purposes.
When you open a job description, find those lines first. Read them slowly. Ignore the rest until you have decided whether the role is real for you.
The wishlist-versus-dealbreaker split
Almost every job description mixes two categories of requirements without labeling them.
- Dealbreakers. Things the team cannot train fast and cannot hire without. The minimum years of experience. A specific credential or license. A core skill the role is built around. Sometimes a location constraint or visa status.
- Wishlist. Things the team would prefer in the abstract. Adjacent skills, soft skills, “nice to haves,” tools the team uses but could teach, industries that would be a bonus.
The split matters because the dealbreakers are real and the wishlist mostly is not. Candidates who match every wishlist item are rare to nonexistent. Candidates who match the dealbreakers and roughly half the wishlist are the ones who get hired.
The order is the signal. Requirements lists are usually written in priority order, with the most important items at the top. If “8+ years of B2B SaaS marketing experience” is bullet one and “experience with Webflow” is bullet seven, the first one is the real filter. The second is preference.
How to read the responsibilities section
The responsibilities section is the section to take literally. This is the work the person in the chair will actually do. Read it for two things.
What this role actually is
If the responsibilities are “lead a team of five, set the quarterly roadmap, present to the executive team monthly,” the role is a manager role even if the title is “Senior Director, Strategic Initiatives.” If the responsibilities are “execute the content calendar, ship two blog posts a week, and run weekly social campaigns,” the role is an executor role even if the title sounds senior.
Title inflation is everywhere. Trust the responsibilities, not the title.
Whether you want this job
Most candidates skip this read in the first pass and regret it in the final round. Read the responsibilities and ask honestly: is this how I want to spend my Tuesday afternoons for the next two years? If the answer is no, save the application energy for a role where the answer is yes. A search is finite. Each application has a cost.
How to read the requirements section
The requirements section is the section to read structurally rather than literally. The order is the message.
The first two or three bullets
These are the real screening criteria. If a job description says:
- 8+ years of product management experience in B2B SaaS
- Track record shipping at least two major products end-to-end
- Bachelor’s degree or equivalent experience
That is what the screen will check. If you do not match items one and two, the recruiter will not pass your resume to the hiring manager, and the hiring manager would not advance it if she did. Apply where you match these first lines.
The middle bullets
The middle of the requirements list is usually wishlist territory — preferred tools, preferred industries, preferred years of experience with specific functions. Match roughly half of these and the role is in range. Match all of them and the role is a near-perfect fit. Match none of them and the role is a real stretch.
The bottom bullets
The bottom of the list is almost always template language — “strong communication skills, ability to work cross-functionally, comfortable in fast-paced environments.” This is not actionable for you and not actionable for the screening recruiter. Ignore.
CareerCanopy is built for the part of the search where you are reading job descriptions in volume and trying to tell which ones are worth a real application versus which ones are someone else’s job in disguise.
Signals hidden in the rest of the post
A few other parts of a job description carry real signal if you know what to look for.
The compensation range
If the range is listed and the floor is below your number, this role is not actually open to paying you. Walk away unless you are willing to negotiate hard against the floor with little to push back with. If the range is listed and your number sits inside the top third, the role is realistic and there is room to negotiate. If no range is listed in a state that requires disclosure, that is a small warning sign — usually a remote role being routed around the rule, sometimes a company that has not bothered to comply.
The team description
A job description that names the team — “you’ll join the four-person growth pod reporting to the Director of Growth” — is more honest than one that does not. If the post says only “you’ll collaborate with cross-functional partners across the org,” the role’s actual context is unclear. Ask in the screen.
The “about us” paragraph
This paragraph is marketing and contains very little hiring signal. Skim once for industry and stage. Skip otherwise.
Phrases to read carefully
A short list of phrases that often carry meaning:
- “Wear many hats” or “willingness to roll up your sleeves” — usually under-resourced, expect scope creep.
- “Self-starter, comfortable with ambiguity” — there is no plan yet; you will be writing it.
- “Hands-on leader” — manager who is also expected to do individual contributor work.
- “Fast-paced environment” — neutral on its own; combined with “wear many hats,” it means understaffed.
- “We move quickly and value autonomy” — minimal oversight, sometimes good, sometimes a sign of chaos.
None of these are dealbreakers in isolation. Stacked together, they describe a specific kind of role you can choose to take or skip with eyes open.
The actual screen for whether to apply
A short version of how to decide, after reading the four to six load-bearing lines:
- Do I match the first two or three requirements? If no, skip. If yes, continue.
- Do the responsibilities describe work I have actually done, or work I want to do next? If neither, skip.
- Is the comp range, if listed, in a range I can accept? If no, usually skip.
- Have I read enough of the role to write a custom top-third of my resume for it? If yes, apply. If no, this is not actually a fit yet — figure out the rest before clicking submit.
Three out of four yeses is a normal apply. Four out of four is a strong apply. Two or fewer is usually a no. The hardest discipline in a stalled search is saying no to roles that almost fit but do not, because every almost-fit application drains an hour and produces silence. The roles that fit produce screens. Save the energy for those.
Reading the posting date and revision history
Two pieces of metadata most candidates ignore. The posting date and any “reposted” markers carry signal.
A role posted within the last week is fresh — the team is at the top of the funnel and is reading early applications carefully. A role posted three months ago and still listed is often one of three things: stalled, slow-moving, or a “always open” requisition the company keeps live as a pipeline. The first is a normal apply with normal expectations. The third is unlikely to produce a fast response.
If a role keeps reappearing on the company’s careers page every few weeks with the same title, the company is having trouble filling it. That is sometimes a signal that the comp is below market, the role has a hard-to-find skill mix, or the team is difficult to work for. Worth a closer look at the team and comp before investing the application energy.
What changes when you read this way
Two things shift, usually inside a week. First, you apply to fewer roles, with custom resumes per role family, and screen rates start rising. Second, you stop reading every job description as a list of reasons you are not qualified, and start reading it as a short test for whether the role is real for you right now. Both changes compound. The search starts behaving more like a search and less like a generator of silence.