Frontend

Engineering
Interview Guide

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:

·  Two coding interviews

·  One system design interview

·  One management interview

·  One values interview

To fully understand which stage of the interview process you’re in and what’s expected, we
recommend thoroughly reviewing each email your coordinator sends.

Our interview process is broken up in to three stages. This means your interviews will be scheduled
in three stages to progress you effectively.

System
Coding 1 Coding 2 Management Values
Design
(60 min) (60 min) (60 min) (45 min)
(60 min)

STAGE 1 STAGE 2 STAGE 3

Following the completion of each stage, your Recruiter will be in touch and let you know whether
you will be progressing to the next round of interviews.
Interview details and preparation
CODING INTERVIEWS

For browser coding

This interview requires you to write and execute code in a browser environment, building a simple
interactive user interface. Be prepared with an IDE set up on your computer that is suitable for the
framework you are most familiar and comfortable with. Please set up enough so that you can print
the current time (when initially loaded) on a page in your browser, as a starting point.

For JavaScript coding

This interview requires you to write and execute code in an environment where you can see the
logged output of your code. Be prepared with an IDE set up on your computer that is suitable for
the framework you are most familiar and comfortable with. Please set up enough so that you can
see the log of the current time when your program is run, as a starting point.

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. Your environment setup is not
part of the interview.

Each 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.

·  Please download Zoom prior to your interview as you will utilize 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.

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.

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,
or 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.
MANAGEMENT INTERVIEW

The Management Interview is a 60-minute interview with one of our engineering managers that
will focus on how you approach various aspects of your role in a team environment. 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.

How to prepare:

Think about project(s) that best represent the scope of work where you have had measurable
impact, learned lessons and felt stretched. These projects don’t always have to be your best
or most recent 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 learned 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.
VALUES INTERVIEW

The Values interview is 45 minutes and includes a set of behavioral interview questions, aimed at
assessing how your thought process and actions are aligned with our core set of company values.

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-centered’? How have you put the customer
first? What trade-off(s) did you make to do this?

Open company, no bullsh*t

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 privatization and decision making? What are
examples when you or the team have missed the mark? How did you
react? How did you approach fixings things?
Team Match:

Once you have completed the Management & Values stage, your feedback is then reviewed
and evaluated by our unbiased Hiring Committee. Successful candidates will progress
through to our Team Match process at which point, you have the opportunity to meet
with the Hiring Manager(s) who have open roles via a Team Match Call, and will have the
opportunity to select a preferred team before a final offer.

Purpose of the Team Match Call

The purpose of the Team Match Call is to connect you with a Hiring Manager(s), who will
provide a brief introduction about their team. The main focus of the call should be to address
questions you have regarding the team you will be joining, and your role within it. This is not
an interview and is designed to be a mutual matching process.

Take advantage of this opportunity to seek clarification on any and all questions, to ensure
you feel supported and prepared to inform your decision around which team you’ll choose to
join. You will then have a 24 hour time frame to make a decision once teams are presented
to you.

What Teams are hiring?

Hiring teams are based on business priorities and may be subject to change. This is why we
complete the assessments and interview components first.
FINAL HELPFUL TIPS

Research

As with any interview, showcasing you’ve done some research will help you and the interviewer
get the most out of your time together. We suggest reviewing your interviewers on LinkedIn and
researching Atlassian to get a good feel of our culture and values.

Questions

Your interviewer will provide you with adequate time to ask questions so we recommend coming
prepared with questions/topics you’d like to learn more about. If for any reason there is a question
you don’t get the opportunity to ask during the interview, please reach out to your recruiter or
coordinator who can assist you.

As a side note, we run Global ShipIt days and our engineers love to talk about these - feel free to
watch a video on them here.

Finally, we want to ensure you have the very best possible candidate experience with us at
Atlassian, so please let us know if you need any accommodations or adjustments for your interview.

Best of luck!
Disclaimer
Atlassian reserves the right to amend and/or supplement the mentioned policies and/or programs
at any time at Atlassian’s discretion. If there are matters mentioned in this overview that are
covered by more specific policies with extended details and/or instructions, those specific policies
will prevail.

©2023 Atlassian. All Rights Reserved. CSD-8648_DRD-12/23