The interview process was pretty straightforward.

• Phone Screen
• Code Screen
• Onsite (Virtual)

One of the onsite sessions involved writing a pseudo-API for a construct they use often in their applications (I don't want to give it away).

The interviewer for that session seemed engaged for the first 15-20 minutes of that portion. Then, he had his mic on mute, looking at his other monitor for the rest of the session.

At the end, he said the code I wrote (which was rough around the edges, in my opinion) was okay and not to worry about the details, even though we had 10-15 minutes left.

The rest of the interview consisted of technical/system level design questions, which I thought I did okay on (?).

Most interviewers were pleasant. The hiring manager was a little short and spoke very quickly, but seemed very intelligent.

Recruiter syncs at the end were appreciated, as opposed to ghosting after a quick turnaround. They offered feedback, but the feedback given was more along the lines of, "Well, you probably know what you failed on." (This was not the recruiter's fault; they go off of information the team provides them).

Disclaimer: I didn't have much experience with caching/content delivery professionally before applying for the job.

Q: Why do you want the position?

Q: TCP v.s. UDP

Q: Basic Caching Algorithms