How to know if a job is worth applying to

Why this decision matters more in 2026

Greenhouse's 2026 update to its State of Job Hunting research reports that three in five candidates suspect they have encountered a ghost job, and Greenhouse platform data classifies 18-22% of postings as ghost jobs. Combine that with the share of postings where the requirement spine, level, or compensation does not match a serious applicant, and the share of postings that are truly worth a tailored package is a minority of what you see on aggregator job boards.

The cost of getting this wrong is concrete: 30-90 minutes per tailored application, multiplied by every weak posting that should not have been in the batch. The cost of getting it right is three to five minutes of structured scoring before you start.

The 7 factors

Each factor is independent — a strong score on one does not compensate for a weak score on another. Score each from 0 (weak) to 10 (strong). Below 50 total points usually means Skip or send-one-question Maybe. Above 70 usually means Apply with a tailored package.

A. Role fit

The strict definition: can you prove every must-have line in the requirement spine with a concrete project from the last three years? Not nice-to-have lines, not filler lines, not adjacent experience. Must-have lines.

How to score: list the 4-7 must-haves. For each, ask whether you have a project where you owned that work, not just touched it. Score 10 if every must-have is a clear owner-level match. Score 5 if half are owner-level and half are participant-level. Score 0 if fewer than half are owner-level. The most common application mistake is applying to roles where you have done some of what is asked but never owned the work — recruiters can tell.

Example — strong fit:a posting asks for "5+ years owning enterprise SaaS sales pipeline with $1M+ annual quota." You have 6 years of named pipeline ownership across two companies with documented quota achievement. Score: 10.

Example — weak fit: the same posting; you have 3 years of inside-sales experience with no named pipeline and no quota documented. Score: 3.

B. Proof strength

Even when role fit is real, the resume cannot make the match obvious without concrete proof. Proof strength asks: do you have specific metrics, scope, tools, stakeholders, and outcomes that map to the must-haves?

How to score: for each must-have you scored as a real fit, count whether you have at least one bullet-ready proof point — a number, scope, tool, named stakeholder role, or measurable outcome. Score 10 if every must-have has at least two proof points. Score 5 if half do. Score 0 if most claims would have to be made without proof.

Example:the must-have is "built and shipped onboarding flows." Strong proof: "designed and shipped activation onboarding for 18 product surfaces, reducing time-to-first-value from 11 days to 4." Weak proof: "worked on onboarding projects."

C. Compensation

Salary transparency laws now cover postings to candidates in California, Colorado, Hawaii, Illinois, Maryland, Minnesota, New York, Washington, and several other US jurisdictions, with similar disclosure rules under the EU pay-transparency directive. If a band is required and missing, that is a yellow flag for posting legitimacy (factor G) and a separate question for compensation.

How to score: if the band is published, score 10 if the midpoint covers your minimum acceptable comp, 5 if the band stretches enough that the high end is acceptable but you would need to negotiate, 0 if the high end is below your minimum. If the band is missing and not legally required, score from your own research on the company and level. If the band is missing where required, score 3 — the absence itself is a posting-quality signal.

D. Growth upside

Compensation buys this year. Growth upside buys the next five. Growth upside includes scope of role responsibility, stage of company, peer caliber, product surface, exposure to senior leadership, and equity if relevant.

How to score: ask three questions. Will this role expand the scope of work you can credibly claim two years from now? Will the team and peers raise your ceiling? Will the company stage and trajectory make the resume line valuable in three years? Score 10 if all three are yes; 5 if two; 0 if fewer than one. Lateral moves with no growth upside score low even when comp is right.

E. Logistics

Location, remote scope (remote-global vs remote-US vs remote-state-of-CA-only), commute, travel expectations, time zone overlap requirements, visa sponsorship, security clearance. These are the boring factors that disqualify candidates after several rounds when they could have been checked in 60 seconds at the top.

How to score: 10 if every logistical constraint is a clear yes. 5 if one constraint is ambiguous and would need a clarifying question. 0 if any constraint is a clear no (you do not have the visa status the role requires, the time zone overlap is impossible, the on-site requirement is incompatible). One no on logistics is enough to skip; do not tailor for roles you cannot legally or practically take.

F. Market signal

Market signal is everything around the role: how is the company doing, is the team growing or contracting, are funding cycles or earnings consistent with hiring, what do former employees say, is the function strategic or cost-center, are layoffs recent? This is the factor most easily glossed over and most often determines what the role is really like inside.

How to score:spend 5 minutes on the company. Recent funding, earnings, headcount trend (LinkedIn employee count is a public, noisy, but useful proxy), press coverage, and Glassdoor/Blind sentiment for the team if available. Score 10 if signals are clearly positive and the role is core to the company's next year. Score 5 if signals are mixed. Score 0 if signals are clearly negative (recent layoffs in the function, missed earnings, public restructuring).

G. Posting legitimacy

Is the posting an active, specific hiring motion or a ghost? The four pattern categories RoleWorth flags via regex are commission-only language, training-fee scams, vague-scope filler, and low-specificity urgency. Additional manual signals: stale repost dates, missing hiring manager or team, no clear timeline, missing or absurdly wide salary band, talent-pool routing, company-source mismatch, and broken application links.

How to score:10 if the role appears on the company's own careers page, is fresh, has a clear team or manager, lists a real band, and the application path works. 5 if one or two signals are weak. 0 if three or more weak signals or any scam-adjacent hit. The BLS JOLTS definition of a job opening (specific position, available work, start window inside 30 days, active recruiting) is a useful baseline. If you cannot defend the posting against that definition, score it down.

Worked example: high-score role

Senior Product Manager, growth-stage SaaS, posted on company Greenhouse board, 11 days old, two referrals from your network.

• A Role fit: 9 — you have 5 years of PM ownership at similar scope; every must-have maps to a real project.
• B Proof strength: 8 — three concrete shipped outcomes with metrics and named stakeholders.
• C Compensation: 9 — published band, midpoint matches target.
• D Growth upside: 8 — team is strong, peer caliber raises ceiling, stage is right.
• E Logistics: 10 — remote-US, no visa issue, time zone fine.
• F Market signal: 8 — recent Series C, function is core, recent press positive.
• G Posting legitimacy: 9 — on company careers page, fresh, hiring manager named in posting.

Total: 61 / 70 = 87%. Apply with a fully tailored package. Pair the application with a referral ask and a recruiter note within 48 hours.

Worked example: low-score role

Same job title, posted on an aggregator job board, no company name visible at the company source, posting 47 days old, third repost in 90 days, no salary band where one is required.

• A Role fit: 6 — broad enough that you fit, but the requirement spine is vague.
• B Proof strength: 5 — you have proof, but the posting does not say what you should be proving.
• C Compensation: 3 — no band where required.
• D Growth upside: 4 — company is unclear at the source.
• E Logistics: 7 — looks fine but no specifics.
• F Market signal: 3 — cannot find the company on the company's own site.
• G Posting legitimacy: 1 — stale, reposted, missing band, no team.

Total: 29 / 70 = 41%. Skip outright, or send one precise clarifying question before tailoring ("Is this role actively interviewing this month, and which team owns it?"). Do not invest a 60-minute tailoring session.

How to use the framework in a batch

The framework is most valuable when used across a batch, not a single role. Score 20-30 postings in one sitting (three to five minutes each). The distribution of scores tells you what to do next:

• If most scores are below 50: the source mix is wrong. Stop applying from aggregator boards and shift to company-careers pages, referrals, and recruiter networks.
• If most scores are 50-65 with weak Proof strength: the bottleneck is your proof bank, not the postings. Spend a session documenting concrete projects with metrics before applying to more.
• If most scores are 50-65 with weak Role fit: your targeting is too broad. Narrow the role titles and seniority levels you apply to.
• If a few scores are 70+: apply to those with full tailored packages and a follow-up plan. Skip the rest.

How RoleWorth runs this for you

RoleWorth's Worth Score automates the seven factors against a single job and your Proof Bank. The 0-100 score is computed from the same 7-block heuristic — A Role fit, B Proof strength, C Compensation, D Growth upside, E Logistics, F Market signal, G Posting legitimacy. The score is shown with a breakdown by block, so you can see which factor pulled the score down and decide whether the gap is fixable with a clarifying question or a proof addition.

RoleWorth does not promise interviews. What it does is make the apply / maybe / skip decision visible before you spend an hour tailoring. The decision is yours; the score is the input.