Atlassian Interview Process 2026 — Rounds, Tips & Questions

What are Airflow Sensors and when would you use a FileSensor vs an HttpSensor vs an ExternalTaskSensor?

Atlassian values "open company, no bullshit" and "play as a team". Describe a situation where you raised a concern about a technical decision that the team had already committed to. How did you raise it, and what happened?

Design Bitbucket's code review system (Pull Requests). Multiple reviewers comment on specific lines of code. The PR is mergeable when all reviewers approve. Cover: diff computation, inline comments anchored to code lines, and what happens when new commits invalidate existing comments.

Design Confluence's page version history. Every edit creates a new version. Users can view any historical version and restore it. Cover: delta vs full-snapshot storage, efficient diff computation, and how you handle concurrent edits creating a branch.

Design Jira's real-time collaborative issue editor (multiple teammates editing the same ticket simultaneously). Cover: Operational Transformation vs CRDTs, conflict resolution, last-write-wins vs merge, and how you persist the final state while keeping latency low for users on slow connections.

Atlassian is fully distributed (no offices). Describe how you have successfully collaborated with engineers in different time zones. What tools and processes made it work and what broke down?

Explain how Jira's JQL (Jira Query Language) parser works. Walk through lexing, parsing, and AST generation. How do you translate a JQL query like "assignee = currentUser() AND status = Done" into an efficient SQL query?

Given a list of Jira sprint start/end dates, find all sprints that overlap with a given date range. Implement an efficient solution using interval trees or sorted arrays with binary search.

Design the search feature for a workspace tool (like Confluence) that indexes millions of documents across thousands of teams, ensuring users only see search results from spaces they have permission to view.

Design the data model for a Kanban board (like Trello/Jira) supporting boards, columns, and cards, where cards can be reordered within and across columns efficiently without renumbering every card on each move.