How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a hard difficulty System Design question, commonly asked during Onsite rounds at Amazon.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Amazon during technical interviews.

Design a risk management ticketing system | Amazon Interview Question

Q: Design a risk management ticketing system

This question evaluates competency in system architecture, data modeling, access control and RBAC, idempotent API design, concurrency control, search and indexing, background job orchestration, and auditability for high-volume services.

Design a Risk Management Ticketing System

Context

You are designing a ticketing platform used by human users (analysts, managers, admins) and an automated risk-scanner bot. The system must support high volume, prevent duplicate tickets from automated sources, ensure safe concurrent updates, and provide auditability and reporting.

Requirements

Ticket lifecycle and states with valid transitions.
Role-based access control (RBAC) for humans and a bot role.
Idempotent ticket creation to avoid duplicates from the bot.
Concurrency control on updates.
Search and filtering across ticket attributes and free text.
Notifications (immediate and digest) to users.
Monthly reporting for users and managers.
Cover: storage schema, APIs, background jobs for report generation, audit trails, and scaling for high volume.

Deliverables

High-level architecture and components.
Data model/schema (relational core, search index, queues, caches).
API design, including idempotency and concurrency.
Lifecycle/state machine and RBAC model.
Background jobs for reporting, notification handling.
Auditability approach.
Scaling and reliability strategies.

Requirements

Ticket lifecycle and states with valid transitions.

Role-based access control (RBAC) for humans and a bot role.

Idempotent ticket creation to avoid duplicates from the bot.

Concurrency control on updates.

Search and filtering across ticket attributes and free text.

Notifications (immediate and digest) to users.

Monthly reporting for users and managers.

Cover: storage schema, APIs, background jobs for report generation, audit trails, and scaling for high volume.

Deliverables

High-level architecture and components.

Data model/schema (relational core, search index, queues, caches).

API design, including idempotency and concurrency.

Lifecycle/state machine and RBAC model.

Background jobs for reporting, notification handling.

Auditability approach.

Scaling and reliability strategies.

Design a risk management ticketing system

Quick Overview

Design a Risk Management Ticketing System

Context

Requirements

Deliverables

Solution

Submit Your Answer to Earn 20XP

Design a risk management ticketing system

Quick Overview

Design a Risk Management Ticketing System

Context

Requirements

Deliverables

Solution

Submit Your Answer to Earn 20XP