Before the interview
Do the homework that pays off
Most candidates walk in having skimmed the job description and browsed the company's About page. That's not preparation — that's the bare minimum. The people who get offers are the ones who show up understanding what the team actually needs and can connect their experience to it in the first five minutes.
Pull the JD into a doc and highlight the must-haves. Not every bullet matters equally. Find the 3–4 things they really care about and build your prep around those.
Write three wins that map to those must-haves. Specific stories with outcomes. If they need someone who can scale operations, have a story where you scaled operations — with a number attached.
Research team, product, and recent news in under 30 minutes. Check LinkedIn for who you're meeting, scan their blog or press page, and look for recent product launches or challenges. This gives you context to ask smart questions.
Nail your intro. The "tell me about yourself" question is where most people lose momentum. See the TMAY method for how to make it unforgettable.
Answer toolkit
Use STAR to stay sharp
Behavioral interview questions ("Tell me about a time when…") are where interviews are won or lost. The STAR framework keeps your answers structured so you don't ramble, and ensures you always land on impact — not just activity.
Pick stories that show scope, impact, and decisions. Interviewers want to see how you think, not just what you did. Choose examples where you had to make a judgment call and it led to a measurable result.
Keep it tight: 15–20 seconds for each S, T, A, R. That's about 60–80 seconds total. If you're going longer, you're losing them. Practice with a timer until it feels natural.
End with a metric, not a feeling. "It went really well" doesn't land. "We reduced churn by 18% in one quarter" does. Always close with a number.
Have two backups for each core competency. If your first story doesn't resonate or they ask a follow-up, you need another one ready to go. Prepare more than you think you'll need.
STAR in one line
Situation and Task set context. Action shows judgment. Result proves impact.
Situation
Task
Action
Result
Questions to ask
Signal judgment, not just curiosity
The questions you ask tell the interviewer more about your thinking than most of your answers do. Generic questions ("What's the culture like?") signal that you didn't prepare. Strategic questions signal that you already think like someone on the team.
"What needs to be true in 90 days for you to call this a great hire?" This shows you're already thinking about delivering results, not just landing the role.
"Where does work slow down between teams right now?" This tells you where the friction is — and positions you as someone who solves cross-functional problems.
"What decision or bet matters most this quarter?" This shows you understand that companies have priorities and trade-offs, and you want to align with what matters now.
"How do high performers earn trust here?" This tells you the unwritten rules — the stuff that actually determines who gets promoted and who stalls out.
Common mistakes
Avoid these traps
These are the patterns that interviewers see over and over — and they're the fastest way to go from "strong candidate" to "pass." Most of them are fixable with awareness and practice.
Story with no result or number. If you describe what you did but never say what happened because of it, the interviewer has to guess whether it mattered. Don't make them guess.
Overlong intros that bury the lead. Starting with your entire career history before getting to the relevant point loses attention fast. Lead with what matters to this role.
Blaming others instead of owning decisions. Even if the situation was someone else's fault, interviewers want to hear what you did about it. Ownership is the signal they're looking for.
No questions that show you understand the business. If your only questions are about PTO and remote work, you've told them you're optimizing for comfort, not impact.
Role fit
Match your experience to their needs
The interviewer isn't evaluating your career — they're evaluating whether you can solve their specific problems. Your job is to translate your experience into their context so clearly that they can picture you doing the work on day one.
Translate past work into the stack, customers, and constraints they have. "I managed a CRM migration" is fine. "I managed a CRM migration for a 200-person sales team on Salesforce, similar to your setup" is better.
Use their language from the JD and site. If they say "velocity," you say "velocity." If they say "customer obsession," you mirror it. This isn't mimicry — it's showing you understand how they think.
Bring one fast improvement idea tied to revenue, cost, or risk. Not a full strategy deck — just one observation that shows you've thought about their business and you already see where you'd add value.
Follow up
Close strong in 24 hours
Most follow-up emails are forgettable — "Thanks for your time, I'm excited about the opportunity." That tells them nothing and sounds like every other candidate. A great follow-up makes the interviewer remember the conversation and, more importantly, remember you.
Call out one thing you connected on as humans. A shared love of coffee, a trip you both took to Iceland, a favorite book. Interviewers talk to dozens of candidates — the person who made a real human connection is the one they remember when it's decision time.
Send a three-line recap with one concrete next step. Reference something specific they shared about the team's goals, and connect it to how you'd contribute. Show them you were listening, not just performing.
Attach a small artifact if relevant. A one-page checklist, a brief, a diagram. Something that demonstrates how you think — not a full deliverable, just enough to show you're already in problem-solving mode.
Subject: Great connecting today
Hi [Name], really enjoyed our conversation — especially [the personal connection, e.g. swapping Iceland travel stories]. Based on what you shared about [goal], I'd focus first on [quick win]. Attached is a short [artifact] that shows how I approach it.
Looking forward to next steps,
[Your Name]