Mid leveltech

Software Engineer
Interview Questions

Covering Google Software Engineer interview questions — Googleyness, coding rounds, and system design prep.. Free, no signup required.

10 questions ready

Q1
Describe a recent project where you had to optimize code performance. What tools or methods did you use to identify bottlenecks, and what was the measurable improvement?
Why they ask this:* They want to assess your hands-on experience with profiling, debugging, and optimization—critical skills for writing production-quality code at scale.
Q2
Walk us through how you would design a REST API endpoint for a feature you've recently built. What HTTP methods, status codes, and error handling would you include, and why?
Why they ask this:* This tests your understanding of API design principles, RESTful conventions, and practical experience building scalable backend services that integrate with frontend or third-party systems.
Q3
Tell us about a time you had to refactor legacy code or work with an unfamiliar codebase. What was your approach, and how did you ensure you didn't introduce bugs?
Why they ask this:* Mid-level engineers frequently inherit or maintain existing code; they're evaluating your ability to navigate complexity, write tests, and make safe improvements under uncertainty.
Q4
How do you decide whether to use caching in your application, and what caching strategies have you implemented? What trade-offs did you consider?
Q5
Describe a situation where you disagreed with a senior engineer's technical approach. What did you do, and what was the outcome?
Q6
Tell us about a project deadline you missed or a feature that shipped with bugs. What happened, what did you learn, and how did you prevent it from happening again?
Q7
Give an example of when you had to mentor a junior engineer or help a teammate unblock themselves. How did you approach it, and what was the result?
Q8
What would you do if you discovered that a critical production bug was caused by code you wrote three sprints ago, and it has been affecting customers for days without anyone noticing until now?
Q9
How would you handle a situation where the product roadmap requires a feature that you believe is architecturally flawed and will create technical debt, but leadership is pushing for a quick release?
Q10
What would you do if a team member frequently ships code without adequate testing or documentation, slowing down code reviews and creating maintenance burden for the rest of the team?
🔒

7 questions locked

Upgrade to unlock all 10 questions with answer guides, videos & PDF

Upgrade to unlock →

Want questions tailored to a specific company?

Try the full generator →