← Back to Directory

Atlassian

Large Enterprises

Most of these Atlassian write-ups come from Software Engineers (48), then Machine Learning Engineers (25). The most reported rounds are the technical phone screen (32), the system design round (31), the behavioral / leadership round (9) and the multi-round onsite (1).

73 interview notes · updated Jun 2026

Atlassian·Machine Learning Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round for an ML Engineer role at Atlassian. Just the one question about helping someone grow, which felt pretty standard but I still fumbled parts of it.
  • Tell me about a time you helped a teammate or peer improve. What gap did you spot, how did you address it, and what changed for them and the team afterward?

“I had a story ready but mid-answer I realized I was spending way too long on the gap and not enough on what actually happened after.”

View Post

Atlassian·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Interviewed for an ML Engineer role at Atlassian and got a sliding window question that felt more like a standard coding screen than anything ML-specific. Pretty straightforward round overall, nothing too surprising.
  • Design a MovingAverage class that takes a window size on initialization and, given a stream of integers, returns the average of the most recent N values each time a new value is added.

“Went with a queue and a running sum so I wouldn't have to recompute the whole window every call.”

View Post

Atlassian·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Atlassian for a software engineer role. The whole thing was one big distributed systems question about building an async web crawler service, and it went pretty deep into territory I wasn't fully prepared for.
  • Design a REST API service where clients submit URLs and the service crawls each URL plus all its sublinks to extract image references. The API should support submitting a batch of URLs and polling for job status and results.
  • How would you architect the crawler itself? Walk through the worker pool, the URL frontier/queue, and how you'd deduplicate already-visited URLs.
  • How would you handle polite crawling, including rate limiting per domain and respecting robots.txt?
  • How do you know when a crawl job is fully complete? Specifically, how do you detect that all sublinks have been discovered and processed?
  • How would you handle failures, retries, and timeouts in the crawler?
  • How would you store intermediate crawl state so the system can recover if a worker crashes mid-job?

“I got the basic shape of it pretty quickly: POST to create a job, GET to poll status, return discovered images once done.”

View Post

Atlassian·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Atlassian system design round that went deep into graph theory pretty fast. The problem started as a classic LCA question but then they kept piling on mutations and concurrency until it was a full distributed systems conversation. Walked away feeling like I'd held my own on maybe 70% of it.
  • Given an organization modeled as a DAG where employees can belong to multiple orgs and orgs can have multiple parent orgs, design a system to find the 'lowest common organization' of two employees.
  • How would you extend the LCO system to support live mutations like adding or removing employees, re-parenting orgs, and changing org memberships while still answering queries efficiently?
  • What are the consistency guarantees your system provides between writes and LCO reads, and how do you handle concurrent mutations?
  • Given your expected query-to-update ratio, which data structure or architectural approach wins, and why?

“I jumped straight to the tree-based LCA solution and the interviewer let me finish before pointing out this is a DAG, not a tree.”

View Post

Atlassian·Software Engineer·Technical Phone Screen

Jun 2026
Atlassian software engineer interview with a tree-based algorithm problem. The question was well-scoped but they pushed on complexity analysis pretty hard afterward.
  • Given a company org chart represented as a tree (departments as internal nodes, employees as leaves), find the deepest department that contains two given employees. Analyze the time and space complexity of your solution.

“I went with a recursive approach pretty quickly, basically a lowest common ancestor problem on a tree.”

View Post

Atlassian·Software Engineer·Technical Phone Screen

Jun 2026
Atlassian technical phone screen that built on a previous org-tree problem, this time throwing in multi-membership to make things messier. The follow-up nature of it meant I felt like I was playing catch-up the whole time.
  • You have the org-tree LCA problem, but now an employee can belong to multiple organizations at once. Given two employees, find the deepest organization that contains both of them, accounting for all memberships. Walk through how the data structure changes, how you'd compute ancestor sets, and how you'd find the deepest common org. What's the time and space complexity?

“The multi-membership twist genuinely tripped me up at first.”

View Post

Atlassian·Software Engineer·Technical Phone Screen

Jun 2026
Atlassian technical phone screen that built on a previous org hierarchy problem, pushing it into DAG territory. The added complexity of multiple parent orgs made the LCA problem a lot messier than the tree version.
  • Given an organization structure that is a DAG (each org can have multiple parents), and two employees each belonging to one or more orgs, find the lowest common ancestor organization that contains both employees.

“The tree version of this problem feels pretty approachable but the DAG twist genuinely changes things.”

View Post

Atlassian·Machine Learning Engineer·Onsite - System Design / Architecture

Jun 2026
Atlassian ML Engineer system design round focused entirely on building an intelligent ticket routing service, basically a Jira-flavored ML platform question. Pretty intense scope for a single session and I definitely underestimated how deep they wanted to go on the ML side.
  • Design a service that lets client companies submit bug tickets and automatically classifies and routes each ticket to the correct internal team. Walk through functional requirements, architecture, the ML model, and how you'd handle scaling and mis-routes.
  • What features would you use to train the classification model, and how would you handle cases where the model's confidence is low?
  • How would you track SLA compliance and surface status updates back to the submitting company?
  • How would you monitor the system in production and detect when the classification model starts degrading?

“This is a big one.”

View Post

Atlassian·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Atlassian ML engineer interview with a data structures question that had a pretty meaty follow-up attached. The core problem was straightforward but the weighted average extension is where things got interesting and where I probably could have done better.
  • Design a data structure that, given a window size N and a stream of incoming integers, returns the rolling average of the last N values after each new value arrives. Walk through the time complexity of your approach.
  • How would you modify the design if you wanted to give more weight to recent values? Compare an exponentially weighted moving average using a smoothing factor against a linearly decaying weight scheme, and discuss the trade-offs around memory, parameter sensitivity, and how each responds to sudden changes in the input.

“Pretty clean once you land on a circular buffer with a running sum.”

View Post

Atlassian·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Atlassian software engineer interview with a system design question focused on a content popularity tracker. Pretty classic design problem but the distributed scaling angle made it more interesting than I expected.
  • Design a system that tracks content popularity on a social media platform, supporting operations to increase a score, decrease a score, and retrieve the most popular content at any time. Walk through your data structure choices, time complexity trade-offs, and how you'd scale this across multiple servers.

“I went straight to a hash map plus a max-heap combo and felt pretty good about it until they pushed on the decrease operation.”

View Post

Atlassian interview FAQ

What rounds are in the Atlassian interview?

Candidates most often report a technical phone screen (32 write-ups), a system design round (31), a behavioral / leadership round (9) and a multi-round onsite (1).

What does the Atlassian technical phone screen cover?

Across 32 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (37 questions), Technical Trade-offs (25) and System Design (16).

What is asked in the Atlassian system design round?

Across 31 system design write-ups, the most tagged question topics are System Design (65 questions), Technical Trade-offs (52) and Data Modeling (18).

Atlassian interview guides by role

48 notes

Atlassian Software Engineer interview questions

25 notes

Atlassian Machine Learning Engineer interview questions