As of 13 August 2026, AI can practise a technical interview.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Do it yourself

   Second choice

   A chat interface, chat-fluent skill, and roughly 30 minutes until you can act on the result.

   How to actually do it

   1. Open the job advert and your CV, then copy the role, seniority, required technical skills and relevant experience into the bracketed sections of the prompt.
   2. Add the likely interview format and a short list of topics you expect, such as coding, system design, databases, cloud services or troubleshooting.
   3. Paste the completed prompt into ChatGPT, Claude or Gemini and answer each question aloud before typing a concise summary of your answer.
   4. Ask the model to continue whenever its follow-up is relevant, and ask it to restate any question that is unclear rather than guessing what the interviewer meant.
   5. Copy every technical correction into a separate note and compare it with the documentation for the relevant language, framework or service before learning it.
   6. Run a second session using the three weaknesses and five follow-up questions from the first session, then record yourself answering without looking at the feedback.

   Prompt

   Act as a demanding but fair technical interviewer for this UK job.
   
   Role and level: [paste the job title and seniority]
   Job description: [paste the job description]
   My CV or relevant experience: [paste the relevant sections]
   Technical areas to practise: [list the languages, frameworks, systems, methods or topics]
   Interview format, if known: [for example, coding exercise, system design, troubleshooting, technical discussion]
   
   Run a realistic mock interview one question at a time. Start with a question suited to the role and level, then ask natural follow-up questions based on my answer. Do not show an ideal answer before I respond. Ask me to explain assumptions, trade-offs, testing, security, performance and failure handling where relevant. Do not invent facts about my experience or the employer.
   
   After each answer, give only brief interviewer-style feedback covering technical correctness, clarity, structure and what I missed, then continue the interview. If you are unsure about a technical claim, say so rather than presenting it as fact. At the end, give me:
   1. A score for each answer using a clear rubric.
   2. The three most important weaknesses to fix.
   3. Corrected explanations for any inaccurate technical answers, separating established facts from assumptions.
   4. Five targeted follow-up questions with concise points that a strong answer should cover.
   5. A short practice plan for my next session.
   
   Keep the interview realistic and do not turn it into a lecture until the final feedback.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.

3. Use a tool built for this

   The distant third