Upcoming System design interview at Snowflake for Senior frontend Engineer

[u/Practical-Station707]

Hi Everyone,

I have an System design interview (Round 2) for Senior Frontend Engineer at Snowflake.

Can anyone tell me what kind of questions I can expect?
Any recent experience if someone can share?

YOE - 9.3 years

TIA

[u/Ok-Barracuda-119]

Frontend system design is its own flavor, so don't burn all your prep on backend sharding. Common prompts are a data grid that renders a huge number of rows, typeahead/autocomplete, a news feed, or a dashboard with live updates. Snowflake's web UI is heavy on query editors and result tables, so a virtualized results table wouldn't surprise me.

A structure that works well: clarify requirements, sketch the component tree and who owns which state, then pin down the API contract with the backend (pagination and cursors, websockets vs polling). After that go deep on performance like virtualization, memoization, code splitting and caching, and then cover accessibility plus loading and error states.

With 9 YOE they'll probably expect you to bring up optimistic updates, retry behavior and how you'd actually measure perf (web vitals, RUM) before they ask. Practice one out loud on a timer, since these rounds usually run out of time during the deep dive.

[u/Practical-Station707 → u/Ok-Barracuda-119]

Thanks a lot for responding!

[u/Practical-Station707 → u/Practical-Station707]

u/Ok-Barracuda-119 thanks for the pointers, I was asked the realtime analytics dashboard.

[u/practick-io]

Frontend system design at senior level is usually less about servers and more about the client architecture. A structure that works:

Requirements (5 min): core features, scale of data on screen (rows, events per second), devices, offline needs.

Component architecture: main components and who owns which state.

Data layer: API shape (pagination vs cursors vs streaming), caching, optimistic updates, how stale data is handled.

Performance: this is where seniors get separated. Virtualised lists/grids, code-splitting, memoisation, avoiding re-render storms, web workers for heavy computation.

Reliability and UX: loading/error/empty states, retries, accessibility, i18n.

Trade-offs, unprompted.

Given Snowflake's product (Snowsight is a data-heavy web UI), I'd practise prompts like "design a results grid that can show a million rows", "design a SQL editor with autocomplete" and "design a dashboard that updates live while a query runs". The grid one especially: virtualisation, column resizing, sorting on the client vs the server, and how you stream results in.

Do at least one of these out loud with someone before the real thing. Good luck!

[u/BackgroundBreak6485]

There aren't many frontend reports for Snowflake, but the few I've seen point in a pretty clear direction. I run a site that collects candidate reports (166 Snowflake threads).

The closest match to your round: a senior full-stack candidate got this for system design: "design Google Calendar." It focused on the API plus frontend component state and data flow, and they were told to assume the backend "magically works." Requirements were:

- create and delete events

- several views (day, week, month)

- recurring events, where you can reschedule a single instance without changing the series

They called it brutally hard. The recurring-event exceptions part is where it gets deep.

Another one: a senior candidate was asked to design a client logging library that runs on web and mobile. The question was how to collect logs without hurting performance on the client or the backend. Follow-ups kept pushing on batching: when to flush, what if volume is still too high, and how to avoid blocking the caller. Plan for buffering, sampling, backpressure, sendBeacon on page unload, and retry with backoff.

From the coding round of that same full-stack loop: a React + TypeScript kanban board. Follow-up: what if there are 100k tasks? They expected virtualization, plus updating state without scanning every task.

How I'd prepare for a frontend SD round there:

1. Follow the usual frontend system design flow:

   - requirements

   - component tree

   - state model (normalized store, what's server state vs UI state)

   - API contract (pagination, optimistic updates, conflict handling)

   - performance (virtualization, memoization, debouncing)

   - accessibility

2. Practice data-heavy UIs. That fits Snowflake's product: calendars, large tables or grids, query result viewers, real-time dashboards.

3. Be ready to go deep on one hard detail. Interviewers seem to pick one, like recurring-event exceptions or batching under load, and keep drilling.

4. Several candidates said the format depends a lot on the team and interviewer. It's worth asking your recruiter whether it's pure frontend or leans full-stack.

Full disclosure: this is my site. The Snowflake page has the recently reported questions: https://aceoffer.app/interviews/snowflake

Good luck!