Atlassian

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·Software Engineer·Onsite - Multi Round

Jul 2026

Got an SDE intern offer from Atlassian for summer 2027 after three rounds: a tough OA, an AI-assisted coding session inside a live repo, and a values-based behavioral round with a senior engineer. The OA was the hardest part by far; the rest was more manageable than expected.

You're given access to an unfamiliar codebase in an IDE with an AI coding agent. Debug existing issues and implement new features using the agent.
Describe a situation where you demonstrated one of our company values.

“This was way less scary than it sounds.”

View Post

Atlassian·Data Scientist·Technical Phone Screen

Jul 2026

SQL question for a Data Scientist role at Atlassian. One question, reasonably tricky, the kind where you think you've got it and then realize there's a wrinkle you almost missed.

Given a team table and a game table, write a single SQL query to find the team name of the 2023 championship winner. The winner could be stored as either team_id or opponent_team_id, there are no ties assumed, but if one exists in the data you should break it by higher score. No hard-coded IDs allowed.

“The part that almost got me was the bidirectional storage.”

View Post

Atlassian·Machine Learning Engineer·Onsite - Behavioral / Leadership

Jul 2026

Behavioral round for an ML Engineer role at Atlassian, focused entirely on values alignment and leadership signals. Standard stuff but the follow-up probing caught me off guard a few times.

Tell me about a time you pushed back on a decision or requirement you disagreed with.
Describe a situation where you drove a meaningful change or improvement in your team or process.
Can you give an example of helping someone else grow, through coaching or mentoring?
Walk me through a time you had to make progress on something without clear direction or requirements.
Tell me about a mistake you made and how you handled it.

“I had a decent story ready but the follow-up on how I handled the conflict after pushing back is where I fumbled.”

View Post

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

Jul 2026

System design round at Atlassian for an ML Engineer role, basically one big question about building an internal enterprise chatbot that integrates with Confluence, Jira, and similar tools. Heavy on architecture and production concerns, less about ML theory than I expected.

Design an internal enterprise chatbot that lets employees ask questions in natural language, pulling answers from internal tools like Confluence and Jira, while enforcing access control, supporting both document Q&A and action-based workflows, and keeping everything auditable. Walk through the high-level architecture, key components, and how you'd evaluate and monitor it in production.

“This is a beast of a question and I think I underestimated how many distinct sub-problems are packed into it.”

View Post

Atlassian·Software Engineer·Onsite - System Design / Architecture

Jul 2026

System design round at Atlassian focused entirely on building a tagging system with a heavy emphasis on REST API design. The problem felt deceptively scoped but the edge cases and concurrency bits made it genuinely tricky.

Design a tagging system (like tagging pages or issues) with a focus on REST API design. Cover CRUD for tags, attaching and detaching tags from entities, listing tags per entity, and searching entities by tag with AND/OR semantics.
How would you handle concurrency and idempotency for tag attach and detach operations?
Walk through the edge cases: what happens when you delete a tag that's still attached to entities, how do you handle rename collisions within a workspace, and how do you approach bulk attach/detach?
How would you design pagination for the tag list and entity search endpoints?

“This is the kind of question where you think you've got it in the first five minutes and then you don't.”

View Post

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

Jul 2026

System design round at Atlassian for an MLE role. The whole thing was one big design question about building a RAG system on top of Jira and Confluence, which sounds straightforward until you get into the permissions and freshness requirements.

Design a RAG system that lets employees ask questions across Jira and Confluence, including cross-product queries like 'what's the status of project X and where's the design doc for it?'
How would you handle document-level permissions so users only retrieve content they're authorized to see?
Jira updates very frequently while Confluence changes less often. How does your ingestion pipeline handle that difference?
How would you make sure the generated answers cite the source Jira issues or Confluence pages correctly?
How would you evaluate this system both offline before shipping and online once it's live?

“This was the whole interview basically.”

View Post

Atlassian·Software Engineer·Technical Phone Screen

Jul 2026

Atlassian SWE interview with a design-heavy coding problem that looked straightforward but had a lot of follow-up potential baked in. The discussion went longer than I expected once we got into trade-offs.

Design and implement a small system where records of (agent_id, rating) arrive over time. The system should compute each agent's average rating and return all agents sorted by average rating descending, with agent_id ascending as a tie-breaker.

“My first instinct was to store raw records and recompute averages on every query, which the interviewer let me talk through before nudging me to think about scale.”

View Post

Atlassian·Software Engineer·Onsite - System Design / Architecture

Jul 2026

System design round at Atlassian for a software engineer role, focused entirely on building a trending/top-N posts feature for Confluence. Pretty deep dive, they wanted the full pipeline from event ingestion all the way through to serving.

Design a system that surfaces the top-N posts on Confluence based on engagement signals like views, likes, and comments within configurable time windows.

“This is a meaty one.”

View Post

Atlassian·Software Engineer·Technical Phone Screen

Jul 2026

Atlassian software engineer interview with a system design coding problem focused on building an agent-rating service. The core challenge was less about getting something working and more about justifying your data structure choices under follow-up pressure.

Design and implement an agent-rating service with two operations: one to record a score (1-5) for a named agent and keep a running average, and another to return all agents ranked by average score descending. How do you keep this efficient?

“I jumped straight to the brute force because I wanted something on the board fast.”

View Post

Atlassian·Machine Learning Engineer·Technical Phone Screen

Jul 2026

Atlassian ML engineer interview, got a nested list problem that looked straightforward but had a twist on the weighting scheme. Took me a bit to realize the depth calculation was inverted compared to the standard version.

Given a nested list of integers, return the sum of all integers weighted by their depth, where deeper integers have LOWER weight (weight = max depth minus current depth). How would you approach this?

“The classic version weights deeper integers more heavily, so I started going down that path before re-reading the prompt.”

View Post

Atlassian interview FAQ

What rounds are in the Atlassian interview?

Candidates most often report a technical phone screen (45 write-ups), a system design round (38), a behavioral / leadership round (10) and an onsite coding round (3).

What does the Atlassian technical phone screen cover?

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

What is asked in the Atlassian system design round?

Across 38 system design write-ups, the most tagged question topics are System Design (101 questions), Technical Trade-offs (75) and Data Modeling (29).