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
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess 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
Build my plan

System Design: Homework System

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

Your question is System Design: Homework System. 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

Homework system design: propose an architectural design and explain why you chose a specific tech stack and what factors you considered.

Asked in the Homework assignment stage. 2 system design questions in the take-home.

Prepare a practical design for an ML system of your choice. State assumptions before selecting components, and explain how the system would support data ingestion, training, evaluation, deployment, inference, monitoring, and iterative improvement.

Address the following:

  1. Define functional and non-functional requirements.
  2. Describe the offline data and training pipeline.
  3. Design the online serving path, including retrieval, ranking, or re-ranking where applicable.
  4. Justify the proposed technology stack and key alternatives.
  5. Explain evaluation, monitoring, failure handling, feature drift, and training-serving skew.

Do not assume a particular business domain. Make clear which scale, latency, availability, cost, and compliance assumptions your design requires.