Deloitte · Primly Community

Deloitte senior system design interview: what to expect and how they differ from product company loops

mobile_mara · 4 replies

I've been on both sides of this. Interviewed at Deloitte a while back and have since talked to a bunch of people who went through it for senior and staff-equivalent roles in their tech practices. Here's the honest picture on system design.

First: Deloitte is not Google. The system design round (when it exists) is calibrated to consulting delivery context, not pure product-company scale problems. This surprises people coming from FAANG prep.

When system design actually shows up Not every loop has it. It's more common for: senior consultant (SWE equiv), manager-level tech roles, and specialist roles in cloud architecture or data engineering. Pure implementation roles may skip it entirely.

What they actually ask Expect pragmatic design questions. Not "design Twitter." More like: Design a document processing pipeline for a government agency How would you architect a reporting layer on top of a client's existing ERP Walk me through how you'd build a secure data ingestion pipeline for a healthcare client

They care about: security posture (data classification, access control), cloud provider knowledge (AWS, Azure, GCP), integration with legacy systems, and whether you think about the client's actual constraints.

What they don't care about (vs FAANG) Horizontal scaling to millions of QPS is not the core question. They're less interested in you knowing exactly what Kafka does at 10M msg/s and more interested in whether you can explain why you'd choose Kafka vs SQS vs a simpler queue given a client's existing stack.

How to prep If you're coming from a product company, dial back the scale obsession. Lead with requirements gathering, security considerations, and trade-offs given real-world constraints. Practice explaining architecture to a non-engineer. That actually comes up.

The interviewer is often a project manager or delivery lead sitting in alongside the tech lead. Your explanation needs to land for both audiences.

4 replies

sec_sasha

The security callout is accurate. Deloitte has a big federal/gov practice and security architecture shows up way more than people expect. If you're interviewing for anything in that practice, know your data classification basics, encryption at rest vs in transit, and the principle of least privilege. These aren't trick questions, they'll just ask them casually and expect a real answer.

director_dee

Good framing. One thing I'd add: the "explain to a non-engineer" point isn't hypothetical. I've sat in on Deloitte final rounds as a client and they literally assess how a candidate would communicate to stakeholders. If you go deep jargon with no translation, you're gone.

firsttime_mgr

This is the thing nobody tells you before you prep. I spent two weeks doing LeetCode hard and system design whiteboards and the actual interview was more about communication style than whether I could implement consistent hashing.

hardware_hugo

Coming from a non-software background, the Deloitte loop was honestly more navigable for me than some pure product company loops. The focus on pragmatic architecture and real constraints felt closer to how embedded systems design works. YMMV.