Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
ExperiencesCoaching
New
Practice
Mock InterviewsTimed interview simulations with feedbackSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Get started

Slack MVP under Time Constraint

HardSystem Design00:00
Practice interviewer
In session
5 left
00:00

Your question is Slack MVP under Time Constraint. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Design Slack, with a constraint of delivering an MVP within 2 weeks; discuss message-delivery scalability and reliability.

Asked in the system_design stage as a one-hour main-loop system design interview. The reported follow-up focused on how to achieve message-delivery scalability and reliability.

Address:

  1. Clarify message, channel, workspace, and delivery requirements.
  2. Propose an MVP architecture and identify what you would defer.
  3. Explain message ordering, deduplication, retries, and delivery semantics.
  4. Design for failures across clients, brokers, databases, and notification providers.
  5. Define observability, capacity planning, and a safe rollout plan.

Discuss the tradeoffs between direct fanout and brokered delivery, push versus pull synchronization, and strong versus eventual consistency. If proposing ML, explain why it belongs in the MVP and how it would be isolated from the critical delivery path.