How to Feed a Job Description to Your Interview Copilot (2026)

When you open a live interview, the biggest advantage of an interview copilot is that it can pull your own experience into the conversation without you having to search for it. To make that happen, you need to give the tool a clear picture of the role you’re applying for. Below is a step‑by‑step guide that works on macOS, followed by tips on how to keep the assistance helpful and ethical.

1. Gather the Job Description in a Friendly Format

• Plain text or PDF – Most hiring portals let you download the JD as a PDF or copy‑paste the HTML into a text file. The copilot can read both, but plain text avoids formatting glitches.
• Trim the fluff – Remove boiler‑plate sections like "About the Company" unless they contain role‑specific expectations. Keep the bullet points that list required skills, day‑to‑day duties, and success metrics.
• Save with a clear name – For example Senior‑Product‑Manager‑JD.pdf. The naming helps the app locate the file quickly.

2. Load the Description into the Copilot

1. Open the overlay – Click the menu‑bar icon, then choose Load Job Description.
2. Drag‑and‑drop – Drop the file onto the prompt window. The app will parse the text in a few seconds.
3. Confirm the extraction – A brief summary appears: key skills, primary responsibilities, and any listed metrics. If something looks off, you can edit the extracted list directly.

What the Copilot Does Next

3. Align Your Resume with the JD Before the Call

• Tag your resume – In the resume file, add hidden comments (Ctrl‑Shift‑C) next to each bullet that matches a JD skill. For example, <!-- matches: Agile, roadmap -->.
• Prioritize stories – For each high‑impact JD item, think of a 45‑90‑second anecdote that shows you delivering that skill. Write a short script in a notes app; the copilot can surface it when the relevant keyword is heard.
• Test the match – Use the Preview button in the overlay to see how the tool would respond to a sample question like "Tell me about your experience with cross‑functional teams." Adjust the script until it feels natural.

4. Using the Copilot During the Live Interview

1. Permission – The copilot asks for microphone access. Grant it; the app will listen only while you’re on the call.
2. Real‑time detection – As the interviewer asks a question, the model identifies the core skill being probed (e.g., "leadership").
3. Suggested bullet – A small, non‑intrusive overlay appears with a concise reminder: "Lead a 5‑person team to launch X, delivered 30% faster than target."
4. Speak, don’t read – Treat the suggestion as a cue. Deliver the story in your own voice, adding specifics that the tool might have missed.
5. Follow‑up handling – If the interviewer asks a deeper question, the copilot updates its context and can suggest a follow‑up point, keeping the conversation on track.

When to Trust the Copilot

• Grounded in your documents – If the suggestion pulls directly from a line in your resume, it’s safe.
• High‑level prompts – For vague questions like "What are your strengths?" the tool may give a generic outline; you should flesh it out yourself.
• Avoid over‑reliance – Never let the overlay dictate the entire answer. You still need to adapt to tone, body language, and any new information the interviewer shares.

5. Knowing the Boundaries

• No live fact‑checking – The copilot does not verify claims against external sources. If you’re asked about market size or a competitor’s revenue, you must answer from memory or admit you’ll follow up.
• Privacy limits – The app only processes audio locally; it does not upload your conversation to a server. However, it does store the JD and resume mapping on your machine for the duration of the interview.
• Stealth mode – In screen‑sharing scenarios, the overlay stays off‑screen, but you should still be aware that the tool is listening. Some companies have policies against AI assistance; always check the interview guidelines first.
• Legal considerations – Using a copilot to fabricate achievements is unethical and could be discovered later. The tool is a reminder, not a replacement for honesty.

6. Best‑Practice Checklist

• Before the interview: Have the JD loaded, resume tags in place, and a few rehearsed stories.
• During the interview: Keep the overlay visible only to you, speak naturally, and verify each suggestion against your own memory.
• After the interview: Review the session log (if you saved it) to see which prompts helped and which missed the mark. Refine your tags for the next interview.

How to practice this

1. Mock interview with a friend – Load a real JD, run the copilot, and have a partner ask typical questions. Notice how quickly the overlay surfaces relevant points.
2. Edit the extraction – Intentionally introduce a mismatch (e.g., remove a skill from the JD) and see how the tool reacts. This builds awareness of its limits.
3. Record and review – Use the macOS screen recorder to capture a practice session (audio only). Play it back to evaluate whether you relied too heavily on the suggestions.

---

FAQ

• Q: Can I use the copilot for a group interview? A: Yes, but the overlay may become cluttered if multiple people ask questions simultaneously. Focus on one speaker at a time and pause the tool if needed.
• Q: What if the JD is in a scanned image? A: The copilot includes basic OCR; however, accuracy varies, so double‑check the extracted text.
• Q: Does the tool work with non‑technical roles? A: It parses any bullet‑pointed responsibilities, so it can assist with product, marketing, or operations roles, though the quality of suggestions depends on how clearly the JD is written.
• Q: How do I ensure the copilot doesn’t break interview etiquette? A: Keep the overlay off‑screen when sharing your screen, and never let the tool speak for you. Use it only as a personal prompt.