Typical Recruiter screen -> technical phone screen -> onsite loop. Overall my experience was just ok, some good, some bad. 1) Recruiter screen - nothing special, but overall the recruiters weren't very good. Their emails were always short and cryptic, they took a long time to get back with feedback at every step of the process, and in the end didn't give me any feedback about why I was rejected. 2) Techincal phone screen - One problem that you can solve in the language of your choice. It's a bit confusing if you do it in Java, I had to ask a number of questions to get clarification on how exactly the code they provide works. I still got it done, it's about LeetCode Easy/Medium difficulty. But it's not a problem you'll find on leetcode, just a simple json serialization question that requires recursion and some careful string building. 3) Virtual on-site (during COVID lockdown) - three technical rounds and one behavioral round a) algorithm round - they asked a very common LeetCode design type question. I had done this one many times before and burned right through it. I even implemented it two different ways. b) system design - this one was interesting, the prompt for the problem is quite lengthy (not just "design a X") and you have to communicate with the interviewer quite a bit. I had fun and the interviewer was easy to talk to. c) coding/design hybrid - this one was strange. It's hard to know what exactly to focus on here (and if you ask, the interviewer won't point you in a certain direction). You basically do a simple system design and then write pseudocode to implement the APIs for it. I had to write a bit of SQL as well. This was the interview I wasn't sure I did good on or not, they don't do a good job of setting expectations for this one. After the on-site, they took 2+ weeks to get back to me with a decision, but ultimately it was no. I thought I did well, and they didn't give me any reason for saying no. Sometimes you just get unlucky.

Basic process was what you'd expect from most Bay Area technology companies, although my process happened to be for a remote position. 1. Recruiter chat / phone screen: I chatted briefly with a recruiter about what I might be looking for in a new role, what I had done, the usual. Just don't act like a crazy person and you'll be fine. 2. Technical phone screen: Done via video, and used something similar to Coderpad, so you'll have syntax highlighting and even Vim emulation if you want it. The interviewer asked me about my background and then proceeded to do a technical question, and expand on it a bit if you have time. The question here was pretty simple, all things considered. 3. Onsite: Set up a time to fly out to SF, and interviewed with 3 engineers and the hiring manager over lunch. One thing to note that's neat is there's a coffee bar behind reception, and it's pretty good coffee for free. First interview was focused on systems design. Lunch was mostly a time to ask about the current projects/challenges they're facing. The catering was pretty good! The second technical interview, after lunch, was focused on coding. Up to this point, the questions were pretty reasonable. Certainly harder than the phone screen, but doable. The final interview was more of a blend of both systems design and coding, and was slated to take an hour and a half, and boy did it. I think it'd be helpful to clarify a little more at the outset where you want to end up with this one, since I got focused on specific issues from time to time and it turned out that wasn't what the interview wanted to focus on. That ended up wasting some time that I probably didn't want to waste considering the scope of the question. I spoke with the recruiter briefly at the end, where they'll likely ask about compensation expectations. Make sure to have a number in mind before you walk in, even if you aren't planning on disclosing it. I was given an offer about 4 days after the on-site, which I ended up declining in favor of another offer with a better compensation package. I thought the culture was generally good, and I enjoyed speaking with folks there. The whole process took around a month, but that could be compressed if you're trying to move quickly. I was in the process of coordinating with several companies, which ended up making it take a little longer than it would have normally.