Intervu is in beta — feedback welcome at support@intervu.io

Google Senior Software Engineer Interview Questions

6 real practice questions for the senior-level Senior Software Engineer role at Google (Technology), spanning behavioral, technical, system design, and leadership. Lead technical projects and mentor junior engineers. The first 3 questions below include what Google interviewers actually listen for, plus likely follow-ups.

Questions
6
Categories
Behavioral (2), Technical (2), System Design (1), Leadership (1)
Difficulty mix
2 medium · 4 hard
Avg. answer time
~4 min

Behavioral Questions (2)

  1. 1.Tell me about a technical decision you made that you later regretted. What did you learn?

    hard~3 min

    What interviewers look for

    • Honest acknowledgment of the mistake
    • Shows ownership and accountability
    • Explains what they learned from it
    • Describes how they apply that learning now
    • Shows humility and growth mindset

    Likely follow-ups

    • How did you communicate the mistake to stakeholders?
    • How do you make technical decisions differently now?

    Company context

    At Google, intellectual humility is valued. The best engineers learn from their mistakes.

  2. 2.Describe a time when you led a technical initiative that required buy-in from multiple teams.

    hard~3 min

    What interviewers look for

    • Shows ability to influence without authority
    • Demonstrates clear communication of technical vision
    • Handled objections and concerns effectively
    • Achieved alignment and successful execution
    • Built consensus across different perspectives

    Likely follow-ups

    • How did you handle teams that were initially resistant?
    • What would you do differently next time?

Technical Questions (2)

  1. 3.Implement LRU Cache with O(1) get and put operations. Explain your design choices.

    medium~3 min

    What interviewers look for

    • Uses hash map + doubly linked list combination
    • Correctly implements get and put with O(1) time
    • Handles edge cases (capacity 0, duplicate keys)
    • Clean, readable code structure
    • Discusses thread-safety considerations

    Likely follow-ups

    • How would you make this thread-safe?
    • How would you implement LFU (Least Frequently Used) instead?
  2. 4.How would you design a global-scale distributed database?

    hard~4 min

System Design Questions (1)

  1. 5.Design a real-time collaborative document editing system like Google Docs.

    hard~5 min

Leadership Questions (1)

  1. 6.Tell me about a time when you had to make a trade-off between shipping quickly and code quality.

    medium~3 min

More Google interview questions