← Back to Directory

Atlassian interview notes, page 1 of 11

Large Enterprises

Most of these Atlassian write-ups come from Software Engineers (60), then Machine Learning Engineers (28) and Data Scientists (12). The most reported rounds are the technical phone screen (45), the system design round (38), the behavioral / leadership round (10) and the onsite coding round (3).

104 interview notes · updated Aug 2026

Atlassian·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Coding round for an ML Engineer role at Atlassian. One algorithmic question, a tricky LCA variant, and it was more involved than the classic version I'd practiced.
  • Given the root of a binary tree and two node values p and q, return their lowest common ancestor only if both nodes actually exist in the tree. If either is missing, return null.

“This is LC 1644, the nastier sibling of the standard LCA problem.”

View Post

Atlassian·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Atlassian software engineer round with a text justification problem. Pretty implementation-heavy, more about getting all the edge cases right than any clever algorithm.
  • Given an array of words and a max line width, format the words into fully justified lines where each line is exactly maxWidth characters. Extra spaces are distributed evenly between words, with left gaps getting more if it doesn't divide evenly. The last line is left-justified with trailing spaces.

“Took me a while to get all the cases sorted out.”

View Post

Atlassian·Software Engineer·Technical Phone Screen

Apr 2026
Atlassian SWE interview with a scheduling problem that looks deceptively simple until you realize they want the actual court assignments, not just the count. Pretty classic interval scheduling territory but with an extra layer.
  • Given a list of tennis court bookings (each with an id, start time, and end time), assign each booking to a court so no two bookings on the same court overlap, using the fewest courts possible. Return the full assignment of booking to court.

“I knew meeting-rooms II but for a second I started going down the path of just counting the max overlaps and forgot they wanted the actual mapping back.”

View Post

Atlassian·Software Engineer·Technical Phone Screen

Apr 2026
Atlassian software engineer screen, one coding question, pretty straightforward. Nothing that'll keep you up at night.
  • Given two strings s and t, write a function to check whether s is a subsequence of t.

“Two pointers, scan both strings once, done.”

View Post

Atlassian·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Atlassian for a software engineer role, focused entirely on capacity planning for a logging and analytics pipeline. Pretty technical and open-ended, more back-of-envelope math than I expected.
  • You own a logging and analytics pipeline. Walk through how you'd estimate the storage needed one year from now, covering ingest rate, growth assumptions, retention tiers, compression, replication, indexing overhead, and spike buffers. Give a rough number and explain how you'd validate and revisit it.

“This was the whole interview basically.”

View Post

Atlassian·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Atlassian for a software engineer role. The whole thing was one massive question about kiosk infrastructure at global scale, and it went deep fast. Walked away feeling like I covered maybe 60% of what they were actually probing for.
  • Design a system for refilling game cards at 125,000 physical kiosks worldwide, supporting both credit card and cash payments. Cover the kiosk-to-backend protocol, offline mode during network outages, idempotency for refill transactions, payment authorization and reconciliation, cash handling with audit trail, fraud and chargeback handling, software update distribution, fleet monitoring and alerting, and capacity/hot-shard concerns. Also discuss failure modes: double-charges, lost refills, kiosk compromise, and network partitions.

“This was a beast.”

View Post

Atlassian·Software Engineer·Technical Phone Screen

Apr 2026
Atlassian software engineer round with a graph/connection tracking problem. Pretty straightforward premise but the implementation details are where things get interesting.
  • You're given a stream of bidirectional connection and disconnection events between users. After processing the full stream, return two groups: users with fewer than N connections, and users with N or more connections. Only include users who appeared in at least one event.

“My first instinct was to just count connections as a number per user, which works until you realize disconnects can happen and you need to avoid double-counting.”

View Post

Atlassian·Software Engineer·Technical Phone Screen

Apr 2026
Atlassian coding round, one tree problem the whole time. Felt manageable until I started second-guessing my base cases mid-interview.
  • Given a binary tree root and two target node references, find the lowest common ancestor of the two nodes. Make sure to handle edge cases like null nodes, a target that doesn't exist in the tree, a single-node tree, and the case where both targets are the same node.

“I knew the standard recursive approach going in, propagate a found-flag or the node itself back up the tree.”

View Post

Atlassian·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Atlassian for a software engineering role. Just the one question but they really wanted the full story, not a quick answer.
  • Tell me about a time you were a mentor or a mentee. Walk through the context, the goals, what actions were taken, what challenges came up, and what both people got out of it. What did you take away about giving or receiving guidance?

“I went with a mentee story because I figured it'd be easier to show growth from my side.”

View Post

Atlassian·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Atlassian for a software engineer role, focused entirely on load balancing for a collaborative document service. The question had a lot of layers and I felt like I was playing catch-up the whole time.
  • You have a document-sharing service where requests are load balanced using round-robin across a stateless app tier. What problems does this cause for a collaborative editing workload?
  • How would you fix the issues you identified with round-robin routing for this kind of workload? Walk through your solutions.

“I started with cache locality which felt safe, but then they kept pushing and I realized there were like four other angles I hadn't touched.”

View Post