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

Billing Module for AWS Storage

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

Your question is Billing Module for AWS Storage. 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 a billing module: users on AWS get cloud storage by subscription, extra storage auto-allocated when exceeded, usage logs written every 15 minutes to a DB, and the billing module parses logs per user id and sends data to AWS billing.

Asked in the Technical 2 stage.

Explain the deterministic billing path and identify where ML could safely assist, such as detecting anomalous usage or forecasting capacity, without changing billable usage without validation.

  1. Clarify requirements and data contracts.
  2. Design ingestion, aggregation, idempotency, and retry handling.
  3. Size storage and processing using the known 15-minute logging interval, stating missing assumptions.
  4. Propose offline and online ML components, if appropriate.
  5. Define evaluation, monitoring, drift detection, and failure recovery.