Read a job posting like a recruiter

Most people read a job posting from the top. They get through the company’s description of itself, skim the responsibilities and then check the skills list against their own. That order puts the least useful part first and the most useful part in the middle. A recruiter reads it differently. They start with which team has the opening, move to what the person will have to do, then look at what the team needs, and finish with the facts that decide whether an offer is possible. Read in that order, a posting answers one question. Have you done this work before?

The four reads, in order

The first read is the company and the team

Every company describes itself in large words. Innovative, mission-driven, fast-growing, obsessed with customers. That paragraph is nearly the same in every posting and says almost nothing about whether you fit. Skim it.

What matters is the team. Look for the line that says which group the role sits in and what that group does. A posting for a product analyst might belong to a growth team running experiments, a finance team forecasting revenue or an operations team measuring warehouse throughput. Those are three different jobs with one title. Then look for why the opening exists. Words like first, build out or founding mean they need someone who has built from nothing. Words like scale, migrate or reliability mean they need someone who has run something mature.

If the posting never names the team, the responsibilities usually reveal it. Ask yourself what kind of work would fill this person’s week.

The second read is what you will do

The responsibilities section is the job. It is the closest thing in the posting to the hiring manager’s own picture of a good hire. Read each line and give it one of three marks. Done it, done something equivalent, or not done.

Be generous with equivalent, but honest. Two companies solving the same problem use different principles, methods and tools. A team running payroll on one platform and a team running it on another are doing the same work. A marketer who ran paid campaigns for a retail brand has done most of what a software company means by performance marketing. The industry, the vocabulary and the stack differ, and the work is the same.

Be strict with not done. Reading about something, taking a course on it or watching a colleague do it is not having done it. Recruiters can tell the difference with one interview question.

The core test is whether you have done it before, maybe a different way

Hiring is a bet on who will succeed in the role, and the safest bet is someone who has done the work before. That is why recruiters weigh responsibilities more heavily than the skills list. A person who has carried most of the responsibilities, at a different company, in a different industry or with a different stack, is far more likely to be hired than a person who has every listed skill and has never carried the work.

If no applicant has done all of it, the team looks for those who have done several parts. So the count matters. Most of the responsibilities done or equivalent is a strong reason to apply. A few is a stretch that can work when the rest is learnable. None, however well the keywords line up, is a reason to look elsewhere.

Your own résumé may not show everything you have done. If you mark a line as done but your résumé never mentions it, fix the résumé before you apply, because the recruiter only sees what is on the page. The guide on crafting your résumé covers how.

The third read is what they need

Now read the requirements and preferences. A stated requirement is a gate and a preference is a tiebreaker. The skill lies in telling which missing items actually rule you out.

Pay attention when a team is very specific. A posting that names one rare skill several times, or asks for experience in a narrow domain, is telling you that this is why the role is open. People with that skill are hard to find, which is why the posting insists on it. If you have it, apply even when other parts are thin. If you do not, the rest of your fit will not make up for it.

The fourth read is the additional information

The end of a posting usually holds the practical facts. Visa sponsorship, work authorization, citizenship or clearance rules, location and office days, travel, the pay range and benefits. Most of it is benefits text you can skim, but a few lines here decide whether an offer is possible at all.

Read these as facts, exactly as stated. “We are unable to sponsor visas for this role” means what it says. A citizenship rule tied to a government contract is a hard rule. If the posting says nothing about sponsorship, do not assume it offers it and do not assume it refuses. Check the employer’s filing history or ask the recruiter. A pay range below your floor is also a fact to respect before you spend an hour on the application.

Decide fit or not fit in five minutes

1. Skim the company text. Find the team and why the role exists. One minute.
2. Mark each responsibility as done, equivalent or not done. Two minutes.
3. Check the requirements for any true gate you do not meet. One minute.
4. Read the additional information for sponsorship, authorization, location and pay. One minute.
5. Decide. With most responsibilities covered and no gate missing, apply. With a few covered and the rest learnable, apply with a short note. With little covered, or a gate missing, move on.

Then write one sentence on why you fit. If you cannot write it, the recruiter will not be able to write it either.

A worked example of a fit the skills list hides

The applicant. Four years as a planning analyst at a parcel delivery company. They forecast daily package volume for each depot, built the SQL and spreadsheet model that decided when depots added shifts, and ran a project with depot managers that cut sorting delays. They use Tableau, not Looker, and have never worked in grocery. They can work in the country without sponsorship and live within commuting distance.

First read. The team runs a fulfillment network and is expanding, so it needs someone who can plan capacity ahead of growth. The applicant’s work points straight at that. Second read. Forecasting volume per site, done. A capacity model for shifts and space, done. Working with site managers on bottlenecks, done. Monthly cost per order, equivalent, since they reported cost per parcel. Third read. SQL, yes. Looker, no, but Tableau is close and a reporting tool is learned in weeks. Grocery is only preferred. Fourth read. The office is within reach and no sponsorship is needed.

Someone reading only the skills list might skip this posting because of Looker and grocery. A recruiter would call this applicant first.

A worked example of a keyword match that is not a fit

The applicant. Three years as a data analyst at a retail chain. Python and SQL every day, dashboards for the merchandising team, and one notebook project that predicted demand by store, which was never deployed. A statistics degree and a course certificate in machine learning.

First read. A core revenue team rebuilding its ranking system needs someone who has already run models in production at scale. Second read. Training and shipping ranking models, not done, because the demand notebook never reached production. Online tests that decide launches, not done. Owning a feature pipeline, partly equivalent at best. Serving at low latency, not done. Third read. Python, SQL and the degree all match, so the keyword overlap looks high. Production machine learning and learning-to-rank, which are the job itself, are missing. Fourth read. Remote work and sponsorship are both fine, so nothing blocks an offer except fit.

This is the case that wastes the most applications. The overlap feels like fit because the tools match, and the responsibilities show that it is not.