Every candidate said they now use artificial intelligence. Interviewers heard “I use ChatGPT in my workflow” many times but barely noticed. If you want to truly stand out, you need to talk about judgment and results, not tools.
In short: Hiring managers won’t screen you for using artificial intelligence. Almost everyone does this. They are screening whether you know when to trust it, when to overturn it, and whether you can explain specific results. That’s the whole game.
What hiring managers are really listening to
No one is impressed by “I use artificial intelligence in my process.” That’s stakes, like saying you know how to use email.
What they listen to is judgment. Can you tell a story about a time when something went wrong with artificial intelligence and you discovered it? Can you explain why you chose to write something yourself rather than generate it? This is what separates those who understand these tools from those who simply use them.
This is in line with what is happening in the wider recruitment world. Jobs where AI eliminates routine tasks but raises standards of judgment and decision-making will grow faster and pay better than jobs where AI makes it easier for anyone to do the job. The interviewer is trying to figure out which category you fall into, whether they would say so or not.
A mistake almost everyone makes
A weak answer sounds like this: “I use AI tools like ChatGPT and Midjourney to speed up my work.”
There’s nothing wrong with that, but it’s easy to forget. It doesn’t tell the interviewer what you think. Anyone can say this, including candidates who don’t actually know what they’re doing.
Stronger answers point to specific situations, specific decisions, and specific outcomes. Specificity makes answers memorable and difficult to fake.
if you are a designer
Don’t use tools to guide. Lead with decisions.
Weakness: “I use artificial intelligence to generate design concepts.”
Better: “When I’m exploring early concepts, I’ll use AI to generate some directions that break out of my own default patterns. But I won’t release anything without redrawing it myself, because the AI output tends to skew toward generic layouts that don’t hold up in real content and edge cases.”
This answer shows that you understand its value and limitations. It also quietly shows that you know what “general AI design” looks like, which is what the interviewer is trying to screen for.
If you are a developer
The story the interviewer wants is not “AI writes code faster.” It’s “I know when to trust AI-generated code and when not to.”
Weak: “I use Copilot and Cursor every day.”
Better: “I use AI to produce boilerplate and first drafts, but anything involving authentication, payments, or data processing is manually reviewed line by line. I find that the AI-generated code looks good but has subtle security issues, so I don’t consider the AI output as complete until I’ve verified it myself.”
If you have a real-life example of this, use it. If you haven’t, honestly you’re still building muscle rather than inventing a story. Interviewers can usually tell the difference.
If you hold a non-technical role
Product managers and other non-technical candidates often either exaggerate technical proficiency or completely underestimate their contributions. Neither works.
A better approach: Talk about how AI will change your processes, not your technical skills. “I use AI to synthesize user research faster, but I always spot-check summaries against the original transcript because I see it removes contradictions that are actually the most important insights.”
Problems you may encounter and how to deal with them
“Take me back to a time when AI didn’t work for you.” Be prepared with real answers. This is the most common way for interviewers to differentiate between real users and people who memorize talking points.
“How do you decide when not to use artificial intelligence?” Answer with principles, not atmosphere. Things like “Anything customer-facing or high-risk will be done with people at the center” is specific. “It depends” is not.
“What AI tools do you use?” Name them, but don’t stop there. The tool name is the least interesting part of the answer.
Red flags interviewers are trained to catch
- I can’t give specific examples, I can only give general statements.
- It’s impossible to describe when artificial intelligence goes wrong
- List tool names, e.g. Resume Keyword Dump
- They get defensive when asked how to verify AI output
These factors are not disqualifying in themselves, but they add up quickly during a 30-minute interview.
bottom line
The candidates that stand out so far are not those who use artificial intelligence the most. They are the ones who can explain, especially when they don’t.
FAQ
Do I need to mention the name of a specific AI tool in the interview? Yes, briefly, but don’t stop there. Naming tools without explaining your judgment about using them is the most common way candidates sound interchangeable.
What if I don’t have much experience with AI yet? Say it honestly and tie it into what you’re doing to develop that skill. Interviewers often respect the honesty of fabricated stories that fall apart in follow-up questions.
Is it a red flag to say I don’t use AI regularly? Not on its own. If you can’t explain why, or the role clearly requires proficiency in AI and you have no plans to develop it, then that’s a red flag.
If I were a designer or product manager, how technical should my answer be? Not really. Focus on decisions and results, not implementation details. Interviewers for design and product roles are assessing judgment, not engineering depth.
What’s the biggest mistake candidates make? Talk about the use of AI in general terms rather than telling a specific, real story. Specificity makes the answer credible.