3 ms·

I am emphatically not saying you shouldn't tailor your technical questions to your audience. Commits to the kernel can be prime-facie evidence that someone can

I am emphatically not saying you shouldn't tailor your technical questions to your audience. Commits to the kernel can be prime-facie evidence that someone can code. A good shell script can be the same. I have no degree. I don't write code for a living. I'm actually almost precisely the opposite of the stereotype of the stuck up software engineer, aside from being a white dude in my early thirties. What I am saying is: I have met many people who can configure a database, but cannot talk to developers as equals about how to write code about it, and there's really an interesting split of reasons why that doesn't work. The fact remains that it doesn't. You can build operations teams for some tasks, and you should - you can't run your own large hardware or compute or database clusters without having some entirely operations focused people. You should not ignore their opinions or pain points. You shouldn't call them SRE, though. The point of SRE is to build systems and run them, and you want them to have feet on either side of that line.

zaptheimpaler 5y ago
I understand and agree - im sorry i don't mean to attack you personally, its more of a satire about FAANG interview processes. My first comment was responding to the quote about difficulties hiring SREs at Google and their interview process in particular (the quote in the parent comment came from Google). It wasn't intended to be read as a position one way or the other on any and all coding questions or interviews - I don't think there are any simple black and white rules there. The text justification question is listed somewhere on leetcode as being commonly asked by Google and is a bit more involved than a simple leftpad or "do you know how to code" sort of question.
- GauntletWizard 5y ago
  Apropos of nothing, I went and did that leetcode problem - Getting the algorithm took me about 10 minutes, figuring out how I'd messed up my fenceposting took another 25, and figuring out what they wanted for the last line took me about an hour. Ugh.

zaptheimpaler 5y ago

I understand and agree - im sorry i don't mean to attack you personally, its more of a satire about FAANG interview processes. My first comment was responding to the quote about difficulties hiring SREs at Google and their interview process in particular (the quote in the parent comment came from Google). It wasn't intended to be read as a position one way or the other on any and all coding questions or interviews - I don't think there are any simple black and white rules there. The text justification question is listed somewhere on leetcode as being commonly asked by Google and is a bit more involved than a simple leftpad or "do you know how to code" sort of question.

GauntletWizard 5y ago
Apropos of nothing, I went and did that leetcode problem - Getting the algorithm took me about 10 minutes, figuring out how I'd messed up my fenceposting took another 25, and figuring out what they wanted for the last line took me about an hour. Ugh.