Atlassian interview process (2026)

Round-by-round breakdown of the Atlassian software engineering interview across 4 levels and 26 rounds: interview mode, sample questions, and worked solutions.

Atlassian salary & ratings · All interview processes

Software Engineer Intern (SDE Intern, Summer, ~8 weeks / up to 6 months)

Difficulty: Medium · Timeline: 3-6 weeks · Recommended prep: 6-8 weeks · Cooldown: No formally published intern cooldown. Candidate reports sug

  1. Round 0: Online Assessment (HackerRank coding test)

    Assessment · 90 minutes · difficulty 2/5 · elimination round

    Mode of interview: Online assessment · HackerRank

    Sample question: Group Anagrams — Given an array of strings, group the anagrams together (words that use exactly the same multiset of letters). Return the groups in any order.

  2. Round 1: Technical Coding Interview

    Phone · 45-60 minutes · difficulty 2/5 · elimination round

    Mode of interview: Remote phone or video interview

    Sample question: Number of Islands — Given an m x n 2D binary grid where '1' is land and '0' is water, count the number of islands. An island is a group of adjacent lands connected 4-directionally (horizontally or vertically), and the grid is surrounded by water on all edges.

  3. Round 2: Manager & Values Round (Behavioral)

    Behavioral · 45-60 minutes · difficulty 2/5

    Mode of interview: Live behavioral interview

Software Engineer / SDE (P4) — Bengaluru

Difficulty: Medium · Timeline: ~4-6 weeks · Recommended prep: 4-8 weeks · Cooldown: ~6-12 months

  1. Round 0: Recruiter / Exploratory call

    Phone · 15-30 min · elimination round

    Mode of interview: Remote phone or video interview

  2. Round 1: Online Assessment (HackerRank) — campus/entry path

    Assessment · ~90 min · difficulty 2/5 · elimination round

    Mode of interview: Online assessment

    Sample question: Design Snake Game — On a width x height board, implement a snake that starts at the top-left cell and processes a sequence of moves (U/D/L/R). It eats food in the given order (each eaten food grows the snake by 1). The game ends (return -1) if the snake hits a wall or its own body. Return the final score.

  3. Round 2: Coding Interview — Data Structures

    Onsite · ~45-60 min · difficulty 2/5

    Mode of interview: Onsite or virtual onsite interview

    Sample question: Stock Price Fluctuation — Design a data structure over a stream of (timestamp, price) records where any timestamp may be corrected later. Support update(timestamp, price), current() (price at the latest timestamp), maximum() and minimum() over the currently-valid prices.

  4. Round 3: Code Design / Low-Level Design

    Onsite · ~45-60 min · difficulty 2/5

    Mode of interview: Onsite or virtual onsite interview

    Sample question: Design a Tagging System (tag content across Jira/Confluence/Bitbucket/Trello) — Design a service that lets users attach and query free-form tags on entities (Jira issues, Confluence pages, Bitbucket PRs, Trello boards). Focus on the REST API (create/attach/detach/search-by-tag), the many-to-many tag<->entity data model, a top-K popular-tags dashboard, autocomplete, caching, and pagination at ~100M tag requests/day.

  5. Round 4: System Design

    System_design · ~60 min · difficulty 2/5

    Mode of interview: Live system design interview

    Sample question: Design a Confluence Engagement Feed / Top-N Popular Content — Design a system that surfaces an engagement-ranked feed of recently active Confluence content (or the top-N most popular pages/posts in a workspace). Cover event ingestion (views/edits/likes), the ranking signal, caching of computed feeds, and freshness vs. cost trade-offs.

  6. Round 5: Values interview

    Behavioral · ~45 min · difficulty 1/5

    Mode of interview: Live behavioral interview

  7. Round 6: Manager interview

    Behavioral · ~45 min · difficulty 1/5

    Mode of interview: Live behavioral interview

  8. Round 7: Hiring committee review

    Offer · async

    Mode of interview: Offer discussion

Senior Software Engineer (P5) — Bengaluru

Difficulty: Hard · Timeline: ~4-6 weeks · Recommended prep: 6-10 weeks · Cooldown: ~6-12 months

  1. Round 0: Recruiter / Exploratory call

    Phone · 15-30 min · elimination round

    Mode of interview: Remote phone or video interview

  2. Round 1: Karat technical screen

    Phone · ~60 min · difficulty 2/5 · elimination round

    Mode of interview: Remote phone or video interview

    Sample question: All O'one Data Structure — Design a structure supporting inc(key), dec(key), getMaxKey() and getMinKey(), all in O(1). inc increments a key's count (adding it at 1 if new); dec decrements (removing at 0). getMax/getMin return any key with the largest/smallest count, or empty string if none.

  3. Round 2: Coding / Data Structures (loop)

    Onsite · ~45-60 min · difficulty 3/5

    Mode of interview: Onsite or virtual onsite interview

    Sample question: Logger / Sliding-Window Rate Limiter — Implement a rate limiter allowing at most L requests within any window of W time units for a client. Given a stream of non-decreasing request timestamps, print 'true' if the request is admitted, else 'false'. Discuss fixed-window vs. sliding-window log trade-offs.

  4. Round 3: Code Design / LLD (loop)

    Onsite · ~45-60 min · difficulty 3/5

    Mode of interview: Onsite or virtual onsite interview

    Sample question: Design Real-Time Collaborative Editing (Confluence / Google-Docs-like) — Design the core of a multi-person real-time collaborative document editor: concurrent conflict-free edits, cursor/presence, version history and rollback, and sharing. Discuss Operational Transformation vs. CRDT, the WebSocket sync protocol, and consistency guarantees.

  5. Round 4: System Design (loop)

    System_design · ~60 min · difficulty 3/5

    Mode of interview: Live system design interview

    Sample question: Design a Multi-Tenant Issue-Tracking System (Jira-like) — Design a multi-tenant Jira: users/projects/issues, configurable workflows, per-organization custom fields. Discuss tenancy isolation (single DB with org_id vs. sharded), extensible schema (relational core + JSONB for custom fields with indexing), and scaling reads.

  6. Round 5: Manager interview (loop)

    Behavioral · ~45 min · difficulty 2/5

    Mode of interview: Live behavioral interview

  7. Round 6: Values interview (loop)

    Behavioral · ~45 min · difficulty 1/5

    Mode of interview: Live behavioral interview

  8. Round 7: Hiring committee review

    Offer · async

    Mode of interview: Offer discussion

Principal Software Engineer (P6) — Bengaluru

Difficulty: Hard · Timeline: ~5-8 weeks · Recommended prep: 8-12 weeks · Cooldown: 6-12 months

  1. Round 0: HR / Recruiter screen

    Phone · ~30 min · elimination round

    Mode of interview: Remote phone or video interview

  2. Round 1: System Design (loop)

    System_design · ~60 min · difficulty 4/5

    Mode of interview: Live system design interview

    Sample question: Design a Web Crawler / Image-Scraping System — Design a distributed web crawler that, given seed/URL lists, fetches pages (variant: crawl the given URLs for images and store only image URLs), respects politeness/robots, dedupes URLs, and scales to billions of pages. Cover the frontier queue, dedup (bloom filter), scheduling, storage and failure handling.

  3. Round 2: Leadership & Craft / Strategy

    Behavioral · ~45-60 min · difficulty 3/5

    Mode of interview: Live behavioral interview

  4. Round 3: Values interview

    Behavioral · ~45 min · difficulty 2/5

    Mode of interview: Live behavioral interview

  5. Round 4: Coding / Data Structures (loop)

    Onsite · ~60 min · difficulty 3/5

    Mode of interview: Onsite or virtual onsite interview

    Sample question: Closest Common Parent Group (LCA of a set of nodes in an org hierarchy) — Given an N-ary org hierarchy (each node has one parent; groups contain sub-groups and employees) and a target SET of employees, return the deepest group that is an ancestor of all targets — i.e., the lowest common ancestor of the whole set.

  6. Round 5: Low-Level Design (loop)

    Onsite · ~60 min · difficulty 3/5

    Mode of interview: Onsite or virtual onsite interview

    Sample question: Design a Cloud File-Storage & Search System (Drive/Dropbox-like) — Design a cloud file-storage service supporting upload/download, folder hierarchy, sharing/permissions, and full-text/metadata search over stored files at scale. Cover blob storage + metadata store, chunking/dedup, the search index, and consistency of metadata vs. object store.

  7. Round 6: Hiring committee review

    Offer · async

    Mode of interview: Offer discussion

Other companies' interview processes

Worked sample solutions (code, design diagrams, and STAR answers) for every round are available in the FAANGPlus app: open interview processes.