Interview Fundamentals
The common interview formats, what each is designed to evaluate, and the basics of preparing for any of them.
What you'll learn
- Distinguish common interview formats and what each is designed to evaluate
- Identify appropriate preparation steps before an interview
- Recognize when it's appropriate to ask questions of the interviewer
Prerequisites
Explanation
Not all interviews are testing the same thing, and preparing for the wrong one is a common, avoidable mistake. Three formats show up repeatedly:
- HR or screening interviews are usually early, shorter conversations focused on basic fit: your background, your availability, your communication, and whether your expectations (role, compensation range, location) roughly match the position. They rarely go deep on technical skill.
- Technical interviews focus on role-specific ability — solving a problem, explaining a past project in technical depth, or walking through your reasoning on a task related to the actual job.
- Panel interviews involve multiple interviewers at once, often representing different stakeholders (your future manager, a peer, someone from another team). They're evaluating the same things a one-on-one interview would, but from multiple perspectives simultaneously, which means a good panel answer often needs to work for more than one type of listener at once — technical enough for the peer, clear enough for a non-technical stakeholder in the room.
Confusing formats leads to a mismatch: giving a screening-style, high-level answer in a technical interview can read as unprepared to go deep, while treating a screening call like a technical deep-dive can waste the interviewer's limited time on details they weren't trying to evaluate yet.
Preparation basics apply across all three formats, but two matter enough to call out specifically. First, research the organization beyond its name — what it does, roughly how it makes money or delivers its mission, and ideally something specific enough that it couldn't apply to any other company you might be interviewing with that week. This shows up naturally in how you answer "why this role," and its absence is easy for an interviewer to spot. Second, prepare questions to ask the interviewer. Nearly every interview ends with some version of "do you have any questions for us?" — treating this as optional or answering "not really" is a missed opportunity to show genuine engagement, and it can even read as disinterest. Good questions are specific to the role or team, not answerable by re-reading the company's public website.
A third, quieter preparation step is reviewing your own background before you go in — not memorizing a script, but making sure you can speak specifically about your own recent work and experience without having to reconstruct it on the spot under mild pressure. Interviewers can generally tell the difference between someone speaking from genuine familiarity with their own experience and someone reconstructing it in real time.
Interview formats and their focus
HR/Screening: basic fit and logistics. Technical: role-specific skill and reasoning. Panel: the same evaluation from multiple stakeholders at once.
Example
Checks whether all three basic preparation steps for an interview have been completed.
function hasPreparedBasics(prep) {
return (
prep.researchedOrganization === true &&
prep.hasQuestionsToAsk === true &&
prep.reviewedOwnBackground === true
);
}
// Example: hasPreparedBasics({ researchedOrganization: true, hasQuestionsToAsk: false, reviewedOwnBackground: true }) -> falseGuided exercise
Guided exercise
Write identifyInterviewFocus(formatLabel) using this mapping: 'hr-screen' -> 'fit-and-communication', 'technical' -> 'role-specific-skill', 'panel' -> 'multiple-stakeholder-perspectives'. Return null for any other, unrecognized formatLabel.
Checks: Maps 'technical' to 'role-specific-skill' · Maps 'hr-screen' to 'fit-and-communication' · plus 1 hidden check
Code editor. Press Escape then Tab to leave the editor if keyboard focus becomes trapped. Press Control+Shift+M inside the editor to toggle Tab-key focus trapping.
Stuck? Get a hint.
Independent exercise
Independent exercise
Write isReadyForInterview(prep) where prep is { researchedOrganization: boolean, preparedQuestionsCount: number, reviewedOwnBackground: boolean }. Return true only if researchedOrganization is true AND reviewedOwnBackground is true AND preparedQuestionsCount is at least 2.
Checks: Accepts prep meeting all three criteria, at the question-count minimum · Rejects prep with fewer than 2 prepared questions · plus 1 hidden check
Code editor. Press Escape then Tab to leave the editor if keyboard focus becomes trapped. Press Control+Shift+M inside the editor to toggle Tab-key focus trapping.
Stuck? Get a hint.
Common mistakes
- Walking in with zero prepared questions for the interviewer, or dismissing the question as unimportant.
- Giving the same generic answers regardless of format, instead of adjusting depth for HR versus technical rounds.
- Failing to research the organization beyond its name, which becomes obvious in a generic 'why this role' answer.
- Treating a panel interview as a conversation with only one person in the room, ignoring other stakeholders' likely concerns.
Knowledge check
Takeaway
Knowing which interview format you're walking into changes what you should prepare — and preparing questions to ask is not optional in any of them.
Summary
HR/screening, technical, and panel interviews evaluate different things and reward different kinds of preparation. Researching the organization, preparing genuine questions to ask, and reviewing your own background apply across all three formats.
Your notes
Notes save automatically.
Finished this lesson?
Mark it complete to track your progress and schedule a future review.
AI tutor
The optional AI tutor isn't enabled in this deployment. All lessons, exercises, quizzes, and search work fully without it.