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

Card Delivery System Design

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

Your question is Card Delivery System Design. 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 Card Delivery System.

Asked in the system design stage. Described as a typical system design round.

Explain how you would design an end-to-end system for Revolut card delivery, including delivery-time prediction, carrier or service selection, and status prioritization. Clarify the requirements you need, estimate scale, and describe the data, model-serving, and monitoring architecture. Address online versus batch processing, latency and availability, delayed feedback, feature drift, training-serving skew, and operational failure modes. Discuss how you would evaluate the system offline and through controlled production experiments. Keep the design practical and explain the tradeoffs behind your choices.