Interview Preparation: What to Do Before, During & After

Preparation is the difference between good and great interviews

Most candidates show up to interviews underprepared. They've read the job description and maybe browsed the company website. That's not enough. The candidates who get offers are the ones who prepare systematically.

Before the interview

Research the company deeply

Go beyond the "About Us" page:

• Recent news: Press releases, funding rounds, product launches
• Company blog: Engineering blogs reveal technical priorities and culture
• Glassdoor reviews: Look for patterns, not individual complaints
• LinkedIn: Check the interviewer's background and shared connections
• Product: Actually use the product if possible. Having specific opinions shows initiative.

Study the job description

Highlight the top 5 requirements. For each one, prepare a specific example from your experience that demonstrates that skill. Use the STAR method:

• Situation: Set the context
• Task: What was your responsibility?
• Action: What specifically did you do?
• Result: What was the measurable outcome?

Prepare your questions

Always have 3-5 thoughtful questions ready. Good questions show engagement:

• "What does the first 90 days look like for this role?"
• "What's the biggest technical challenge the team is facing right now?"
• "How does the team handle code reviews and knowledge sharing?"

Avoid questions about salary, PTO, or anything easily found on the website.

Practice out loud

Reading answers in your head isn't the same as saying them. Practice with a friend, record yourself, or use a mock interview tool. Focus on being concise — most answers should be 60-90 seconds.

During the interview

Behavioral interviews

Use STAR for every answer. Keep stories specific and recent. Generic answers like "I'm a great communicator" mean nothing without an example.

Template: "In my role at [Company], we faced [Situation]. I was responsible for [Task]. I [Action], which resulted in [Result — with numbers if possible]."

Technical interviews

• Think out loud. Interviewers want to see your problem-solving process, not just the answer.
• Ask clarifying questions. Don't assume — confirm edge cases, constraints, and expected input/output.
• Start with a brute force solution. Then optimize. A working solution beats an unfinished optimal one.
• Test your code mentally or with examples before saying you're done.

Case interviews (PM, consulting, strategy roles)

• Structure first. Break the problem into a framework before diving in.
• State your assumptions explicitly.
• Use numbers. Even rough estimates show analytical thinking.
• Drive toward a recommendation. Case interviews want a decision, not just analysis.

After the interview

Send a thank-you email within 24 hours

Keep it brief: thank the interviewer, reference something specific you discussed, and reaffirm your interest.

Example: "Thanks for taking the time to discuss the Senior Engineer role. I enjoyed our conversation about the migration to microservices — it's exactly the kind of architecture challenge I'm looking for."

Reflect and document

Write down every question you were asked while it's fresh. Note what went well and what you'd improve. This becomes your study guide for future interviews.

Follow up (if you haven't heard back)

If the recruiter gave you a timeline and it passes, send a polite check-in. One follow-up email is fine. Multiple follow-ups is pushy.

The preparation starts with your resume

Great interview preparation begins before you even get the interview. A tailored resume that matches the job description's keywords gets you in the door — and those same keywords become the talking points you'll discuss in the interview. When you use ResumeIdol to tailor your resume, save the output — it's essentially a cheat sheet for your interview prep.