Ask This One Question to Spot Devs Who Can’t Code Without AI

Introduction 

AI tools are everywhere right now. GitHub Copilot, ChatGPT, code generators. They are making development faster and sometimes smarter. But they are also creating a problem that a lot of hiring managers are only starting to see. 

Some developers are becoming dependent on AI to the point where they can’t actually code without it. They can copy, paste, and tweak, but when the tool is gone, the real skill isn’t there. 

That is a scary thing to find out after someone is already on your team. The good news? You can catch it early if you know what to ask. 

The One Question That Tells You Everything 

It’s simple: 

“Can you walk me through how you would solve this problem without using any AI tools?” 

Not “What’s the answer?” Not “Can you write the code right now?” You want to see their thought process. 

When you ask this, you are looking for how they break down a problem, not whether they can memorize syntax. 

A strong developer will: 

• Start with understanding the requirements 
• Map out the logic in plain language 
• Explain trade-offs and edge cases 
• Talk through how they would test it 

Someone who leans too hard on AI tools often skips the middle steps. They will give you vague answers or struggle to explain why they would choose one approach over another. That’s your red flag. 

Why This Works 

AI can generate code, but it can’t replace problem solving. Real developers think through problems, even if they later use AI to speed up writing the solution. 

By forcing the conversation away from “write me code” and toward “show me your brain at work,” you see if the foundation is there. 

You’re not testing for memory. You are testing for understanding. 

How to Use It in an Interview 

You don’t need to make it complicated. This works with almost any coding problem. 

1. Pick a small but real-world task. Something they might actually face on the job. 
2. Ask them to talk, not type. Make it clear they don’t need to write perfect code. You want to hear their thinking. 
3. Pay attention to the gaps. If they can’t explain the steps without reaching for a tool, that is what you are trying to uncover. 

Here’s an example: 

“Imagine you need to take a list of transactions and group them by customer. Walk me through how you would handle that without using any AI tools.” 

It’s not about whether they say for loop or LINQ or SQL. It’s about whether they can break down the steps in a logical way and explain why. 

What to Do if Someone Trips on It 

Not everyone who struggles with this question is a bad hire. Some people freeze in interviews. Some are just rusty on whiteboard talk. 

What you are looking for is pattern, not perfection. If they can’t explain basic logic or give you a plan in their own words, they may be too dependent on AI to stand on their own. 

You can also follow up with: 

• “What part of this problem would you ask AI to help you with?” 
• “If the AI suggestion was wrong, how would you catch it?” 

The second question is just as telling. Developers who use AI well know how to validate and correct it. Developers who lean on it blindly won’t have a clear answer. 

Why This Matters in 2025 

AI isn’t going away. It’s becoming part of every developer’s toolkit, and that’s fine. The problem isn’t using AI. The problem is relying on it so much that you lose the ability to build or debug without it. 

If a developer can’t code without AI, you will see it the moment: 

• Your environment blocks external tools 
• You have to debug something the AI built 
• The project requires custom logic AI can’t guess

 Those moments are expensive. They create delays, bad code, and stress for the rest of the team. 

Catching it early saves you from hiring someone who looks great on paper but can’t actually deliver when it matters. 

Other Ways to Spot AI Dependence 

That one question is the fastest test, but you can layer in a few other checks: 

• Ask them to review broken code. Developers who understand fundamentals can spot issues quickly. AI-reliant devs often struggle. 
• Remove autocomplete. Have them work in a stripped-down editor for a test task. See if they can navigate without AI prompts. 
• Check their questions. Developers who understand the work ask smart clarifying questions. Copy-paste coders don’t. 

These don’t need to be formal tests. They can be quick exercises or conversation starters during an interview. 

Building Teams That Use AI Well 

The goal isn’t to avoid AI. The best developers know how to use it without letting it take over. 

When you find someone who: 

• Understands the fundamentals 
• Can solve problems without a crutch 
• Uses AI to speed up, not substitute thinking 

…you’ve got a strong hire. That combination is where AI becomes a boost, not a risk.