A job posting is written by several people with different goals. A recruiter wants a wide pool. A hiring manager wants the last person who left to be replaced. Legal wants a paragraph about equal opportunity. The result is a document where the real job is one third of the text, and the rest is filler you have to learn to skip. This post gives you a repeatable way to read one in about ten minutes.
Start with the verbs, not the nouns
Most postings open with a company pitch and a list of technologies. Skip both on the first pass and read only the sentences that say what you will do. Underline every verb.
Compare two lines from a sample posting (invented for this post):
- “Own the billing service end to end, from schema changes to on-call.”
- “Collaborate with cross-functional stakeholders to drive impactful outcomes.”
The first line tells you the task, the scope and a cost: you carry a pager. The second could describe any job in any industry. If a posting has plenty of the second kind of sentence and none of the first, the work has not been decided yet, or the author did not know it. Both are things you want to learn before you apply.
Verbs also show seniority. “Implement” and “support” describe work handed to you. “Design”, “decide” and “own” describe work you hand to others. A title that says senior with a verb list that says implement is a mismatch you can raise in the first call.
Sort every requirement into three piles
Copy the requirements list into a note and mark each line with one of three labels.
- Must have. It appears in the title, in the first three bullets, or in the sentence about the daily work. If you lack it, the posting is probably not for you.
- Nice to have. It sits under a heading with that word in it, or it names a tool that sounds like a preference (“experience with Kafka is a plus”).
- Decoration. A trait nobody can verify: “self-starter”, “passionate”, “thrives in ambiguity”.
Then count. A posting with 4 must-haves and 12 nice-to-haves is a normal one. A posting with 15 must-haves is a wish list, and few people will meet all of them. A common mistake is to rule yourself out on a line from the second or third pile.
Look for the first-year outcomes
Good postings say what success looks like after some months: “ship the new checkout flow”, “cut the nightly job from six hours to under one”. These sentences are the most useful in the document, because they are the closest thing to a task list.
If the posting has none, write the outcome you would guess and keep it for the interview. “I read the role as mainly about stabilising the payments service. Is that right?” is a strong first question, and the answer tells you more than the posting did.
Signals that the job is bigger than it sounds
Some phrases are code for scope that was not budgeted.
- “Wear many hats” often means the team is small and the role covers work from two or three departments.
- “Fast-paced” with no mention of team size often means turnover, or an absence of process.
- “Generalist” next to a long list of specific tools means you are expected to be an expert in most of them.
- A single opening for a team you can name on the careers page, with a title one level above everyone else, can mean you are being hired to manage people you have not met.
None of these is proof of a bad job. Each one is a question. A small team may be exactly the environment you want, as long as you are choosing it and not discovering it in week three.
Signals that the job is smaller than it sounds
The opposite also happens. “Work with leading technologies” can sit on top of a maintenance role for a system three versions behind. Look for:
- A stack list with no version numbers or recent tools, next to words like “legacy” or “modernisation”.
- Verbs like “maintain”, “monitor”, “triage” and “respond”, with no verb about building anything.
- Large company, narrow title, and a reporting line two layers from anyone who decides what gets built.
Maintenance work is real work and some people prefer it. The point is to read the verbs and choose it deliberately.
What a vague posting hides
When a posting says little, the employer may not have a settled idea of the role, or it may be a pipeline posting kept open to collect resumes. Check for four facts and note which are missing:
- A salary range or a stated level.
- A team name or a manager’s title.
- A location rule that says what “remote” or “hybrid” means.
- A posting date. A role that has been open for months and is still listed has either been hard to fill or is not urgent.
Each missing fact is a free question for the recruiter. You will get a straight answer from a good employer and a slippery one from a bad one, and that difference is worth knowing before you spend an evening on a cover letter.
A ten-minute routine
Do this for every posting you are seriously considering:
- Read verbs only, once (2 minutes).
- Sort requirements into three piles (3 minutes).
- Write the first-year outcome in one sentence, as stated or as guessed (2 minutes).
- List the missing facts and the questions they create (2 minutes).
- Decide: apply, ask first, or skip (1 minute).
Keep these notes next to the posting. They become the core of your cover letter, since a line like “I read this role as mostly about payments reliability” is more specific than anything on your resume, and they become your question list for the first call.
Where Zorlya fits
Reading postings by hand does not scale past a dozen a week. Zorlya scores each posting against your resume, skills, salary floor and location, and shows the four parts of the score, with one sentence on why the job fits once you refresh your matches, so you can see where it is strong and where it is weak. The score is a place to start, not a verdict, and the ten-minute routine above still applies to anything you plan to act on. The how it works page shows the steps, and the post on how Zorlya scores a job explains the four parts.