Atlassian Machine Learning Engineer interview questions

25 Machine Learning Engineers have shared notes from their Atlassian interviews, with the questions they were asked in each round. That is 34% of the 73 Atlassian interview notes on Screna AI.

25 Machine Learning Engineer interview notes

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·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·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Atlassian ML Engineer interview had at least one coding round with a classic string manipulation problem. Nothing too wild but it's the kind of question that feels easy until you're actually writing it out under pressure.
  • Given a secret number and a guess, return a hint string showing how many digits are correct in both value and position (bulls) and how many digits appear in the secret but are in the wrong position (cows). Format the result as 'xAyB'.

“My first instinct was to just loop through and count matches, which gets you the bulls fine.”

View Post

Atlassian·Machine Learning Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Atlassian for an MLE role. Just one question but it had a lot of layers to it, more of a conversation than a standard interview.
  • Describe a situation where you had to make meaningful progress despite unclear requirements, shifting priorities, or missing data. How did you frame the problem, what trade-offs did you accept, and how did you keep stakeholders informed about uncertainty?

“This one took me a second to land on a good story.”

View Post

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

May 2026
ML system design round at Atlassian for an MLE role. The whole session was one big open-ended design problem around building a search system for something like Jira or Confluence, and they expected you to drive it pretty much end to end.
  • Design a search system for one of Atlassian's products, such as Jira issues or Confluence pages, covering retrieval, ranking, and the full ML pipeline.
  • How would you handle document updates and deletions in your indexing pipeline without causing stale or inconsistent search results?
  • What embedding model would you choose for semantic search here, and how would you get training data to fine-tune it for this domain?
  • How would you evaluate the quality of your search system, both offline and in production?

“This is a beast of a question.”

View Post

Atlassian·Machine Learning Engineer·Technical Phone Screen

May 2026
Atlassian ML Engineer interview that went deep into graph theory territory. The LCA-on-a-DAG problem caught me pretty flat-footed and I spent most of the time trying to remember why my tree intuition kept breaking.
  • Given a DAG where nodes can have multiple parents, define what 'Lowest Common Ancestor' means in that context and describe an algorithm to compute it.

“My first instinct was to just adapt the tree recursion and it immediately fell apart.”

View Post

Atlassian·Machine Learning Engineer·Technical Phone Screen

May 2026
Atlassian ML Engineer interview that ended up being more of a systems coding round than anything ML-related. The core problem was a calendar-style booking system with some data structure discussion baked in.
  • Design and implement a tennis court reservation system that supports booking a court for a time interval without overlaps, canceling an exact booking, and querying whether a court is occupied at a given time. Walk through your choice of data structure for managing non-overlapping intervals per court and the time complexity of each operation.
  • How would you extend the system to support rescheduling a booking and finding the next available slot of a given duration on a specific court?

“I went with a sorted structure per court and explained the overlap check logic first before writing any code.”

View Post

Atlassian·Machine Learning Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Atlassian for an ML engineer role. Just one question but it went deep, they really wanted the full arc from screw-up to process change.
  • Tell me about a significant mistake you made at work. How did you find out about it, how did you handle the fallout, and what did you actually change afterward?

“The part that tripped me up was the 'what did you change' bit.”

View Post