Senior Data Engineer Interview Experience - Bangalore Rural, Karnataka
Process
The first round was coding and SQL. The interviewer was clueless if my answer was right or what the correct answer was.
The second round was system design. The interviewer was again not prepared and asked for 10 minutes to look for questions. They were on call support, pausing calls in between.
The third round was product sense. I really didn't understand what the expectation was. I didn't understand the questions or slang, and I didn't even understand when the interviewer was switching context.
For cultural fit and managerial rounds, no one was from the DE team or the actual hiring team, and no one had an answer about the actual team.
After completing all rounds, I received feedback saying I was technically not fit. It would have been better to reject me after the first or second round to save time and effort.
It was a waste of time, non-productive, and offered zero learning.
Questions
Some SQL and DSA Questions
Design Library Management System
Product sense: How to measure Slack success?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Atlassian Senior Data Engineer role in Bangalore Rural, Karnataka.
Success Rate
Atlassian's interview process for their Senior Data Engineer roles in Bangalore Rural, Karnataka is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for Atlassian's Senior Data Engineer interview process in Bangalore Rural, Karnataka.
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
