How to Answer "Why Should We NOT Hire You?" (and Other Interview Trap Questions)

Somewhere around the twenty-minute mark, the interview stops being a conversation and turns into a small experiment. The hiring manager pauses, says "okay, something a little different now," and drops a question that has no clean answer. Why should we not hire you. Sell me this pen. Tell me about a time you failed. Where do you see yourself in five years.

Most people treat these like landmines. They freeze, grab the safest-sounding line they can invent on the spot, and walk out sure they blew it. A candidate with nine years under his belt posted about exactly this after being asked for two reasons not to hire him. He gave what he called "two BS reasons," lost his nerve, and figured it cost him the offer.

Here's the part almost nobody tells you. The answer usually isn't what's being graded. Read enough of these interviews from both sides of the table, and the interviewers who bother to explain their own reasoning all circle the same point: they're watching how you handle the pressure, not which door you pick. So let's go trap by trap, in the order of what each one is really measuring, and I'll hand you a way to answer that doesn't need you to lie or grovel.

"Why should we NOT hire you?"

This is the flagship trap, the one that hit 21,000 upvotes when that senior candidate vented about it, and it's nasty because both obvious moves backfire. Invent a fake weakness and you sound rehearsed. Get honest about a real one and you can talk yourself right out of the offer. Freezing and mumbling "two BS reasons," like the guy in that thread, is the default outcome for a reason.

What works is a genuine limitation that only bites in a situation this employer probably doesn't have. My favorite version, which one person swears he's rolled out repeatedly and gotten away with: "if you want someone who's going to sit in this exact role for a long stretch, you probably shouldn't hire me, because I'm likely to get promoted out of it." A bit cocky, sure. But it reads the room, answers honestly, and turns the "flaw" into the thing most managers actually want.

The other legitimate move is to hand the question back for clarity. Something like, "I want to give you a useful answer, so can I ask what you're hoping to learn here?" That does two jobs. It buys you a beat, and it tests whether the interviewer wanted a real conversation or was just enjoying watching you squirm. If they get prickly, that's information about the place, not about you. Plenty of hiring managers were never trained to interview, and a hostile version of this question is often a red flag pointing back at the employer.

One thing I'd be careful with: flipping the question fully around ("what's the biggest reason I shouldn't pick your company?") is a gamble. The senior candidate I mentioned tried it and the interviewer got visibly annoyed and ended the call. It can land as confident with the right person and combative with the wrong one. Read the temperature before you swing. It's the same judgment you'd use reading whether a green Open To Work badge helps or hurts you: context decides.

"What's your biggest weakness?"

Same family, quieter delivery. And the number-one way to fail it is the humble-brag everyone can smell from across the room. "I'm a perfectionist." "I just care too much." "I work too hard." Interviewers have heard it ten thousand times and it tells them you'd rather perform than be honest.

Name something real but contained, then spend most of your breath on the system you built to manage it. Maybe you used to sit on decisions too long, so now you give yourself a hard deadline and a "good enough to ship" bar. Maybe you're weak at interrupting people, so you started sending a written agenda before meetings you run. The weakness is the setup. The mechanism you built is the actual answer, because it shows you can spot a gap in yourself and engineer around it. If you want to work the flip side of this too, it pairs naturally with how you talk about your strengths in the same interview.

"Sell me this pen"

Everyone remembers the Wolf of Wall Street version, where the trick is to manufacture urgency and get you to sign something. That's theater. The actual skill this is meant to test is discovery, and most people fail it by launching straight into a pitch about the pen's smooth ink and comfortable grip.

Don't sell yet. Ask. "What do you currently use to write? When you're signing something important, what matters to you about the pen in your hand? How often does yours run out at a bad moment?" You're finding out whether they even need a pen before you position one. As one commenter put it, the whole point is figuring out if the buyer needs the thing at all, and selling is more listening than talking. If they don't need it, a strong answer can be to say so and pivot to what they do need.

A quiet caveat. Sometimes this question shows up in an interview for a role that has nothing to do with sales. One person applied for an operations internship and got hit with "sell me this pen," then learned mid-interview the job was actually sales. That's not a test, that's a bait and switch, and it's fair to name it politely and decide whether you still want the seat. It's the same instinct that helps you spot when a robotic one-way video interview is worth your time or not.

"Tell me about a time you failed"

This one has a scorecard you can't see, and a hiring manager spelled it out plainly: when he asks about a failed project, he's watching to see whether you throw your teammates under the bus or include your own role in the outcome. The jargon for it is internal versus external locus of control. Do you believe things happen to you, or do you own your part?

So the "failure" you pick matters less than how you carry it. There's a great before-and-after from a candidate who got asked this twice, four years apart. The first time he blamed another team, nailed the technical part, and didn't get the job. The second time he owned a real mistake, a staging step he skipped that caused five hours of production downtime, and walked through exactly how he changed the process afterward so it couldn't happen again. He got that one.

Pick something that genuinely went wrong, say clearly what your piece of it was, and land on the concrete fix or lesson. Skip the fake failures dressed up as successes ("I failed because I set the bar too high"). They read as a dodge, which is the one thing this question is built to catch.

"A coworker is behind on their work. What do you do?"

Careful with this one, because the instinct that feels most virtuous is usually the wrong answer. "I'd jump in and help them finish, because that's what a good teammate does." One candidate got rejected three times in a row on that exact reply before it clicked.

These scenario questions test priorities and boundaries, not niceness. Managers who hire regularly are blunt about it. One said the worst answers she hears are "we all worked a bunch of extra hours" (second only to "did nothing"), and that she watches for people who quietly burn their time fixing things for "the team" while their own accountable work slips. Another manager pointed out that the business already set the priorities, and changing them on your own without looping in your chain of command isn't teamwork, it's freelancing.

The answer they're actually after has three moves. Help with the immediate thing if you can do it without blowing your own deadline. Figure out whether this is a one-off crunch or a pattern. And if it's a resource or training gap, escalate so the person gets real support instead of becoming your permanent side project. That's the difference between looking like a leader and looking like a doormat.

The "no right answer" trade-off

Here's the purest example of the whole genre. A hiring manager asked a project manager candidate to choose: ship on time with known quality issues, or ship late with everything fixed, no discussion allowed, no extra information. Then he explained himself. In ten years of hiring, he'd never once rejected someone based on which option they picked. What he watches for is whether the candidate sits with the discomfort or immediately grabs the "safe" answer they think he wants. The people who fish for the response they think he's looking for give themselves away instantly.

So think out loud. Name your assumptions before you commit. "If the quality issues are known and we can be transparent with the client, I'd probably ship and manage it openly. If they're the kind of defect that could blow up on someone, I'd eat the delay." One commenter caught exactly this nuance: the word "known" is doing a lot of work, and a strong candidate flags that the answer changes when the risk is severe or uncertain. As another interviewer put it, it's never about a right answer, it's "how would you navigate the problem." Show them the working, not just the destination.

"Why are you leaving your current job?"

The trap here is simple and people fall in it constantly: they badmouth their current employer. Even when the complaints are legitimate, the interviewer isn't hearing "that place was toxic." They're hearing a preview of how you'll talk about them in a year. Venting reads as a future liability.

Keep it neutral and pointed forward. You're moving toward something this role offers, more scope, a specific kind of problem, a team structure that fits how you work, not running away from a villain. If the truth is that your last job was genuinely bad, compress it into one calm, non-bitter sentence and get to what you're looking for next. Nobody expects your old job to have been a dream. They just don't want a grudge on the payroll.

"What are your salary expectations?"

This one feels like a trap because it often is one, and there's a specific mechanism underneath it that's worth understanding. Candidates keep getting burned for naming a number that's inside the posted range. Someone saw a listing at 42k to 75k, asked for 60k, and got told there wasn't budget for that. How, when 60 is comfortably inside 42 to 75?

A compensation professional explained the sleight of hand in a comment I keep coming back to. The posted "range" and the actual "budget" for a role are not the same thing. The range is a wide pre-set band tied to a whole career ladder, and hiring anywhere near the top usually needs special approval. The budget is the real money the department has allocated, and it's often clustered near the bottom of that range. So the posting isn't lying, exactly. It's just showing you the ceiling of a building you'll be hired into the basement of.

Two practical moves. First, try to make them name a number before you do. "What have you budgeted for this role?" is a fair question, and if pay-range laws apply where the job is, that number may already be on the posting. As of 2026, roughly sixteen states plus Washington, D.C. require employers to publish a good-faith pay range, with Illinois and Minnesota's rules taking effect in January 2025. Second, if you have to go first, come with a researched range and anchor toward the top of it rather than the middle. One candidate simply refused to name a number, kept returning "how much are you offering," and ended up with an offer well above what he would have asked for. He'd have lowballed himself if he'd blinked.

"Where do you see yourself in five years?"

Half the internet thinks this is a dead question, and honestly they're not wrong. But it still gets asked, and it still has a scorecard. What they're checking is whether your realistic trajectory includes this company at all, or whether you'll be gone in eighteen months the second something shinier appears.

The two ways to bomb it are over-promising and clowning. Saying you want the interviewer's job in five years is a swing that mostly misses. Saying "who knows, look at COVID and AI, nobody can predict anything" is funny in a Reddit thread and career-limiting in the room. Give a plausible growth arc that plausibly runs through this role, more depth in the work itself, more ownership, maybe leading a piece of it. You don't have to promise to die at the company. You just have to sound like someone who'd stick around long enough to be worth training. If you read the room right, the signs you're doing well tend to show up right after answers like this.

"Do you have any questions for us?"

The one universal rule here: never say "no, I'm good." It reads as low interest every single time. Beyond that, this is the one section where I'm going to tell you the internet genuinely disagrees with itself, because it does.

The strong questions are about the work and the reality of the role. What are the biggest problems you'd want this hire to solve in the first ninety days? What does someone who's excellent in this role do that someone who's merely fine doesn't? What's the team's hardest challenge right now? These signal that you're already thinking about performing, and they hand you a free roadmap for the job. One person credited a closing question like that as the "cherry on top" that got him references an hour after the interview, though he was quick to add that he'd also prepped like crazy and the question didn't do the work alone.

Now the part the tip lists skip. Some interviewers actively dislike the feedback-fishing closers. The "is there anything that makes you think I'm not the best candidate?" question, which gets passed around as a power move, rubs a lot of hiring managers the wrong way. One who hires in fintech said flatly he wouldn't hire someone who asked it, because it forces the interviewer into an awkward spot when they're supposed to keep the conversation positive, and it reads as difficult to work with. Others said asking them to critique your resume or interview technique is simply out of place, save it for a follow-up email if you must. My take: ask sharp questions about the job, skip the gimmicks that put the interviewer on the spot. There's a whole art to the questions that reveal what the role and the environment are really like, and none of the good ones are gotchas.

The trap running underneath all of them

There's one more trap that isn't a specific question, and it catches more people than any single curveball. It's the gap between what's on your resume and what you can actually defend when someone asks a calm follow-up.

A hiring manager described interviewing someone whose top bullet under their last job was "Managed implementation of XYZ." His warm-up question, the friendly one meant to relax the candidate, was "tell me about implementing XYZ and the challenges you hit." Crickets. The candidate eventually admitted they'd played a minor part and didn't really know the thing. That's the trap. Not a gotcha riddle, just your own resume turned into a question.

Another interviewer drew the line cleanly. Exaggerate your six months of experience into "a couple of years" but answer the questions competently, and most people will cut you slack. Claim you're an expert and whiff the basics, still survivable. Claim you did something and then can't answer a single question about it, and the whole thing collapses, because now they can't trust anything else you wrote. The market is genuinely unfair in both directions, and job postings do their own share of stretching. But the practical defense on your side is simple. Everything you write down, be ready to talk about for two full minutes without flinching. If you can't, take it off the page. The same discipline that gets you through the endless modern interview loop starts with a resume you can defend cold, and it's what turns these trap questions from ambushes into openings.

The pattern, once you see it

Step back and every one of these questions is doing the same job. It's manufacturing a small, controlled moment of pressure to see who you are when the script runs out. The trade-off question checks whether you can sit in discomfort. The failure question checks whether you own things. The teamwork scenario checks whether you understand priorities. The salary question checks whether you'll hold a boundary. Even "sell me this pen" is really asking whether you listen before you talk.

Which means the meta-answer is almost always the same. Stay composed. Think out loud. Be honest about a real thing rather than perfect about a fake one. And remember it's a two-way conversation, not an interrogation, however the person across the table is behaving. The candidates who internalize that stop treating curveballs as threats. A weird question just becomes another place to show them how you think, which is the only thing they were ever really buying.