For the aforementioned organization hierarchy, design thread-safe add/remove operations for users and groups. Propose an API and concurrency strategy (e.g., reader–writer locks, fine-grained locking, lock ordering to avoid deadlocks, or immutable snapshots with copy-on-write). Explain how to guarantee linearizable or at least read-consistent queries while updates occur, and how to handle long-running reads. Discuss contention hot spots, performance trade-offs, failure recovery, and how to test concurrency correctness (stress tests, race detection).

This question evaluates concurrent system and API design skills, focusing on thread-safety, atomic updates, consistency models, durability, deadlock avoidance, and testing of in-memory hierarchical user/group data structures.

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

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)

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)

Ensure thread-safe updates to org hierarchy

Quick Overview

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

Context

Task

Solution

Submit Your Answer to Earn 20XP

Ensure thread-safe updates to org hierarchy

Quick Overview

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

Context

Task

Solution

Submit Your Answer to Earn 20XP