​🎯 The Challenge: Trust in the Hiring Funnel

​Hiring has a trust crisis on both sides of the funnel — recruiters can't tell which applicants are real, and candidates can't tell which employers are. Talent acquisition runs on a basic assumption: that the person applying is who they say they are, and that the company reaching out is who it says it is. Generative AI has broken both halves of that assumption at once. Your job for the day is to rebuild it.

​You can attack either side of the funnel — or the seam between them.

​Side A — Trust coming in: the applicant flood. A role that used to draw 30 applicants now draws 500, and a growing share aren't real, aren't qualified, or are gaming the system. Candidates embed hidden prompt-injection text to manipulate the AI tools that screen resumes. And increasingly, applicants appear qualified but look strikingly alike — the same phrasing, the same structure, the same accomplishments — a tell that everyone is leaning on the same AI tools to write their applications. Recruiters are drowning, and the tools meant to help have no clear winner yet. The challenge: reliably separate real, qualified humans from AI-inflated noise — without punishing legitimate candidates who simply used AI to polish their resume.

​Questions worth chasing:

​- What signals — behavioral, identity, provenance — actually distinguish a real applicant from a manufactured one?

​- When applications converge on the same AI-generated look, how do you tell genuine signal from sameness?

​- How do you detect a manipulated or machine-generated application without false-flagging honest people?

​- How do you surface the candidates who deserve attention fast, inside an existing recruiting workflow rather than replacing it?

​Side B — Trust going out: impersonation and candidate scams. Bad actors register look-alike domains to send fake offer letters, run deepfake recruiter calls, and scam job seekers out of money and data. Employers have almost no way to detect it or warn candidates. The challenge: make it harder to impersonate a real employer, and easier for a candidate to verify that an offer or a recruiter is genuine.

​Questions worth chasing:

- ​How would a candidate confirm that an offer or outreach is legitimately from the company?

- Can impersonating domains be detected and flagged early?

- What does a lightweight "trust signal" look like on a careers page or an offer letter?

• Design (out of 5)
  Is it usable and coherent? Would a recruiter or candidate actually understand and trust the interface in the moment they need it?
• Uniqueness of Idea (out of 5)
  Does it attack the trust problem from an angle that isn't already a crowded field of look-alike tools? Original framing of the signal or the verification approach counts here.
• Technical Execution (out of 5)
  Does it run? We reward a real, demonstrable solution to a narrow slice over a broad concept that doesn't work. Bonus for fitting into a real hiring workflow (e.g., plugging into an ATS) rather than replacing it.
• Real-World Impact (out of 5)
  Does it solve a big real world problem?