Common Interview Questions
Master these frequently asked interview questions with proven frameworks. Each question includes why it's asked, how to structure your answer, and example responses.
1. Tell Me About Yourself
Why They Ask: This is usually the opening question. They want a quick overview of your background and to see if you can communicate clearly and concisely.
The Framework
Structure your answer chronologically, starting from education and moving forward:
- Education (5-10 seconds)
- First relevant experience (15-20 seconds)
- Subsequent experiences (15-20 seconds each)
- Current situation and why you're here (10 seconds)
Total time: 60-90 seconds maximum
The Script
"Well, as you can see from my resume, [go through your background chronologically, hitting key points]... and that's what brings me here today, and why I'm excited to learn more about this opportunity."
Example Answer
"Well, as you can see from my resume, I graduated from UC Berkeley with a degree in Computer Science in 2018. After graduation, I joined a startup called TechCo as a junior developer, where I worked primarily on their mobile app using React Native. After two years there, I moved to BigCompany as a mid-level engineer, where I've been for the past three years working on backend services using Node.js and Python, focusing on payment processing systems. I'm looking for my next challenge where I can take on more technical leadership, and that's what brings me here today and why I'm excited to learn more about this opportunity."
- Keep it concise - This is not your life story
- Focus on relevant experience - Skip jobs unrelated to the position
- End with why you're there - Connect your background to this opportunity
- Practice it - This should sound natural, not rehearsed
2. Tell Me About Your Projects
Why They Ask: They want to understand the depth and complexity of your work, your technical skills, and your ability to explain technical concepts.
The Framework
For each project, use the STAR method:
- Situation - What was the context?
- Task - What was the goal?
- Action - What did YOU do?
- Result - What was the outcome?
Example Answer
"One project I'm particularly proud of is a real-time analytics dashboard I built at my current company. We had a situation where our sales team was making decisions based on day-old data, which was causing us to miss opportunities. I was tasked with creating a real-time dashboard that would pull data from multiple sources. I designed and implemented a solution using React for the frontend and a Node.js backend with WebSockets for real-time updates, pulling data from our PostgreSQL database and external APIs. The result was that our sales team could now see customer activity in real-time, which led to a 30% increase in conversion rates."
What to Emphasize
- Your specific role - Use "I" not "we" (be clear about your contribution)
- Technical decisions - Why did you choose those technologies?
- Measurable results - Numbers make impact clear
- Challenges overcome - Shows problem-solving ability
Don't describe a team project without clarifying YOUR specific contribution. Interviewers want to know what YOU did, not what your team did.
3. What Are Your Salary Expectations?
Why They Ask: To determine if you're within their budget and to see if you know your market value.
The Strategy: Deflect → Ask → Wide Range
This is a three-step process. Each step is used only if the previous one doesn't work.
Response 1: Request More Details
"I need to know quite a bit more about the details of the role before I can give you an accurate answer. I'd like to get more of a feel for the culture, the team structure, and the specific responsibilities before discussing compensation."
Goal: Get them to provide more information and delay the salary discussion until you have an offer.
Response 2: Ask for Their Range
If they press you, flip it back to them:
"I understand. Could you share the approved salary range for this position? That would help me understand if we're in the same ballpark."
If they give you a range:
"That range would work fine for me."
(Even if the low end is your target, say this. You can negotiate later when you have an offer.)
Response 3: Give a Wide Range
If they absolutely insist on a number and won't share their range:
"Based on my experience and the market for this type of role, I'd be looking at something between $120,000 and $180,000 annually, depending on the full compensation package including benefits, equity, and growth opportunities."
Make your range wide enough that:
- The bottom is acceptable to you
- The top is ambitious but not ridiculous
- You leave room for negotiation
Whoever mentions a number first typically has less negotiating power. Try to get them to show their cards first. If you must give a range, go wide.
Details You Might Need to Know
If they ask what details you need, mention:
- Official job hours and flexibility
- Overtime expectations
- Remote work policy
- Travel requirements
- Benefits package
- Equity/stock options
- Bonus structure
- Professional development budget
4. Why Should We Hire You?
Why They Ask: They want to see if you understand the role and can articulate how you meet their needs.
The Framework
- Show enthusiasm - Start with energy
- Restate their needs - Show you understand what they're looking for
- Match requirements to your experience - Go down the list
- (Optional) Express desire - Show you want to work there specifically
The Script
"I was hoping you'd ask me that! As I understand it, you're looking for somebody who [list their requirements].
[Go through each requirement and explain how you meet it]:
- You mentioned you need someone with X years of experience - I have Y years working with [specific technology]
- You're looking for expertise in [skill] - I've been doing that for Z years at [company]
- You need someone who can [responsibility] - At my current role, I [specific example]
[Optional closing]:
And honestly, I've always wanted to work at an organization like this because [specific reason], so I'm really hoping you'll select me."
Example Answer
"I'm glad you asked! As I understand it, you're looking for somebody who has strong backend development experience, can work with microservices, and has led technical projects.
First, I have 5 years of backend development experience, primarily with Node.js and Python, which aligns with your stack. Second, I've spent the last two years specifically working on microservices architecture, breaking down monoliths and designing distributed systems. And third, I've led three major technical projects at my current company, including mentoring junior developers.
Plus, I've been following [Company's] work in [specific area] for a while now, and the chance to contribute to that mission is really exciting to me. That's why I'm hoping you'll select me."
Generic answers like "I'm a hard worker" or "I'm passionate" don't differentiate you. Specific examples of how you meet their stated requirements do.
5. What Is Your Weakness?
Why They Ask: They want to see if you're self-aware and honest, but they're also checking if you have any deal-breaker flaws.
The Strategy: Strength Disguised as Weakness
Pick a "weakness" that is actually a strength taken too far, then explain how you've learned to manage it.
The Framework
- The "Weakness" (A Strength) - "I have very high standards"
- The Temporary Problem - "Unfortunately not everyone shares those standards, which can sometimes lead to frustration"
- The Fix - "But I've learned to use good communication to smooth that over so it's not a problem"
Example Answers
For Code Quality:
"I would say I'm really particular about code quality and best practices. I'm very thorough in PR reviews and don't let things slip by. Sometimes this can lead to longer review cycles or friction with teammates who might not share the same attention to detail. But I've learned to communicate my feedback constructively and explain the reasoning behind my suggestions, which has turned it into a teaching moment rather than a point of conflict."
For Thoroughness:
"I tend to be very thorough and detail-oriented, which means I sometimes spend more time than necessary on tasks, especially in the planning phase. I want to make sure I've considered all edge cases. I've gotten better at this by setting time-boxes for planning and checking in with my team to make sure I'm not over-engineering solutions."
For High Standards:
"I have very high standards for the work I produce, and unfortunately not everyone shares those same standards. This can occasionally lead to a bit of frustration when I see work that doesn't meet the quality bar I expect. But I've learned to use good communication to address this - I'll have conversations about our quality standards and why they matter, and I'll offer to pair program or mentor team members who need help meeting those standards."
What NOT to Say
❌ Real weaknesses that are deal-breakers:
- "I'm not good with deadlines"
- "I struggle with communication"
- "I don't like testing my code"
- "I have trouble working with others"
❌ Fake weaknesses:
- "I'm a perfectionist" (too cliché)
- "I work too hard" (sounds insincere)
Good thing + minor negative consequence + how you fix it = Perfect weakness answer
6. Why Did You Leave Your Last Job? / Why Do You Want to Leave?
Why They Ask: They're checking for red flags. Were you fired? Do you have problems with coworkers? Are you going to have the same issues here?
The Golden Rule
Never speak negatively about anyone or anything. Stay positive and forward-focused.
The Framework
- Express gratitude for your current/previous role
- Focus on growth and future (what you want, not what you're leaving)
- Connect to this opportunity (why this role is the right next step)
The Script
"I'm very grateful for the opportunities I've had at [Current Company] and have learned a great deal. I've reached a point in my career where I'm ready for greater challenges and a broader scope of responsibilities.
When I saw the description for this role, it was a perfect match for my desire to move into [Specific Area] and apply my skills in [Specific Requirement], which is exactly what I'm looking for.
I'm particularly excited about the chance to work with a leader in the industry like your company, as I believe my experience in [Key Skill] would immediately contribute to the goals of the [New Team]."
Example Answers
If You're Looking for Growth:
"I've been at StartupCo for three years and I've grown a lot there - I went from junior developer to mid-level engineer. But we're a small team of 5 engineers, and I've hit a ceiling in terms of technical mentorship and complex challenges. I'm looking for an opportunity to work on larger-scale distributed systems and learn from senior engineers, which is what attracted me to this role."
If You Were Laid Off:
"Unfortunately, my company went through a restructuring and my entire department was eliminated. It wasn't performance-related - they were shutting down that product line. While it was disappointing, I'm grateful for the experience I gained there, and I'm excited to bring those skills to a more stable organization like yours where I can contribute long-term."
If You're Looking for Better Tech Stack:
"I've really enjoyed my time at CurrentCo, but the technology stack is becoming outdated - we're still on legacy systems that aren't widely used in the industry anymore. I'm looking for a role where I can work with modern technologies like the ones you're using here, which will help me grow as an engineer and stay current in the field."
What NOT to Say
❌ Negative reasons:
- "My boss is terrible"
- "The company is toxic"
- "My coworkers are incompetent"
- "They don't pay enough"
- "The work is boring"
Even if these things are true, keep them to yourself. The interviewer will wonder if you'll say the same things about them someday.
- Instead of "My boss micromanages" → "I'm looking for more autonomy"
- Instead of "The work is boring" → "I'm seeking more challenging problems"
- Instead of "Bad company culture" → "I want to work somewhere with strong collaboration"
7. Where Do You See Yourself in 5 Years?
Why They Ask: They want to know if you have career goals, if those goals align with this role, and if you're likely to stay with the company.
The Strategy: Brief Answer + Redirect
Give a quick, reasonable answer, then flip it back to them with a question about the company.
The Script
"I expect to be advancing based on my job performance and likely taking on some new responsibilities."
[Immediately pivot to asking them]:
"Actually, do you mind me asking where you see this company going in the future?"
Alternative Questions to Ask
- "What are the long-term plans for this department?"
- "What does the growth path typically look like for someone in this role?"
- "Where do you see the industry heading in the next few years?"
- "What are the opportunities for advancement at [Company]?"
Why This Works
- Shows you're reasonable - Not overly ambitious or unrealistic
- Shows you're thinking about growth - You want to advance, not stagnate
- Gets them talking - People love talking about their company/industry
- Takes pressure off you - Redirects the conversation away from you
Example Expanded Answer (If They Press)
"In five years, I see myself as a senior or lead engineer, likely with some mentorship or technical leadership responsibilities. I want to deepen my technical expertise while also helping to guide architectural decisions and mentor junior developers. But honestly, I'm more focused on finding the right fit where I can grow and contribute meaningfully. Where do you see this team evolving over the next few years?"
- ❌ "I want to be a manager" (if this is an IC role)
- ❌ "I want your job" (can seem threatening)
- ❌ "I don't know" (seems aimless)
- ❌ "I want to start my own company" (signals you won't stay long)
8. What Are Your Strengths?
Why They Ask: They want to hear you articulate why you're qualified. This is your chance to sell yourself.
The Strategy: Match Strengths to Job Requirements
Your "strengths" should be the exact things they listed in the job description.
The Framework
"My greatest strengths are the ways I satisfy your job requirements. Specifically:
[List their requirements and how you meet each one]"
Example Answer
"I'd say my greatest strengths align directly with what you're looking for in this role:
First, my 6 years of experience building scalable web applications - I've worked on systems serving millions of users.
Second, my expertise in React and Node.js, which is your primary stack. I've been working with both for 4+ years.
Third, my experience with cloud infrastructure, particularly AWS - I've designed and deployed microservices using ECS, Lambda, and RDS.
And fourth, my strong communication skills - I've led technical discussions with both engineers and non-technical stakeholders, which seems important for this role since you mentioned cross-functional collaboration."
Types of Strengths to Highlight
Technical Strengths:
- Years of experience with specific technologies
- Depth of knowledge in a particular area
- Breadth across full stack
- System design capabilities
Soft Skills (With Technical Context):
- Communication: "I can explain complex technical concepts to non-technical stakeholders"
- Problem-solving: "I'm skilled at debugging complex distributed systems issues"
- Leadership: "I've mentored 5 junior developers"
- Adaptability: "I've successfully learned new tech stacks on the job"
Don't just say "I'm a good communicator." Say "I'm skilled at writing clear technical documentation and have led architecture review sessions with 20+ engineers."
9. How Do You Handle Stress?
Why They Ask: They want to know if you'll crack under pressure or if you can stay productive during tight deadlines and challenging situations.
The Strategy: Quick and Confident
This is usually not a deep question. They just want assurance that stress won't be a problem.
Response 1: The Quick Answer (90% of the Time)
"Oh, I actually handle it very well."
That's it. Most interviewers will move on.
Response 2: If They Press for More (10% of the Time)
"A certain amount of stress is sometimes unavoidable in this industry, especially around releases or when dealing with production issues. But it's never been a problem for me in the past. I stay focused on solutions rather than dwelling on problems, and I prioritize effectively to tackle the most critical issues first."
Example Expanded Answer
"I handle stress pretty well. In my current role, we've had several high-pressure situations - production outages, tight deadlines, major releases. I've found that staying calm, breaking problems down into manageable pieces, and communicating clearly with my team helps keep things under control. For example, during a recent critical bug that was affecting customers, I was able to quickly isolate the issue, implement a fix, and coordinate the deployment with minimal impact."
What They Want to Hear
- ✅ You stay calm and focused
- ✅ You don't let stress affect your work quality
- ✅ You can prioritize effectively under pressure
- ✅ You've handled stressful situations before successfully
What NOT to Say
❌ "I don't really experience stress" (sounds unrealistic) ❌ "I cope by working longer hours" (suggests poor work-life balance) ❌ "Sometimes I get overwhelmed" (red flag) ❌ Detailed stories about being stressed (makes them think you can't handle it)
Don't over-explain. The more you talk about stress, the more it sounds like it might be a problem for you. A confident, brief answer is best.
Quick Reference: Question Summary
| Question | Key Strategy |
|---|---|
| Tell me about yourself | Chronological, 60-90 seconds, end with why you're here |
| Tell me about your projects | STAR method, emphasize YOUR role, quantify results |
| Salary expectations | Deflect → Ask their range → Wide range if pressed |
| Why should we hire you? | Show enthusiasm, restate needs, match your experience |
| What's your weakness? | Strength disguised as weakness + how you manage it |
| Why did you leave? | Grateful for past, focused on growth, excited about future |
| 5 years from now? | Brief answer about growth + redirect to them |
| What are your strengths? | Match exactly to job requirements |
| How do you handle stress? | "Very well" + brief example if pressed |