Recruiting developers has never been easy. But throw AI into the mix and everything becomes harder.
I’ve hired dozens of developers over the years. And I’ve made mistakes. Lots of them.
Traditional coding interviews are broken. Live coding sessions stress people out so much that good developers choke. Their code looks terrible even though they’re capable. But home based tests? They’re just as flawed now because anyone can use ChatGPT or Claude to write perfect code.
So what do we do?
The Problem
When you give someone a coding task to complete at home, you have no idea if they actually wrote the code. Maybe they used AI. Maybe their friend helped. Maybe they copied it from Stack Overflow. You just don’t know.
But when you put them in a room and say “code this for me right now,” you get artificial pressure. Their brain freezes. They forget basic syntax. They make silly mistakes they’d never make normally.
Neither approach tells you if they can actually do the job.
What Works
I found something better. Give them code to write at home. But then have them walk through it with you in the interview.
This approach comes from looking at how other smart CTOs handle hiring. The best method combines both worlds. You get the benefit of letting people work in a comfortable environment without time pressure. But you also get to see if they truly understand what they built.
How It Works
Send them a coding task before the interview. Something relevant to your actual work. Give them enough time to do it properly.
Then in the interview, ask them to explain their code. Walk through it line by line. Ask about their choices. Why did they structure it this way? What tradeoffs did they consider? How would they handle edge cases?
If someone just copied AI code without understanding it, they won’t be able to explain the thinking behind it. They’ll stumble when you ask about specific decisions. But if they used AI as a starting point and then understood and refined it, they’ll talk confidently about the changes they made and why. Good developers who use AI will say things like “I started with this approach from ChatGPT but then modified it because⦔ They own the code even if they didn’t write every line from scratch.
What to Look For
Good developers love talking about their code. They’ll explain their reasoning. They’ll mention alternative approaches they considered. They’ll point out parts they’d improve given more time.
People who didn’t write the code will give vague answers. They’ll say things like “I thought this was the best approach” without explaining why. They can’t discuss the alternatives because they never thought about them.
The Benefits
This method respects everyone’s time. Developers get to work in their normal environment with their tools. You get to see how they actually think about problems.
It filters out people who just used AI without understanding anything. But it doesn’t punish people for using AI as a tool – which is what good developers do anyway.
You also learn how they communicate about technical topics. Can they explain complex ideas simply? Do they think about the user impact? These things matter as much as coding ability.
Making It Fair
Not everyone has existing code they want to share. Some people work on proprietary systems. Others are new to the field. That’s fine – just give them a reasonable task that won’t take more than a few hours.
Keep the task relevant to what they’d actually do in the role. Don’t ask them to implement a red-black tree if you’re hiring for web development. Give them something that mirrors real work.
The Time Investment
Yes, this takes more of your time as the interviewer. You need to actually read their code and prepare thoughtful questions. But hiring wrong costs way more than spending an extra hour in interviews.
Good developers appreciate when you take the time to understand their work instead of putting them through arbitrary coding challenges.
Why This Matters Now
AI isn’t going away. If anything it’s going to get better at writing code. We need to adapt our hiring practices now.
The developers you want to hire are already using AI tools to be more productive. They’re not trying to hide it – they’re using it intelligently to solve problems faster.
The trick is finding people who can work with AI effectively versus people who just copy and paste without understanding.
Bottom Line
Stop trying to catch people cheating with AI. Start looking for people who can use all available tools to solve real problems and then explain their thinking clearly.
Give them code to write at home. Then have them teach you how it works. The best developers will love this approach. The ones who can’t explain their own code? You didn’t want to hire them anyway.
That’s how you hire developers in 2025. Not by fighting against AI, but by working with the reality that it exists.
