J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Atlassian en sept. 2018
Entretien
Very pleasant and genuine process with Atlassian here. I had an initial call with recruiter from Spain as she headhunted my profile for position in Sydney office. They are open in mentioning that they provide relocation benefits/visa for your whole family (so you and your spouse can work in Australia). The recruiter discussed about the process which will take everything done remotely, no onsite i’m assuming.
The first interview was regarding pair coding via Bluejeans with Java. I was asked to share my screen. Given a simple factory pattern OOP classes with JUnit tests, i was asked to work on creating tests and fix bugs that is separated into 4 different questions. I remember the interviewers was very kind and told a few tips for me to be less nervous. It ended with open troubleshooting question as the time was nearing an end.
I was told to wait 1-2 days for the feedbacks and it came through. Although even able to understand and work on the coding questions, unfortunately i was a bit slower than expected as i didn’t do pair coding that often. The feedback was very detailed and thorough, this shows how much attention spent by interviewer.
Although i didnt get the position, i had a pleasant time going through the process with Atlassian.
J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Atlassian (McLean, VA)
Entretien
2 interviews in 1 day at the start, one technical and one design. Both were done with proctors who asked questions surrounding the existing team I would be joining. I don't think the interview process was difficult and appreciated the discussion I had during the design interview.
Questions d'entretien [1]
Question 1
How would you design a system to handle rate limiting for an API?
J'ai postulé en ligne. Le processus a pris 2 mois. J'ai passé un entretien chez Atlassian
Entretien
Two screening calls, one interview prep call, and six rounds of interviews. Coding rounds were very much of the "gotcha" variety. Beyond the basic requirements outlined at the start each had an additional, opinionated requirement, and there's no way to discover what that is until it's too late to refactor. If your solution (one of many possible, each with tradeoffs) contains the magic thing, Atlassian lets you through. Otherwise you're out.
Atlassian runs a large number of candidates through the interview process, then runs something closer to a lottery than an evaluation in order to whittle down the numbers. Not good for the candidates OR their employees having to constantly run interviews!
Questions d'entretien [1]
Question 1
Coding rounds were for a middleware URL router and a multi-user rate limiter.