Atlassian Data Engineer interview reports center on live SQL and Python: CTE and rolling-window queries plus a short coding problem, with one candidate naming time pressure as the main challenge.
$146K
Avg. Base Comp
$190K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The Data Engineer reports we have point to a technical screen built around SQL and Python under time pressure. One candidate who received an offer describes a coding interview with three connected SQL questions followed by one Python problem. Every SQL question needed a CTE: a ranking and join problem, a rolling average over the last three days, and a rolling sum followed by a count. The Python question was a basic search for a target number's position in a list, and once the candidate solved it, the interviewer asked for a different approach.
A second candidate, who did not get an offer, describes the whole process as a single 60-minute technical screen. Roughly 30 to 45 minutes went to coding, with an anagram-style string grouping problem in Python and SQL questions ranging from easy to medium. Their main lesson was to settle on an approach before typing and to be quicker and more confident with SQL.
The pattern across both accounts is that the questions are practical rather than tricky, but they reward fluency. Practice rolling calculations with window functions and CTEs, rehearse a second solution to simple Python problems, and time yourself. Neither report gives a total process length, so ask your recruiter how many stages to expect.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Atlassian process.
I went through the coding round for the Data Engineer role at Atlassian, and it was heavy on SQL and Python, which makes sense for what the role demands. The first interview consisted of three SQL questions that built on each other, followed by one Python programming problem. The SQL questions all required CTEs and got progressively more complex—the first was a ranking and join problem, the second asked for a rolling average over the last three days, and the third involved a rolling sum followed by a count query. The questions felt straightforward once I understood what they were asking, but they definitely required solid preparation on window functions and CTE syntax. The Python question was a basic search problem asking me to find the position of a target number in a list, and when I solved it, the interviewer pushed me to come up with an alternative approach, which was a good signal they wanted to see how I think through trade-offs. Overall the technical bar was fair—nothing tricky or unfair, but you need to be comfortable with SQL window functions, rolling calculations, and basic Python algorithms going in. The process moved quickly; I got feedback within a few days of my interview.
Prep tip from this candidate
Focus heavily on window functions and CTEs for rolling calculations (rolling averages, rolling sums)—those came up consistently. Have multiple approaches ready for basic Python search/loop problems and be prepared to optimize or refactor on the spot.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Atlassian
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Integer to Roman | |
| Target Indices | |
| Trial User Segmentation | |
| Target Value Search | |
| Dijkstra implementation | |
| Concurrent LLM Serving | |
| Decreasing Subsequent Values | |
| Why Do You Want to Work With Us | |
| LRU Cache 1 | |
| Fraudulent Upvotes | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Top Three Salaries | |
| Comments Histogram | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Experiment Validity | |
| Download Facts | |
| Random SQL Sample | |
| Minimum Change | |
| String Shift | |
| Customer Orders | |
| Average Quantity | |
| Top 3 Users | |
| Last Transaction | |
| Manager Team Sizes | |
| Month Over Month | |
| Find the First Non-Repeating Character in a String |
Synthesized from candidate reports. Individual experiences may vary.
One candidate describes the whole process as a single 60-minute technical screen, with roughly 30 to 45 minutes spent writing code, SQL, and Python for data engineering. Expect to write working code live and to be judged on speed as well as correctness.
A candidate who received an offer reports three SQL questions that built on each other and all required CTEs: a ranking and join problem, a rolling three-day average, and a rolling sum followed by a count. Another candidate reports easy-to-medium SQL. Practice window functions under a timer.
Reported Python problems vary in difficulty. One was a basic search for a target number's position in a list, after which the interviewer asked for an alternative approach. Another was a medium anagram-style string grouping task where planning before coding saves time.
