Start practising

INTERVIEW PREP · AUSTRALIA, US AND INDIA

Atlassian software engineer interview

The rounds at each level, what interviewers score, the Company values, and the questions candidates report, linked to problems you can solve here with the editor, walkthrough video and solutions in four languages.

Based on public candidate reports and Atlassian's own careers pages, checked November 2026. Processes vary by team and change over time. AlgoRung is not affiliated with Atlassian.

Track my Atlassian prep Jump to questions
Your level

Levels

AlgoRung levelAtlassian titleExperienceInterviews after screeningDesign rounds
SDE 1P30 Graduate / entry Software EngineerNew grad to about 2 years about 3Yes
SDE 2P40 Software EngineerAbout 2 to 5 years about 5Yes
SDE 3P50 Senior Software EngineerSenior, about 5 to 10 years about 5Yes
SDE 4P60 Principal, P70 and aboveStaff, principal and above about 5Yes

The rounds, in order

Pick your level above to see only your rounds. Each step links to a guide on how that round is scored.

  1. Phone / recruiter screen · 30 min

    A recruiter call about background, motivation, location and pay, where the target level gets set.

    All levels

  2. Phone / recruiter screen · 60 min

    An outsourced interviewer (Karat) runs it: about 20 minutes of quick-fire design or fundamentals questions, then one or two easy-to-medium coding problems.

    SDE 2, SDE 3, SDE 4

  3. Online assessment · 90 min

    Intern and graduate candidates report a timed test with two or three DSA problems before any live interview.

    SDE 1

  4. Coding (DSA) · 60 min

    The 'Data Structures' half of the coding interview: an algorithm problem with follow-ups, scored on clean code, naming and testing your own work without being asked.

    All levels

  5. Low-level design / machine coding · 60 min

    The 'Code Design' half: build a small working component that can be extended, such as a popularity tracker, then handle new requirements, tie-breaks and concurrency.

    All levels

  6. System design (HLD) · 60 min

    A systems design discussion with no coding, where the interviewer adjusts the follow-ups to see how you adapt to new trade-offs.

    SDE 2, SDE 3, SDE 4

  7. Hiring manager · 60 min

    One past project in depth, ownership, mentoring and how you collaborate.

    SDE 2, SDE 3, SDE 4

  8. Behavioral · 45 min

    The values interview, usually led by someone outside engineering, with roughly one question per value and probing follow-ups.

    All levels

  9. Hiring committee

    An independent committee reviews all the feedback and the CV and makes the final call.

    All levels

  10. Team match · 30 min

    Approved candidates are sometimes placed on a team only afterwards, and some wait weeks for a match.

    SDE 2, SDE 3

ScreeningCodingDesignBehavioralDecision

What interviewers look for

  • Readable, production-quality code rather than clever one-liners
  • Testing your own code without being prompted
  • Explaining trade-offs out loud
  • Design that extends cleanly when new requirements arrive
  • Owning a past project end to end and why it mattered
  • Real examples, with humility, behind each value

Topics to focus on

Weighted by what candidates say comes up and by the reported questions below.

Behavioral: Company values

A dedicated values interview tests fit with all five values, usually one question per value, led by an interviewer from another department. Strong technical scores do not make up for a weak values result.

Open company, no bullshitDisagreement and candor

Disagree with data, respectfully, then commit fully once the decision is made.

  • Tell me about a time you disagreed with your manager. What happened?
  • Describe a decision you argued against but then had to carry out.
  • Tell me about the hardest feedback you have given or received.
Build with heart and balanceCollaboration and inclusion

Show how you helped others succeed and made people feel they belonged.

  • Describe a decision you argued against but then had to carry out.
  • Tell me about a time you helped a teammate succeed.
  • Describe a project that needed several teams. How did you get them aligned?
Don't #@!% the customerCustomer focus

Start from a real user problem and show how your decision changed something for them.

  • Describe a time you changed a plan because of what you learned about the user.
  • Tell me about a time you had to balance a customer need against a technical constraint.
Play, as a teamCollaboration and inclusion

Show how you helped others succeed and made people feel they belonged.

  • Describe a decision you argued against but then had to carry out.
  • Tell me about a time you helped a teammate succeed.
  • Describe a project that needed several teams. How did you get them aligned?
Be the change you seekInvention and simplification

Show a simpler or new way of doing something and the measurable result.

  • Tell me about a time you simplified a complex process or system.
  • Describe an idea of yours that the team adopted.
  • Tell me about the most ambitious project you have proposed.

All behavioral questions · Write your STAR stories in the story bank

Coding questions candidates report

Each links to the AlgoRung problem: write-up, animated walkthrough, solutions in Java, Python, C++ and JavaScript, and an editor with hidden tests. Shared questions show the other companies that ask them.

Difficulty
Topic
3 questions
  1. Lowest Common Ancestor of a Binary Tree Medium Trees & BST also Google, Meta, Netflix +1
  2. Merge Intervals Medium Intervals also Netflix, LinkedIn, Oracle
  3. Two Sum Easy Arrays & Hashing also Amazon, Microsoft, Swiggy

Atlassian coding questions by topic · Atlassian SDE 1 interview · Atlassian SDE 2 interview · Atlassian senior interview · Atlassian staff interview

Also reported, not on AlgoRung yet (2)

Rank Teams by Votes · Design Snake Game

Design questions

Every level gets a code design (LLD) round where you build and extend working code. P40 and above add an HLD round, usually framed around collaboration products like issue trackers and wikis. At P50 and P60 the bar shifts to deep trade-offs, scaling and cross-team impact.

Also reported: Popularity tracker with tie-breaks (LLD)

Atlassian system design questions in detail · How to answer any design question: the LADDER method

Worth knowing

Interviewing at Atlassian?

Add the date and your level. AlgoRung builds a plan back from the interview day, schedules revisions before it, and counts problems you have already solved for every company that asks them.

Start my Atlassian plan

Sources

Written in our own words from these public pages and candidate reports, checked November 2026. Company names are trademarks of their owners.

All companies