Snowflake Interview Questions
& Process

I had two phone interview coding problem rounds. The first one, with a Chinese Professor, wasn't focused on the implementation but rather the problem-solving approach. The task was to guess a hidden number, and while it sounded like Binary Search, there was a twist: feedback on my guess wasn't immediate, only the result of the previous guess was given, making it a Delayed Binary Search. The second round, with a Caucasian Male, involved a very straightforward BFS problem. I'm not sure why I didn't pass; maybe it was a 'team match' issue or a subtle optimization they were looking for. The first round was a classic 'think-on-your-feet' brainteaser. A Delayed Binary Search typically requires wasting a move or managing two search intervals because the nth guess depends on the (n-1)th result, testing state handling and asynchronous feedback.

The last interview stage involved a mock cold call. The interviewer chose a prospect from LinkedIn and presented common objections like 'Why should I tell you that?' and 'I'm not sharing that' during the discovery phase. It was an interesting way to conduct a mock cold call for an interview. Given my nearly 10 years of experience, I found it easy to handle, but I won't be moving forward with this company. They don't seem to set candidates up for success, and I suspect entry-level candidates might struggle with this part.

First, there's a recruiter screening call for about 30 minutes to check your experience and see what role level fits. Then, a 30-minute chat with the hiring manager about your background, mostly scenario stuff and some tech talk. Stage 3 is a 90-minute technical architecture deep dive, where you'll do rapid-fire definitions of tech terms, then tackle an architecture exercise in 15 minutes, followed by more tech definition questions based on your exercise. After that, a 60-minute stakeholder role play where you present an architecture from a past project like you're talking to business stakeholders, and they'll ask you questions about communicating tech to non-tech people. Finally, an in-person leadership sync for 30 minutes with a Head of Department or Director.

The interview process was pretty simple and not too hard overall. The questions were mostly about my past experience, why I was interested in the role, and my general background. I talked to a few different people from various departments who explained what they do and how we'd work together across teams. Getting updates between interview rounds and the final response took more time than I expected.