I have an onsite with Google for SWE-SRE, 2.5yoe in 2 weeks. (Also, this was direct, no PS) I was told I'll have 3 coding rounds, 1 system design and the last one I'd have to pick between: a) Troubleshooting b) UNIX/Linux internals Questions: 1. I've mentioned my background below - what should I pick? 2. What technical knowledge does Troubleshooting cover? Networking and Linux CLI observability tools? Would I have to prepare very differently for this than OS internals? 3. Any concise book or resource suggestions for both? Background: I have some basic experience troubleshooting production issues (app runtimes, memory, disk IO, network IO, thread contention, and a basic idea of what exists out there, I.e. many known unknowns), but not very academic knowledge. For OS internals, my knowledge is a lot more academic, and I'd have to prep a lot to be competent. Current TC: 0 (masters student) [LeetCode prep is going well, please don't suggest that]
I did 4 coding rounds for new grad SWE, headcount was full so being considered for SWE-SRE but apparently as I’ve learned fairly recently even the SRE org is having headcount issue so I haven’t received an offer after passing HC long ago :/ , kinda sucks
SRE is a small org. What makes you think it will have more HC?
fair enough , that was my initial impression too but why keep candidates in the pool then if there is no future possibility of an offer ? I mean the only other thing recruiter could have in mind is let’s keep them waiting until next headcount refresh , google is known for its slow process anyway
I did all coding. I don’t think you have to pick one, ask the recruiter.
Swap the Troubleshooting/Internals round for a coding round. I did that and ended up getting an offer last month. I know of a friend who’s much smarter than me, ended up doing troubleshooting and a bit of negative feedback affected her HC result. If you’re not totally comfortable with troubleshooting or internals, swap it.
Thanks! 4 coding + 1 system design, so when will networking questions be asked? They will cover that, won't they?
Nope. Didn’t cover that at all
Thanks folks, I'll see if I can swap this out for coding.
Hmm I interviewed for SWE track in SRE as well and got 5 coding rounds... not sure if my track was different from SWE-SRE?
I was told 4 coding + 1 system is SWE track, And 3 coding + 1 system + 1 option is SWE-SRE track. I really don't know what these tracks imply beyond 'title'
SWE-SRE are hired as “SWE” so they can transfer to any other SWE project trivially. SE-SRE will do interviews & ladder transfer.
Anyone have any details on the SE track interview? What type of Linux internal questions are covered?
Suggest you to go from 3 coding interviews to 4. This is what I did
Oh - I had a feeling he mentioned that option. At the end I was under the impression that SWE-SREs HAD to pick one of OS internals or Troubleshooting - are you saying I have the option not to?
Yes