Atlassian · Primly Community

Atlassian frontend engineer interview: what they actually ask (went through it in 2026)

frontend_fran · 5 replies

just finished my atlassian frontend engineer interview loop last month and wanted to write up something real since most posts i found were vague or old.

background: 4 YOE, primarily React, applied for a mid-level FE role on one of their cloud products.

the loop structure recruiter screen, then a tech screen, then a 4-round virtual onsite. the onsite had: one frontend-specific coding round, one general algorithms round, one system design (with a frontend slant), one behavioral.

the FE coding round they gave me a coderpad problem that was essentially: build a small UI component from scratch. no framework, just vanilla JS and HTML. it wasn't "implement a virtual DOM" level, more like "here's a spec for a filterable list, make it work." they cared a lot about event handling, DOM manipulation basics, and edge cases. accessibility came up as a follow-up. if you've been living in React abstractions for years, dust off your vanilla JS skills. seriously.

the algorithms round standard LC-medium stuff. i got a graph traversal problem. nothing FE-specific.

system design with FE angle they asked me to design a collaborative editing feature (very on-brand for atlassian given confluence/jira). we talked about operational transforms vs CRDTs at a high level, real-time sync, handling offline states, component architecture. it was a discussion not a quiz, the interviewer was adding to the design with me.

behavioral atlassian values. had two stories get dug into pretty hard. practice the STAR format but make sure the R (result) is concrete, not vague.

total process from application to offer was about 6 weeks. the interview experience itself was pretty pleasant, no gotcha vibes.

feel free to ask questions.

5 replies

mobile_mara

the vanilla JS thing is real. i interviewed at a company that uses a similar pattern (product company, heavy on their own tooling) and got burned by not knowing how to do a basic debounce by hand. feels silly but it matters when you're in the room.

infra_ines

curious, did comp come up early or just at the end? and was the offer in line with what you expected for atlassian mid-level FE?

frontend_fran

recruiter asked for range at the start, offer came through at the end of week 6. it was in line with what i'd seen online for atlassian mid-level, which i'll say ranges roughly 180-230k TC depending on your level and location. i'm remote US so no bay area adjustment for me. they didn't budge much on base but the RSU grant had some flex.

sam_recovering

glad it was a positive experience. i've been wary of atlassian because the process is long but your writeup makes it sound reasonable. was there any take-home or was everything in the live rounds?

bootcamp_bri

no take-home from my experience either, all live. the vanilla JS angle in the FE round is consistent with what i've heard from other atlassian FE candidates. definitely worth a refresher on DOM events and basic state management without a framework.