J'ai postulé en ligne. Le processus a pris 2 mois. J'ai passé un entretien chez Atlassian (Sydney) en août 2017
Entretien
One of the best recruitment process I have ever gone through.
Applied online for SRE Summer Internship. Then shortlisted after resume review. Three stages after this:
a. Coding Test- Standard coding and algorithmic questions in Python.
b. Phone Interview- Experience check/confirmation, behavioural interview, cultural alignment with Atlassian, side projects and interest in Software/Site Reliability.
c. Onsite Interview- Comprises of 3 stages:
1. Technical knowledge interview: This checks your experience and knowledge of Operating Systems, OOP, Algorithms, Python and Networking. A few questions were quite hard and required strong understanding of concepts to be able to answer correctly.
2. Project Description: Explain in depth the design of a current or previous software project. Choose a project that of which you can show off all the technical details, explaining what your role was. It should be a good quality and big project.
3. Coding Test: Understand a REST API on the spot by referencing the documentation provided. Then operate on it in different ways to get the desired output as asked from the interviewers. Need to obtain and process different JSON responses to answer different questions correctly.
Got an offer 2 business days later.
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.