- The problem
- Fake resumes, cloned portfolios and duplicate profiles, with no tool built to catch them.
- What I did
- Designed a verification prototype, tested it, then rebuilt the idea around a role-based trust score.
- Where it landed
- A complete MVP design: new verification, candidate profile and dashboard, ready to build.
What recruiters kept saying
- “I spend more time verifying a candidate than actually interviewing them.”
- “Fake resumes are one thing. But I’m more afraid of not catching them.”
- “I don’t want to chase down 6 tabs. I just need a signal I can trust.”
Recruiters became detectives
Remote hiring made it easy to apply from anywhere, with anything. Recruiters on r/recruiting, Hacker News and LinkedIn described the same wall: resumes that looked solid and fell apart on a second look, portfolios full of projects no one could verify, and candidates who weren’t real people at all.
Their tools weren’t built for it. So they googled, cross-checked links and back-channeled, or made a gut call. My problem statement for the first version was simple: help recruiters verify candidates in real time, so they waste less effort on fraudulent applications.
Chapter one: Simple Tech Talk
Simple Tech Talk was a startup connecting technical talent with recruiters, and verification was one tool inside it. My co-founder sparked the idea and led development; I led the research, flows and interface in a four-week sprint.
I had no direct access to recruiters then, so I collected their complaints from forums, clustered them in affinity maps, and built a persona from the pattern: Adrienne, a lead technical recruiter with no time to learn a new tool.
- Search. Look a candidate up by name, email or phone.
- Signals. Pull LinkedIn, GitHub and Facebook, and flag duplicates or mismatches.
- Verify. Send a verification email the candidate has five minutes to answer, with three tries before they’re marked unverified.
- Status. Every candidate shows Verified, Timed Out or Failed at a glance.
The sixth session
I ran six usability sessions with peers and non-recruiters. Five found the flow intuitive; one missed that the recent activity panel scrolled, which I fixed. The sixth asked one question that undid the product:
“What if the candidate has multiple emails… or gives someone else access?”
Usability participant, session six
The interface worked. The logic didn’t. Confirming an email doesn’t confirm who is behind it. I had designed for saving recruiters time, when what they needed was a reason to trust someone. Good UX can’t fix a broken concept, and the project stopped before it shipped.
Chapter two: SimpleVerify
Years later, with more product experience and a new technical co-founder, I came back to the same problem. This time the research went further: thread synthesis across Reddit and LinkedIn, interviews with technical recruiters, and affinity mapping to cluster what kept coming up.
Three composite personas kept the design honest about speed, scale and accountability:
- The lead technical recruiter. Dozens of open roles and no time to learn a tool. Every feature had to make her faster.
- The agency sourcer. Forty to fifty candidates a day. Summaries had to be skimmable and sortable.
- The operations manager. Decisions had to stand up to scrutiny, which led to audit logs, exports and override notes.
What changed
The old flow was a gate: the candidate answered an email in five minutes or failed. The new one is a picture that keeps filling in. SimpleVerify starts working the moment a recruiter adds someone, and the recruiter makes the final call.
A score you can question
The first version said yes or no. SimpleVerify gives a layered trust score and shows its work. It reads public signals and the candidate’s own uploads, flags inconsistencies, and explains every flag. A flag for possible AI writing is a reason to look, not an automatic fail.
Three core flows
- New verification. Enter a candidate’s name, email, phone and role. SimpleVerify gathers public signals right away and sends the candidate a branded request for their resume and portfolio, so a profile exists before they reply.
- Candidate profile. The trust score and how it was composed, each signal with its match confidence, the resume scan, and the recruiter’s notes and overrides.
- Dashboard. Candidates to review, recent verifications, AI alerts and a timeline of what the team verified, flagged or overrode.





Where it stands
The MVP design is complete. The next steps were the build with my technical co-founder, integrations with Greenhouse and Lever where recruiters already work, and pilots with small recruiting agencies to test it on real hiring.
The longer idea is a candidate trust passport: a verified history a candidate owns and carries from one application to the next, so honest people don’t prove themselves from scratch every time.
What I learned
The first version taught me that clean flows can hide a weak idea, and that the most useful session is the one that breaks your logic. It also taught me the limits of designing from forum posts: real insight came from talking to recruiters, which is what I did the second time.

