A four-part answer structure
- Name one or two specific uses tied to your actual job.
- Describe how you verify or edit what it produces.
- Give a result: time saved, quality improved, something shipped.
- Name a boundary: where you don't use it, and how you handle confidential information.
What the interviewer is really testing
In 2026 this question appears across engineering, product, marketing, finance and operations roles. Companies have mixed experiences with AI — real productivity gains alongside confident errors and data leaks — so they want people who capture the first without the second. The question tests four things at once: whether you keep your skills current, whether you think critically about tool output, whether you can describe your own workflow clearly, and whether you can be trusted with company data.
Sample answers by role
- Software engineer: “I use an assistant in my editor for boilerplate and tests. For anything touching auth or payments I write it myself and use the assistant only to review. Last quarter it cut the time to add test coverage to a legacy module from about a week to two days. I don't paste production data or secrets into external tools; we use the company-approved one.”
- Product manager: “I use it to summarise interview notes and draft first versions of specs, then rewrite the problem statement myself because that's where judgement lives. It roughly halved my synthesis time after a round of twelve customer interviews. I check every quoted insight against the original notes.”
- Data analyst: “I use it to draft SQL and explain unfamiliar queries. I always run the query on a sample and compare against a known number before trusting it. It's fastest for joins across schemas I don't know well.”
- Marketer: “I generate variations of ad copy and subject lines, then pick and edit. The brand voice and claims review stay manual. Testing more variants raised our email open rate, but the winning lines were usually edited heavily.”
Mistakes that hurt
| Answer | Why it hurts | Better |
|---|---|---|
| “I don't really use AI.” | Can sound out of date at AI-forward companies | Explain a deliberate choice, or a tool you're evaluating |
| “I use it for everything.” | Suggests no judgement or verification | Name where you don't use it and why |
| “It writes my code.” | Raises ownership and quality concerns | Describe review and testing |
| Pasting company data into public tools | A security red flag | Mention approved tools and data boundaries |
| Vague enthusiasm | No evidence | One concrete workflow and result |
If you genuinely don't use AI much
Honesty is fine, with a reason. “My current employer hasn't approved any tools for our codebase, so I use them only on personal projects — mainly for learning unfamiliar libraries — and I'm keen to work somewhere they're part of the workflow” is a good answer. So is a principled one about the kind of work where you have found AI unhelpful, as long as you show you have tried it.
Related questions to prepare
- “What's a time AI gave you a wrong answer, and how did you catch it?”
- “How would you decide whether our team should adopt an AI tool?”
- “What should never be delegated to AI in this role?”
- “How do you keep your skills sharp when AI does more of the routine work?”
Prepare one short story for the first of those. A specific error you caught — a hallucinated API, a wrong number in a summary — demonstrates verification better than any general statement.
Practising your answer
Write your answer in four bullet points following the structure above, then say it out loud in under ninety seconds. A free AI interview assistant such as CoPilot Interview can ask you this question in a mock interview, score your answer and suggest follow-ups. Pair it with our guide to AI engineer interview questions if the role builds AI products rather than just using them.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly. Everything else on this page applies whichever tool you use, or none.
Frequently asked questions
How should I answer “How do you use AI at work?”
Name one or two specific uses tied to your job, explain how you verify the output, give a concrete result, and state a boundary — where you don't use it and how you protect confidential data.
Is it bad to say I don't use AI in an interview?
Not if you explain why, such as employer restrictions or a deliberate choice for certain work, and show you have tried it. Saying it without context can sound out of date at AI-forward companies.
Why do interviewers ask about AI use?
To test whether you keep your skills current, think critically about tool output, can describe your workflow, and can be trusted with company data.
What is a good example of using AI at work?
A specific workflow with a measurable result and a verification step — for example, drafting tests with an assistant, reviewing each one, and cutting the time to cover a legacy module from a week to two days.
Practise on real interview questions
Run 145 real interview questions across 10 tracks, answer out loud and see a structured answer to compare with yours. Free, no signup.
Try a practice question