4 ms·

So how much of that stuff do you actually do day-to-day?

by mnd999 6y ago

cbanek 6y ago
Yeah seriously, it seems like a lot of the questions revolve around the TCP stack. Maybe it was a more networking type job?
- Lammy 6y ago
  Companies like Google have hundreds of thousands of machines and nothing they do will ever run on just one box. I can see why they'd select for networking knowledge.
- pansa2 6y ago
  It doesn’t seem unreasonable for an SRE position. Presumably the focus of the interview would be quite different if you were applying to work on, say, V8 or the Go compiler.
itronitron 6y ago
Apparently Google SREs spend a lot of time watching the clock.
- fzeroracer 6y ago
  The irony of the clock brain teaser is that it operates on two assumptions. One being that the person asked has experience with analog clocks (which, given that it's 2020 has become less relevant) and the second being that said clock behaves according to standard specifications. If the clock was instead a jump hour clock for example, then that tosses the trickery out of the window. Which is really what that brain teaser is about; testing that your cultural understanding of how an analog clock functions is correct.
  - jrockway 6y ago
    I think getting the correct answer in code is easier than solving the "trick question" about 3:15. If I were the interviewer here, I would make sure the candidate states their assumptions and that the code they wrote follows those assumptions. You can make the hour hand stick right at the number for the entire hour, or you can have it smoothly sweep as the minutes (or seconds) increase. I would not care and consider both to be reasonable interpretations (but I've never seen a clock that sticks at the hours; it is harder to implement in hardware). I honestly wouldn't even ask this question because it's too simple. It's two divisions, a subtraction, and then a modulo 360. It is awkward when your interview question only takes 5 minutes and you have to awkwardly fill 55 minutes with follow up questions ("and how would you test that?").
praptak 6y ago
Ranging from none to "whatever you happen to know about this stuff is not enough". Quickly building mental models for unknown stuff is the top skill. I'm afraid nobody even tries to assess this in the interviews.

So how much of that stuff do you actually do day-to-day?

by mnd999 6y ago

So how much of that stuff do you actually do day-to-day?

Yeah seriously, it seems like a lot of the questions revolve around the TCP stack. Maybe it was a more networking type job?

Lammy 6y ago
Companies like Google have hundreds of thousands of machines and nothing they do will ever run on just one box. I can see why they'd select for networking knowledge.
pansa2 6y ago
It doesn’t seem unreasonable for an SRE position. Presumably the focus of the interview would be quite different if you were applying to work on, say, V8 or the Go compiler.

itronitron 6y ago

Apparently Google SREs spend a lot of time watching the clock.

fzeroracer 6y ago
The irony of the clock brain teaser is that it operates on two assumptions. One being that the person asked has experience with analog clocks (which, given that it's 2020 has become less relevant) and the second being that said clock behaves according to standard specifications. If the clock was instead a jump hour clock for example, then that tosses the trickery out of the window. Which is really what that brain teaser is about; testing that your cultural understanding of how an analog clock functions is correct.
- jrockway 6y ago
  I think getting the correct answer in code is easier than solving the "trick question" about 3:15. If I were the interviewer here, I would make sure the candidate states their assumptions and that the code they wrote follows those assumptions. You can make the hour hand stick right at the number for the entire hour, or you can have it smoothly sweep as the minutes (or seconds) increase. I would not care and consider both to be reasonable interpretations (but I've never seen a clock that sticks at the hours; it is harder to implement in hardware). I honestly wouldn't even ask this question because it's too simple. It's two divisions, a subtraction, and then a modulo 360. It is awkward when your interview question only takes 5 minutes and you have to awkwardly fill 55 minutes with follow up questions ("and how would you test that?").

praptak 6y ago

Ranging from none to "whatever you happen to know about this stuff is not enough". Quickly building mental models for unknown stuff is the top skill. I'm afraid nobody even tries to assess this in the interviews.