Is This Job Worth Applying To? A Five-Step Test That Ends in Apply, Ask First, or Pass
Definition. Whether a job is worth applying to depends less on how well you match it than on how many essential conditions the posting leaves unclear. When those conditions are unclear, the correct move is Ask First, not apply anyway.
Most “should I apply” advice collapses into a match score: count the requirements you meet, divide by the total, act on the result. That arithmetic answers a different question — whether you could do the job — and ignores the one that determines your cost: whether the posting tells you enough to know what the job is. A role you match at 90% can still be a bad use of your week if three essentials are missing from the text.
This framework is the one JOBOK applies to a posting. It is a decision aid, not a forecast: it tells you which action is justified by the information you have, not whether you will get the job.
Step 1: Split the text into three tiers
Read the posting as three different kinds of sentence, not one block of demands.
- Tier A — stated requirements. The section labelled requirements, qualifications, or “what you bring”. This is the only place a hard gate can live.
- Tier B — responsibility descriptions. What the person does all day. A description of work is not a bar to entry.
- Tier C — unspecified. Everything the posting should have said and did not: reporting line, team size, success metric, compensation structure.
The most common screening error is treating Tier B as Tier A: reading “own the roadmap” as “must have owned a roadmap”. The second most common is skipping Tier C entirely, because its absence is invisible.
Step 2: Check six essentials, one by one
Mark each as resolved or unresolved. Resolved means the posting states it in words, not that you can guess it.
- Scope split — how much of the job is strategy, execution, or support.
- Decision chain — who this role reports to and who overrules it.
- Success metric — what performance is measured on in the first six months.
- Compensation structure — base, variable, and how variable is calculated, in numbers.
- Employment form — permanent, fixed-term, contract, freelance trial, and work authorization terms.
- Process — number of stages, expected timeline, and who interviews.
A newly created role has no predecessor to define the decision chain or the success metric, which is why those two deserve an explicit question rather than a best-case assumption.
Step 3: Confirm the posting is live
A decision framework applied to a dead posting is wasted work. Check the posting date, whether the same role appears under several titles, whether the requirements are copy-paste generic across unrelated roles, and whether the company has published anything about the team this role sits in. JOBOK publishes a free rule-based check for posting dates and common ghost-job signals; it uses no AI and consumes no credits. (JD Decode)
Step 4: Name what would change your mind
Before assigning a verdict, write one sentence: “I would not apply if ___.” A single disqualifying condition — an on-call rotation you cannot take, a commission-only structure, a relocation requirement — outranks every match percentage. If you cannot name one, you have not finished reading the posting.
Step 5: Assign the verdict by rule, not by mood
| Verdict | Trigger | Next action | What it is not |
|---|---|---|---|
| Apply | 0–1 essentials unresolved, no disqualifying condition, Tier A requirements evidenced | Tailor and send; prepare the unanswered essentials as interview questions | A prediction of an interview |
| Ask First | 2–3 essentials unresolved, but the role is plausible on what is written | Contact the recruiter or hiring manager with the specific questions; decide after answers | A softer way of saying no |
| Pass | 4+ essentials unresolved, or any disqualifying condition present | Stop work on this posting; revisit if the posting is revised | A judgment about the employer's quality |
The boundary matters more than the labels. Ask First exists because a binary apply/don’t-apply choice on incomplete information shifts all the uncertainty onto you. The output of Step 5 should therefore be the verdict plus the unresolved list that produced it — not the verdict alone.
Printable checklist
- Tier A requirements listed separately from Tier B duties
- Six essentials marked resolved or unresolved, with the exact wording noted
- Posting liveness checked (date, duplicate titles, generic requirements)
- One disqualifying condition written down, or explicitly ruled out
- Verdict assigned by the rule in Step 5
- Unresolved essentials converted into questions for the employer
Frequently asked questions
How many unresolved items justify Ask First?
This framework draws the line at two to three unresolved essentials out of six, with no disqualifying condition. Below that, the information is sufficient to act; above it, you are making a decision on assumptions rather than evidence.
Isn't Ask First just delaying the application?
It is a different action with a shorter path: a recruiter can answer two questions in one message. Delaying would mean waiting without asking; Ask First means the application waits until the answer arrives.
What if the posting has no requirements section at all?
Then every Tier A gate is unresolved, which is itself the finding. Treat the whole posting as Tier B and Tier C, and ask for the requirements in writing before investing tailoring time.
Does a high match score ever outweigh missing essentials?
No, for the reason in the definition above: fit predicts whether you could do the work, while missing essentials predict whether you understand what the work is. This framework deliberately ranks the second question first.
Sources
- JOBOK JD Decode (product page): https://jobok.app/jd-decoder (accessed 2026-11-04)
- JOBOK pricing and free quota: https://jobok.app/pricing (accessed 2026-11-04)