Pasting your résumé and the job description into an AI interview assistant changes three things. Live answers stop being generic and start referencing your actual projects, tools and results. The AI mock interview builds its behavioral, technical, system design and coding questions from the two documents instead of from a generic bank. And the résumé builder uses the job description to tailor what you submit. Without the paste, the tool only knows the question it just heard; with it, the tool knows who is answering and what the employer asked for.
This page explains each of those changes, shows the difference with an example we wrote, and spends real time on the other half of the question: what you should never paste into any AI tool, and why.
Three places the paste shows up
CoPilot Interview reads the two documents in three modes:
- Live mode. When the interviewer asks a question during a call on Zoom, Microsoft Teams or Google Meet, the structured answer that appears in about 2 seconds is written with your résumé and the posting as context. A "tell me about a time" question gets an answer built on a project you listed, not an invented one.
- The AI mock interview. An AI interviewer builds questions from the job description and your résumé, reads each one aloud, you answer out loud, and each answer is scored out of 10 with what worked, what to improve and a model answer. A report card ends the round.
- The résumé builder. It tailors your résumé to the job description and exports Markdown or LaTeX.
The same two documents feed all three, so one careful paste at the start of a job search pays off across every session. The AI interview assistant overview describes how the modes connect.
Grounded vs generic: an example we wrote
Take a common question: "Tell me about a time you improved the performance of something."
Without your résumé, the answer has to be generic. Something like: identify the bottleneck, measure before and after, pick a fix, confirm the gain. It is correct and it is empty. The interviewer has heard it from everyone.
With your résumé pasted, the same question returns a structure that points at your material. Suppose your résumé lists "cut nightly report build from 40 minutes to 6 by moving aggregation into the database." The answer now leads with that project: the situation (slow nightly job), what you measured, the change you made, and the result you already wrote down, with a reminder to mention who it helped. You still tell the story in your own words, but you are no longer starting from zero while the interviewer waits.
The job description does the second half of the work. If the posting stresses "cross-functional communication," the suggested answer nudges you to mention the stakeholders you kept informed. You get a structure that fits both who you are and what they said they want.
What the mock interview does with both documents
The AI mock interview is where the paste matters most, because the questions themselves come from the documents. A posting that mentions Kubernetes and on-call rotation produces questions about Kubernetes and on-call rotation. A résumé that lists a migration project produces a question about that migration, and a follow-up about what went wrong. The round reads each question aloud, scores your spoken answer out of 10, and finishes with a report card. If you want to see the kind of questions a posting generates before running a full round, the interview questions from a job description tool does just that step.
Practicing from your own documents is the point. Generic question banks prepare you for a generic interview, and nobody is giving one of those.
What to paste and what to leave out
| Paste it | Leave it out | Why |
|---|---|---|
| Your résumé as you would send it to an employer | Your home address, date of birth, government ID numbers | The model does not need them to write an answer, and nothing you paste should be more sensitive than the résumé itself |
| Project descriptions with outcomes and your role | Source code, credentials, API keys, internal URLs | Secrets have no interview value and should never leave your machine |
| The public job posting, including requirements and "nice to have" lines | Confidential documents the recruiter shared under NDA | Respect the agreement; summarize in your own words if you need the context |
| A one-line note on why you want the role | Patient records, client names, case details, student data | Protected information stays protected; describe situations in general terms |
| Your own performance review wording, if it is yours to share | Colleagues' names or evaluations | Other people's information is not yours to paste |
| Metrics you can defend in the interview | Numbers you are not sure of | A grounded answer repeats what you gave it; if the number is wrong, the answer is wrong |
The short rule: paste what you would be comfortable saying out loud in the interview, and nothing else. Nurses, lawyers, teachers and anyone working with protected data should describe situations in general terms, the same way they would on a résumé.
What happens to the documents you paste
Privacy is the reasonable worry here. During a live session, audio is streamed in short encrypted segments through CoPilot Interview's proxy to a speech-to-text model, and the question text goes to the AI model you picked. No audio, transcripts or answers are stored on CoPilot Interview's servers. Session files (transcript, answers, report) are saved in your own Documents folder. Optional anonymous question statistics cover titles, categories and scores, never answers, transcripts, résumés or contact details, and can be turned off in Options. The security page has the full description. None of this changes the advice above: a document that never needed to be pasted is the safest kind.
The limitation: it only knows what you gave it
A grounded answer is only as good as the grounding. If your résumé is two roles out of date, the live answer will reach for two-year-old projects. If it lists a technology you touched once, the mock interview will ask about it as if you were an expert, which is actually useful practice, because a real interviewer will do the same. The tool cannot verify anything you paste, and it cannot know the stories that never made it onto the page. Before an important loop, spend ten minutes updating the résumé and adding one or two lines about recent work, then paste it fresh.
The résumé builder helps here too: tailoring the résumé to the posting is usually when people notice what is missing. And if you are choosing between tools, compare AI interview assistants on whether they take your résumé and job description at all, because a live tool that ignores both is working with one hand behind its back. The real-time interview copilot page explains how the grounding feeds the live window specifically.
Follow the rules of the employer or assessment you're in — many people use it only to practice, which works on the free plan.
Run a mock interview from your own posting
Paste the job description and your résumé and the AI interviewer builds the round from them. Free plan, 15 minutes a day, no signup.
Start a mock interviewFAQ
Do I have to paste my résumé for the AI interview assistant to work?
No. The live mode and the mock interview both run without it. Answers are then generic, so you have to supply the specifics yourself, and the mock interview draws on general questions rather than ones built from your experience.
Does the assistant make up projects if my résumé is thin?
It works from what you pasted, so a thin résumé produces thin grounding rather than invented detail. Add a few lines about recent work before you paste. Never say anything in the interview that you cannot back up, whatever the suggested answer says.
Is my résumé stored on CoPilot Interview's servers?
No audio, transcripts or answers are stored on CoPilot Interview's servers, and the optional anonymous statistics never include résumés or contact details. Session files are saved in your own Documents folder. The security page describes the data flow in full.
Should I paste the whole job posting or just the requirements?
Paste the whole public posting. The responsibilities and "nice to have" lines shape the mock interview questions and nudge live answers toward what the employer emphasized. Leave out anything a recruiter shared confidentially.
Can I update my résumé mid-search without starting over?
Yes. Paste the new version before the next session. The résumé builder can also tailor a version to each posting and export Markdown or LaTeX, and that tailored version is the one to paste for that interview.
What should people in healthcare or law leave out?
Anything that identifies a patient, client or case: names, dates, record numbers, rare details. Describe situations in general terms, the same way you would on a résumé or in the interview itself. The structure of the answer does not need the identifying detail.