Skip to main content

Hiring developers post-AI

·1 min
Kristof Kovacs
Author
Kristof Kovacs
Software Architect & DevOps Consultant

Hello, I’m Kristof, a human being like you, and an easy to work with, friendly guy.

I've been a programmer, a consultant, CIO in startups, head of software development in government, and built two software companies.

Some days I’m coding Golang in the guts of a system and other days I'm wearing a suit to help clients with their DevOps practices.

Hiring devs post-AI, update: we trying a new approach for our preliminary coding test. Our pre-AI approach was that we asked candidates to code up a small URL shortener from scratch, but if you remember me telling about it, the last time we've received 40+ submissions (most clearly AI) compared to the usual 4-6 pre-AI.

Which is kinda okay (we too use AI to boost coding, we are not backward savages šŸ˜…), but AI is just too good at coding small "hello world" things from scratch even without much oversight, and I don't learn anything about the candidates.

With our new test the main difference is that it's not "from scratch" - we are giving a fairly large repo (the FilamentPHP demo for this time), and we're asking for two small features, which is much more closer to actual day-to-day work. Devs are allowed to use AI, but I WILL ask about it, and ask WHY they (or their AI) did certain things.

There are also a few more factors I plan on checking that I don't want to post about in public (not to lower effectiveness), but feel free to ask me, if you are in a similar position as me...


Questions? Comments? Insults?
Feel free to drop me a line below, I love getting messages!