Autocoder

Atlassian Interview Questions and Answers for SDE Roles

Last updated 2026-11-19

Atlassian's published interview guides describe coding interviews that judge code quality and testing, a system design interview, a management interview and a values interview. This page works through questions for each, with model answers.

The questions are practice in the style of the topics Atlassian's guides describe, not a record of past interviews.

CodingTwo 60-minute interviews, your own IDE, per Atlassian
System design60 minutes
BehaviouralManagement interview and 45-minute values interview
Intern programmeSoftware Engineering Intern roles listed

How the rounds are described

Atlassian publishes engineering interview guides. For standard engineering levels (P30 to P50) they describe two coding interviews of 60 minutes each, screen-shared in your own IDE (a CodePair environment can be provided), a 60-minute system design interview about designing a solution to an established problem with trade-offs, performance and reliability, a 60-minute scenario-based management interview with an engineering manager, and a 45-minute values interview. Senior guides swap in craft or leadership interviews. Atlassian lists roles from entry level through Principal and a Software Engineering Intern programme.

These are the guide's descriptions for experienced levels; early-career and intern processes may differ, so confirm with your recruiter.

Related practice

Practical coding problems in this style are in Atlassian coding round questions. For the process see how to crack the Atlassian interview.

Hiring status

An Atlassian job posting says its India engineering team grew from zero to over 20 engineers in under a year, that it hires from entry level to principal, and that Bengaluru is the main India location. Atlassian also lists a Software Engineering Intern, 2027 Intern India posting (IIT Madras campus) in Bengaluru, reported as posted in July 2026; the posting's own requirements mention a 2028 graduate, so confirm eligibility on the page. See Atlassian hiring for the sourced summary, and apply through Atlassian's own careers site, atlassian.com/company/careers.

Atlassian Interview Questions and Answers for SDE Roles: questions with worked answers

  1. 1

    Design the data model and workflow engine for an issue tracker like Jira.

    hard

    Clarify scope: projects, issues, custom fields, workflows. Model Issue with id, project, type, status, assignee and a flexible fields store (JSON column or entity-attribute table). A workflow is a directed graph of statuses with transitions, each transition having optional conditions (who can move it) and post-actions (notify, set field). Store the workflow per project and issue type, validate every status change against it, and keep an append-only history table for audit and activity feeds. Discuss search with an index separate from the primary store. See system design interview.

  2. 2

    Design a notification service for events such as comments and mentions.

    hard

    Events go to a queue; a notification service looks up recipients and their preferences (channel, frequency, muted projects), deduplicates and batches (digest within a window), renders templates and hands messages to channel workers for email, push or chat. Make delivery idempotent with an event id, retry with backoff, send failures to a dead-letter queue, and respect rate limits per user. Discuss ordering, unsubscribe handling and how you test preferences.

  3. 3

    Atlassian's coding interviews assess code quality and testing. What does good look like?

    medium

    Atlassian's interview guides say the two coding interviews run about 60 minutes each, screen-shared in your own IDE, and assess code quality, testing, conceptual thinking, communication and adaptability. Good looks like: clarify requirements, name things well, small functions, handle edge cases deliberately, write a few tests as you go (or first), and be ready to extend the solution when requirements change mid-interview. Working, readable and tested beats clever and fragile.

    python
    # a small function plus the tests an interviewer would like to see
    def merge_sorted(a, b):
        out, i, j = [], 0, 0
        while i < len(a) and j < len(b):
            if a[i] <= b[j]: out.append(a[i]); i += 1
            else: out.append(b[j]); j += 1
        return out + a[i:] + b[j:]
    
    def test_merge_sorted():
        assert merge_sorted([], []) == []
        assert merge_sorted([1, 3], []) == [1, 3]
        assert merge_sorted([1, 3], [2, 3]) == [1, 2, 3, 3]
    java
    import java.util.*;
    class MergeTest {
        static List<Integer> mergeSorted(List<Integer> a, List<Integer> b) {
            List<Integer> out = new ArrayList<>();
            int i = 0, j = 0;
            while (i < a.size() && j < b.size()) out.add(a.get(i) <= b.get(j) ? a.get(i++) : b.get(j++));
            while (i < a.size()) out.add(a.get(i++));
            while (j < b.size()) out.add(b.get(j++));
            return out;
        }
        public static void main(String[] args) {
            assert mergeSorted(List.of(), List.of()).equals(List.of());
            assert mergeSorted(List.of(1, 3), List.of(2, 3)).equals(List.of(1, 2, 3, 3));
            System.out.println("ok");
        }
    }
  4. 4

    How would you keep a REST API backwards compatible as it evolves?

    medium

    Only add, never remove or repurpose: new optional fields and new endpoints are safe, but removing fields or changing meaning breaks clients. Version the API (path or header) for breaking changes, support old versions for a stated deprecation period, and publish a changelog. Clients should ignore unknown fields. Use contract tests against example consumers, and run old and new versions side by side during a migration.

  5. 5

    How do collaborative editors let several people edit the same page?

    hard

    Two main approaches. Operational transformation sends edit operations to a server that transforms concurrent operations against each other so all replicas converge. CRDTs give each character or element a unique ordered identifier so operations commute and merge without a central transformer, at the cost of more metadata. Both need a way to handle offline edits and conflicts. A good answer states the convergence requirement and one trade-off.

  6. 6

    SQL or NoSQL for an activity feed?

    medium

    A feed is append-heavy, read in reverse time order, and usually accessed by a key such as user or project, which suits a wide-column or document store partitioned by that key with time-ordered clustering. A relational database works well at modest scale with an index on (project_id, created_at) and is easier for ad hoc queries and consistency. Decide using access patterns, scale, and consistency needs rather than preference, and say what you would measure.

  7. 7

    How would you cache a read-heavy page and keep it correct?

    medium

    Put a cache in front of the database (and possibly a CDN for public content). Use cache-aside: read from the cache, on a miss load from the database and store with a TTL. Invalidate or update on writes, and discuss stale reads and stampedes when a hot key expires. Key by permission scope when content varies by user. Measure hit rate, and avoid caching data that must be immediately consistent.

  8. 8

    How do you give and receive feedback in code review?

    easy

    Atlassian's engineering guides include collaboration, so answer with concrete habits. As an author: small pull requests with context and tests, welcoming questions. As a reviewer: ask questions before assuming mistakes, separate must-fix from suggestions, praise good work, and review promptly. If you disagree, discuss the trade-offs and the goal, not personal preference, and agree a standard so the argument is not repeated.

  9. 9

    Tell me about a project where you owned the outcome from start to finish (management interview).

    medium

    Atlassian's guides describe a scenario-based management interview covering ownership, impact and collaboration. Pick a project where you drove the goal, not just the code: how you scoped it, handled a surprise or dependency, kept people informed, measured the effect and what you would do differently. Be exact about your own decisions. Use the structure in the behavioural interview guide.

  10. 10

    Tell me about a time you were open about a mistake or a problem.

    medium

    This maps to Atlassian's values interview, which is behavioural. Choose a case where you raised a problem early, even though it was uncomfortable: a missed estimate, a bug you introduced or a risk nobody had named. Explain how you told people, what you proposed and what happened. Show that openness led to a better outcome for the team or customer.

  11. 11

    Tell me about a time you improved how your team works.

    easy

    Describe a pain point (slow reviews, flaky tests, unclear handovers), how you gathered evidence, what you proposed and how you got others to adopt it, then the measured effect. Improvements others adopt are more convincing than ones you did alone. Give a number if you can, such as build time or review turnaround.

Frequently asked questions

How many coding rounds does Atlassian have?

Atlassian's guides for standard engineering levels describe two 60-minute coding interviews, alongside system design, management and values interviews.

Can I use my own IDE?

The guides say coding interviews are screen-shared in your own IDE, and a CodePair environment can be provided.

What is the Atlassian values interview?

A 45-minute behavioural interview that assesses how you work against the company's values. Prepare real stories.

Where can I check Atlassian's openings?

See Atlassian hiring and Atlassian's careers site.

Sources

Related guides

More in Company Interview Questions

See all in this section