It's Tuesday night. You have a technical interview at 10am tomorrow.
You meant to prep over the weekend. You didn't. You skimmed the job description on the subway, saved three Glassdoor threads you never opened, and now you're staring at the recruiter's email trying to decide if it's too late to care. It is not too late. But the next twelve hours have to count, and the forty-five minutes tomorrow morning have to count more.
A handful of our beta users have asked, specifically, how to use IntelliPrompter for an interview. Not a sales call, not a client meeting. An interview, where you're the one being evaluated. This is what I'd actually do.
Here's the playbook. Before, during, after.
Load the context, then rehearse
Open IntelliPrompter and drop three things into the knowledge base: your resume, the job description, and whatever you've got on the company. A recent press release. The team page. A product-launch blog post. Nothing fancy. The point is that during the conversation, when the interviewer says something that touches your background or their product, the overlay has material to pull from. Not generic AI knowledge. Yours.
Then use Rehearse. This is the feature I think gets underused. Rehearse takes a topic ("a time I handled a production incident", "why I'm leaving my current role", "what I know about this company's architecture") and gives you a short structured card: what to watch for, frameworks that apply, questions a good interviewer might ask back, what to avoid saying. It is not a script. It's a pre-flight checklist for the version of you that will be sitting at the kitchen table tomorrow morning with a lukewarm coffee and a slightly sweaty palm.
I run Rehearse on the three or four stories I know I'll want to tell. For each one, the card surfaces the part I usually fumble. The caveat I always forget. The metric I always under-sell. It takes about twenty minutes. It is the single highest-leverage thing you can do tonight.
A quiet second brain
Open IntelliPrompter before you join the call. The overlay sits on your screen only. It does not show up in Zoom. It does not show up in a screen share. It is not visible to the interviewer. This is a hard guardrail for us, not a feature flag. If you'd like to know how that's enforced, we document it on the AI ethics page.
Three things happen in real time once the conversation starts.
It catches when you're rambling. This is the one I personally needed. Interview nerves make me over-explain. The coaching card will quietly flag that I've been talking for ninety seconds and suggest I land the plane. That signal, in the moment, is worth more than any amount of post-hoc feedback.
It stops you from stepping on the interviewer. If the transcript detects you cut someone off, or you're about to answer a half-asked question, the overlay nudges you to let them finish. Interviewers notice this. It's cheap to fix and expensive to leave broken.
It feeds you follow-up questions. About twenty minutes in, when the interviewer says "any questions for me?" and your mind goes blank, the overlay has been quietly tracking what they've talked about and suggests two or three specific, non-generic things to ask. Not "what's the culture like." Something that references what they actually said at minute eleven.
What it won't do
It will not pass the interview for you. If you don't know the answer to a system design question, the overlay cannot invent the answer in your voice. It can suggest a framework. It can remind you of a project on your resume that's relevant. It cannot replace having done the work.
It also won't be invisible to you. The overlay is on your screen. Looking at it costs eye contact. Beta users have told me the trick is to glance, not read. Treat the cards like you'd treat a single bullet in your notes: a trigger, not a teleprompter. (We have a teleprompter mode too, for the parts of the conversation where you want a scripted intro. Interviews are not usually one of those parts.)
If you're the kind of person who gets more flustered when there's a second screen to manage, this might not be your tool. Honest tradeoff. Try it on a mock interview first, not the real one.
Review while it's warm
Within an hour of hanging up, open the meeting review. You get the full transcript, the coaching events that fired during the call, and a short summary of where you did well and where you drifted. The thing I like most: you can see the exact timestamp where the coach flagged you were rambling, and you can hear yourself in that moment. That is a feedback loop you cannot build out of self-reflection alone.
Rate the coaching cards too. Thumbs up, thumbs down, "too much." Those ratings tune the model for your next interview. The system learns what you actually want to be nudged on, which for most people is a surprisingly short list.
Then, if there's a round two, feed what you learned back into Rehearse for next week.
A note on the beta
Interview coaching wasn't in our original roadmap. Three separate beta users asked for it in the first six weeks, in almost identical words: "I have an interview, how do I use this tool for that?" That's the version of product-market fit I trust most. If this is the thing you need it for, we'd like you in the beta.
Waitlist is at intelliprompter.com/beta. Tell me what interview you're prepping for in the signup note. I read them.
Jeff