What Is a Requirements Analysis for a Job Posting?
A requirements analysis sorts a job posting into what it writes down, what the company implies, and what decides the hire. How to run one by hand.
By Michael Robert · Co-founder
A requirements analysis for a job posting is a working list of what the person in the role will have to deliver, ranked by which of those things will decide who gets hired. You build it from the posting and from what you can learn about the company, because a posting writes down only part of what the hiring team wants. The few requirements at the top of that list are more specific than the bullets under "Requirements", and they tell you what your application has to prove.
The term already belongs to people who build software. Wikipedia's entry places requirements analysis in systems and software engineering, as the work of determining "the needs or conditions to meet the new or altered product or project." In a job search, a requirements analysis is done by one candidate, on one posting, to find what will decide the hire.
Who actually reads the requirements on a job posting?
A job posting gets read twice, by two people asking different questions. By my later years as a hiring manager, I had stopped doing a deep dive on the requirements list. HR and the recruiting team vetted candidates against it. I looked for what the business needed from the person in that seat: could they solve the problem the role exists to solve?
Two experiences changed how I read requirements. The first came early in my management career, when I was asked to phone screen a candidate for a sales role. On paper, he met almost none of the prerequisites. On the call, he didn't address the gaps and spent most of the time talking about college football. I said we shouldn't hire him.
I was overruled. He was a referral who knew someone higher up in the company. Better-qualified candidates were in the pool, and he didn't last in the seat.
Whether he could do the job was the question that predicted how that hire went. A requirements analysis puts that question on paper next to the list the screen will use.
What does a job posting leave out?
A posting leaves out the requirements that come from what the company is going through right now: a market it just entered, a product it is replacing, a regulator that started paying attention. In a typical Telosi Requirements Analysis the list runs to about 26 requirements, around 19 written in the posting and around 7 that the company research turned up.
Later in my career, while I was reporting to a VP, I was asked to write a requisition for the first time. My draft was rough, and I got no coaching on it. I was told the company had an old req for the role that we could recycle. That is when I learned that the core requirements on a posting are often baked in and reused from one opening to the next. From then on, I put far more weight on what I learned in the interview than on the list.
One requirement never made it onto the page: how would the skills and experience you built elsewhere help us solve the critical problems in my corner of the organization? Nearly every candidate skipped it.
The few who answered it stand out to this day. One applied as a senior account manager, with years of senior management behind them. They laid what they had done in their previous role over what we were facing, and I was in awe of how closely the two matched. Experience shows in an interview. The answers aren't always polished, but they feel authentic. Someone who has read every chapter of the book tells the story differently.
That overlay is hard to do alone. You are mapping your experience onto another company's living framework, in terms that resonate with the hiring manager. Part of it is knowing what the company is facing before you walk in, which our post on researching a company before an interview goes through layer by layer. The other part is your own record, which is what Experience Mapping checks in a Telosi kit, requirement by requirement.
Domain knowledge is the requirement resumes most often leave unanswered, whether the posting writes it down or not. In a sample of 38 kits we've serviced, about half of the domain-knowledge requirements went unaddressed by the resume, against about 15 percent for soft skills. In an April 2026 survey of more than 2,000 US hiring managers for the staffing firm Robert Half, industry-specific knowledge led the list of skills they say are hardest to find, at 47 percent.
Across every kind of requirement, most of what a resume leaves unanswered is work the candidate has already done (the breakdown is in our experience mapping post). Domain knowledge is the exception: most of those misses were experience the candidate did not have. Research will not give you years in a new industry. It will tell you what the company is dealing with now, so you can speak to its market in specifics, and it warns you early when most of a posting's domain list sits outside your history.
How do I do a requirements analysis on a job posting myself?
Put the posting next to a blank sheet with three columns: what it writes down, what the company implies, and what decides the hire. Work left to right.
Copy every requirement the posting states, one per row, in the posting's own words. Split compound bullets: "5+ years of product management, including payments" is two rows. Mark each row required or preferred. Then reread the responsibilities, because duty lines carry requirements too. "Take our product into new markets" asks for someone who has launched in a new market.
Every other applicant can copy column one. A 2025 working paper by Cui, Dias and Ye studied Freelancer.com after it gave applicants an AI tool that drafts cover letters. Letters started to mirror job posts more closely, and the correlation between that match and getting a callback fell by 51 percent. Employers shifted toward other evidence, including applicants' past work. The study covers freelance jobs only.
Spend most of your time here, on what any outside applicant can read: the company's recent announcements, its release notes, its other open roles on the same team, its customer case studies, and for a public company the latest earnings call. For each thing you find, write the requirement it implies in one line, with the source beside it. Three to five rows is enough. This is application intelligence pointed at one posting, and our post on what to research about a company before applying covers the business problem, the role's challenge and the competition.
Mark each row from the first two columns as a floor, a decider, or neither. A floor is something you clear or you don't, like a license or a required degree. A minimum number of years is softer, and being short on it is a gap to explain in your cover letter. A decider would separate two finalists who both clear the floors. A row is probably a decider when at least two of these are true:
- It is near the top of the posting, repeated, or echoed in a responsibilities line.
- Something in column two explains why the company needs it now.
- Someone without it would struggle in the first six months of the job.
Expect only a few deciders.
A payments role, months after a European launch
A mid-size company that sells invoicing software to small businesses is hiring a Senior Product Manager for its payments team. Requirements: 5+ years of product management, strong cross-functional communication, data-driven decision making. Preferred: payments or fintech experience. One line under responsibilities: "Take our payments product into new markets."
A press release from the spring announcing launches in Germany and France. Release notes since then about invoicing in euros and adding VAT to invoices. A second open role on the same team, for a payments compliance lead. A customer case study about a design agency in France that bills clients in Germany.
| What it writes down | What the company implies | What decides the hire |
|---|---|---|
| 5+ years of product management | (nothing added) | Floor |
| Payments or fintech experience (preferred) | Payments work under European rules: VAT, euro invoicing | Decider; the role likely exists for the European rollout |
| "Take our payments product into new markets" | Has launched a product in a new country | Decider |
| Strong cross-functional communication | Can work alongside a compliance team that is still being hired | Neither. Worth a line in the cover letter |
| Data-driven decision making | (nothing added) | Neither. Every finalist will claim it |
| (not written) | Has built for small-business customers who bill across borders | Possible decider; the case study points to it |
The requirement that most likely decides this hire sits under "Preferred" in the posting. A candidate reading only the first column would put payments experience at the bottom of the resume, if at all.
On your resume, write each clear decider as a line that names the work: the country you launched in, the tax or currency problem you solved there. If a decider is the reason the role is open, like the European rollout here, and you have nothing to show for it, pass before you spend time on the application. For the rewrite itself, see tailoring a resume without sounding generic.
What does Telosi's Requirements Analysis do?
Every Telosi Application Kit starts with a Research Brief on the company, and the Requirements Analysis is built on that brief. It lists every requirement the posting states, is set to add at least five implicit ones, each from a different research finding, and ranks them by how much each decides the hire. Each requirement comes with why it matters to this company. The ranking does the work of your third column: its top band, "What This Hire Is Decided On", holds the requirements this hire turns on, most decisive first.
Experience Mapping then checks your resume against that list. Your portal marks each requirement Full, Partial or Missing and shows the result as requirement coverage: how many of the role's core requirements you fully cover. The kit's tailored resume and cover letter are written from the same Requirements Analysis.
Does Telosi have a job application tracker?
Yes. Every application you build with Telosi lives in your Candidate Portal, and you move it from Kit delivered through Applied, Screen, Interview and Offer as it happens. Each application keeps its documents, its contacts (the hiring manager, the recruiter and each interviewer), and a next step you set.
Before an interview, the Interview prep tab pulls the kit together for that round: who you're meeting, where they'll push, and questions to prepare for and to ask. You log each round and what you learned, and it carries into the next round's prep.
Across applications, a Strengths and gaps chart compares what your target roles ask for with your evidence. For what any tracker should record, see what a job application tracker should actually track.
What do candidates ask about job posting requirements?
What is the difference between explicit and implicit job requirements?
Explicit requirements are the ones a posting writes down: a minimum number of years, a degree, a named tool. Implicit requirements come from the company's situation and stay off the page, like knowing the rules of a country it just launched in. In a typical Telosi Requirements Analysis, about a quarter of the list is implicit.
Should I apply if I don't meet every requirement in the posting?
Often, yes, if you clear the hard floors and can show the requirements most likely to decide the hire. In a November 2024 Harris Poll of 1,001 US hiring decision-makers for the staffing firm Express Employment Professionals, 83 percent said their company had waived some requirements to fill a role, most often years of experience. If what you cannot show is tied to why the role is open, that is a reason to pass.
How do I know if my resume meets a job requirement?
Find the line on your resume that covers it. Does it name a specific piece of work you did? Does it say what came of it? A line that only repeats the posting's vocabulary, with no work behind it, does not meet the requirement yet. Our experience mapping post walks through the test with examples.
Is a requirements analysis the same as matching keywords?
Keywords are one part of it. The posting's written requirements give you the vocabulary a recruiter screen looks for, and Telosi's resume step uses keyword targets set by its Requirements Analysis. A full analysis also covers what the company needs that the posting left out, and which requirements will decide the hire.