Atlassian Coding Screens and Karat: 3 Experiences (Part 2 of 2)

Shared by janebeingjane ·
Company
Atlassian
Reports
3 interview reports
Level
Unknown
Stages
Phone screen → Onsite

Atlassian coding screens from 2025 asked rating averages, a stock-price tracker and an F1 lap problem; an earlier Karat screen built a to-do list.

At a glance

  • Process: a code-design and data-structures screen with two coding tasks (09, 10); the earlier Karat screen opened with a web-flow question, then browser coding (11).
  • Asked: average agent ratings with a time-range or monthly follow-up (09, 10), LeetCode 2034 Stock Price Fluctuation with snapshots (09), and an F1 last-lap improvement problem (10).
  • Outcome: both 2025 screens ended in rejection; in each, a tool incident came up (Google captions in 09, a phone assistant that activated in 10), with no confirmed link to the result.

Coverage: 3 of the series' 11 Atlassian candidates: two coding screens from May 2025 (09, 10) and a Karat screen with a Q3 2023 interview period (11, history). The overview, the question tables for all current reports and the loop and onsite reports are in Part 1.

In this series

What came up

Both current screens here (09, 10) were two-task coding rounds built around averages over ratings, with follow-ups that changed the query.

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Average agent ratings, then a time-range query 1: 09 May 2025
LeetCode 2034, Stock Price Fluctuation, then snapshots and a timestamp query 1: 09 May 2025
F1 driver with the largest last-lap improvement; pit-stop follow-up 1: 10 May 2025
1–5 agent ratings, descending averages, then monthly results 1: 10 May 2025

2 coding screens, May 2025

09: Coding screen — ratings, stock-price snapshots, and a caption-tool dispute

Interview date: May 28, 2025, derived from “Wednesday” in the May 30 report · Stage: Code design and data structures · Outcome update: Rejected

Two coding tasks

The first task calculated average agent ratings, with a follow-up adding a time range. The second was LeetCode 2034, Stock Price Fluctuation. The candidate said they made a mistake in its follow-up and ran out of time to test.

In a June 9 reply, the same author clarified that the follow-up added a snapshot during updates and asked for the maximum price for a supplied timestamp. They did not provide enough detail to establish the snapshot API or its exact historical-query semantics.

Tool incident and outcome

On July 7, the author reported rejection and said they had used Google caption, which the interviewer described as an AI tool. Neither a causal link to the rejection nor permission for a coding assistant was established. The July update is part of the May interview account, not another interview.


10: Coding screen — F1 improvement, monthly ratings, and an unexpected phone activation

Interview date: May 27, 2025, derived from “yesterday” in the May 28 report · Result: Rejected the next day

First coding round

Given drivers and their lap times, identify whose last lap improved most compared with their average over previous laps. The follow-up asked how pit stops should be handled. The author did not disclose the intended pit-stop rule or their implementation.

Second coding round

For a support-ticket system, accept customer ratings on a five-point scale, return each agent's average, and sort agents from highest to lowest average. The follow-up asked how to handle monthly results.

The candidate said ChatGPT on their iPhone unexpectedly activated during this round and began summarizing after they had written the code and explained it. They muted it, explained the unexpected activation, and received an “OK” from the interviewer. The rejection arrived the next day. The report gives neither permission to use AI nor a confirmed reason for rejection.


History (before Nov 2023)

Report 11's interview period is Q3 2023, so it is outside the current counts. Its questions:

Question Reports Last seen
Build a To-do List with a GET Request, following a picture 1: 11 Q3 2023
Explain what happens after posting a website comment 1: 11 Q3 2023

11: Earlier Karat — a reference-picture to-do list and a GET request

Interview period: Q3 2023 in the source header · Report date: December 14, 2024 · Result: Invited to onsite

An old colleague referred the candidate. HR contacted them about a month later and arranged Karat.

Verbal discussion, then browser coding

The interviewer first asked what happens after a comment is posted on a website. The coding task supplied a to-do-list picture and asked the candidate to make a JavaScript GET request and reproduce the displayed result.

Build a To-do List with a GET Request preserves that task's GET-and-render core. The source did not share the picture, endpoint, response data, or interactions, so the practice is a reconstruction rather than a recovery of its exact appearance.

Three days later, the candidate was invited onsite. AI permission is unstated. The 2024 report and 2023 header period remain separate.


Common questions

What does the Atlassian code design and data structures screen ask?

In the two May 2025 reports: two coding tasks each, rating averages with a changing follow-up, plus Stock Price Fluctuation (09) or an F1 lap problem (10).

Is AI allowed in the Atlassian coding screen?

These reports don't establish permission: Google captions were called an AI tool by the interviewer (09), and a phone assistant that switched on by itself was noted (10). Both candidates were rejected, with no stated reason.

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.

Comments

0

No comments yet — be the first to share what you know.