Stage 1. Online screening test (timed 90 mins) - Solve algorithmic programming problems. My advice is to practice a few questions on the platform that they used to issue the test and get comfortable with the platform/programming language. Read all the available questions first and pick the easiest questions to complete first, this will help you get the momentum. You do not need to complete all questions successfully to pass this round (you just need to score enough points). Stage 2. Skype chat session (approx. 30 mins) - A quick and friendly chat with the internal recruitment staff. He/she will set up your expectation for the role and sells you the Atlassian culture (if you were not already sold before you started). No major decisions are made in this round so don't sweat it. Stage 3. Peer programming session (approx. 90 mins) - This is your chance to meet a member of the Atlassian team where you will do some programming exercises in a pair programming environment. You should have been asked about your preferred programming IDE and OS to perform this test. If you were not asked, make sure you specify before the day because you just do not want to be caught with a unfamiliar IDE/OS. Your peer will test your programming skills as well as your test-driven-development practices, so remember to write clear, simple test cases first. Don't be afraid to ask questions and don't make any assumptions about what the code is trying to do. Don't over engineer the solution, keep it simple (and dirty if need be). Some people try to re-factor the code, make it generic, etc. but end up wasting a lot of time. Don't do that, just use simple logic, use for loops, use whatever it takes to first solve the problem, then you can optimise it later. Stage 4. Two-on-one face-to-face session (approx. 120 mins) - Here you meet two other members of the Atlassian team in an all-out brain picking session. Stage 4.1. They will focus on your previous experiences, fails, lessons learnt and everything in between. The session is unstructured and questions will be fired at you in quick successions. Your best friend in this session is to take your time to answer the questions and don't let the pace cause you panic. The more questions you answer badly, the more you will be under fire, so answer each question with due diligence, with depth and stay within the context of the question. Stage 4.2. There will be a mini technical question which they will ask you to solve on a white-board. This is a problem solving exercise that will test your approach to a open-ended problem. This exercise will require around 20 - 30 mins to do, so keep an eye on the time during your interview. If your interviewers have not reach this part after 120 mins of talking, then you are in trouble! The problem here is that they will push ahead with the problem solving activity and give you 5 minutes to sweat it out, and this will not end well. This unfortunately was my failing and was where I was knocked out. Stage 4. Face-to-face session with management team. See other reviews for details because I didn't make it this far. Here are some of the issues I found with the Atlassian recruitment process. Issue 1. Atlassian somehow thinks that all candidates that apply for a role there do not have other commitments apart from applying for work. Most of the interviews were scheduled between 9 AM - 5 PM, this is bad news for those of just that are currently holding down a full-time job and cannot take time off especially for a recruitment process as notoriously long drawn out as Atlassian's. Issue 2. Your chances of getting an offer at Atlassian has a lot to do with luck! This was not apparent to me because I did not visit or read any of the reviews here on glassdoor before going in, but there is an apparent pattern emerging from the reviews. At every stage of the recruitment process, from the point of contact (internal recruiter) to the peer-programming task to the face-to-face session, the experience is different for everyone because it all depends on who you get as your interviewer. If you are lucky, like myself, you will have an awesome point of contact, a great peer programming partner, and unluckily, two very nonchalant face-to-face interviewers. Others have been lucky with face-to-face interviewers but a unprofessional and incompetent point of contact. Just because you are a genius programmer, that does not make you a great interviewer, but an unprofessional and incompetent point of contact is inexcusable Atlassian.