u/FourLeafAI

Candidates who say "I don't know" and follow it with how they'd find the answer get more credit than candidates who bullshit their way through something they clearly don't understand.

IMO the second group is way more common. Long meandering answers full of buzzwords where everyone in the room can tell you're stalling. We're not impressed and we're definitely not fooled.

"I haven't worked with that specific tool, but I'd approach it by looking at the documentation and running a small test case first" is a real answer. It shows problem-solving instinct even when you don't have the knowledge yet.

Just don't overuse it. One or two honest "I don't know" moments build trust. Five in a row means you're underqualified.

Candidates who do some real research and can name specific products, recent news, or team members go a long way in my eyes. "I noticed your team just shipped X" or "I read about your approach to Y in the engineering blog." It changes the dynamic completely because I stop evaluating and starts having a conversation.

Candidates who didn't research give answers that could apply to any company. 'I'm excited about the mission.' 'I love the culture.' Perfectly fine but completely generic and forgettable IMO.

Just spend 10 minutes on the company blog and LinkedIn profiles of the team. It makes a difference.

It’s such an odd and rewarding thing. I added a $5 5 day pass option, and that’s what it took. ~insert it ain’t much but it’s honest work giphy~

Hardest thing I’ve found is pushing product changes into the void, largely based off vibes since I don’t have the volume to run experiments. As a data scientist, that has been a really weird feeling.

Anyway, just wanted to say I feel reinvigorated, and that if anyone is struggling to get customers, the moat of your product is consistency and time, not whatever code you’re pushing with Claude Code

The candidates who negotiate best do three things consistently. They name a specific number instead of a range. They tie it to the role's scope and market data. And they stop talking after the ask instead of backpedaling into a lower number.

Most candidates either skip negotiation entirely or give a range so wide it reads as uncertain. "I'm thinking somewhere between $120K and $160K" tells me you'll accept $120K.

The ones who say "Based on this role's scope and comps in this metro, I'm targeting $145K" get taken more seriously. Even when we can't hit the number, the conversation starts differently.

Every interview I run, I can tell within the first answer whether someone practiced out loud or just thought about their answers.

Practiced candidates answer in 60 to 90 seconds with a clear structure. Unpracticed candidates ramble for three minutes, backtrack twice, and end with 'does that make sense?'

The content quality is often the same. The delivery gap is what separates them. Five spoken repetitions of your top three stories changes the outcome more than ten hours of silent prep.

Say it out loud. Record yourself. Time it. That's the whole trick.

I've been a hiring manager for a long time and I ask one question in every interview that throws people off more than any other. It isn't clever. It isn't on any list of "best behavioral questions."

The question is just: what did you spend most of last Tuesday doing?

Not your biggest project. Not your proudest moment. The most ordinary day of your last week, in detail.

Most candidates are unprepared for it because they've rehearsed the big stories. The "tell me about yourself," the "greatest weakness," the "describe a challenge." None of that prep saves you when I want to know about Tuesday.

What I'm actually testing isn't memory. It's whether you can describe your work with precision when there's no script. People who do good work remember the texture of it. People who perform good work remember the slide deck. The hierarchy of what you mention (did you bring up the teammate you helped, or only the thing you shipped?) tells me more than any STAR-format answer.

The pattern I see most often is that the candidates who answer this worst are the ones who came in best-prepared on every other dimension. They built a polished narrative for the interview. They didn't build one for an arbitrary Tuesday.

If you're prepping for interviews, pick three random days from the past two weeks and practice describing them out loud. If you can't, that's information about your work, not your interview skills.

If you're a hiring manager, try it for a few cycles. The floor of your process rises.

Most candidates stress about reference checks like they're a final exam. They really aren't, I'm just looking for one thing.

Does the way you described your role match how your reference describes it? The specific projects, the scope, the level of ownership. If you said you led the migration and your reference says you were on the team that did it, that's a mismatch I notice.

The other thing that stands out is how quickly your reference responds. Enthusiastic references reply within a day and volunteer specific stories. Lukewarm references take a week and give one-sentence answers.

Pick references who worked directly with you on something specific, not just senior people who barely remember what you did.

Most candidates stress about reference checks like they're a final exam. They really aren't, I'm just looking for one thing.

Does the way you described your role match how your reference describes it? The specific projects, the scope, the level of ownership. If you said you led the migration and your reference says you were on the team that did it, that's a mismatch I notice.

The other thing that stands out is how quickly your reference responds. Enthusiastic references reply within a day and volunteer specific stories. Lukewarm references take a week and give one-sentence answers.

Pick references who worked directly with you on something specific, not just senior people who barely remember what you did.

The "what's your biggest weakness" question isn't a trick. I'm checking whether you can reflect honestly on your own skill gaps.

The pattern that loses points every time is a strength dressed up as a weakness. "I care too much about quality" or "I'm a perfectionist" reads exactly like someone avoiding the question.

The answers I remember name something real and small. "I wasn't great at estimating timelines for cross-team projects, so I started breaking deliverables into two-day chunks and tracking my accuracy against them." Boring, specific, and exactly what I'm looking for.

Pick a real gap. Show me you noticed it and did something concrete about it.

Most post-interview thank-you notes get skimmed and forgotten within seconds.

The ones that get forwarded to the hiring committee do one thing. They reference something specific the interviewer said and connect it back to a real example from the candidate's work. That gives me something concrete to point to when I'm advocating for them.

"Thank you for your time today, I really enjoyed learning about the team" does nothing. Skip the note entirely if you don't have something specific to say.

First-round screens test whether you can talk clearly and your experience roughly fits what they need. Second rounds test whether the team wants to work with you.

The biggest thing I see candidates miss is thinking that the second round is just a "harder first round." The questions fundamentally change and the expected answers change. They want to see how you think on your feet when someone pushes back, not whether you memorized the STAR framework.

The people who advance ask sharp questions about the team, the project backlog, and who they would work with directly. The people who stall give the same polished answers they gave in round one.

Practice by talking, not by reading. Saying your answer out loud five times changes the delivery completely.

The biggest gap in interview prep comes from people writing good answers and saying them out loud

Most people prepare for interviews by reading their notes silently or typing answers. Speaking them under pressure is a completely different skill because filler words multiply, structure falls apart, and you lose the punchline.

By the fifth time you say the same story out loud, your delivery sounds categorically different. Not because the content changed, but because your delivery caught up.

Practice by talking, not reading!

The biggest gap in interview prep comes from people writing good answers and saying them out loud

Most people prepare for interviews by reading their notes silently or typing answers. Speaking them under pressure is a completely different skill because filler words multiply, structure falls apart, and you lose the punchline.

By the fifth time you say the same story out loud, your delivery sounds categorically different. Not because the content changed, but because your delivery caught up.

Practice by talking, not reading!

Not trying to start a fight, but I keep seeing these AI “cheat your interview” tools pop up and I don’t really get the appeal.

Like yeah, maybe you can get through one round if you’ve got something feeding you answers. But the second the interviewer goes off-script or asks a follow-up you weren’t expecting, it falls apart pretty fast.

I’ve seen this happen a few times now (mock interviews + friends going through loops). Someone has a solid answer ready, then gets one layer deeper and just… stalls out.

And even if it “works” once, what’s the plan after that? You’re back in the same spot for the next interview, or worse, on the job.

The only thing that’s actually worked (at least from what I’ve seen) is reps. After a while the questions stop feeling random. You start recognizing patterns. You know how you want to structure answers. You’re not scrambling mid-sentence.

Confidence from that feels very different than “I hope this tool saves me.”

For context, I do work on a product in this space, so I’m obviously biased. But honestly that’s also why I feel pretty strongly about it. The shortcut-y stuff just doesn’t seem to hold up past the first round.

Curious if anyone here has actually had these tools help beyond a single interview, or if it’s mostly a short-term crutch.