Design analytical tracking database

Quick Overview

This interview question evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer for Design analytical tracking database states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Design analytical tracking database

Company: Axon

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Technical Screen

##### Question Design an analytical database for tracking user actions—search item, view item page, login, add to cart, view cart, purchase, view order—so it can efficiently answer pre-written queries such as: How many users from Asia viewed item A this month? What are the three highest-value orders at present? Describe schema, event model, and data flow.

Overview: This interview question evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer for Design analytical tracking database states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

|Home/System Design/Axon
Axon logo
Axon
Aug 4, 2025
mediumSoftware EngineerTechnical ScreenSystem Design
26
0

Design analytical tracking database

Design an Analytical Database for User Actions

Context

You are building an analytics data store to track user behavior and commerce events so that product and business teams can run reliable, fast queries. Assume web and mobile clients emit events at scale (millions/day). Latency target for analytics is minutes, not milliseconds.

Events to Track

  • login
  • search_item
  • view_item
  • add_to_cart
  • view_cart
  • purchase
  • view_order

Example Queries to Support

  1. How many users from Asia viewed item A this month?
  2. What are the three highest-value orders at present?

Task

Describe the schema, event model, and data flow for an analytical database that can efficiently answer the above and similar pre-written queries.

Clarifying Questions to Ask Guidance

  • Clarify users, core use cases, read/write patterns, scale, latency, availability, and data retention.
  • State explicit assumptions before making sizing or architecture decisions.
  • Prioritize the functional path first, then address reliability, security, observability, and rollout.

What a Strong Answer Covers Guidance

  • A scoped requirements summary with concrete non-goals and success metrics.
  • API, data model, architecture, consistency, capacity, and operations.
  • Reasoned trade-offs among simple and scalable designs, including bottlenecks and failure modes.
  • A validation, monitoring, migration, and launch plan appropriate for the risk level.

Follow-up Questions Guidance

  • What breaks first at 10x traffic or data volume?
  • How would you degrade gracefully during dependency failures?
  • What metrics and alerts would prove the design is healthy after launch?

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Axon•More Software Engineer•Axon Software Engineer•Axon System Design•Software Engineer System Design