What sort of positive signal is this supposed to be? Why would presenting point towards a productive employee?
In my experience, this correlates more with soft skills and “one man band” founder/maker companies that tend to sell training products or (if they do exist in a company environment at all) invariably work in DevRel and aren’t pushing code.
This can be found all the time, from many tech talks or conferences large or small and 99% of the time, the person presenting already covers most of the requirements and makes the selection process easier, not harder.
One part I did miss in my post was to require at least 2 out of 3 of them so, I added that in. But I'd rather optimize for hiring candidates who are builders and know what they are talking and what to build even with AI and can easily answer deep technical questions (because they have experience and have done it), than those studying for the interview and need constant hand-holding and are over-reliant on AI.
Remember, this is for recruiting founding engineers and the bar has to be high way above the noise.
Your criteria heavily biases towards very performative and obvious signs of hard work in a commercial setting, completely oblivious to hard work and character outside of it.
Hiring people based on knowing what should be built, how to build and especially knowing how to make the business money is not performative. I'd rather optimizing the hiring process for builders instead of rest-and-vest day-care slackers or leetcode grinders just for passing the interview.
There is nothing more performative than anyone doing these puzzles and answering quiz trivia, which doesn't make you or anyone money and it is only a waste of everyone's time.
Some of the absolute best candidates were always the ones with a github that hadn't seen a commit in half a decade, nary a presentation or conference mentioned in their cv. This was true at two different FAANGs and a couple of other FAANG-adjacent companies.
And surgeons should also have a track record where they can talk about how they do open heart surgery during their free time at home…
A verifiable track record beyond the CV, that is extremely hard to fake with valuable experience that you did not know you needed.
As I said before:
1. Open source contributions to high-profile / major repositories (with code-review in the open with core maintainers). No hello world / demo projects.
2. Production-grade shipped projects / side-projects with paying customers or high-profile companies using it and is bringing in recurring revenue.
3. Given several presentations at conferences discussing anything from your project as a library author, maintainer or at a company showcasing your engineering expertise.
All are extremely difficult to fake and easy to verify and requires a level of effort on the applicant to qualify which filters 90% of noise out there. Years of experience is not a requirement but a bonus.
The rest of the other methods like leetcode, hackerrank, take home projects or quiz trivia, wastes time on both the interviewer and the candidate and both can be cheated easily using AI.
It is that simple.