You got certified, you built something, you used AI at work. Now someone is going to ask you about all three in a room. The exact questions, the answer that works, the answer that loses it, and how to hold your number when they push.
Doing the three moves gets you the interview. Answering the questions about them gets you the job. Almost nobody preps the second one.
People get certified, build something real and use AI at work, then fall apart on the follow-up because they never said it out loud.
Read This With Its Companion
This guide is what to say in the room. The outreach, the proof and the first 90 days are in 3 Claude Moves That Actually Get You Hired.
A certification gets your resume read. What they’re checking is whether the badge means anything.
01
"What did you actually learn?"
Answer shape: one concept, one place you used it. Don’t list the modules.
Works: "How much context these tools need. Now I give it our brand rules and three past emails instead of one line, and a draft went from an hour to fifteen minutes."
Loses it: "It covered prompt engineering, model types and use cases." That’s the table of contents.
02
"What didn’t it teach you?"
Admitting a gap makes everything else more believable.
Works: "The vocabulary, yes. Nothing about a real company, like our data living in four places that don’t match."
Loses it: "It covered everything." Nobody believes that.
The Probe Most People Fail
"Explain one term from that course like I’ve never heard it." Hallucination, token, fine-tuning. Plain words, twenty seconds.
Which cert to take. All built for non-engineers:
Full walkthrough with enroll steps: 3 AI Certifications For Career Switchers.
You can win here. Most candidates talk about what they would do. You have a thing that exists.
01
"Walk me through something you built."
Answer shape: four sentences. Start with the annoying problem, then say what you made. End with what changed and what it cost you.
Works: "We answered the same forty questions all day. I built a helper that reads our old tickets and drafts a reply for the agent to approve, so nothing goes out untouched. It took two weekends, and I rebuilt the search twice."
Loses it: starting with the tools. "So I used Claude and connected it to a spreadsheet and then..."
02
"What broke?"
Have a real failure ready. Works: "The first version summarized a file missing two weeks of data and said nothing. The number looked fine and was wrong. Now it checks row count and dates first, and stops if anything’s missing."
If they ask what you’d do differently, give a rule: "I build the checks before the output. If I can’t tell when it’s wrong, I don’t trust it when it looks right."
When you show it, bring a two to three minute screen recording instead of a live demo that dies on guest wifi. Ask before you share your screen.
"You said it saved six hours a week. How do you know?"
This question decides it. If your answer is "it just feels faster," every other number you gave gets quietly downgraded. Spend twenty minutes measuring it honestly before the interview.
01
The baseline
What it took before, and how you know. Timed is best. Otherwise reconstruct it from calendar blocks or file timestamps, and write it as a range: "two and a half to three hours" sounds like you paid attention.
02
The after
Time it at least three times, end to end, including fixes. If the tool takes four minutes and you spend eleven checking, your number is fifteen.
03
The sample size
"Eight weeks, once a week" is a real claim. "I did it twice" is a guess with a number attached. If your sample is small, say so.
04
What you didn’t count
One sentence, and it wins the room: "That doesn’t count the two weekends I spent building it. Count the build and it paid for itself around week seven."
Then say it in one sentence. "It went from about three hours a week to about forty minutes over eight weeks of timing, and that forty includes checking."
When they push back with "that seems high," narrow it: "The before is my reconstruction, so call it two to three hours. Even at the low end that’s over an hour a week, and I’d rather quote you the low end." Never round up.
Never timed it? Run it three times this week with a timer. "Three runs: 38, 45 and 41 minutes. Before, it was most of a morning" beats a confident six hours that cracks on the first push.
01
"How do you check what AI gives you?"
Answer shape: a specific routine.
Works: "I do three checks every time. First I match the totals to the source, because a summary that adds wrong still reads fine. Then I spot check three line items. Last, I verify anything with a name or a date, because that’s where it invents things."
Loses it: "I always review it carefully." That’s a promise. Everyone says it.
02
"What would you never hand to AI?"
Having a line is the answer. Works: "Anything going to an upset customer goes out in my words. It can draft, but I don’t send its draft. It doesn’t know what happened to that person last week."
The Probe Most People Fail
"How would you know if it was wrong?" The answer is something that fails loudly, like totals that must match a source, a row count or a link you can click. The manager is really asking whether they can hand you something and not check behind you.
Paste this into Claude or ChatGPT with the job description and your story. It plays the interviewer, pushes on your number, and scores you.
One line to end on, if they ask what makes you different from everyone using the same tools: "The tool is the same for everyone. What I bring is knowing what right looks like in this job, so I can tell in ten seconds whether what it handed me is usable."