Welcome! We’re excited to have you interview with our team.
For your upcoming interviews, we want to ensure you’re adequately
prepared for each step of the process.
Our engineering process consists of the following:
One Coding Interview
INTERVIEW One System Design Interview
PROCESS
One SRE Craft Interview
One Values Interview
One Management Interview
To fully understand which stage of the interview process you’re
in and what’s expected, we recommend thoroughly reviewing
each email your CX Coordinator sends.
Coding Interview
This interview requires you to write and execute code.
Be prepared with an IDE set up on your computer that is suitable for
your chosen language - the one you are most familiar and
comfortable with. You will screen share this with your interviewer. If
you are not able to have an IDE set up on your own computer, let us
know prior to the start of the interview and we will have a CodePair
environment ready for you.
The coding interview is capped at 60 minutes and is structured to
help demonstrate coding skills, code quality, and conceptual
thinking. Atlassian’s interviews also assess for adaptability in an
ever-changing environment, navigating blockers, and
communication style.
How to prepare:
If you need a CodePair environment setup please reach out to
your CX Coordinator prior to the interview and they will
arrange this for you in advance
Use an IDE and computer you are familiar with to make the
most efficient use of your time in the interview. If you are
coming onsite and don’t have a laptop, please let your
coordinator know and they will arrange a laptop for you.
INTERVIEW Please download zoom prior to your interview as you will
PROCESS
utilise this to share screens during the interview, whether this
is onsite or remote
If your interview is a zoom interview, find a quiet and
comfortable space with consistent internet access. Log on
~10 minutes early to ensure all systems and hardware are
working correctly
Using a debugger is welcome and encouraged
Communication:
Demonstrating how you think and approach problem solving is
equally important as the end result. Please communicate with
your interviewer throughout each session, so they understand
your thought process.
Testing:
We want to see best practice and testing is crucial to success in
the code task. If you haven't tested in a while, we strongly
recommend brushing up on testing, in particular the TDD
approach.
Problem Solving:
Because problems are rarely limited to a single solution, please
showcase all possible solutions and why the approach you
selected is the best fit. Highlighting other solutions helps the
interviewer understand your thought process.
System Design Interview
The system design portion of the interview is also 60 minutes. The
purpose of the system design interview is for you to demonstrate
technical depth, breadth, and proficiency through designing a solution
to an established problem. Your interviewer will be looking at your
problem-solving thought process, decision making and operational
considerations such as performance and reliability.
INTERVIEW
PROCESS How to prepare:
Seek first to understand:
You’ll be asked to design a solution for a technical problem on a
whiteboard or paper — starting with fundamentals and then building
in complexity. Ask any clarifying questions upfront to ensure you
understand the problem and then continue to communicate with your
interviewer as you progress towards a solution. If your interview is via
zoom, ensure you have a paper and pen available for the technical
problem, alternatively, you can use the whiteboard function in zoom.
Another option is to screen share an editor or drawing tool of your
choice.
Communication:
We want to understand your approach to problem-solving and how
you draw from past experiences when designing something new. Keep
the customer in mind and how your solution might perform and scale.
SRE Craft Interview
The SRE Craft portion of the interview is 60 minutes.
The SRE Craft Interview focuses on the specific skills and capabilities
required in an Atlassian Site Reliability Engineer. Using a generic
system diagram with its basic functions that will be presented to you,
you will first talk about how to assess the health of this system, then
move to troubleshoot a problem that is presented to you. The last part
of the interview will focus on reliability metrics and practices.
To prepare for the interview, think through these 3 aspects of an SRE
role and make sure you communicate your thought process as the
interviewer guides you through this interactive session.
Values Interview
The Values interview is 45 minutes and includes a set of behavioural
interview questions, aimed at assessing how your thought process
and actions are aligned with our core set of company values.
INTERVIEW
PROCESS How to prepare:
We recommend reviewing Atlassian's values and use them as the
foundation of your preparation. Come prepared with relevant
examples/stories of how you've demonstrated living these values in
your current or previous roles and projects.
Be the change you seek
When have you advocated to push for change? What did you learn
from this process? What was the outcome?
Play, as a team
How do you work with other people? How have you helped make a
team/individual more successful if they weren’t performing well? Have
you ever had to put the team’s goals above personal ambitions?
Don’t #@!% the customer
How is your mentality ‘user-centred’? How have you put the customer
first? What trade-off(s) did you make to do this?
Open company no bullshit
What's your approach when having difficult conversations? How have
you resolved conflict in the past? Have you adapted your
communication style to achieve a better outcome in a potentially
negative situation?
Build with heart and balance
How do you think about prioritisation and decision making? What are
examples when you or the team have missed the mark? How did you
react? How did you approach fixing things?
Management Interview
The Management Interview is a 60-minute interview with one of
our engineering managers that will focus on your non-technical
skills. Here we will be looking to understand how you approach
the non-technical aspects of your role in a team environment
and what motivates you! Our questions will be scenario-based,
so please come prepared with examples that demonstrate your
experience across one or more projects that you have been a
part of or have led.
INTERVIEW
PROCESS
How to prepare:
Think about project(s) you have been involved in where you have
had impact, learnt lessons and felt stretched. These projects
don’t always have to be your best ones. In addition, think about
times in your career where you have had to work together with
other teammates, teams or customers to achieve meaningful
outcomes together.
This will be a structured interview where we will ask questions
that will dig into four primary areas:
Your ability to drive outcomes across the software
development lifecycle
How you apply lessons learnt on the job and share them
Your ability to manage conflict across various situations
How you take initiative, lead and inspire in your role
In addition to the above, we are keen to understand how you
collaborate with your teams and get a deeper sense on your
passions and ambitions to ensure the role is in fact the right one
for you!
While we want to learn everything about you, we also want to
give you the opportunity to learn more about us. We will leave
10 minutes at the end of the interview for you to ask questions
about what’s important for you.
