Decision-first job search
How to tell if a job is worth applying to
Effort vs expected return
| Lever | Effort | Return |
|---|---|---|
| Tailor resume bullets | low | high |
| Personalized cover note | medium | medium |
| Recruiter DM | low | high |
| Ask for referral | high | very high |
The 7-signal job-worth framework
Prefer the company career page, a named recruiter, or a referral path. Treat aggregator-only listings as lower confidence until confirmed.
Newer is not always better, but a role older than 30-45 days or repeatedly reposted deserves a Maybe until you see active hiring motion.
Look for team, manager, outcomes, tools, level, and interview path. Vague scope makes tailoring harder to justify.
Name 3-5 real projects, metrics, artifacts, or responsibilities that map to the job's must-have requirements.
Compensation, location, work authorization, travel, schedule, and seniority must be workable before you invest in a custom package.
A quick apply is cheap. A tailored resume, cover note, recruiter DM, and interview prep is a serious unit of attention.
Every good decision ends with one action: apply, ask a clarifying question, request a referral, save for later, or skip.
Apply / Maybe / Skip
Fresh source, clear role, workable logistics, and strong proof match.
Tailor the resume, draft the recruiter note, and move it into the tracker with a follow-up date.
Credible employer, but one or two signals are missing or unclear.
Ask one precise question before tailoring: compensation range, team scope, remote geography, or whether the team is actively reviewing.
Multiple risk signals stack up or a hard dealbreaker fails.
Do not spend a custom package. Save the pattern as search intelligence and move the hour to a stronger role.
Why this matters
FAQ
Product proof
See the product surface behind the claim.
Each page carries the matching RoleWorth surface in a glass-framed proof card: the radar, extension overlay, ATS matrix, review queue, dashboard, or package flow behind the promise.

The public promise, visible above the fold: score first, package second, approve before anything leaves.

Batch scan, ghost-risk skipped count, high-worth jobs, and Apply/Maybe/Skip routing in one product surface.