Most Common Interview Questions
With brutally honest answers.
I've been on both sides of the table — here's what actually matters.
10
Opening
15
Behavioral
10
Technical
10
Culture Fit
5
Closing
The Cheat Sheet
All 50 questions with one-line answer strategies. Bookmark this. Print it. Tape it to your bathroom mirror.
| # | Question |
|---|---|
| 1 | Tell me about yourself. |
| 2 | Why do you want this job? |
| 3 | What are your greatest strengths? |
| 4 | What is your greatest weakness? |
| 5 | Where do you see yourself in 5 years? |
| 6 | Why are you leaving your current job? |
| 7 | Why should we hire you? |
| 8 | What do you know about our company? |
| 9 | What's your salary expectation? |
| 10 | When can you start? |
| 11 | Tell me about a time you led a team through a difficult project. |
| 12 | Describe a time you failed. |
| 13 | Tell me about a time you handled conflict with a coworker. |
| 14 | Give an example of going above and beyond. |
| 15 | Tell me about a time you disagreed with your boss. |
| 16 | Describe a time you worked under extreme pressure. |
| 17 | Tell me about a mistake you made and how you handled it. |
| 18 | Give an example of a time you had to learn something quickly. |
| 19 | Tell me about a time you had to persuade someone. |
| 20 | Describe a time you received critical feedback. |
| 21 | Tell me about a time you managed competing priorities. |
| 22 | Give an example of a creative solution you developed. |
| 23 | Tell me about a time you dealt with an ambiguous situation. |
| 24 | Describe a time you improved a process. |
| 25 | Tell me about a time you had to deliver bad news. |
| 26 | Walk me through your approach to solving a technical problem. |
| 27 | How do you stay current with industry trends? |
| 28 | Explain a complex concept to me like I'm non-technical. |
| 29 | Tell me about a project you're most proud of. |
| 30 | How do you handle a disagreement about technical direction? |
| 31 | What tools and technologies are you most proficient with? |
| 32 | How do you approach code reviews? |
| 33 | Describe your debugging process. |
| 34 | How do you prioritize technical debt? |
| 35 | Tell me about a system you designed from scratch. |
| 36 | What motivates you? |
| 37 | How do you handle feedback? |
| 38 | Describe your ideal work environment. |
| 39 | How do you handle working with difficult people? |
| 40 | What's your management style? (or: How do you like to be managed?) |
| 41 | How do you handle work-life balance? |
| 42 | Tell me about a time you mentored someone. |
| 43 | What are you passionate about outside of work? |
| 44 | How do you handle ambiguity? |
| 45 | What would your coworkers say about you? |
| 46 | Do you have any questions for us? |
| 47 | What does the first 90 days look like for someone in this role? |
| 48 | What's the biggest challenge the team is facing right now? |
| 49 | How does the company measure success in this role? |
| 50 | Is there anything about my background that gives you hesitation? |
Before We Start
I've interviewed hundreds of candidates and been interviewed more times than I can count. I've been the nervous person in the waiting room and the person deciding whether to extend the offer. Here's what I know for certain:
Most interview advice is terrible. It tells you to memorize scripts, use power poses, and answer “What's your weakness?” with “I work too hard.” That advice was written by people who haven't interviewed anyone since 2004.
This guide is different. For each question, I'll tell you what they're REALLY asking, the mistake most people make, a framework for answering, and a sample answer you can adapt. No scripts. Frameworks. Because scripts sound robotic and frameworks sound like you.
Opening Questions
#1-10The questions that set the tone. Get these right and the rest of the interview is a conversation. Get them wrong and you're playing catch-up.
“Tell me about yourself.”
Can you communicate clearly and concisely? Do you know what's relevant?
Reciting your entire resume from birth. Nobody cares about your high school GPA.
Use the 90-second pitch formula: Present Role + Key Accomplishment + Why You're Here. Three sentences. That's it.
Sample Answer
“I'm a senior product manager at Acme Corp where I led the launch of our enterprise platform that grew to $12M ARR in 18 months. Before that, I spent four years in consulting learning how to structure ambiguity into action plans. I'm here because your team is solving the exact problem I've spent the last three years obsessing over — and I want in.”
“Why do you want this job?”
Did you actually research us, or are you mass-applying to everything with a pulse?
Generic answers that could apply to any company. 'I love your culture' means nothing.
Name something SPECIFIC about their product, mission, or team that you genuinely care about. Then connect it to your skills.
Sample Answer
“I've been following your open-source data pipeline project for two years — I've even submitted a PR. The way your team approaches real-time processing is exactly the technical challenge I want to spend the next chapter of my career on. Plus, I noticed you're expanding into healthcare, which is where my domain expertise lives.”
“What are your greatest strengths?”
Are you self-aware? Do your strengths match what we actually need?
Listing generic strengths like 'hard worker' or 'perfectionist.' Those aren't strengths — they're cliches.
Pick 3 strengths that directly map to the job description. For each one, have a 15-second proof point ready.
Sample Answer
“Three things. First, I'm unusually good at translating between technical and business teams — I was the one person both sides trusted at my last company. Second, I ship fast. I cut our release cycle from quarterly to weekly. Third, I'm the person people call when something is on fire at 2 AM, because I stay calm and actually fix it.”
“What is your greatest weakness?”
Are you self-aware? Can you learn and grow? Will you be honest with me?
The disguised-strength answer: 'I work too hard.' Interviewers have heard it 10,000 times and it makes them want to end the conversation.
Name a REAL weakness that isn't a dealbreaker for this role. Then explain what you're doing to fix it. The fix matters more than the weakness.
Sample Answer
“I have a tendency to over-prepare for presentations — I'll spend 8 hours on a deck that needed 2. I've gotten better by setting hard time limits and reminding myself that a B+ deck delivered on time beats an A+ deck delivered late. My manager actually flagged this last year and I've cut my prep time in half since then.”
“Where do you see yourself in 5 years?”
Are you going to leave in 6 months? Does this role fit into a coherent career trajectory?
Being too ambitious ('I want your job') or too vague ('wherever the wind takes me').
Show that this role is a logical next step in a trajectory you've thought about. Align your growth with their growth.
Sample Answer
“In five years, I want to be leading a team that's shipped multiple products from zero to one. This role is the perfect bridge — I'd get hands-on with the build phase while developing the leadership skills to eventually run a product org. If your company is growing the way your last three quarters suggest, those opportunities should open up naturally.”
“Why are you leaving your current job?”
Are you running FROM something or running TO something? Are you going to badmouth us next?
Trashing your current employer. Even if your boss is terrible, complaining about it makes YOU look bad.
Always frame it as running TOWARD something. Growth, challenge, mission alignment. Never blame anyone.
Sample Answer
“I've had a great run at my current company — I was promoted twice and built a team I'm really proud of. But I've hit the ceiling for the type of work I want to do. Your company is operating at a scale and complexity that would stretch me in exactly the ways I'm looking for. It's not about leaving — it's about what I'm moving toward.”
“Why should we hire you?”
What makes you different from the other 200 people who applied? Sell me.
Repeating your resume. They've already read it. This is your closing argument.
The Venn Diagram answer: where your unique skills, their specific needs, and your genuine passion overlap. Be specific.
Sample Answer
“You need someone who can take your ML pipeline from prototype to production. I've done that exact thing twice — once at a Series A startup where I was the first ML engineer, and once at a Fortune 500 where I had to navigate enterprise procurement. That combination of scrappy startup execution and big-company navigation is rare, and it's exactly what this role needs.”
“What do you know about our company?”
Did you spend 20 minutes researching us, or are you winging it?
Reciting their Wikipedia page. That tells them you can Google, not that you care.
Go beyond surface facts. Mention a recent product launch, a quarterly earnings insight, a blog post from their CEO, or a Glassdoor trend. Show you've done real homework.
Sample Answer
“I know you just closed your Series C at a $2B valuation, which is impressive given the current market. But what actually caught my attention was your CTO's blog post about rebuilding your authentication layer from scratch — that level of technical courage is rare in a company your size. I also noticed you're hiring heavily in APAC, which tells me international expansion is a priority.”
“What's your salary expectation?”
Can we afford you? Will you accept our range? Are you going to be a difficult negotiation?
Throwing out a number too early. The first person to name a number in a negotiation usually loses.
Deflect, then anchor high. Say you're focused on the right fit first, but that you're targeting a range based on market data. Always give a range, never a single number.
Sample Answer
“I want to make sure we're aligned on scope and expectations first — compensation should reflect the role, not the other way around. That said, based on market data for this role in this market, I'm targeting the $150K-$175K range for base, with the understanding that total comp includes equity, bonus, and benefits. I'm flexible for the right opportunity, but that's my benchmark.”
“When can you start?”
How urgent is our timeline, and will you honor your commitments to your current employer?
Saying 'immediately' when you haven't quit your current job. It signals you'd leave them the same way.
Be honest about your notice period. If you can be flexible, say so. Respecting your current employer actually makes you MORE attractive, not less.
Sample Answer
“I'd want to give my current team a proper two-week notice — they've been good to me and I believe in leaving things right. So realistically, I could start on [date three weeks out]. If there's flexibility on your end for a slightly earlier start to overlap with onboarding materials, I'm open to that conversation.”
Behavioral Questions
#11-25"Tell me about a time when..." — Use the STAR Method: Situation, Task, Action, Result. Every answer should take 90 seconds to 2 minutes.
“Tell me about a time you led a team through a difficult project.”
Can you actually lead, or do you just manage? What's your style under pressure?
Taking all the credit. The best leaders talk about what their TEAM accomplished.
STAR Method: Situation (set the scene in 2 sentences), Task (what was your specific role), Action (what YOU did — be specific), Result (quantify it).
Sample Answer
“We had 6 weeks to migrate 2 million user accounts to a new auth system with zero downtime. I broke the team into three pods — migration, testing, and rollback planning. I personally wrote the rollback scripts because I didn't want to delegate the highest-risk piece. We migrated 100% of accounts with zero incidents and actually came in a week early.”
“Describe a time you failed.”
Can you own your mistakes? Do you learn from failure or repeat it?
Picking a fake failure ('I cared too much') or one that was clearly someone else's fault.
Pick a real failure. Own it completely. Then spend 70% of your answer on what you learned and what you do differently now.
Sample Answer
“I launched a feature without proper load testing because we were racing a competitor. It crashed on day one under 3x expected traffic. I owned it in the post-mortem, and I built a launch checklist that became standard for the entire engineering org. That checklist has prevented at least four similar incidents since. The failure cost us a week. The lesson saved us months.”
“Tell me about a time you handled conflict with a coworker.”
Are you going to create drama on my team? Can you handle disagreement like an adult?
Saying you've never had conflict. That either means you're lying or you're a pushover.
Show that you addressed it directly, privately, and professionally. The resolution matters more than the conflict.
Sample Answer
“A senior engineer and I disagreed on architecture — he wanted microservices, I wanted a monolith for our stage. Instead of escalating to our manager, I asked him to lunch and said, 'Let's build the decision matrix together.' We listed the tradeoffs, weighted them, and the data actually supported a hybrid approach neither of us had considered. We shipped it together and it's still running.”
“Give an example of going above and beyond.”
Are you the type who does the minimum, or do you see what needs to be done and do it?
Describing something that was actually just... your job. Going above and beyond means BEYOND your role.
Pick something where you identified a need nobody asked you to fill, took initiative, and created measurable impact.
Sample Answer
“I noticed our customer churn was spiking but nobody on the product team was tracking why. On my own time, I built a cancellation survey, analyzed three months of data, and presented findings to the CEO. Turns out 40% of churn was from a single onboarding friction point. We fixed it in two weeks and churn dropped 23% the next quarter.”
“Tell me about a time you disagreed with your boss.”
Can you push back respectfully? Or are you either a yes-man or a rebel?
Either saying you never disagree (yes-man) or telling a story where you went around your boss (political liability).
Show that you raised the concern with data, respected the final decision, and maintained the relationship regardless of the outcome.
Sample Answer
“My boss wanted to cut our QA team in half to save budget. I put together a one-page analysis showing that QA had caught bugs that would have cost us 10x the savings in customer incidents. I presented it privately, not in a meeting. He appreciated the data, kept the team at 75% capacity, and I supported that compromise fully. We avoided two major incidents that quarter.”
“Describe a time you worked under extreme pressure.”
Do you crumble, panic, or perform? What does your stress response look like?
Describing pressure you created yourself through poor planning. That's not resilience — that's disorganization.
Pick an externally-imposed pressure situation. Show your process: how you prioritized, communicated, and delivered.
Sample Answer
“Our biggest client threatened to leave — $4M ARR — because of a data integrity issue. I had 48 hours. I assembled a three-person war room, triaged the root cause in 6 hours, built and tested the fix by hour 30, and personally presented the post-mortem to their CTO. They renewed for three years. I slept for 14 hours after that.”
“Tell me about a mistake you made and how you handled it.”
Same as the failure question, but with emphasis on the HANDLING. What's your crisis protocol?
Minimizing the mistake. Own the full scope of the damage before explaining the recovery.
Mistake + Immediate Response + Long-term Fix + What Changed. Speed of acknowledgment matters.
Sample Answer
“I accidentally pushed a config change to production that took down our payment system for 22 minutes. I caught it myself via monitoring, rolled it back within 4 minutes, and sent an incident report to the entire company within the hour. I then built an automated config validation pipeline that prevents similar issues. My mistake. My fix. My new system.”
“Give an example of a time you had to learn something quickly.”
How do you handle being thrown into the deep end? Are you a fast learner in practice, not just in theory?
Picking something easy. 'I learned a new Slack feature' is not impressive.
Pick something genuinely difficult with a tight timeline. Show your learning methodology, not just the outcome.
Sample Answer
“I was asked to take over our Kubernetes infrastructure with zero k8s experience — the previous engineer left with two days' notice. I spent the first weekend reading the docs cover to cover, the second week pair-programming with our DevOps contractor, and by week three I was handling deployments solo. Within two months, I'd reduced our deployment failures by 60%.”
“Tell me about a time you had to persuade someone.”
Can you influence without authority? This is a critical leadership skill.
Describing a time you steamrolled someone. Persuasion isn't about winning — it's about aligning.
Show empathy first (you understood their position), then evidence (data or logic), then alignment (how your proposal served their goals too).
Sample Answer
“Our sales team wanted to promise a feature to close a $500K deal, but engineering couldn't deliver it in the timeline. Instead of saying no, I mapped out what we COULD deliver in that window, showed how it addressed 80% of the client's use case, and proposed a phased roadmap for the rest. Sales got their deal. Engineering got a realistic timeline. The client is still with us.”
“Describe a time you received critical feedback.”
Are you coachable? Will you get defensive, or will you actually improve?
Saying the feedback was wrong. Even if it was, this answer needs to demonstrate coachability.
Describe the feedback honestly. Show your initial reaction (it's okay to say it stung). Then show the concrete change you made.
Sample Answer
“My skip-level told me my presentations were too technical for executive audiences — I was losing the room. It stung because I'd spent hours on those decks. But she was right. I started leading with the business impact, burying the technical details in an appendix, and practicing with non-technical friends. My next board presentation got a standing question from the CEO. That feedback changed my career.”
“Tell me about a time you managed competing priorities.”
Can you triage? Do you know the difference between urgent and important?
Saying you did everything. If everything is a priority, nothing is.
Show your prioritization framework. What did you say NO to? That's the interesting part.
Sample Answer
“I had three deadlines in the same week: a product launch, a board deck, and a team offsite I was organizing. I couldn't do all three well. I delegated the offsite logistics to my most organized direct report, pushed the board deck by two days (after getting buy-in from my VP), and personally drove the product launch. The launch shipped on time. The board deck was better for the extra two days. And my report crushed the offsite.”
“Give an example of a creative solution you developed.”
Can you think laterally? Will you find solutions or just escalate problems?
Describing a solution that was obvious. Creative means it surprised people.
Set up the constraint that forced creativity, then reveal the insight that others missed.
Sample Answer
“We needed to reduce cloud costs by 40% but couldn't reduce features. I noticed we were running identical staging environments for 12 teams 24/7, but they only used them during business hours. I built an auto-scaling scheduler that spun environments down at 7 PM and up at 7 AM. Saved $180K annually. The solution took me a weekend. Nobody had thought to look at the schedule.”
“Tell me about a time you dealt with an ambiguous situation.”
Can you make decisions with incomplete information? Or do you freeze without a playbook?
Waiting for perfect information. In ambiguous situations, the ability to ACT is the skill.
Show how you created structure from chaos. What framework did you apply? How did you de-risk the decision?
Sample Answer
“We acquired a company with no documentation on their codebase, no knowledge transfer, and the entire engineering team had already left. I spent three days mapping the architecture through code reading, set up monitoring to understand usage patterns, and built a decision tree: what to keep, what to rewrite, what to kill. We saved 60% of their codebase and retired the rest. It wasn't perfect, but it was decisive.”
“Describe a time you improved a process.”
Do you accept broken things, or do you fix them? Are you an optimizer?
Describing a minor tweak. Process improvement should have measurable impact.
Before State + What You Changed + After State (with numbers). The delta is the story.
Sample Answer
“Our hiring process took 47 days from application to offer. I mapped every step, found three bottlenecks — scheduling, duplicate interviews, and slow reference checks — and fixed each one. Automated scheduling saved 5 days. Consolidated interviews saved 8 days. Parallel reference checks saved 4 days. New average: 30 days. We stopped losing candidates to faster-moving competitors.”
“Tell me about a time you had to deliver bad news.”
Can you be honest when it's uncomfortable? Do you sugarcoat or do you lead?
Burying the bad news in qualifications. Leaders lead with the truth.
Show that you delivered the news directly, took responsibility where appropriate, and immediately offered a path forward.
Sample Answer
“I had to tell our CEO that the feature he'd promised the board would ship in Q1 was going to miss by six weeks. I didn't send an email — I booked a 1:1, led with the timeline, explained the root cause without making excuses, and presented three options for the path forward. He wasn't happy, but he told me later it was the most professional bad-news delivery he'd received. We shipped in Q2 and exceeded the original spec.”
Technical & Role-Specific
#26-35These vary by role, but the frameworks are universal. Show your methodology, not just your knowledge.
“Walk me through your approach to solving a technical problem.”
Do you have a systematic methodology, or do you just guess and check?
Jumping straight to the solution without explaining your diagnostic process.
Reproduce + Isolate + Hypothesize + Test + Document. Show you have a repeatable process.
Sample Answer
“First, I reproduce the issue reliably — if I can't reproduce it, I can't fix it. Then I isolate variables: is it data, code, infrastructure, or configuration? I form hypotheses ranked by likelihood, test the most likely first, and document everything I try so I'm not going in circles. Once fixed, I write the post-mortem and add monitoring to catch recurrence.”
“How do you stay current with industry trends?”
Are you a lifelong learner, or did you stop growing when you got the job?
Listing podcasts and newsletters. Everyone does that. Show me what you've BUILT with what you've learned.
Name specific sources, but more importantly, show how learning translates to action.
Sample Answer
“I read Hacker News and specific Substacks daily, but reading isn't learning — building is. Last month I read about edge computing patterns and spent a weekend prototyping an edge-cached API for my side project. That prototype directly informed a caching strategy I proposed at work that reduced our P99 latency by 40%. Learning without application is just entertainment.”
“Explain a complex concept to me like I'm non-technical.”
Can you communicate across domains? This is the single most valuable skill in tech.
Using jargon and then saying 'does that make sense?' That's not simplifying — that's patronizing.
Use analogies from everyday life. Start with WHY it matters, then HOW it works. Avoid jargon entirely.
Sample Answer
“If they asked about APIs: 'Think of a restaurant. You don't go into the kitchen — you tell the waiter what you want, and the kitchen sends it out. An API is the waiter. It lets two systems talk to each other without either one needing to know how the other works internally. Your phone's weather app uses an API to ask a weather service for the forecast.'”
“Tell me about a project you're most proud of.”
What do you value? What excites you? And can you articulate impact clearly?
Picking something impressive but irrelevant to the role. Align your pride with their needs.
Pick the project that best demonstrates the skills this role requires. Explain the challenge, your contribution, and the measurable outcome.
Sample Answer
“I built an internal tool that automated our monthly reporting. It sounds mundane, but it replaced 40 hours of manual work across 6 teams every month — that's 2,880 hours per year returned to actual product work. The engineering was straightforward; the hard part was getting 6 teams to agree on data definitions. I'm proud of it because it's still running two years later and nobody thinks about it. The best tools disappear.”
“How do you handle a disagreement about technical direction?”
Can you debate ideas without making it personal? Do you optimize for being right or being effective?
Always deferring to seniority. Good technical cultures need people who push back with evidence.
Data over opinions. Propose an experiment or proof-of-concept that lets the code settle the argument.
Sample Answer
“When my tech lead and I disagreed on database architecture, I suggested we each build a proof-of-concept and benchmark them against our actual query patterns. His approach was faster for writes, mine for reads. Our workload was 80% reads. The data decided. No ego, no hierarchy — just benchmarks. We went with my approach and he contributed the write-optimization layer.”
“What tools and technologies are you most proficient with?”
Do your skills match our stack? And can you learn what you don't know?
Listing every technology you've ever touched. Nobody believes a resume with 40 technologies.
Tier your skills: Expert (could teach a course), Proficient (ship production code daily), and Familiar (have used in projects, would need ramp-up time).
Sample Answer
“Expert: Python, PostgreSQL, AWS — I've been shipping production systems in these for 6+ years. Proficient: TypeScript, React, Docker — I use these weekly and can move fast. Familiar: Go, Kubernetes, Terraform — I've used them in projects and could ramp up in a few weeks. I'd rather be honest about my tiers than pretend I'm an expert in everything.”
“How do you approach code reviews?”
Are you collaborative? Do you mentor or tear people down? Do you care about quality?
Being either a rubber-stamper or a nitpicker. Both are toxic.
Show that you review for correctness, clarity, and maintainability — and that you frame feedback as questions, not commands.
Sample Answer
“I focus on three things: does it work correctly, will the next person understand it, and does it create tech debt? I always start with what I like about the PR — it's not about ego, it's about creating psychological safety so people actually listen to the critique. I phrase feedback as questions: 'What if we extracted this into a helper?' rather than 'Extract this.' It lands differently.”
“Describe your debugging process.”
Are you systematic or do you change random things until it works?
Saying 'I Google it.' Everyone Googles it. Show me the process AROUND the Googling.
Check logs + Reproduce + Binary search the problem space + Fix + Add tests to prevent regression.
Sample Answer
“Step one: read the error message. Sounds obvious, but most people skip it. Step two: reproduce locally. Step three: binary search — I comment out half the system until I isolate which half contains the bug, then repeat. Step four: fix it. Step five: write a test that would have caught it. The test is more important than the fix, because the fix solves today's problem. The test solves tomorrow's.”
“How do you prioritize technical debt?”
Can you balance speed and quality? Do you understand business context?
Either ignoring debt entirely ('we'll fix it later' — you won't) or refusing to ship until everything is perfect.
Quantify the cost of the debt in engineering hours, incident frequency, or velocity impact. Then compare to the cost of fixing it.
Sample Answer
“I maintain a tech debt register with estimated impact — hours lost per month, incidents caused, velocity drag. When debt costs more than the sprint it would take to fix, it goes on the roadmap. I present it to product in their language: 'This debt costs us 2 features per quarter.' That framing gets prioritized faster than 'the code is messy.'”
“Tell me about a system you designed from scratch.”
Can you think architecturally? Do you consider scale, reliability, and maintainability?
Overcomplicating it. The best architectures are boringly simple.
Requirements + Constraints + Options Considered + Decision Rationale + What You'd Change With Hindsight.
Sample Answer
“I designed our event-driven notification system. Requirements: 10M notifications per day, under 500ms delivery, multi-channel (email, push, SMS). I chose a message queue architecture with Kafka because we needed replay capability and ordering guarantees. The key decision was making notifications idempotent — so if anything failed, we could safely retry. It's been running for 18 months at 99.97% uptime. If I rebuilt it today, I'd add better dead-letter queue handling.”
Culture Fit
#36-45They're evaluating whether you'll thrive or self-destruct in their specific environment. Honesty wins here.
“What motivates you?”
Will this role keep you engaged? Are you intrinsically or extrinsically motivated?
Saying 'money.' It might be true, but it's not what they want to hear. Also: 'making a difference' is too vague.
Be specific and genuine. Connect your motivation to something the role actually offers.
Sample Answer
“I'm motivated by shipping things that real people use. Not prototypes, not roadmap items — actual shipped products where I can watch usage metrics climb. There's a specific dopamine hit I get from seeing a feature I built handle 10x the traffic I expected. If the role involves shipping, I'm going to be deeply engaged. Desk research and strategy docs don't give me the same energy.”
“How do you handle feedback?”
Are you coachable? Will you improve or get defensive?
Saying 'I welcome all feedback.' Nobody welcomes ALL feedback. Show some honesty.
Acknowledge that feedback can sting, then show you have a process for absorbing and acting on it.
Sample Answer
“My first reaction to critical feedback is usually defensive — I think that's human. But I've trained myself to say 'thank you, let me think about that' instead of reacting in the moment. I go for a walk, sit with it for an hour, and nine times out of ten, the feedback was right. I keep a running doc of feedback I've received and what I've done about each piece. Accountability to myself.”
“Describe your ideal work environment.”
Will you thrive here or be miserable? Are our cultures compatible?
Describing a fantasy workplace. Be honest about what you need so neither of you wastes time.
Describe your genuine preferences, then tie them to being productive. Research their culture first so you can align naturally.
Sample Answer
“I do my best work in environments with high autonomy and clear ownership. I want to know what success looks like, and then I want the freedom to figure out how to get there. I love async communication for deep work and synchronous meetings for brainstorming. I'm not great in cultures where every decision needs five approvals — I move fast and I'm accountable for the outcomes.”
“How do you handle working with difficult people?”
Will you be the difficult person? Can you maintain professionalism regardless?
Saying you've never worked with a difficult person. That means either you've been incredibly lucky or you're the difficult one.
Show empathy (understand WHY they're difficult), boundaries (what you won't tolerate), and a specific example.
Sample Answer
“I had a colleague who was brilliant but combative in every meeting. Instead of avoiding him, I started having 1:1 coffee chats. Turns out he felt like leadership didn't value his expertise. Once I started asking for his input BEFORE meetings, he became my strongest ally. Most difficult people aren't difficult — they're frustrated. Address the frustration and the difficulty usually evaporates.”
“What's your management style? (or: How do you like to be managed?)”
Will you mesh with your future manager? Do you know yourself well enough to answer this?
Saying 'I'm flexible' without specifics. Everyone says that. Give them something real.
Describe your preferences with the caveat that you adapt. Mention what brings out your best AND your worst.
Sample Answer
“I thrive with a manager who sets clear goals and then gets out of the way. Weekly 1:1s for alignment, but not daily check-ins. I do my worst work when I'm micromanaged — I start second-guessing everything. But I also need direct feedback, not the kind wrapped in three compliments. Tell me straight and I'll fix it fast. I'd rather know where I stand than guess.”
“How do you handle work-life balance?”
Are you going to burn out in 6 months? Are you going to disappear at 4:59 PM every day?
Being dishonest in either direction. Don't pretend you work 80-hour weeks, and don't pretend you never check Slack after 5.
Show you're sustainable. The best answer demonstrates intensity during work hours and genuine recovery outside them.
Sample Answer
“I work intensely during my hours — deep focus blocks, no social media, aggressive prioritization. But I protect my evenings and weekends because I've learned the hard way that chronic overwork kills creativity before it kills productivity. I'll absolutely work a weekend during a launch or crisis, but that should be the exception, not the norm. Sustainable pace produces better work than heroics.”
“Tell me about a time you mentored someone.”
Do you invest in others, or are you purely focused on yourself?
Taking credit for their growth. The best mentorship stories make the mentee the hero.
Describe who you mentored, what you taught, and where they are now. Make THEM the protagonist.
Sample Answer
“I mentored a junior engineer who was technically strong but struggled to communicate in meetings. We did weekly mock presentations where I'd play difficult stakeholder. After three months, she presented our Q3 roadmap to the VP of Engineering — alone. She got promoted six months later. She's now a senior engineer at a FAANG company. I'm prouder of her career than half of my own accomplishments.”
“What are you passionate about outside of work?”
Are you a real person? Do you have depth beyond your resume?
Making it too work-related ('I'm passionate about code!'). Show genuine personality.
Be authentic. Pick something you actually care about and show WHY. Interesting people get hired over boring people at equivalent skill levels.
Sample Answer
“I'm obsessed with kitesurfing. There's something about harnessing wind to launch yourself 30 feet in the air that puts quarterly roadmaps in perspective. I also spend an embarrassing amount of time building mechanical keyboards. Neither of these things are on my resume, but they keep me curious, present, and willing to be a beginner — which I think makes me better at my actual job.”
“How do you handle ambiguity?”
Can you be productive without a perfect brief? Most startup/growth roles are 80% ambiguity.
Saying you love ambiguity. Nobody LOVES ambiguity. Show you're effective IN it.
Show your process for creating clarity: ask the right questions, define scope, set milestones, iterate.
Sample Answer
“I don't love ambiguity, but I'm effective in it. My process: first, I identify the three questions that would most reduce uncertainty and go find answers. Second, I define the smallest possible scope that delivers value. Third, I ship that and use the feedback to decide what's next. I've found that one week of building teaches you more than three weeks of planning when the problem is genuinely ambiguous.”
“What would your coworkers say about you?”
Do you have self-awareness? And will you repeat it honestly?
Only sharing the positive. Mixing in one constructive piece makes the whole answer more credible.
Share what you've ACTUALLY been told — ideally from recent performance reviews. Mix positive and constructive.
Sample Answer
“They'd say I'm the person who makes complicated things simple, and that I'm relentlessly direct — sometimes too direct. My last 360 review said I was the strongest cross-functional communicator on the team, but that I sometimes move so fast I don't bring people along for the journey. I've been working on that — slowing down to explain the 'why' before jumping to the 'what.'”
Closing Questions (Questions to Ask THEM)
#46-50The questions YOU should ask. This is your chance to interview THEM. Never, ever say "No, I think you covered everything."
“Do you have any questions for us?”
Are you thoughtful? Are you evaluating US as much as we're evaluating you?
Saying 'No, I think you covered everything.' This is the single worst answer in any interview.
Always have 3-5 questions prepared. Ask about the ROLE, the TEAM, and the COMPANY. Avoid questions about perks — you're not there yet.
Sample Answer
“Always say yes. Below are 10 questions that interviewers consistently say are impressive.”
“What does the first 90 days look like for someone in this role?”
(This is YOUR question to ask them.) You're signaling that you're already thinking about execution and onboarding.
Not asking this. It shows you're thinking beyond getting the offer.
Ask this in every interview. The answer tells you whether they have a plan for you or are hiring and hoping.
Sample Answer
“You're not asking for a syllabus — you're evaluating whether they've thought about your success. If they can't answer this, it's a yellow flag about organizational maturity.”
“What's the biggest challenge the team is facing right now?”
(YOUR question.) Signals you want to solve problems, not coast. Also reveals red flags.
Not asking this. You need to know what you're walking into.
This question does double duty: it makes you look engaged AND gives you intel about the role's reality.
Sample Answer
“Listen carefully to the answer. If they say 'scaling' or 'technical debt,' that's normal. If they say 'we're trying to figure out what this team actually does,' run.”
“How does the company measure success in this role?”
(YOUR question.) Shows you're outcome-oriented and want clear expectations.
Not asking this and then being surprised when your definition of success doesn't match theirs.
If they can't articulate success metrics, you'll never know if you're performing well. That's a problem.
Sample Answer
“The best companies will give you clear KPIs. If they say 'we'll figure it out together,' that can be fine for an early-stage startup, but concerning for a mature company. You want to know how the scorecard works before you sign up to play.”
“Is there anything about my background that gives you hesitation?”
(YOUR question.) This is the power move. Most candidates are too scared to ask it.
Not asking this. It gives you a chance to address objections BEFORE they discuss you without you in the room.
Ask this at the end of every final interview. If they have a concern, you can address it live. If they don't, you've just demonstrated supreme confidence.
Sample Answer
“This question catches interviewers off guard in the best way. If they say 'You don't have experience with X,' you can respond immediately: 'That's fair — here's how I'd ramp up on X based on my experience learning Y.' You've just turned a rejection into a conversation. Most candidates never get that chance because they never ask.”
10 Questions That Make Interviewers Say “Great Question”
These are the questions that separate forgettable candidates from memorable ones. Pick 3-5 for each interview.
“What does the first 90 days look like for someone in this role?”
Why it works: Shows you're already thinking about execution.
“What's the biggest challenge the team is facing right now?”
Why it works: Signals you want to solve problems, not coast.
“How does the company measure success in this role?”
Why it works: Shows you're outcome-oriented.
“What would make someone wildly successful vs. just okay in this role?”
Why it works: Reveals the unwritten expectations.
“Why is this role open? Is it new or a backfill?”
Why it works: Context about team stability and growth.
“What's the team's biggest recent win?”
Why it works: Reveals what they value and celebrate.
“How does feedback flow on this team?”
Why it works: Tells you about management culture.
“What's the most common reason people leave this team?”
Why it works: Brave question. Reveals red flags early.
“Where do you see the company in 3 years?”
Why it works: Shows long-term thinking and evaluates stability.
“Is there anything about my background that gives you hesitation?”
Why it works: The power move. Address objections live.
Glen's Take
Here's the thing nobody tells you about interviews: the person across the table is usually just as nervous as you are. They're terrified of making a bad hire. They have a boss breathing down their neck to fill the role. They've already interviewed 15 people who all blurred together.
Your job isn't to be perfect. It's to be memorable. And the way you become memorable is by being genuinely, uncomfortably honest. When you give a real answer instead of a polished one, the interviewer leans forward. When you admit a real weakness instead of a fake one, they trust you. When you ask “Is there anything about my background that gives you hesitation?” they remember you at 11 PM when they're deciding between you and the other finalist.
I've hired people who bombed technical questions because they showed me how they think. I've rejected people who aced every question because they felt rehearsed and hollow. The interview isn't a test. It's a conversation about whether you and this company are going to make each other better.
Prepare the frameworks. Practice out loud. Then walk in and be yourself — the version of yourself that's done the homework. That version is unstoppable.
Get Glen's Musings
Occasional thoughts on AI, Claude, investing, and building things. Free. No spam.
Unsubscribe anytime. I respect your inbox more than Congress respects property rights.
More From Glen
Level Up Your Interview Game
FAQ
What are the most common interview questions?
The most common interview questions include “Tell me about yourself,” “Why do you want this job?”, “What are your strengths and weaknesses?”, “Where do you see yourself in 5 years?”, and behavioral questions using the STAR method. Most interviews draw from about 50 standard questions across opening, behavioral, technical, culture fit, and closing categories.
How do you answer “Tell me about yourself” in an interview?
Use the 90-second pitch formula: start with your present role and a key accomplishment, briefly mention relevant background, and end with why you're interested in this specific role. Keep it under 90 seconds, focus on what's relevant to the job, and never start with your childhood or education.
What is the STAR method for interviews?
The STAR method is a framework for answering behavioral interview questions: Situation (set the scene briefly), Task (explain your specific responsibility), Action (describe what you did — be specific), and Result (quantify the outcome). It keeps your answers structured and prevents rambling.
How should you answer “What is your greatest weakness?”
Name a real weakness that isn't a dealbreaker for the role you're applying for, then explain what you're actively doing to improve. Never use disguised strengths like “I work too hard” — interviewers see through it immediately. The fix you describe matters more than the weakness itself.
What questions should you ask at the end of an interview?
Always ask questions. Strong options include: “What does the first 90 days look like?”, “What's the biggest challenge the team faces?”, “How does the company measure success in this role?”, and the power move: “Is there anything about my background that gives you hesitation?” Never say you have no questions.
Know someone who has an interview coming up?
Keep Exploring
Side Hustle Tier List
Every side hustle ranked from S-tier to F-tier. Some of these actually work.
Read moreBillionaire Daily Routines
What the richest people on earth actually do all day. The 5 AM thing is real.
Read moreWhich Billionaire Are You?
Take the quiz. Are you a Bezos, a Buffett, or a Zuckerberg?
Read moreBest Investing Books
The 25 books that will actually make you a better investor, ranked and reviewed.
Read more