Tell me about the most complex project you have led.

"Process is very inline with what is explained here and on youtube, prepare stories that fit the questions"

"Very smooth and clear, the recruiter laid down what the expectations are, and the coding interview was mostly leetcode medium level."

"Interviewer were assessing for the role, They were looking for control plane experience. My experience is been with data plane and they were not interested with after then"

"The interviews are easy/medium difficulty for an experienced engineer. The first coding round includes Java-related questions before moving on to an easy LeetCode-style problem. There is no virtual onsite; candidates are required to go to the office in San Francisco, and there are four rounds in total. The interviews are very friendly and feature relatively easy-to-solve problems."

"The interview consists of two parts: a 45 min LC style coding and 15 mins conversation on your prior projects. The 45 min question was to build an arithmetic evaluator. For that, you have to use the Shunting Yard algorithm. It was only "+", "-", "(" and ")". I'm not sure if we would have used more operators, maybe some with precedence, if I had gone further. I had a hard time understanding the interviewer. I learned later on from Chat that you should contact your recruiter immediately if this happens."

"The process was good. Scheduling was easy and automated. Recruiter was good in providing clear expectations of the different rounds. The technical interview - the technical lead wasn't impressive, seemed like they had a solution in mind, and would not be open to discussing different approaches."

"This was one of the hardest loops I had completed. The hiring manager screen and behavioral interviews were standard. The system design interview for a TPM was challenging. The expectations for a TPM included a great deal of technical depth."