Senior Data Engineer Interview Experience - Sydney, Australia
Process
I completed the first coding round at Atlassian for a Data Engineer role.
As this role requires strong SQL and Python skills, the coding round featured three sequential SQL questions and one Python-based programming question.
The questions were fairly straightforward if you had prepared well.
I am still awaiting a response from Atlassian regarding my interview. Hoping for the best!
Questions
SQL Questions:
-
The first question was based on ranking and joining to get the solution.
-
The second follow-up question used the same database and tables. It asked for a rolling average based on the last 3 days.
-
The third question was again based on a rolling sum and then a count query based on that rolling sum.
All of the SQLs required CTE statements.
Lastly, the Python programming question was a basic for loop to search for the position of a target number. The interviewer asked for a different approach to solving it.
Was this helpful?
Interview Statistics
The following metrics were computed from 2 interview experiences for the Atlassian Senior Data Engineer role in Sydney, Australia.
Success Rate
Atlassian's interview process for their Senior Data Engineer roles in Sydney, Australia is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Candidates reported having very good feelings for Atlassian's Senior Data Engineer interview process in Sydney, Australia.
Atlassian Work Experiences
- 1.0Smart People, Terrible ManagementSenior Data Engineer • Current EmployeeAugust 14, 2025Pros: There are some smart and kind people there.Cons: Incredibly high turnover. A majority of my team had less than 6 months' experience. You'd think they'd pair new people with experienced people, but no, they'd put all the new hires together. Your manager would ask you to do something, then during your review, they'd tell you that the thing they asked you to do lacked business impact. My manager flat-out told me that some teams will have more business impact, and that the team I was on was maxed out at "meets expectations" no matter how good we were. My face time with my managers ranged between 2-6 hours a quarter. You will always have to work outside of normal business hours. I had scrum calls at 11:30 at night. I got no help from our platform team during my working hours, which made my tickets stretch on or forced me to work until 2:00 am to be online at the same time as them. The managers I encountered looked at everything so simplistically, with barely a surface-level understanding. This is the level of thinking I encountered: "Person A made 5 tables, Person B made 7 tables. Therefore, Person B > Person A." Zero understanding of variations in complexity of tasks. That same shallow thinking applies to PR (pull request) count. If Person A thoroughly tests and validates their code and deploys once versus Person B, who releases a buggy piece of crap and has to deploy 10 patches, management will applaud Person B. If Person A writes their code DRY and Person B is a copy-pasta wizard, management will applaud Person B.
- 4.0Nice place to spend some timeSenior Data Engineer • Current EmployeeBengaluru, Karnataka, IndiaMay 11, 2025Pros: Structured Process Segregation of Responsibilities PayCons: Rigorous Review process Half-yearly review cycle. Too many extra things to worry about other than the main work.
- 4.0Good Balance, Bad LeadershipSenior Data Engineer • Current EmployeeBengaluru, Karnataka, IndiaOctober 29, 2024Pros: Work-Life Balance Remote WorkCons: Leadership is clueless. Nepo Hiring.
Atlassian Interview Questions
