SaaS & dev tools · Sydney, Australia

Atlassian.

Jira, Confluence, Bitbucket, Trello and Loom, multi-tenant collaboration tools on Atlassian's cloud platform.

its questions lean on

rate limiting
cross-product platform services
crawling
multi-tenancy
clean extensible code

The rounds, as candidates describe them

Third-party screen (Karat)About 20 minutes of short system design scenario questions, then 30 minutes of coding.source ↗
Data structuresA practical data-structures problem with scale and multithreading follow-ups.source ↗
Code designWorking, extensible code for a design problem; the rate limiter is the common one.source ↗
System designA high-level design round.source ↗
Managerial and valuesA management round and an Atlassian values round, both able to change the level or the outcome.source ↗

Reported by candidates

From public interview write-ups; each links its source.

Design a Rate Limiter (LLD)Low-level design
LLD-03 · Design a Rate Limiter →IP-02 · Design a Rate Limiter →reported in:LeetCode Discuss · Atlassian Senior SWE, code design round, offer (2025) ↗LeetCode Discuss · Atlassian P4/SDE2, offer (2022) ↗LeetCode Discuss · Atlassian SDE 2 P4 Bangalore, offer (2021) ↗
Design a Tagging SystemSystem design
W09 · DAY 01 · Tenant Isolation Strategies →W07 · DAY 02 · Indexing Pipeline →W01 · DAY 04 · Hot Keys and Skew →reported in:LeetCode Discuss · Atlassian P50, tags management HLD (2025) ↗LeetCode Discuss · Atlassian Senior SWE Bengaluru, tags shared by Jira and Confluence (2024) ↗LeetCode Discuss · Atlassian P6 Sydney (2023) ↗
Design a Web CrawlerSystem design
IP-05 · Design a Web Crawler →W02 · DAY 05 · Distributed Cron & Job Scheduling →reported in:LeetCode Discuss · Atlassian Senior SWE, web scraper for nested URLs and images (2025) ↗LeetCode Discuss · Atlassian P6 Sydney (2023) ↗LeetCode Discuss · Atlassian Senior Backend (Node) (2022) ↗
Design a Distributed Job SchedulerSystem design
IP-17 · Design a Distributed Job Scheduler →W02 · DAY 05 · Distributed Cron & Job Scheduling →reported in:LeetCode Discuss · Atlassian Principal Engineer Bangalore (2024) ↗
Design a Snake GameLow-level design
no lesson for this one yetreported in:LeetCode Discuss · Atlassian P50, LLD round (2025) ↗LeetCode Discuss · Atlassian SDE-2 P4 Bengaluru, offer (2022) ↗
Design a Voting and Ranking SystemLow-level design
IP-14 · Design a Real-Time Leaderboard →reported in:LeetCode Discuss · Atlassian Senior Engineer P5, rank teams (2024) ↗LeetCode Discuss · Atlassian SSE P5, votes and ranking (2022) ↗
Design a URL RouterLow-level design
no lesson for this one yetreported in:LeetCode Discuss · Atlassian Senior Backend (Node), code design round (2022) ↗
What problems does consistent hashing leave unsolved?Concept
W01 · DAY 01 · Partitioning Deep-Dive →W01 · DAY 04 · Hot Keys and Skew →reported in:LeetCode Discuss · Atlassian Senior SWE, Karat scenario question (2025) ↗
What changes when you take a production app beyond one country?Concept
W09 · DAY 03 · Data Residency and GDPR →W01 · DAY 02 · Replication Trade-offs →reported in:LeetCode Discuss · Atlassian Senior SWE, Karat scenario question (2025) ↗

Likely, from what they build

Our pick, not a report: questions that fit Atlassian's products.

Design a Multi-Tenant SaaS PlatformSystem design
W09 · BOSS · Design a Multi-Tenant Enterprise SaaS Platform →W09 · DAY 01 · Tenant Isolation Strategies →W09 · DAY 02 · Noisy Neighbor Prevention →
Design Webhook DeliverySystem design
W02 · DAY 04 · Webhook Delivery System →W03 · DAY 04 · Dead Letters and Poison Pills →
Design a Collaborative EditorSystem design
SQ-20 · Google Docs Collaboration →W05 · DAY 04 · Conflict Resolution →
Design a Notification SystemSystem design
IP-06 · Design a Notification System →W06 · DAY 03 · Real-Time Channels: WebSockets and SSE at Scale →

Study path

Every lesson the questions above point to, once, in order.

Company names and logos are trademarks of their owners, shown only to identify each company. This course isn't affiliated with or endorsed by any of them.