Northstar Technical Search
Reviewed with Work Proof
Report v1
Sep 4, 2026
Developer work evidence report
Sam Rivera
Claim coverage unavailable
Claims checked: unknown. Overall evidence coverage: 76%. Claim-level evidence must be established before showing a score. Account and website availability alone do not verify work.
Executive summary
Too few resume claims have documented comparable evidence to show a scored summary. Account or website availability does not verify the candidate’s work. Review the individual claims and discuss responsibilities and outcomes in the interview. Missing public evidence does not imply the work did not happen.
Claims reviewed
Resume statements compared with captured public evidence.
Designed and maintained a TypeScript API service.
Public repository history shows relevant API routes, validation, tests, and activity over fourteen months. This supports project presence and activity, not sole authorship or reported impact.
Production experience with PostgreSQL and schema migrations.
Migration files and query code support hands-on use. Production traffic and operational responsibility are not public.
Reduced API latency by 40% at a previous employer.
Employment, education and certifications need an authoritative source such as the employer, the institution or the issuing body. Work Proof does not check them, and their absence here says nothing about the candidate.
Findings worth reviewing
Deterministic prompts for human review, not hiring decisions.
A portfolio project could not be linked to a public repository.
info · site not linked to repo
Public artifacts checked
Interview questions
A mixed bank of questions, mostly from the resume, plus the role and any candidate-linked code, each with what to listen for and follow-ups. Resume topics also work without public code.
Why does the request handler validate the idempotency key before opening the database transaction?
Revision unavailable in this older source snapshot; exact-line authorship is not established.
sample/api-service · src/routes/payments.ts:42-78
Model answer
It rejects malformed requests before taking a database connection or lock, while the transaction still enforces the uniqueness boundary for valid concurrent requests.
Follow-ups
- What race condition still needs a unique database constraint?
- How would you test two requests arriving at the same time?
What can go wrong if this migration adds the non-null column in one step on a large table?
Revision unavailable in this older source snapshot; exact-line authorship is not established.
sample/api-service · db/migrations/024_add_workspace_key.sql:1-18
Model answer
The rewrite or lock can block traffic. A safer rollout adds a nullable column, backfills in batches, adds validation, then enforces non-null separately.
Follow-ups
- How would you monitor the backfill?
- When could the one-step migration still be acceptable?
Resume answers are discussion guides; the candidate must explain their own work. Code references confirm activity on a file path, not authorship of every line. This pack is included in the exported PDF.