careerscorebuild your score

one score,(with receipts)

the verified proof-of-work index for tech talent.

Converts scattered evidence into a domain aware score, an evidence passport, and a path recruiters trust as a screening shortcut.

why now — the problem
candidate

proof is scattered (and self-claimed)

Evidence is spread across a GitHub account, a portfolio domain, a Vercel deployment, a hackathon Devpost, three certificates in three issuer portals, a transcript, and a PDF resume that flattens all of it into bullet points anyone can fabricate. There is no single, trusted, portable artifact.

recruiter

screening is manual & noisy (and prestige-biased)

Screening means manually reconstructing the same four things every time — education, skills, experience, projects — from documents that are unverified by default. At volume this collapses into crude proxies: university brand, keyword matching, referral networks.

the wedge

produce a verified, domain-calibrated evidence profile that a candidate owns and a recruiter can trust at a glance — and we sit between both sides of a transaction that is painful for both.

what the user gets — the product
AI / Machine LearningFinal-year / New-gradverification confidence 83%
0
/ 1000
CAREERSCORE
Proof-of-Work / Projects
0/250
Skill Signal
0/200
Education Signal
0/150
Experience Signal
0/150
Market Readiness
0/100
Identity & Evidence Quality
0/100
Momentum
0/50
742/1000

careerscore — domain-adjusted, norm-referenced

83%

verification confidence — weighted evidence at L2+

78th

percentile — vs. new-grad ml profiles

figure 3.1 — two headline numbers (score + confidence), a detected domain, and a per-pillar breakdown where every bar is clickable down to its evidence.

first principles — the physics
01

the llm never sets the score

The model only extracts facts and explains results. The score itself is deterministic TypeScript over numeric features. Same evidence in → same score out, every time.

02

two numbers, never one

We always emit Score and Verification Confidence separately. A 900 at 40% confidence and a 720 at 92% are different objects — confidence is what makes a score safe to share.

03

proof-of-work outranks prestige

Prestige is capped; shipped, verifiable artifacts dominate. A candidate from a weaker school can — and should — outrank a prestige profile through real work.

04

the ruler depends on the domain

There is no universal “tech” ruler. Each detected domain supplies its own weight vector and proof checklist, so the score measures the right things.

05

raw points mean nothing alone

742 is meaningless in isolation — exactly like a raw SAT count. Every score is norm-referenced to a percentile within domain and career stage.

06

honesty before predictiveness

We launch a transparent heuristic, collect outcomes, then calibrate the weights against success. We never claim predictive power we have not earned.

the differentiator — domain intelligence
select a domain

research-tilted: education and momentum rise; published benchmarks and model cards count.

signature fingerprint
torchtensorflowtransformersCUDApapers

AI / ML — research-tilted

ai / ml research

sum = 1000
Proof-of-Work
250
Skill
200
Education
190
Experience
110
Identity / Evidence
100
Market
90
Momentum
60

table 6.3 — illustrative domain weight matrix; every row sums to 1000. a backend engineer applying for ml roles can switch their target domain and see how they score on the ml ruler.

trust mechanics — verification
six evidence levels
  1. L0
    self-claimed

    User typed “I interned at X.”

  2. L1
    document uploaded

    Internship certificate PDF on file.

  3. L2
    public source cross-checked

    GitHub repo / portfolio / hackathon page matches the claim.

  4. L3
    oauth / api verified

    GitHub connected via OAuth; account identity confirmed.

  5. L4
    issuer verified

    University email, company email, signed certificate, Credly badge.

  6. L5
    partner verified

    An institution or employer partner confirms directly.

the two-number model, in practice
742/1000
83%
78th
verified evidence (L2+)
0/100
norm percentile (ml new-grad)
0/100

a self-claimed resume has zero marginal trust. a signed, evidence-graded, domain-calibrated profile has real trust — the only thing that lets an employer act on the output.

from diagnostic to infrastructure — the hiring bridge
stage 1

candidate diagnostic

risk: none

Private, candidate-facing score, passport and roadmap. Zero employment-law exposure. This is the entire MVP.

stage 2

candidate-controlled sharing

risk: low

The candidate generates a signed verified profile and chooses to send it. Candidate-initiated, consentful — the recruiter gets pre-verified evidence.

stage 3

employer screening-assist

risk: regulated

Employers see ranked, domain-matched, evidence-backed candidates — but the tool never auto-rejects. A human decides. Full compliance scaffolding required before launch.

stage 4

verified talent infrastructure

risk: high / later

Talent pool, ATS & assessment integrations, partner API. Network effects compound. Only after Stage 3 is proven, audited and trusted.

Human-in-the-loop, never auto-rejects. Explainable, job-related, bias-audited — age and protected attributes are excluded as inputs.

how it is built — built to be trusted
01DET

ingest

CV, GitHub, links, certs → private storage

02DET

parse / ocr

PDF / DOCX / image → text

03LLM

extract facts

Structured claims via constrained LLM

04DET

verify

OAuth, issuer, cross-check → evidence level

05DET

classify domain

Primary + secondary + confidence

06DET

feature extract

Facts → numeric feature vector

07DET

score

Domain weight vector → pillars → total (deterministic)

08DET

norm

Percentile vs. domain × stage cohort

09LLM

explain

LLM narrates score + roadmap

10DET

profile

Passport, signed share, dashboard

deterministic / verifiable llm-assisted (extraction & explanation only)

if the score matters, people will attack it.

the governing rule: self-claimed inflates nothing. the cheapest path to a higher score is to do verifiable work.

  • upload someone else’s cvIdentity binding; name/email match across connected accounts; phone verification for any public score.
  • fake or borrowed githubOAuth connect; account age, contribution graph and email signals; mismatches flagged.
  • fork-farming repositoriesForks earn nothing without detected meaningful contribution; original commit history required.
  • ai-generated “projects”Require live URL + commit history + deployment metadata; reward sustained history over one-shot dumps.
  • prompt injection in a resumeAll uploaded text is untrusted input — it can never alter system prompts or scoring logic.
careerscore — early access