Atlassian Full Onsite Interview Experience for SDE Position
Interview Experience
I had my Karrat interview a few weeks ago. The interview was a Snake game; these kinds of questions aren't difficult, but there are many corner cases to consider and handle well. VO: Coding 1: Likou57
Full Details
I had my Karrat interview a few weeks ago. The interview was a Snake game; these kinds of questions aren't difficult, but there are many corner cases to consider and handle well. VO: Coding 1: Likou57 Coding 2: Design a rate limiter;
follow-up also needs to be calculated individually for each customer/IP. SD: Design a role access system, supporting both role-based and resource-based approaches. I wasn't well-prepared and answered haltingly. It seems the interviewer wanted something like an AWS managed policy—flexible and configurable. It's quite challenging without preparation. It's been at least two weeks and I still haven't received a response. I asked HR for a follow-up, but they haven't replied. Does this mean I'm being rejected? I don't need feedback, just some kind of reply!
About This Question
This is a candidate experience report from a atlassian interview for a swe role during the onsite round reported in 2025.
It covers the following topics: Rate Limiter .
Difficulty rating: Hard
Topics
More Atlassian Interview Questions
About Atlassian Interview Reports
This question was reported by a candidate who interviewed at Atlassian. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Atlassian are the higher-signal extractions to take from this report.
For broader preparation context, the Atlassian interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Atlassian reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Atlassian Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Atlassian reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.