Guide · Framework
How to know if a job is worth applying to
Most application advice tells you how to tailor a resume after you have decided a job is worth tailoring for. This guide is about the decision before that. It walks through a 7-signal framework, the same blocks RoleWorth's Worth Score uses internally, so you can score any posting in three to five minutes and decide Pursue, Maybe, or Skip before spending 30-90 minutes on a tailored package.
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 postings where the must-have requirements, level, or compensation do 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 signal 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. Target constraints
The strict definition: can you prove every must-have requirement 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. Job specificity
Job specificity asks whether the posting is serious enough to evaluate. A high-specificity posting names outcomes, team/function, seniority, tools, compensation, reporting line, and success criteria. A low-specificity posting hides behind generic verbs.
How to score: list the concrete information the posting gives you. Score 10 if the role has clear responsibilities, outcomes, level, team, work mode, salary or compensation logic, and application path. Score 5 if half the role is clear but the rest needs a recruiter question. Score 0 if the posting is mostly boilerplate, vague urgency, or a talent-pool intake.
Example:strong specificity says "own activation onboarding for SMB product surfaces, measured by time-to-first-value and activation rate." Weak specificity says "drive cross-functional initiatives in a fast-paced environment."
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 Target constraints: 9 — the role matches the scope, seniority, work mode, and compensation bar you set before tailoring.
- B Job specificity: 8 - responsibilities, outcomes, seniority, and team are clear.
- 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 Target constraints: 6 — broad enough to consider, but the must-have requirements are vague.
- B Job specificity: 5 - the posting lists broad responsibilities but hides team, success metrics, and reporting line.
- 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 Job specificity: the source mix is noisy. Prioritize company career pages, named teams, and roles with clear outcomes before tailoring.
- If most scores are 50-65 with weak target constraints: your targeting is too broad. Narrow the role titles, seniority levels, work modes, and compensation ranges you pursue.
- 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 signals against a single job, its source, its liveness evidence, and your target constraints. The 0-100 score is computed from the same 7-signal decision model: target constraints, job specificity, compensation, logistics, source trust, liveness, and ghost risk. The score is shown with a breakdown by block, so you can see which signal pulled the score down and decide whether the gap is fixable with a clarifying question or a source check.
RoleWorth makes the pursue / maybe / skip decision visible before you spend an hour tailoring. The decision is yours; the score is the input.
Quick answers
Why does this framework have seven signals?
Because three is too few to capture the real reasons applications fail, and twelve is too many to score in five minutes. Seven is the minimum that covers fit, job specificity, money, logistics, source trust, liveness, and ghost risk. Each maps to a block in RoleWorth's Worth Score.
Is this just gut feel with extra steps?
It is structured gut feel. The signals force you to score the things you would otherwise hand-wave. The most common application mistake is treating a posting as 'worth applying' because of a single strong factor while ignoring weak signals: unclear scope, weak source, stale repost, missing salary, or broken application path. The framework surfaces what your gut was missing.
How long should this take per job?
Three to five minutes for an initial scan, longer if a factor needs verification (checking the company source, asking the recruiter a clarifying question). The point is not perfection — it is making the apply/maybe/skip decision visible before you spend 30-90 minutes tailoring.
What if I score a job low but really want it?
Score low but want is a useful signal. It often means the role is aspirational, which is fine — but the application strategy is different. Aspirational roles should be paired with a referral ask or a recruiter conversation before submission. Cold applications to roles you score below 50 are usually not worth the resume-tailoring effort.
How does this connect to RoleWorth's Worth Score?
The seven signals are the same blocks Worth Score uses internally. The score is 0-100, computed from a decision model: A Target constraints, B Job specificity, C Compensation, D Logistics, E Source trust, F Liveness, G Ghost risk. The framework here is the human-readable version of the same logic, so you can run it manually or let RoleWorth run it on a batch.
Should I really skip a job that scores low?
Skip is not the only choice. The three honest options are Pursue, Maybe, and Skip. Maybe means 'send one clarifying question before tailoring' — a short message to the recruiter or hiring manager that tests whether the weak factor is real. Many Maybes upgrade to Pursue after one question. Skip is reserved for postings where multiple factors are weak or a scam-adjacent signal appears.
Sources