6 ms·
I interviewed at Google for an SRE:Systems role around a month ago; I can share my anecdotes. The first interview put me in contact with a recruiter who would
by dijit 7y ago
I interviewed at Google for an SRE:Systems role around a month ago; I can share my anecdotes.
The first interview put me in contact with a recruiter who would basically be my guide throughout the process, at first he asked me some basic questions to feel out where I was weak and then told me to prepare those weaknesses for the next round.
The next round was 2 phone interviews, lasting about an hour each and over different days, one focused on my programming skills (of which, I have little because sysadmins don't typically do anything relating to data structures) and the second one was surrounding linux internals and debugging (which I was very strong on).
I spent roughly 2 working days worth of time preparing for them.
Preparing for the on-site was pleasant, I was put in touch with another google recruiter who ensured I knew where I was going and what I was doing, they told me that I'd be there the whole day and while they couldn't tell me what I would be asked/who I would meet/what to prepare; they gave me an approximation of the _kind_ of questions, very broadly.
I spent roughly 18 working days preparing in my weak areas, including leetcode/data structures and reading comp-sci papers (paxos and ilk).
On the day, I went through about 5, 1-hour long interviews that focused on various aspects of SRE (one of them being 'googliness'), some were about distributed systems (where the interviewer got hung up on the fact that I said I would use postgres instead of making my own database) and others were heavily programmer focused (linux internals was more about knowing the implementation of 'ls', scripting was all about the kinds of questions you get on leetcode).
I'm not going to lie, it was gruelling, and I'm typically pretty comfortable interviewing;
I thought I'd be fine with these interviews because I'm considered to be "shit hot" in sysadmin/writing glue by my peers, but I guess not, as I'm not a Google-SRE. :)
(sidenote: everything in TFA rings true, including the tips, google recruiters are quite transparent about your process. But they also said that the last stage is not the interview, it's roughly 5 hiring committees that are looking at your application "package" through different lenses)
- speedgoose 7y agoI would never dare to suggest writing a new database in a professional context, even less during an interview. Probably as a joke at the coffee machine because it's ridiculous but otherwise no. It's so many distributed databases around there, no one is better than one good PostgreSQL for the majority of uses cases.
- bauerd 7y agoGoogle's requirements differ. Also if the interview question was about distributed systems, "I'll just use Postgres" is not super constructive
- speedgoose 7y agoGoogle has good in-house database software that fit their requirements. I wouldn't say that I can do better in an interview.
- bauerd 7y agoYes but that in-house database software did not fall from sky. Google developers wrote it. Remember their interview process is generalised. Even for candidates not expected to implement databases, they test for the awareness of tradeoffs posed by distributed databases: read-after-write/eventual consistency, linearizability, how many masters /quorum/leader election, etc. "Just use Postgres" does not demonstrate any of that, it's not what the interviewer was after.
- speedgoose 7y agoThat's true. We don't know how was the interview, perhaps it was about implementing a distributed database from scratch, perhaps it was about storing as many personal data as you can.
- inkeddeveloper 7y agoI would hope the answer to "how would you write a distributed database from scratch" isn't "I'd use PostgreSQL." Actually, I'd probably do the same.
- lcfcjs2 7y agoNot sure I would agree with this. People who say PostgreSQL for everything haven't ever needed a use case of Big Data, or quickly searchable datasets.
- OhSoHumble 7y ago> (where the interviewer got hung up on the fact that I said I would use postgres instead of making my own database Huh? Google thinks it's valuable for their SREs to be hand-writing databases in place of industry standards? SREs specifically?
- bowmessage 7y agoThey were probably looking for something non-relational, not suggesting you write your own.
- dijit 7y agoThe exact message I got back was "Attempted to use magic software solution", so I believe they intended for me to say "some kind of relational" or "some kind of non-relational" database and maybe some key criterion about what kind of access pattern instead of me internalising the problem and pulling out a ready-made solution.
- username90 7y agoWhen I worked on the infrastructure parts of Google I worked on systems with millions of QPS, does PostgreSQL really handle that kind of load gracefully?
- dijit 7y agoPostgres was just one part; I was describing a sharding solution that was using Postgres as long term storage underneath with a memory-based distributed message queue for ingestion and sharded cache layer for egress. Sure, PostgreSQL scales relatively nicely on single nodes but I chose it because it has a write-ahead log, strong transaction isolation and b-tree indexing, which would have been useful given the question I had.
- username90 7y agoDid you put all the data in a single postgres? Since a million queries per second is more than postgres can handle. And if you don't put them all in one database then what is the point of postgres features like transactions or indexing? At least on the teams I saw people did these things in code, or they used a solution some other engineer at Google had written, I don't think there are any public databases which handles these things nicely without costing ridiculous amounts to run. So yes, writing a database is a part of the responsibilities a SWE at Google could be expected to handle. And this isn't some kind of special role, the people working on these things were normal L3-L5 engineers. Edit: Note that there were SRE's working on these things as well, infrastructure teams are often mixes of SWE's and SRE's and their roles overlap somewhat, sometimes SRE's builds entire things themselves because they understand the production environment better.
- asdfman123 7y agoTo be really good at those interviews you have to practice to be really good at those interviews. It takes a tremendous amount of time to get good enough that you can't possibly fail (especially for people like me, who are incapable of thinking clearly when they're asked to perform in front of others). My brother hires for a consulting firm and he was talking about how there really is a shortage of talent out there. That's true, but in an earlier era, companies would hire a bunch of people out of college and spend resources training them. I know there are a lot of intelligent people out there who would be more than capable of performing if the entry bar wasn't set so high. Unfortunately, I guess that model doesn't work in the era of job hopping.
- toomuchtodo 7y ago> My brother hires for a consulting firm and he was talking about how there really is a shortage of talent out there. Exceptional talent is rare. There's only a shortage if you're unreasonable. Lots of employers are some combination of apathetic, unreasonable, or plain ol' lazy. It costs them nothing to fish for talent for 6-12 months, accept hundreds of applications, and then complain when a unicorn didn't come along who was willing to take at or below market rate.
- ubercow13 7y agoOn the contrary that sounds quite expensive
- toomuchtodo 7y agoYou'd be surprised how many businesses survive in spite of themselves.
- ryandrake 7y agoAnytime somebody complains that there is a “shortage of talent” you need to immediately ask them 1. What level of talent they are looking for and 2. What level of compensation they are offering. Often the answers are 1. Top 25 percentile and 2. Bottom 25 percentile, so it’s no wonder they can’t find anyone.
- lppkabacaba 7y agoThe same things, but in august 2019. I spent about a month to prepare for the on-site. The sections time-limit was about 45 minutes(not the 1hour) Failed on one coding section and on Googliness. HR coordinator said that I've slightly below the acceptable hiring level. Also, the free seminars for NALSD finished the two weeks before my interview. Also, I heard that I have only two remaining attempts of on-site at Google
- dijit 7y ago> I have only two remaining attempts of on-site at Google LOL WAT. This is a good enough reason for me to stay away tbh. I did not hear this from my recruiter.
- lppkabacaba 7y agoIt was said "unofficially"