5 Things to Do Before an Interview

You already know you should research the company, but skimming the homepage the night before rarely helps. This section covers what to actually look for: the recent facts, the exact job description, and the people in the room.

• The job description, line by line. Map each requirement to a story you can tell.
• Recent, specific news. A product launch, funding round, or public roadmap gives you concrete things to reference.
• Your interviewers. Check their public role and background so you can pitch answers at the right level.

Turn what you find into three or four talking points you can weave into answers, not a script you recite.

Reading notes silently feels productive and hides the real gap: saying the words. Practice your two or three core stories aloud until the structure is automatic, then stop, because over-rehearsed answers sound flat.

Consider a backend engineer interviewing for an L5 role at a public cloud vendor. She could reread her project notes ten times, but the first time she says the migration cut p99 latency out loud, she hears herself ramble. Two spoken run-throughs fix what ten silent reads could not.

You can run a full practice round against an AI interviewer on the /mock-interview page, which is closer to the real thing than talking to a mirror.

For a remote interview, treat the setup as part of the prep. Open the actual meeting app, Zoom, Google Meet, or Microsoft Teams, and check your camera, microphone, and internet on it, not on a different app that should behave the same.

• Sit where the light is in front of you, not behind.
• Silence notifications and close anything you do not need.
• Have water, your resume, and a notepad within reach.

If you plan to use a live assistant, install and sign in ahead of time. SubcueAI runs as a native macOS and Windows app and as a Chromium browser extension side panel, and the walkthrough lives on the /tutorial page. One honest limit: if an interview is proctored, recorded, or screen-shared, a live assistant is out of scope, so plan to rely on your own preparation there.

Two things candidates skip and later regret: questions to ask, and the boring logistics.

• Ask two or three specific questions. Tie them to something real about the team or product, not a generic what is the culture like.
• Confirm the basics. The exact time and time zone, the joining link or address, and who you are meeting.
• Build in a buffer. Be ready ten minutes early so a last-minute glitch does not become the first impression.

If your resume needs a quick tune before you send it or reference it, the free builder is on the /resume-builder page.