Skip to main content

Prepare for interviews

Interview Preparation focuses on communication with recruiters and hiring managers: prepare answers to the retained common questions, choose questions that help you evaluate the role, and follow up appropriately afterward. It does not teach coding, technical-assessment behavior, conversation practice, or a universal hiring-process map.

Know who can answer what​

A recruiter conversation commonly covers process, logistics, location, working language, availability, compensation expectations, and working terms. Direct detailed team or technical questions to someone who can confirm the answer when the recruiter cannot.

A hiring-manager conversation commonly covers the team and how your relevant experience relates to its work. Review the role description so you can adapt the restored answer frameworks and interviewer questions to its stated needs.

This is orientation, not a promise that every process follows the same stages or that one person's title guarantees what they know.

Confirm the remote conversation​

Before a remote interview, confirm:

  • the date and time zone;
  • the participants;
  • the meeting link;
  • any access needs;
  • a backup contact if the link or plan fails; and
  • that the required device and connection work.

Review the role description and relevant public company information, such as what the company says it does and the product or service connected to the role. Do not investigate personal details, infer culture or personality, or build a generic stack-and-news checklist.

Recheck legitimacy when a new person, email domain, document, payment request, or sensitive-information request appears. Use the detailed inbound legitimacy guidance before sharing data or money.

Work through the section​

The section excludes coding, algorithms, system design, technical-interview curricula, mock-interview programs, in-person etiquette, general during-interview behavior, and a separate offer-stage salary-negotiation curriculum. The salary-expectations answer on the common-questions page is the recorded exception.