How the scores are built.

Workage keeps the signals it reads apart from the scores it produces, and shows you the arithmetic in between.

Building blocks
Eight, three of them openable scores
Ranking
Fixed, published weights
ATS
24 fixed checks, no AI
Learning
Outcome snapshots from application one

Eight building blocks

Candidate strength, company signal, and match fit open to the values underneath them. The rest are rules you can read in full.

Candidate strength

A calibrated profile score built from experience depth, proven skills, resume craft, GitHub evidence, and professional completeness, with the single largest gap named, not a vanity percentage.

Company signal

Company quality from five measured signals: responsiveness, hiring velocity, posting freshness, time to first response, and whether the employer is verified. Each carries its sample size, so a score from four applications is not shown as settled.

Explainable matching

Every match opens to its ten drivers: skill coverage, missing must-haves, seniority fit, domain alignment, compensation fit, location and remote fit, employer signal, your strength against the role bar, posting freshness, and competition. Open any score and you see the arithmetic.

Canonical skills

Skills resolve to canonical entries, not raw strings, so "Postgres", "PostgreSQL", and "psql" count once. Coverage is measured against what the role requires, weighted by what it insists on.

Repeatable ATS checks

Parseability, structure, and content checks run as fixed rules. Same resume, same score, every time. Language suggestions stay advisory and never move the number.

Freshness that decays

A 40-day-old post is not the same opportunity as one from this morning. Freshness decays continuously and reposts are collapsed, so a stale listing cannot pass as a live one.

Assisted, not automated

One-click apply on Greenhouse, Lever, and Ashby. Everywhere else the browser extension fills the form in your own session, highlights what it could not map, and you click Submit. Workage never submits silently.

Learning from outcomes

Feature snapshots and outcome logs let ranking improve over time, with replies, interviews, offers, and rejections all feeding back, without changing how the product feels to use day to day.

Four properties the scoring keeps

Same inputs, same score, every time.

Reproducible

Ranking is plain arithmetic with fixed, published weights. No randomness and no quiet drift between two views of the same posting an hour apart.

Every number traces back to a row.

Auditable

Open any score and you get the drivers, their weights, and the underlying values with their source and timestamp attached. If a match moved, you can find what moved it.

Thin evidence is marked thin, not hidden.

Calibrated

A job with thin extracted data scores neutral rather than flattering. An unverified claim is labelled as unverified. The product would rather say it does not know than guess convincingly.

AI never sets the ranking.

Bounded

AI reads files and drafts text. It does not decide the order. That line is the difference between a score you can check and one you can only argue with.

Three steps, kept separate

Everything is read into one record first.

Inputs

Resumes, code evidence, professional profiles, postings, company records, people, applications, and replies detected by the browser extension are read into your record, each detail with its source, before anything is scored. Reading and judging are separate jobs, and keeping them separate is what lets you check the second one.

Three scores, kept apart on purpose.

Scoring

Candidate strength, company quality, and match fit are computed independently. Collapse them into one figure and the product loses the ability to tell you which of the three is actually the problem, which is the only thing you needed to know.

The loop closes, then it sharpens.

Outcomes

Applications and results are logged against the feature snapshot that produced the recommendation. Ranking improves from what worked rather than from what sounded right, and the interface stays exactly where you left it.