0

How to prepare for Staff Software engineer Role - L6 @ (Google)

Profile picture
Senior Software Engineer at Taro Community4 months ago

I am already working as an SDE3 in a mid-size tech company with 10 YOE, I have recently applied to a Staff-SE Role at Google, and have been contacted by the recruiter,

Now I am not sure what to study, I interviewed twice with Google around 4 years back, but that time they contacted me for L4, and I wasn't able to clear the coding rounds both times. I think I am a good Software engineer, it is just that, solving these Leetcode problems is not my cup of tea. And to be honest, with my current workload and other responsibilities, grinding leetcode feels not worth the effort.

So now I am clueless, would they still ask the same kind of coding questions even for Staff role, or how to go about preparation?

429
2

Discussion

(2 comments)
  • 2
    Profile picture
    Tech Lead/Manager at Meta, Pinterest, Kosei
    4 months ago

    Interestingly, as you become more senior, the emphasis on DSA/Leetcode problems goes down.

    Imagine the extreme case of interviewing for a Distinguished Engineer role. Someone interviewing for this role has probably built some huge industry-changing infrastructure or a new programming language. It would be silly to ask them to reverse a linked list šŸ˜… The entire interview would be some bespoke process.

    However, as a Staff Engineer, you'll still have some DSA questions. Perhaps not as much as a new grad, but you should still prepare for it.

  • 0
    Profile picture
    Tech Lead @ Robinhood, Meta, Course Hero
    4 months ago

    I feel you, but you're definitely going to get LeetCode problems in your Google interview. Google/Meta have been notorious for DSA-heavy interviews for the past 15 years, and it's still the case (Meta E6 loop has DSA too).

    It's on my backlog to convert this into a much higher-quality course, but this should still help a lot: [Masterclass] How To Ace Your Big Tech Interview - Data Structures And Algorithms

    For Staff, it's also important to deeply understand Staff behavior and work backwards from that to show the corresponding signals. Behavioral interviews are a big part of that (check out the leveling section): [Course] Master The Behavioral Interview As A Software Engineer