Interview coaching is a 1:1 mock interview with someone who knows the role, followed by specific feedback on what worked and what to change before the real interview. On ADPList you can book a session to practice behavioral, coding, system design, product case, portfolio or leadership interviews.
Each mentor lists their own sessions, so what you can book depends on who you pick. The sections below explain how to choose a mentor for your type of interview and how to book.
Practice the interview you actually have coming up, with someone who knows that kind of interview, and get feedback you can act on.
Interview coaching is practice with feedback: you run a realistic mock interview with someone who knows the role, then go through what worked and what didn't. Good coaching is specific to the interview type, such as behavioral, coding, system design, product case or portfolio review, and to the company and level you're targeting.
Each interview format tests something different, so a session should practice the format you're facing. Use this table to decide what to ask for and what to bring.
| Interview type | What you practice | What to bring | Go deeper |
|---|---|---|---|
| Behavioral | Structured stories using STAR (situation, task, action, result), and handling follow-up questions | Four to six stories from your resume | Amazon Leadership Principles prep |
| Coding | Talking through your approach while you solve a problem | The language you'll interview in | Engineering mentorship guide |
| System design | Scoping, trade-offs and explaining a design out loud | A past system you built | System design interview practice |
| Product case and product sense | Framing the problem, choosing metrics and weighing trade-offs | The product area you're applying to | Google PM interview questions |
| Portfolio presentation (design) | Telling the story of one or two case studies in the time you're given | Your deck | Portfolio review |
| Offer and salary conversation | What to say, and when to say it | The offer details | Salary negotiation practice |
If your loop mixes formats, such as a coding round followed by system design and a behavioral round, practice them in the order you'll face them. For executive and leadership interviews, bring a short account of a team you led, a hard call you made and what changed because of it, and ask the coach to push on the trade-offs.
Job description and level. Send the posting, the company and the level before the session, so the coach can pitch questions where the real interviewer will. If you know who will interview you, share their role too.
Format. Live coding, whiteboard, take-home debrief and panel interviews each feel different. Name the one you have coming up, and say how long the real round runs so the practice fits the same time.
Cold, then debrief. Ask for a straight run with no hints, then go through the feedback together. Stopping to fix every answer hides how you sound under pressure. The debrief is where the real learning happens.
Two changes. Leave with your own notes on the two biggest things to change, not a long list. Two changes you actually make beat ten you forget by the interview.
Second round. Book a follow-up that goes straight to your weakest area, before the real date. Start the second session by running the same question again, so you can both hear whether the change worked.
You need both, for different jobs. Practicing alone, with a question bank or an AI tool, is good for reps: getting your stories straight, timing your answers and getting used to saying them out loud. A person who has run interviews for the role is better at the parts a question bank can't judge: whether your answer would pass at that company, which follow-up questions your answer invites, and whether you sound like the level you're applying for.
A friend or peer sits in between. Practicing with someone in your field is better than talking to a mirror, but unless they have run interviews for the role, their feedback tells you how an answer sounds rather than whether it would get you to the next round.
A practical split is to do your reps alone, then use a coaching session to test them against someone who knows interviews like yours. For extra practice reps, try the AI interview coach.
The best fit is usually someone who does the job you're interviewing for, ideally with experience on the interviewer's side of the table. Use the role notes below to decide who to shortlist.
Look for a product manager at your level or above, ideally one whose profile shows experience interviewing PMs. Ask for a product sense or execution case, then a debrief on how you framed the problem, chose metrics and handled trade-offs. For more on the PM loop, see product manager interview practice. If your loop is at Google, see Google PM interview practice.
Look for an engineer at the level you're applying for, preferably someone who mentions running coding or system design interviews. Ask them to run the round the way their team does while you talk through your approach out loud, then go through where your reasoning lost them. See software engineer interview practice and the system design interview guide, or look through software engineering mentors.
For design roles, rehearse your portfolio presentation with a designer who has hiring experience, and use portfolio review for feedback on the deck itself. Students and first-job candidates: look for someone with experience hiring for entry-level roles and ask for a behavioral run plus a resume review. For executive and leadership interviews, use the advice under the table above.
On ADPList, each mentor's profile shows their current role and background, the areas they list as expertise, and the sessions they offer, with the length of each and, where the mentor has added one, a short description. To book a practice session:
To find someone who interviews for your target role, browse mentors by the role you're interviewing for, then book a session before your interview date.
You can practice behavioral interviews, coding and system design rounds, product case and product sense interviews, design portfolio presentations, and executive or leadership interviews. Pick a coach who runs that format in their own job, tell them the company and level you're targeting, and ask them to simulate the real round as closely as they can, follow-up questions included.
An interview coach runs a realistic mock interview, then gives you specific feedback on what worked and what didn't. They help you tighten your stories and the structure of your answers, point out habits you can't see yourself, and calibrate you to the level you're applying for. A good session ends with two or three concrete things to change before the real interview.
Two or three focused sessions is a reasonable plan: one to find your weak spots, one to fix them, and one close to the real date to rehearse under realistic conditions. Add more if you're switching roles or facing several formats in one loop, such as coding and system design. Between sessions, practice on your own so each session builds on the last one.
Common ones are not researching the company, giving generic answers without specific examples, skipping a clear structure such as STAR for behavioral questions, not asking thoughtful questions at the end, and losing track of time during technical problems. Rambling past the question is another: answer it first in a sentence or two, then add the detail that supports your answer.
Possibly, depending on the mentor and the session. Free sessions are available on ADPList; some mentors offer paid sessions. Price and scope are separate checks on the mentor's profile or in the booking flow: what a session costs, and whether it says it covers mock interviews. A general mentorship session isn't necessarily a mock interview, even if the mentor's bio focuses on interviewing, so don't assume one includes the other.
Not necessarily, so don't plan around a free mock. If the session that matches your round is paid, you can still get ready before paying: practice out loud on your own first, then use the paid session on the format you're least ready for, such as a system design round or a product case.