Things I've Learned About Job Interviews After Doing Way Too Many Of Them
I spent years on both sides of the table. First as the person asking questions, then as the person sweating through answers in fluorescent-lit conference rooms. What follows isn't advice from a career coach who's never actually hired anyone. It's the accumulated result of bad candidates, weird edge cases, and a few times I hired someone I shouldn't have because I was tired and impressed by charisma instead of substance. Here's the thing nobody tells you: the interview isn't about demonstrating you can do the job. You already proved that with your resume. The interview is about proving you won't be a drag on the team. That's it. Everything else is secondary. I once sat through a 90-minute technical interview with a candidate who could solve every problem on the whiteboard in half the time I could. Clean code, optimal algorithms, explained each step clearly. He also spent 20 minutes explaining why his last three bosses were incompetent. We didn't hire him. Not because he was a bad engineer—he was genuinely great. But every project he touched would have required me to manage his frustration rather than his output. That's the calculation that matters.
So the first rule, the one most people miss: your technical skills are table stakes. What they're actually evaluating is whether working with you daily would make their life easier or harder. Frame everything through that lens. When I was hiring, I stopped caring about the perfect answer almost immediately. I cared about what happened when the candidate hit a wall. Would they panic? Would they guess confidently? Would they ask a clarifying question? The last one was the strongest predictor of future performance, by a wide margin. People who ask good questions during an interview tend to ask good questions when they're stuck on the job too. There's also a counter-intuitive thing about showing weakness. I used to flag this as a red flag—candidates who admitted they didn't know something. Then I realized the ones who admitted it were the ones who would tell you when something was broken. The ones who never admitted uncertainty were the ones who'd ship code with a known issue and pretend it was fine because they couldn't face saying "I don't know." After that realization, I started preferring candidates who said "I'm not sure, but here's how I'd figure it out" over the ones who bluff their way through.
Now let's talk about what to actually do. Do research the team, not just the company. Look at LinkedIn. See who you'd be reporting to, who your peers are, what their backgrounds look like. If you can reference a specific project one of your potential teammates worked on and ask a thoughtful question about it, you immediately shift from generic candidate to someone who actually cares about the role. I've seen this move a candidate from the "maybe pile" to the "hire" pile more than once. Do prepare stories, not scripts. Most candidates either wing it or memorize answers like they're reciting poetry. Neither works. Have 5 to 7 story buckets you can draw from—things like "a time I disagreed with my manager," "a time I made a mistake," "a time I had to learn something quickly." These map to almost every behavioral question. When you have real stories ready, you sound natural because you're telling actual events, not performing.
Get the Full Details
Do ask questions that reveal how you think. This is where most candidates botch the second half of the interview. They ask things like "what's the culture like?" which gets you a PR answer. Instead, ask things like "what's the biggest thing your team is struggling with right now?" or "how do decisions get made when there's disagreement?" You get real information, and you demonstrate that you're already thinking about how you'd fit into their actual workflow. Now the don'ts, which are where most people fail. Don't rehearse your answers out loud to a mirror. I'm serious. This is the most common prep mistake I see. It makes you sound rehearsed. Candidates who practice this way have a flat, monotone delivery and their eyes glaze over slightly because they're recalling rather than communicating. Practice by talking to a real person, preferably one who'll interrupt you and throw curveballs. Simulated pressure matters more than polished delivery.
Don't badmouth anyone. This seems obvious until you're in the room with someone who's been laid off and spent 45 minutes explaining how their former company was run by idiots. It doesn't matter if they're right. You will not look honest; you will look like a liability. I've seen candidates tank offers over this. One guy talked so negatively about his previous employer that the hiring manager literally stopped taking notes and just stared at him. The offer was gone before the question "do you have any questions for us?" even came up. Don't pretend to know things you don't. I covered this above with the weakness angle, but it bears repeating because people consistently ignore it. A confident wrong answer is worse than an honest uncertainty. Wrong answers create downstream problems. Uncertainty is solvable. Here's an edge case that threw me for a loop. I was interviewing a candidate for a senior role, and she kept deflecting every behavioral question back to her team. "We did this," "My team accomplished that," "We decided to go with..." I started marking her down as someone who couldn't own her contributions. Then I asked a direct follow-up: "Okay, but what was your specific role in that decision?" She paused and said, "I'm sorry, what do you mean? I led the project." She genuinely didn't understand why I was asking. She had been promoted into a leadership position without ever having to articulate her individual impact. She was competent but had no framework for self-reflection. We didn't hire her for the senior role. She needed a different position where she could develop that skill first.
This is the kind of thing that doesn't show up on any "dos and don'ts" list. Most interview guides will tell you to be confident and take ownership. They won't tell you that confidence without self-awareness is a specific failure mode that's hard to spot in a 45-minute conversation. Another thing to watch for: salary expectation discussions. If you bring up money too early, you look transactional. If you wait too long, you look naive. The sweet spot is usually when they bring it up first, which tends to be toward the end of a later-round interview. If they ask you directly, give a range, not a number. Something like "based on my research and experience, I'm looking at the 90 to 110 range, but I'm flexible depending on the total package." That keeps the conversation open. A word on follow-ups. Sending a thank-you note is expected but largely irrelevant to the decision. What matters more is sending a brief follow-up that adds something. Maybe you reference something you discussed and add a thought you had afterward. Maybe you share a relevant article or resource. This signals ongoing engagement without being performative. I've seen this land candidates back on the shortlist after they'd already been passed over once.
The hardest part about interviews is that the evaluation is inherently flawed. Interviewers are tired. They're biased toward people who remind them of themselves. They confuse confidence with competence. They remember the candidate who made them laugh more than the one who solved the problem correctly. None of this is unique to any industry or company. It's just human. So you optimize for what you can control. Your preparation. Your honesty. Your ability to listen and respond rather than recite. The rest is noise. I've hired people who bombed interviews and passed on people who nailed them. Both happened. The pattern that actually predicted success wasn't interview performance—it was the quality of their questions and how they handled uncertainty. Those two signals, more than any polished answer, told me who would actually do the work.
