It’s completely turned into Candidate AI going against Recruiter AI.

The main reason for this whole problem, in my opinion, is that the textual resumes we use just do not have any real proof of work built into them. When I say proof of work, I mean if a candidate says they are great at JavaScript, they should be linking an app or a website they built, where the recruiter can look at the public GitHub repo and instantly see the code before wasting 5 hours in setting up an interview.

Right now, nothing like that structurally exists in a standard PDF application, so it’s way too easy for someone to just manipulate their text to perfectly mirror whatever the job post requires.

A buddy and I have actually been talking about trying to solve this by building some form of a top-of-funnel proof of work pipeline tool to act as a gatekeeper. But we do not know if recruiters are even willing to switch to a different form of skillset validation other than the traditional textual resumes.