771–780 of 969 posts
Clearly he know's much more about the questions than the interviewer but he's mistaken the nature of the interview.
This really is a preliminary phone screen and he should have recognised the interviewers lack of experience early and just played the game.
I'd be be tempted to not go ahead with him just for his lack of emotional intelligence.
Earlier quoted context omitted.
https://en.wikipedia.org/wiki/Apophasis
Do you really think there's no such thing as a simple observation without intent? I'm not allowed to find it odd that a Web site about a Web server operated by the same Web server went down under a Web load, and remark upon it yet stop short of drawing or stating a conclusion because I don't have all the facts? How many times do I have to say that I have no intent, here? Apply Occam and cui bono . I don't even bloody…
Earlier quoted context omitted.
> "Could you write out what an HTTP request and response looks like on the board?" Why should anyone remember what an http request or response should look like? Statically typed vs. dynamically typed language? Fuck. Are these entry-level positions or for someone with 10 years work-ex? A simple search on Google can tell anyone the answer of these questions, why do you expect people to carry an imprint of it in their m…
That's a preposterous attitude. Just imagine if we took a similar approach to hiring for other kinds of jobs: "OK, so you'd like to work here as a mechanic. What's the difference between automatic and manual transmission?" "It's not fair to expect me to know that off the top of my head. If I need to know, I'll just do a Google search."
You're gonna have a hard time drawing a comparison between a line of work where you build things and one where you fix things.
Earlier quoted context omitted.
> "Could you write out what an HTTP request and response looks like on the board?" Why should anyone remember what an http request or response should look like? Statically typed vs. dynamically typed language? Fuck. Are these entry-level positions or for someone with 10 years work-ex? A simple search on Google can tell anyone the answer of these questions, why do you expect people to carry an imprint of it in their m…
Static versus dynamic typing is so fundamental that I don't see how a programmer could be remotely competent without having been exposed to those concepts enough to have internalized them. It would be like an accountant not knowing what the number 4 is. Yes, you can look it up, but if you need to then how did you ever get this far?
And then your non-engineer phone screener who's expecting the answer to match the scripted sheet will conclude that I don't know this "fundamental" thing and thus am unqualified.
Site's down?
ctrl-f for "down" next time :P
Is this for real? Does Google really hire interviewers that stupid? The list of questions is really dated. They're all pre-1990. The answers are dated, too. A Linux inode is the file system's representation of the base info of a file, from which the file's data blocks can be found. It also carries file metadata, but its real function is as the root of the file's block index tree. The format depends on the file system…
In terms of algorithmic time complexity, it is O(1)
Earlier quoted context omitted.
A civil engineer is a professional engineer. I would assume your father is a certified PE [1]. This rubbish flies in our industry since we are not professional engineers. [1]: https://en.wikipedia.org/wiki/Principles_and_Practice_of_Eng...
Nonsense. It's because your industry is relatively new and hasn't established the same institutions.
> Nonsense.
s/\./:
I had the exact same questions (apparently for SRE-SWE prescreen), but a slightly more intelligent recruiter (who had actually chased me for 2 years before I agreed to interview, so they were a bit more invested than the OP's guy). I went on to a phone screen and then on-site interviews, and then the hiring committee. The HC decided that coding/algo was strong, but that they needed a stronger "signal" re system design, and to my surprise, scheduled me two more sys design interviews (I did a total of 7 on-sites). I prepared by reading all the Google, Facebook, and Amazon systems papers and did 6 mock interviews with Gainlo, where interviewers all gave pretty good feedback (which led me to believe I wasn't a total idiot). When I went to my final Google interviews, I thought I did pretty well except for a couple of TCP/IP questions related to checksums and congestion control. I found those odd because all the prep materials that recruiters sent me listed knowledge of TCP specifics as optional, and this isn't my area of expertise anyway.
Oddly, one of the interviewers also seemed surprised that I wasn't a TCP/IP guru (--I bet that now he's telling his buddies stories about a candidate who couldn't do the SRE equivalent of Fizzbuzz or something similar.)
A week later I get the rejection and a long survey containing a link to the job for which they applied on my behalf. It was an SRE position that required deep knowledge of TCP/IP and various other network protocols.
My actual areas of expertise (for the last 10 years) are 3D graphics and computational geometry.
Lesson learned: always check the description of the job that overly eager recruiters apply for on your behalf. Had I known, I would've studied all about TCP/IP and prepared for that level of detail. All that time I thought that I was applying for a general SWE track, and I simply expressed interest to be matched to teams specializing in infrastructure and distributed systems later.
Earlier quoted context omitted.
Could you explain how static typing makes less safe programs?
Static typing is basically a bunch of free type-based unit tests. You can write safer programs in dynamic languages, but you need to write and maintain a lot more tests.
Compare static with N tests, vs not static with N tests. In what case would the not static be safer?