How to Prepare for a Job Interview
What to actually research, how to practice without sounding rehearsed, and the questions that trip up otherwise well-qualified candidates.
Most interview prep advice is generic enough to apply to any job at any company, which is exactly why it doesn't help much. Specific preparation beats general preparation almost every time.
Research the role, not just the company
Reading the "About Us" page tells you almost nothing useful. Instead: read the actual job description twice and note which 3-4 responsibilities are listed first (job descriptions are usually front-loaded with what matters most), look up the team or department on LinkedIn to see who you'd actually be working with, and check what people who've worked there say about the day-to-day — not the marketing copy, the lived experience.
Prepare stories, not talking points
"Tell me about a time you handled conflict" isn't really asking for a definition of conflict resolution — it's asking for a specific story with a beginning, a decision you made, and an outcome. Prepare 4-5 real stories from your own experience ahead of time (a project that went wrong, a disagreement with a manager, a time you had to learn something fast) and mentally tag which competencies each one demonstrates. Then adapt the same story to whatever question actually gets asked, instead of trying to have a pre-written answer for every possible phrasing.
The questions people underprepare for
"Why this company, specifically?" trips up more candidates than it should, because "I need a job" is the honest answer and also not a good one to say out loud. Have a real, specific reason — something about the actual work, the team, or the problem the company is solving — not a reworded version of their mission statement.
"What are you looking for in your next role?" is really asking whether you know yourself well enough to know what you want. Vague answers ("growth," "a good culture") sound like you haven't thought about it. Specific answers ("more ownership over a whole feature area instead of just execution," "a team that does code review seriously") sound like you have.
Ask questions that show you've thought about the role
Save your questions for things you couldn't have found from a Google search. "What does success look like in this role after 6 months?" and "What's the biggest challenge someone in this role would be dealing with in the first few months?" tend to get much more honest, useful answers than "what's the culture like?" — and they signal that you're evaluating the job seriously, not just trying to get an offer.
The logistics that are easy to forget
Test your video call setup the day before, not five minutes before. Have a copy of your resume open in case they reference something specific on it. And if it's in person, plan to arrive with buffer time — arriving flustered costs more than arriving 15 minutes early and waiting in the lobby.
After the interview, a short, specific thank-you note (referencing something actually discussed, not a generic template) takes five minutes and genuinely does get noticed.