Evidence pipeline - consent-first
This is not a social-proof wall. Each row below is an evidence format RoleWorth is instrumented to collect: the starting problem, the product surface involved, and the outcome signal required before anything becomes a public evidence note. Entries marked draft format are measurement designs, not claims about signed customer results.
Spending two hours tailoring Workday applications that later looked stale, reposted, or low-fit. Wanted to know which roles deserved the tailoring hour before opening a doc.
Surface used
Worth Score gates everything
Outcome signal needed
Draft format: use Worth Score to separate low-signal postings from roles worth tailoring, then spend package work only on roles that clear the decision bar.
Resume keywords matched DevRel jobs, but the actual proof story was scattered across product launches, community work, and technical writing.
Surface used
Resume Match Check + Application Kit
Outcome signal needed
Draft format: pair the keyword gap report with proof points from the user's own resume so the package reads specific instead of generated.
Clients pasted job links into Slack. The coach manually checked posting age, recruiter activity, salary band, and fit before giving advice.
Surface used
Partner referral program + batch run
Outcome signal needed
Draft format: run a weekly batch over client links, flag ghost-risk and weak-fit roles first, then send clients only the opportunities worth tailoring.
RoleWorth will not publish interview-rate, time-saved, or ghost-job-avoidance claims until the underlying outcomes are real, consent-safe, and reviewable. If you want to contribute an early study, write to hello [at] roleworth.com. We will redact sensitive details and give you final sign-off before anything goes live.