Atlassian Full Stack Interviews: 11 Experiences (Part 1 of 2)

Shared by janebeingjane ·
Company
Atlassian
Reports
8 interview reports
Level
Full-time
Stages
Phone screen → Onsite

Atlassian full-stack and frontend interviews from 2023 to 2026 mix browser building, login and web-flow talks, and system design; AI rules vary by team.

At a glance

  • Process: Karat or a technical screen, then coding, a Full Stack Craft discussion of web and login internals, system design, and behavioral or leadership rounds (05, 07).
  • Asked recently: building a browser interface in 4 of the 10 current reports (01, 03, 06, 08), browser-to-server or login flows in 4 (05, 06, 07, 08), and a separate system design in 5 (01, 03, 04, 05, 07). The feed view backed by an API came up twice (01, 03).
  • AI tools: rules differed by team. Candidate 02 used AI on one backend part of a bank app; 01 had every AI feature disabled and checked over screen share; 04's team coded manually; two coding screens had tool incidents (09, 10).
  • Practise first: Build a Feed Grid from an API, Build a File Directory Tree and Social Post Comments.

Coverage: 11 Atlassian candidates in a two-part series split by stage: senior and L5 frontend, P40 and P50 full stack, ML/AI product engineering and unspecified coding roles. This part holds the overview and the 8 loop and onsite reports (01–08); Part 2 holds the coding screens and the earlier Karat (09–11). Report 11 (interview Q3 2023) is history, outside the current counts. Report dates run from December 2024 to October 2026.

In this series

  • Part 1 (current): overview, question tables and the 8 loop and onsite reports (01–08)
  • Part 2: coding screens and Karat — two 2025 coding screens and an earlier Karat screen (09–11)

What came up

These counts cover the 10 current reports in both parts (01–10). Browser building and web-flow talks matter as much as algorithms.

Topic Reports Last seen
A separate system-design question 5 of 10 Oct 2026
Building or reproducing a browser interface 4 of 10 Oct 2026
Browser-to-server flows or login internals 4 of 10 Nov 2025
An explicit AI restriction, manual-only statement or tool incident 4 of 10 Oct 2026
Identifiable algorithm or data-structure tasks 3 of 10 Nov 2025
AI mentioned for mock practice 2 of 10 Nov 2025
Behavioral or leadership rounds 2 of 10 Sep 2026
Object-oriented player design 1 of 10 Sep 2026
AI-assisted work on a bank-app backend part 1 of 10 Oct 2026 (report date)

Rows: system design 01, 03, 04, 05, 07; browser interface 01, 03, 06, 08; browser-to-server 05, 06, 07, 08; AI restriction or incident 01, 04, 09, 10; algorithms 05, 09, 10; AI for mock practice 05, 07; behavioral 04, 07; OOD 04; AI-assisted 02.

What the reports say about AI tools

In a report posted on October 30, 2026, a candidate described coding a bank app with AI. The app appeared to have several parts, and only one was assigned. Later replies identified the backend and described uncertainty about interface changes and the boundary between implementation and design discussion.

Other candidates received different instructions. The October frontend screen required every AI feature to be disabled and checked the IDE settings over screen share. The September ML/AI product-engineering candidate said their own team used manual coding.

A separate applicant also reported an invitation to a round named “AI enabled Backend Coding” on September 19, 2026. That applicant did not share a completed interview or a task. The original author of that thread said they had not taken the round and that their own team used manual coding. The invitation and the bank-app interview are separate accounts.

Questions we found

These tables cover the 10 current reports in both parts.

AI Coding

Question Reports Last seen
Bank-app backend part; the assigned feature was not disclosed 1: 02 Oct 2026 (report date)

Project Coding

Question Reports Last seen
Build a Feed Grid from an API: static view, then API data 2: 01, 03 Oct 2026
Reproduce a supplied layout in plain HTML/CSS (reference not shared) 1: 06 Oct 2025
Build a File Directory Tree 1: 08 Jan 2025 (report date)

Algorithms / Data Structures

Question Reports Last seen
Find robots whose available parts contain every requested part type 1: 05 Nov 2025
Delivery Origins and Reachable Destinations 1: 05 Nov 2025
Popular Content: increase/decrease popularity and return the most popular item, O(1) follow-up 1: 05 Nov 2025
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

Low-Level Design / OOD

Question Reports Last seen
Music-player OOD: playback, queue, loop, shuffle; practice: Music Player Operation Sequence 1: 04 Sep 2026

System Design

Question Reports Last seen
Design a Responsive Product Catalog Search Frontend 1: 01 Oct 2026
Design a Searchable Emoji Picker 1: 03 Sep 2026
Social Post Comments, with notifications and scaling 1: 04 Sep 2026
Top-N Confluence posts 1: 05 Nov 2025
Image picker (requirements not disclosed) 1: 07 Sep 2025

Web Architecture / Full Stack Craft

Question Reports Last seen
Walk through a login's frontend, backend and network flow 2: 05, 07 Nov 2025
Explain what happens after a frontend form is submitted 1: 05 Nov 2025
Trace an avatar upload through display, with resolutions and optimization 1: 06 Oct 2025
Explain a login page's implementation in engineering depth 1: 08 Jan 2025 (report date)

8 loop and onsite reports

01: L5 frontend — a six-cell feed and an explicit AI ban

Interview period: Q4 2026 · Report date: October 12, 2026 · Role: Frontend, L5 · Result: Rejected

A LinkedIn recruiter sent an invitation the day they spoke. The candidate scheduled the screen a week out and felt underprepared.

Technical screen

The local IDE was allowed, but every AI feature had to be disabled. The interviewer required screen sharing and checked the settings.

The task behind Build a Feed Grid from an API used feed records with feed_text, feed_id, and createdAt. The candidate first had to render static data in six cells, arranged as two rows and three columns, then fetch feeds from a supplied API and populate the view. React hooks and their use also came up.

There were 20 minutes for coding. The candidate struggled with the grid, later pointing to grid-template-columns: repeat(3, 1fr) as the layout they wished they had used, and did not finish.

Ten-minute system-design discussion

The next task was a searchable product-catalog frontend: a search input above a product grid, an unlimited number of products, the component tree, and fast updates after typing or filtering. The unfinished coding task had left the candidate discouraged during this discussion.


02: AI coding onsite — one backend part of a bank app

Interview period: Q3 2026 · Report date: October 30, 2026 · Stage: Onsite · Result: Rejected

The candidate explicitly said they used AI to write code. The bank app appeared to have several parts, with one selected for the interview. In a reply, the candidate said they had drawn the backend part.

Implementation and interface discussion

The candidate could not tell how much had to be implemented and how much only needed an explanation. An interface issue came up. They thought the AI's proposed change was reasonable, but said there was still an overall correctness problem. They also felt that changing someone else's interface on that scale would be unusual for a normal pull request.

The interviewer discussed design, leaving the candidate unsure whether the conversation was a hint to change the code or an open discussion. A later reply repeated that uncertainty about hints and verbal explanation.

The report does not name the assigned feature, share the repository or interface contract, or identify the AI tool, time limit, tests, or grading criteria. It establishes actual AI use in one interview, while leaving the exact backend task unknown.


03: Senior frontend — build the view, then feed it mock API data

Interview period: Q3 2026 · Report date: September 24, 2026 · Role: Senior frontend

A LinkedIn recruiter arranged this screen.

Coding and design

  1. In about ten minutes, build a Twitter-like feed list with HTML and CSS.
  2. In the next fifteen minutes, render data from a mock API in that view. This is the same feed-view family as Build a Feed Grid from an API, but this report does not specify a six-cell grid.
  3. Spend about fifteen minutes designing a search field and emoji picker. The interviewer asked relatively few questions, and the candidate drove the discussion.

AI permission is unstated. The practice combines this account with entry 01's grid; its fixture and tests are reconstructed.


04: ML/AI product engineering — music-player objects and a manual-only loop

Interview period: Q3 2026 · Report date: September 19, 2026 · Team: Acquired BCNY team, ML/AI product engineering · Result: Passed; later reported an offer

The two-week process emphasized communication, product thinking, and culture fit. A September 30 update confirmed an offer and said the application had covered a broad level range.

Phone screen: music player

The interviewer asked how to represent a player and stub play, pause, and next, then added a Spotify-like queue, playlist looping, and shuffling. The emphasis was object-oriented programming and communication. Music Player Operation Sequence is a bounded simulator; its deterministic shuffle and serialized outputs are practice conventions.

Onsite system design

Design a comments section for social-media posts, in the style of Instagram or Facebook. The source specified fewer than one million users and assumed login, users, and posts already existed. Discussion covered APIs, database design, scaling reads and writes, notifications, and scaling server and database resources.

Project deep dive, leadership, and behavioral rounds

The candidate discussed a system they had worked on, using project diagrams and going into individual components. They called the leadership and behavioral questions standard without giving their wording.

In replies on September 19 and 21, the author confirmed manual coding for this team. The team's AI-related work did not establish AI-tool permission.


05: P40 full stack — Karat, popularity updates, and a preparation-only GPT mention

Interview period: Q4 2025 · Report date: November 6, 2025 · Role: P40 full stack · Result: Rejected after system design

Karat: twenty minutes of web flow, thirty minutes of coding

The verbal discussion followed what happens after submitting a frontend form. The candidate felt the interviewer was checking for particular terms and repeated questions when those terms were missing. Their suggestion to practice this with GPT concerned preparation; they did not say GPT was allowed during the interview.

The first coding problem supplied parts such as Rosie_wheel, Sam_case, Sam_mirror, and Rosie_case, plus requested types wheel,case. The task was to find every robot for which all requested parts were present. In that small example, Rosie qualifies and Sam lacks a wheel.

The second problem was Delivery Origins and Reachable Destinations, called Cart Routes in the report. Given downward-directed cart-route pairs, return each start location and all terminal locations it can reach. The supplied edges were B→K, C→K, E→L, F→G, J→M, E→F, C→G, A→B, A→C, G→H, and G→I. The expected memberships were A→{K,H,I}, E→{H,L,I}, and J→{M}. The source defined N as the number of input pairs; it did not require the practice version's sorted output.

Later coding: Popular Content

Implement increasePopularity(contentId), decreasePopularity(contentId), and getMostPopular(). The initial discussion allowed O(log n). Follow-ups asked for O(1), then how to return the item first increased when several items tie. The author compared the optimization to LeetCode 432.

Full Stack Craft and system design

Craft traced login through the frontend, backend, and network, then asked about login-related work, decisions, and trade-offs in prior projects. The candidate felt it was a longer version of Karat without much depth. The system-design prompt was Top-N Confluence posts. They felt that discussion had gone well but were rejected afterward; no reason was supplied.


06: Full stack — avatar-upload discussion, then an unavailable layout reference

Interview date: October 23, 2025 · Report date: November 19, 2025 · Role: Full stack · Status at posting: No update after Karat

Karat frontend discussion and implementation

First, explain the path from clicking a profile-avatar upload button to seeing the new avatar on the profile page. The interviewer also asked about different image resolutions and optimization.

Next, reproduce a finished sample's layout using plain HTML and CSS. Time ran out as the candidate finished that portion. They thought there might have been further questions, but did not receive them. The reference image and its layout details were not included in the report, so there is no verified runnable reconstruction of this particular task.

Retake choice

An email soon offered the option to book a retake within 24 hours, before the candidate knew the first result. Asked how the attempts would count, the interviewer said both reports would go to the company. The candidate remained unsure how the company would weigh them. The report gives no AI-tool instruction.


07: P50 full stack — login internals and ChatGPT/Claude mock practice

Interview period: Q3 2025 · Report date: September 9, 2025 · Role label: P50 full stack · Source cohort field: New graduate

The sequence was one coding round and one Full Stack Craft round, followed by system design, then two behavioral interviews.

Coding

The author named two variants using the phonetic shorthand 吴流 and 酒吧流, apparently referring to LeetCode 56 and 986. That identification is an interpretation; the actual variants, inputs, and follow-ups were not described.

Full Stack Craft

The discussion began with login and covered frontend/backend interaction, TLS, DNS, React, and database partitioning. The author said it resembled the supplied preparation example and tested whether the candidate understood the concepts, without going deeply into them. They recommended ChatGPT or Claude for mock practice. That is a preparation suggestion, not a statement that AI was allowed in the round.

System design and behaviorals

The design topic was an image picker. The author felt it was straightforward and did not provide requirements. Both behavioral rounds used similar topics, with a detailed topic list from the recruiter; no exact questions were shared. Early results arrived within a day or two, while the last two rounds took more than a week. The report does not give a final hiring outcome.


08: Full-stack onsite — directory-tree UI and a separate Craft discussion

Interview period: Q1 2025 · Report date: January 23, 2025 · Role: Full stack

Browser coding

Build a file directory-tree interface from a simple supplied mock and data. The candidate could use a local IDE or a tool such as CodeSandbox, debug in the browser, and choose a framework freely. The report did not provide the original mock, data, or detailed interactions; the practice exercise supplies a bounded version.

Full Stack Craft

Explain a login page's implementation in depth, with practical engineering knowledge. In a later reply, the author confirmed that this Craft discussion did not require coding. That clarification does not remove the separate browser-coding round above.

Permission to choose an IDE or framework does not establish permission to use AI, which the report does not address.


Patterns across the reports

These patterns compare reports from both parts.

  1. The feed task had a static step and an API step. Both 2026 frontend screens, entries 01 and 03, used that sequence. Only entry 01 specified the two-by-three layout, record fields, React-hook discussion, and AI restriction. Those details should not be transferred to the other candidate's interview.
  2. Full Stack Craft could sit beside a separate coding task. Entries 05, 07 and 08 describe a login-centered Craft discussion as well as another coding round. Their reported depth differed: entry 08 emphasized a deep dive, while entries 05 and 07 described shallower conversations.
  3. Similar agent-rating tasks led to different follow-ups. The two May 2025 screens, entries 09 and 10 (Part 2), both involved averages. One added a time range, while the other asked about monthly results. Neither report supplies the other's missing rules.

Common questions

Can you use AI in the Atlassian coding interview?

It depends on the round and team. One onsite candidate used AI on a bank-app backend part (02), while a frontend screen required every AI feature off (01) and an ML/AI team coded manually (04).

What is the Atlassian Full Stack Craft interview?

A discussion of how web features work end to end, usually starting from login: frontend, backend and network flow (05, 07, 08). It sat beside a separate coding round in all three.

What does the Atlassian frontend screen ask?

Build a view in HTML and CSS, then fill it with API data, in two 2026 reports (01, 03), followed by a short frontend system design.

Does Atlassian use Karat?

Yes, for some full-stack candidates: a web-flow discussion plus coding (05, 06), and an earlier Karat screen in Part 2 (11).

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesAtlassian Coding Screens and Karat: 3 Experiences (Part 2 of 2)
0 total reactions. Your reactions: none.

Comments

0

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