Earlier quoted context omitted.
I had a disastrous phone interview this week throughout which I remained calm and focused but immediately after putting the phone down I emailed the recruiter to say I wasn't interested. The "Technical" part was just trivia. Never-mind that I was sat in front of a computer and could have googled everything asked, I chose not to do that. So yes, I stumbled when asked "what does the using keyword do". I explained how i…
The first Google phone screen for SRE candidates is so scripted that you can probably Google the questions and get exact answers. It's been years since I've had it, but I remember it being the exact same questions, about UNIX internals and TCP/IP. This type of recruiting seriously turns me off because you can tell they're hiring minimum wage call center workers to read a script and filter out the 9/10 candidates that…
The follow up phone interviews are what really matters (before the onsite of course) with actual engineers and go more in-depth with coding questions (among other things) at least.
I remember my recruiter was a really knowledgeable guy and he knew his stuff even though he wasn't an engineer. We had a nice chat and he was able to keep up with my (basic, obviously) responses of how TCP works, how to implement inode-based filesystems or whatever information you can read out of a stat call... Nothing too fancy but still it didn't sound like rehearsed script to me.