Everyone's using ChatGPT to prep for interviews. And most people end up sounding the same. Recruiters feel it. They can't always explain why, but after the fifth candidate with a perfectly structured answer about their "biggest career challenge", something clicks. The problem isn't that you're using AI. It's how you're using it.
Where AI actually helps, and where it hurts
ChatGPT is good at a few things: structuring your thoughts, suggesting questions you might get, explaining company context. Where it fails: it doesn't know your story. It generates a plausible answer, not your answer. And when you memorise that answer, you're not telling a story in the interview, you're reciting one. People hear the difference.
- Good: generating question lists by role type or company
- Good: giving feedback on your draft answers
- Good: explaining technical concepts before a technical interview
- Bad: writing answers for you to memorise word for word
- Bad: asking for the "perfect answer" to a behavioural question
Prompts that actually work
The difference between a useful and a harmful prompt is simple: a useful one makes you think, a harmful one thinks for you. Here are specific examples you can use right now.
1. Mock interview with feedback
Not "give me an answer", but "ask me a question and tell me what's wrong with my answer". Prompt: "You're a recruiter at a product IT company. Run a mock interview with me for the role of [role]. Ask one question at a time. After each of my answers, give specific feedback: what sounded good, what was vague, and what I could add." This gives you a live dialogue, not a monologue.
2. Breaking down a job posting for hidden expectations
Prompt: "Here's the job description: [paste it]. What is this company actually looking for between the lines? What pain points are they trying to solve? What interview questions should I expect based on this text?" After this you don't just have a question list, you have context. And in the interview you're answering the unasked question, which is what actually matters.
3. Help with STAR, but not a replacement
Prompt: "I'll tell you a situation from my career. You tell me: is there a clear STAR structure here, where I'm missing detail, and what's worth emphasising for the role of [role]." Then you write your situation in your own words and get feedback, not a template. That preserves your voice.
Write your answers first without AI. Out loud or in notes. Then send them to ChatGPT for feedback. If you do it the other way around, you'll always be fitting yourself to its text, not the other way around.
Techniques to stay yourself
There are a few specific things that help you avoid "over-reading" AI answers until you lose your own voice.
- 1After prepping with AI, close the chat and say your answer out loud in your own words. What you remember is yours. What you forgot wasn't yours to begin with.
- 2Keep your rough edges. A pause, an "um", a false start and reset, a specific detail that seems minor. These are signs of a real person, not a bot.
- 3Use AI for questions, not answers. It's great at generating 30 questions you might get asked. Come up with the answers yourself.
- 4Check that you can explain every sentence in your answer. If ChatGPT wrote "I focused on reducing operational costs through process optimisation" and you can't give an example, that's not your answer.
What to do if you're not a native "corporate" speaker
This is a genuinely real issue for many Ukrainian tech professionals. If the interview is in English and you're not immersed in an English-speaking environment, AI looks like a lifeline. But here's the catch: your accent, your grammar, your B2-level with real mistakes, all of that is actually fine. Tech recruiters are used to it. They've hired people from India, Poland, Brazil. They evaluate substance.
What's not fine: sounding like ChatGPT but looking like someone speaking B2. The mismatch between the "quality" of the language and the level of live conversation is immediately obvious. Better to speak how you speak, but with prepared substance. Prompt for this: "Here's my answer to the question [question]. Fix the grammar but keep my style and language level. Don't make it more formal or complex."
Where to stop
There's a moment when preparation turns into anxiety with a tool. You already know the answers to 40 questions, you've practised STAR on five examples, and you still open ChatGPT one more time. That's not preparation anymore. That's procrastination wearing the costume of productivity.
Stop when: you can answer basic questions without notes, you understand what makes this company different from its competitors, and you have 3-4 specific examples from your own work that you remember without prompting. That's it. After that comes the human factor, and AI can't help you there. Trackr's AI Coach can help with the structured prep, but the final step is always yours.
The day before the interview, stop all prep at 8pm. Completely. Your brain absorbs information during sleep better than in one more hour of prompts. If you don't know something by 8pm the night before, it won't appear overnight.
Quick checklist before the interview
- Analysed the job posting through ChatGPT and understood the company context
- Created a list of questions they might ask (not answers)
- Wrote my own answers in my own words, got AI feedback on them
- Ran at least one mock interview in dialogue mode with ChatGPT
- Can retell my answers without any notes
- Checked the schedule and details in my interview tracker and won't be panicking tomorrow morning
Organise your job search with Trackr
Track applications, analyse your CV with AI, and prepare for interviews - free.
Get started free