If you land on a great team, consider these factors: interesting tech challenges, clever colleagues, autonomy, good compensation (for Australia), competent leadership, and excellent work-life balance.
If you land on a poor team:
Ask how many people have left a team in the last six months before joining.
Y'all spend a lot of time assessing the impact of your engineers. Perhaps you should apply ever greater scrutiny to your M80s+. Some of them are bad leaders, and the fish rots from the head.
The recruiter reached out to me and scheduled a screening interview through Google Meet. The interview was common: describing the company and position, asking questions about experience and salary expectations, and answering any questions you have.
I went through Atlassian’s coding design interview recently, and the experience was surprisingly poor for a company of this scale. The exercise itself was simple, and I completed the implementation correctly. The interviewer gave me positive feedback
I went through the full Atlassian interview pipeline over about 1.5 months, including: * Karat Live Coding – I passed two rounds. The interviewer changed the problem twice mid-session to make it harder, but I solved all versions successfully. *
The recruiter reached out to me and scheduled a screening interview through Google Meet. The interview was common: describing the company and position, asking questions about experience and salary expectations, and answering any questions you have.
I went through Atlassian’s coding design interview recently, and the experience was surprisingly poor for a company of this scale. The exercise itself was simple, and I completed the implementation correctly. The interviewer gave me positive feedback
I went through the full Atlassian interview pipeline over about 1.5 months, including: * Karat Live Coding – I passed two rounds. The interviewer changed the problem twice mid-session to make it harder, but I solved all versions successfully. *