How to Use ChatGPT for Interview Preparation

Prepare a resume and a job description before you prompt

A useful session starts with two documents you already have: the role you want, and the lines on your resume you are willing to defend. Paste the job description, or the parts of it that describe the work. You do not need your entire resume. A project section and the skills you can explain are enough to begin.

Remove account numbers, addresses, phone numbers, and government IDs before you paste anything into a third-party chat. If a line is not true, do not include it so the model can "improve" it.

Identify evidence that actually fits the role

Ask for a comparison, not a new biography. The model should list skills, projects, and experience the resume states, then list requirements you cannot evidence yet. Assumptions need a label. Missing evidence is a study list, not a paragraph to memorise.

You are an interview coach. I will paste a target role, a job description, and only the resume lines I am willing to share.
List skills, projects, and experience that the resume explicitly supports for this role.
List requirements I cannot evidence yet.
Mark every inference as an assumption.
Do not invent employers, metrics, or tools.
Do not write a script for me to memorise.

Target role: [ROLE]
Job description: [PASTE JOB DESCRIPTION]
Resume lines: [PASTE ONLY WHAT YOU ARE WILLING TO SHARE]

The interactive builder further down writes a longer version of this instruction from your own fields, still on this device.

Practise HR questions and project explanations

For HR questions, point the model at a framework and at your facts. Behavioural questions can use STAR. "Tell me about yourself" should not. The HR answer framework shows which structure fits which question, and the STAR method guide is the longer reference for experience stories. The STAR Answer Builder is there when you want to draft one story field by field.

For a project, require this sequence: problem, architecture, what you personally did, decisions, challenges, how you tested, and the outcome. If the outcome has no number, say that. Do not accept a metric the model adds.

Request criticism instead of praise

Models default to encouragement. That feels useful and hides weak answers. Ask it to quote the vague lines, say what to cut, and refuse to add achievements you did not state. Score the answer on the same dimensions InterviewEra uses in a mock: communication clarity, technical depth, answer structure, confidence, and relevance.

Critique the answer below as an interviewer would.
Score it only as weak, mixed, or strong on clarity, technical depth, structure, confidence, and relevance.
Quote the vague parts.
Tell me what to cut.
Do not rewrite it with achievements I did not state.
Do not compliment me before the critique.

Question: [QUESTION]
My answer: [WHAT YOU WOULD ACTUALLY SAY]

Practise adaptive follow-up questions

A real interviewer does not stop at your first paragraph. Ask for one question, answer it in your own words, then take one follow-up about why you chose that approach or what you owned. The model should judge your answer before it shows a cleaner structure. If it dumps five model answers at once, tell it to stop and wait.

Ask me one interview question for [ROLE] based on the skills I list.
Wait for my answer.
Then ask one follow-up about ownership or a trade-off.
Evaluate my answer before you show a stronger structure.
Use only facts I have already told you.
Tell me to say the improved version aloud, not to memorise it.

Skills I can defend: [SKILLS]

When you want questions without a chat transcript, use the Interview Question Generator or browse the interview question hub.

Convert suggestions into answers you can defend

Keep a line only if you can explain it for another minute. If the suggestion adds a tool, a metric, or a teammate's work, delete it. Say the answer aloud. If you stumble, the sentence is too long or the fact is not yours. The spoken confidence guide is about clarity and pace, not about sounding like someone else.

Do not memorise the generated paragraph. Interviewers notice a script when the follow-up leaves the script. Keep a few anchor facts and a structure, then talk.

Verify technical claims and company information

Check APIs, complexity claims, and framework behaviour against official documentation when the answer depends on them. Check company facts against that company's careers page or another primary source you can name. InterviewEra's company guides, including Amazon, Microsoft, TCS, Infosys, and Wipro, describe patterns. They are not a promise that your invite will use the same rounds.

Keep personal information out of the chat

The prompt builder on this page does not upload the form to InterviewEra. ChatGPT is still a separate product. Paste only what you would be comfortable repeating. Skip full addresses, identification numbers, and other people's private details. Leave the resume field empty if you only want a role-level plan.

A realistic day of preparation

1. Read the job description and mark three requirements you can evidence.
2. Run one prompt for gaps. Write the gaps down. Do not "solve" them by editing your resume in the chat.
3. Speak one HR answer and one project explanation. Record the project answer if you want to hear the pace.
4. Take one follow-up you did not expect. Note the fact you could not support.
5. If the spoken version is the weak part, start a focused mock. Reading another generated answer will not fix delivery.

The placement preparation guide is the longer campus roadmap. This page is the ChatGPT slice of that work.