Communication from the internal recruiter was good throughout the process, except for the part where I didn't receive any feedback after failing the technical interview. It would be beneficial to get honest feedback on areas for improvement, but I felt ghosted by Atlassian afterward. I understand they likely have a high volume of candidates, so it's probably not a pleasant experience being the bearer of bad news to unsuccessful candidates.
I spent a significant amount of time building a robust automation framework that ran properly on their CI pipeline, only for it to be undone by the technical interview. I admit I did not perform well, despite the technical recruiter providing tips, tricks, and links to their candidate experience portal.
For some reason, I experienced a mental block during the interview. The technical questions were quite basic, so basic that I likely didn't prepare for them and wasn't using them in my day-to-day job. The interviewers were very nice and supportive during the interview.
The interviewers also mentioned the role of a Quality Engineer as more of a coaching position from the sidelines rather than being hands-on. In the end, perhaps it wasn't a good fit as I'm unsure if I could contribute consistently. I don't feel it should even be called an "Engineer" if there are no technical aspects involved, such as building automation frameworks.
What are the metrics to measure on performance tests?
Find 3 issues on the provided code.
The following metrics were computed from 1 interview experience for the Atlassian Senior Quality Engineer role in Sydney, Australia.
Atlassian's interview process for their Senior Quality Engineer roles in Sydney, Australia is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Atlassian's Senior Quality Engineer interview process in Sydney, Australia.