Menu
Case file 05 · Marketplace · Hiring

ZapMyJob

Hiring by proof of work: artifacts, micro-tasks and voice screening instead of resumes.

File summary

Beta
Filed under
Marketplaces, Voice AI
Built by
Varun Chennuri, with an AI engineering team

01

The problem

A resume says what someone claims they can do.

ZapMyJob asks for proof instead.

02

What I built

Hiring by proof of work, instead of resumes.

  • Artifacts: work a candidate has actually made.
  • Micro-tasks: short, real pieces of work.
  • Voice screening.
  • Now in beta.

03

How AI agents built it

Built with the two-model loop from How I build.

  1. [PLACEHOLDER: ZAPMYJOB-SPECIFIC BUILD NOTES]
See the full method

04

Architecture sketch

Drawn the way it sits on my desk: boxes for the moving parts, arrows for the flow, dashed lines for what is wired in alongside.

  1. 01CANDIDATE
  2. 02PROOF OF WORKartifacts micro-tasks voice screening
  3. 03HIRING TEAMdecides on proof, not resumes
ZapMyJob proof-of-work sketchA candidate builds a proof-of-work profile from artifacts, micro-tasks and voice screening, and the hiring team decides on that proof instead of a resume.CANDIDATEPROOF OF WORKartifactsmicro-tasksvoice screeningHIRING TEAMdecides on proof, not resumes
ZapMyJob proof-of-work sketch:A candidate builds a proof-of-work profile from artifacts, micro-tasks and voice screening, and the hiring team decides on that proof instead of a resume.

05

Results

Real numbers only. Anything not confirmed yet is marked as a placeholder.

  • Betacurrent statusBasis: ZapMyJob
  • [PLACEHOLDER]confirmed beta numbersBasis: To be confirmed

06

Stack

  • [PLACEHOLDER: STACK]
StatusBeta

Next step

Want this for your company?

Start a 7-day sprint and get a working AI product: two AI models that review each other, tests on every change, and me on every risky call.

Start a sprintRead how I build