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 Technical Screen rounds at Atlassian.

What role is this question designed for?

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

Ensure thread-safe updates to org hierarchy | Atlassian Interview Question

Quick Overview

Ensure thread-safe updates to org hierarchy evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Ensure thread-safe updates to org hierarchy

Thread-safe Organization Hierarchy: API, Concurrency, and Consistency

Context

You are building an in-memory organization directory that manages groups (hierarchical) and users. Multiple threads will concurrently read and mutate the hierarchy. The workload is read-heavy with periodic updates.

Assume:

Groups form a tree (or forest) identified by stable IDs; groups can have child groups.
Users have unique IDs and can be members of multiple groups.
The service runs in a single process but must be crash-safe via durable storage.

Task

Design thread-safe add/remove operations for users and groups.

Propose a minimal API for:
- Creating/deleting users and groups
- Adding/removing a user to/from a group
- Moving a group under a new parent
- Querying users, groups, and memberships
Propose a concurrency strategy (e.g., reader–writer locks, fine-grained locking with lock ordering, immutable snapshots with copy-on-write, or MVCC/RCU). Specify:
- How writes occur atomically
- How readers are isolated from in-progress writes
- Deadlock avoidance strategy (if using locks)
Consistency guarantees:
- How to guarantee linearizable writes (or at least read-consistent snapshots) while updates occur
- How to serve long-running reads without blocking writers
Discuss:
- Contention hot spots and performance trade-offs of your approach
- Failure recovery (durability model, recovery steps)
- How to test concurrency correctness (stress tests, race detection, linearizability/snapshot checks)

Constraints & Assumptions

Preserve the scope, facts, inputs, and requested outputs from the prompt above.
If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.
Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

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?

Quick Overview

Context

Assume:

Groups form a tree (or forest) identified by stable IDs; groups can have child groups.

Users have unique IDs and can be members of multiple groups.

The service runs in a single process but must be crash-safe via durable storage.

Task

Design thread-safe add/remove operations for users and groups.

Propose a minimal API for:

Creating/deleting users and groups
Adding/removing a user to/from a group
Moving a group under a new parent
Querying users, groups, and memberships

Propose a concurrency strategy (e.g., reader–writer locks, fine-grained locking with lock ordering, immutable snapshots with copy-on-write, or MVCC/RCU). Specify:

How writes occur atomically
How readers are isolated from in-progress writes
Deadlock avoidance strategy (if using locks)

Consistency guarantees:

How to guarantee linearizable writes (or at least read-consistent snapshots) while updates occur
How to serve long-running reads without blocking writers

Discuss:

Contention hot spots and performance trade-offs of your approach
Failure recovery (durability model, recovery steps)
How to test concurrency correctness (stress tests, race detection, linearizability/snapshot checks)

Constraints & Assumptions

Preserve the scope, facts, inputs, and requested outputs from the prompt above.

If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.

Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

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?

Ensure thread-safe updates to org hierarchy

Quick Overview

Ensure thread-safe updates to org hierarchy

Ensure thread-safe updates to org hierarchy

Thread-safe Organization Hierarchy: API, Concurrency, and Consistency

Context

Task

Constraints & Assumptions

Clarifying Questions to Ask Guidance

What a Strong Answer Covers Guidance

Follow-up Questions Guidance

Submit Your Answer to Earn 20XP

Ensure thread-safe updates to org hierarchy

Quick Overview

Ensure thread-safe updates to org hierarchy

Ensure thread-safe updates to org hierarchy

Thread-safe Organization Hierarchy: API, Concurrency, and Consistency

Context

Task

Constraints & Assumptions

Clarifying Questions to Ask Guidance

What a Strong Answer Covers Guidance

Follow-up Questions Guidance

Submit Your Answer to Earn 20XP