About

I'm Shaphy, founder and CEO of Talentz.ai. I'm building Zee, a team of AI agents that finds, engages, and assesses candidates on proof of work instead of resumes, so the agents do the heavy lifting and the hiring manager makes the call. Before this I built PriceSenz, an AI-first services company, and I write Tech Vibes with Shaphy on building agent-first companies in public.

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking

Maker History

  • Talentz
    TalentzThe signal layer for hiring.
    Aug 2026
  • 🎉
    Joined Product HuntAugust 6th, 2026

Forums

1mo ago

180 applications for one engineering role. 40 of them were the same resume.

180 applications for one senior engineering role last month. About 40 read like the same resume.
Same action verbs. Same keyword density mapped to the JD. Same metrics with no context attached. Written for the parser, not for a person.
The standard fix is detection. Spot the AI resume, discount it. But detection only tells you the document is unreliable. It tells you nothing about who is actually good. You have filtered noise and gained zero signal.
So the first filter is now doing no work, and everyone is still running it.
I have started skipping the resume as the opening screen and looking at what someone has actually shipped instead. Better signal. Slower. Does not scale cleanly yet, and it disadvantages people whose best work is behind an NDA.
Disclosure, I build hiring software, so I am biased toward thinking the resume is the wrong input. Which is why I want the argument and not the agreement.
Two questions.
  What phrase are you seeing on repeat? Mine is spearheaded cross-functional initiatives.
  If you dropped the resume as filter one, what replaced it, and what broke?

View more