To research your interviewers with AI, gather their public professional information yourself (title, team, the company's bio, their professional profile, and any talks or articles), paste a short summary into a chatbot, and ask what this person is likely to care about in the interview and which of your stories and questions fit. Keep it professional: no personal life, no private details in the chat, and no contact beyond the normal interview channels.
About 15 minutes per interviewer is enough. The payoff isn't small talk about their background; it's choosing the right example to lead with and asking one question only that person can answer well. Our guide on how to research your interviewer before the call covers the manual version; this page adds the AI steps and the privacy rules that come with them.
What AI is good for here, and what stays with you
| Part of the task | AI helps by | You still have to |
|---|---|---|
| Turning a title into priorities | Explaining what a person in that role on that team typically owns and worries about | Check it against the job description and what the recruiter told you |
| Matching your stories | Suggesting which of your stories fits this person's focus | Pick the story and make sure it's true and yours |
| Drafting questions | Writing questions tied to the team's public work | Choose one or two you genuinely want answered |
| Long talks or articles | Summarising a transcript or article you paste | Read or watch enough yourself to discuss it honestly |
| Finding the right person | Web-search chats can surface pages, sometimes about someone else with the same name | Confirm name, company and title on the company's site or the invitation |
Sources: what to use and what to leave alone
| Source | Use it for | Rule |
|---|---|---|
| The invitation or recruiter email | Name, title and the type of round | If it doesn't say who you'll meet, ask the recruiter |
| The company's team or leadership page | Their official role | Can be out of date; cross-check |
| Their professional networking profile | Role history, tenure, team | Read it like any professional bio; don't message them before the interview |
| Talks, articles, podcasts, papers or open-source work under their name | What they care about professionally | Read one piece properly rather than skimming five |
| The team's announcements or blog | What the team is working on | Use it for questions, not flattery |
| Personal social media, family, home, photos, health, politics | Nothing | Off limits: don't look for it, and never paste it into a chatbot |
A 15-minute routine per interviewer
- Minutes 0–3: note their name, title and the round type from the invitation: recruiter, hiring manager, peer, skip-level or another team.
- 3–7: read their professional profile and the company bio yourself, then write a three-to-five-line summary in your own words.
- 7–10: find one public piece of their professional work, if there is one, and note its main point.
- 10–13: paste your summary into a chatbot with prompts 1 and 2.
- 13–15: choose one story to lead with and one question for this person (prompt 3), and add both to your prep notes.
If you find nothing, that's normal; many people have little public work. The title and round type are enough for prompt 1.
What to paste into the chatbot, and what never to
Paste
- Their title and team, and roughly how long they've been in the role.
- The topics of their public talks or articles, summarised in your words.
- The job description and a one-line list of your stories.
Never paste
- Personal details: family, home location, photos, health, age or anything similar.
- Contact details, or anything from a private or personal account.
- Screenshots of their profile; summarise the professional parts instead.
- Confidential information from your current employer, or details about other candidates.
And don't ask a web-search chat to "find everything about [name]". Ask for professional work only, with sources, and check that each source is about the right person: same name, same company, same title. A chatbot that mixes up two people with the same name will hand you confident, wrong facts.
Four prompts for interviewer research
1. The role lens
I'm interviewing for [job title] at [company]. One interviewer is a [their title] on the [team] team, and the round is a [round type]. Based on the role, not the person, what is this interviewer likely to care about in a candidate, and what are they likely to probe? Job description: [paste]. Separate what the job description says from your general assumptions.
Why it works: it works even when you find nothing public, and it keeps the analysis about the job.
2. Professional themes
Here are my notes on this interviewer's public professional work: [your summary]. Which professional themes come up, and which parts of the job description connect to them? Use only my notes; don't add anything about the person.
Why it works: "use only my notes" stops the chatbot from filling gaps with guesses about a real person.
3. Story and question match
Here are my prepared stories, one line each: [list]. Given those themes, which story should I lead with for this interviewer, and why? Then suggest three questions that someone in their role could answer especially well. Each must connect to the team's public work or the job description, not to the interviewer personally.
Why it works: it turns research into the two things that change the interview: your first example and your questions.
4. Panel plan
My panel has [number] interviewers: [titles and round types]. Make a table with one row per interviewer: what they're likely to weigh, the story I should have ready, and one question for them. Base it only on titles, round types and the job description.
Why it works: panels reward answers that reach everyone at the table, and a quick plan keeps you from aiming every answer at one person.
Worked example: from flattery to a better first story
A candidate interviewing for a site reliability role with a fictional engineering manager who gave a public conference talk about reducing on-call alerts. An example we wrote.
First plan (the AI's first suggestion, unedited)
"Open by mentioning her conference talk and saying how much you enjoyed it. Lead with your most complex technical project to show depth. Ask her what she likes most about working at the company."
Revised plan (after the candidate's edits)
"Don't open with the talk; mention it once only if on-call comes up. Lead with the story where I wrote runbooks and removed duplicate alerts on my last team, because alert load is clearly something she cares about professionally. Ask: 'The job description mentions improving the reliability of the payments API. What causes most of the team's on-call pages right now?'"
The research changed which story comes first and produced a question only this manager can answer well. It didn't turn into compliments, and nothing personal went into the chat.
Check the AI, and use the research lightly
- Wrong person. Name collisions are common. Confirm company and title before you rely on anything.
- Out-of-date titles. People change roles; the invitation is the most current source.
- Personality guesses. "She probably prefers concise answers" is invention. Ignore guesses about someone's character.
- Assumptions dressed as facts. Ask the AI to separate what your notes say from what it inferred.
- Don't recite it back. Research should shape your examples and questions. Mentioning a talk is fine once, briefly, if it's relevant.
- Normal channels only. Don't send connection requests or messages before the interview; questions go through the recruiter. A thank-you note afterwards, by email or through the recruiter, is fine.
For more question ideas, see questions to ask the interviewer and questions to ask a hiring manager. Research the company first with our AI company-research guide, then rehearse your lead story out loud in an AI mock interview. Our guide on how to use AI for interview prep shows where this fits in the week before an interview.
Where CoPilot Interview fits
CoPilot Interview is an AI interview assistant whose AI mock interview builds questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10, a good way to rehearse the story you chose for each interviewer. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Paid plans are Standard at $24.99 a month and Pro at $39.99 a month.
It runs as a desktop app for Windows 10 and 11 and macOS 12 or later, a free iPhone and iPad companion on the App Store (iOS 16 or later) and an Android companion in beta. The desktop app's live help shows captions of the interviewer's question and a structured answer in about two seconds; if you use it, follow your employer's rules. Online assessments, proctored tests and AI-led rounds typically forbid outside help, so prepare for those instead.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
Is it okay to research your interviewer before an interview?
Yes. Looking at an interviewer's public professional information, such as their role, team and published work, is common and sensible preparation. Stay on the professional side: nothing personal.
Should I mention that I looked up my interviewer?
At most once, briefly, and only if it's professional and relevant, for example a talk on a topic that comes up. The research should mostly show in the examples you choose and the questions you ask.
Can I use ChatGPT to look up my interviewer?
You can use a chatbot with web search to find professional sources, but confirm each source is about the right person, ask for professional work only, and don't paste personal details into the chat. Summarising what you read yourself is the safer route.
What if I can't find anything about my interviewer?
That's common. Use their title and the round type: a hiring manager, a peer and a recruiter each tend to weigh different things, and the role-lens prompt above works without any personal research.
Should I connect with my interviewer on LinkedIn before the interview?
It's better to wait. Keep contact to the normal interview channels before the interview, and send a thank-you note afterwards by email or through the recruiter.
Rehearse it out loud before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview