Senior Data Engineer Interview Experience - Perth, Western Australia
October 1, 2022
Negative ExperienceNo Offer
Process
My first chat with the talent person was good. They provided thorough information about the next interview, which was described as a collaboration with two people to provide a high-level solution to a problem.
However, the actual interview consisted of vague questions, such as, "Can you describe how you would get data into a data warehouse?" No matter how I answered, it didn't seem to be the right answer for what they wanted. I repeatedly asked for clarification on the expected level of detail, but they were unable to explain.
I sent an email to the talent person afterward to describe what happened. The following day, I received an email stating that they would not be proceeding with my application.
Questions
How would you get data into a data warehouse?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Atlassian Senior Data Engineer role in Perth, Western Australia.
Success Rate
0%
Pass Rate
Atlassian's interview process for their Senior Data Engineer roles in Perth, Western Australia is extremely selective, failing the vast majority of engineers.
Experience Rating
Positive0%
Neutral0%
Negative100%
Candidates reported having very negative feelings for Atlassian's Senior Data Engineer interview process in Perth, Western Australia.
Atlassian Work Experiences
1.0
Smart People, Terrible Management
Senior Data Engineer • Current Employee
August 14, 2025
Pros: 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.0
Nice place to spend some time
Senior Data Engineer • Current Employee
Bengaluru, Karnataka, India
May 11, 2025
Pros: Structured Process
Segregation of Responsibilities
Pay
Cons: Rigorous Review process
Half-yearly review cycle.
Too many extra things to worry about other than the main work.
4.0
Good Balance, Bad Leadership
Senior Data Engineer • Current Employee
Bengaluru, Karnataka, India
October 29, 2024
Pros: Work-Life Balance
Remote Work
Cons: Leadership is clueless.
Nepo Hiring.
- 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
Explore Interview QuestionsTaro 75Google Interview QuestionsMeta Interview QuestionsAmazon Interview QuestionsApple Interview QuestionsNetflix Interview Questions
Explore Interview ExperiencesOpenAI Interview ExperiencesAnthropic Interview ExperiencesPerplexity Interview ExperiencesWindsurf Interview ExperiencesMistral AI Interview Experiences
