Atlassian Interview Experiences

Overview

How Atlassian interviews actually run, based on candidate reports (Blind, Glassdoor, Reddit) and Atlassian’s own early-careers hiring guide. Team and level shift the exact mix, so treat this as a prep map.

It's a Graduate Program, not a placement day

Atlassian hires India graduates and interns through a rolling Graduate Program (recruiting window roughly July-December, start date in July) out of its Bengaluru office - the team behind Jira, Confluence, Bitbucket, and platform tooling. There’s no single fixed-date drive across colleges, so applying early in that window matters more than waiting for a “placement day,” and no fixed CGPA cutoff is published. Check current requirements on Atlassian’s early-careers page rather than trusting a forwarded cutoff number.

Reported total compensation for an India-based, entry-level Software Engineer (Atlassian calls this level P30) clusters in the roughly ₹33-50 LPA range per self-reported aggregator data (levels.fyi), with a reported median near ₹40-41 LPA - treat this as a rough, self-reported band, not a guaranteed offer, since it shifts with role, location, and hiring cycle.

How to use this page

Read the round table first, then the experiences. Practise DSA with a focus on narrating your approach, keep one practical system design answer ready, and prepare a separate professional story for each of Atlassian’s five values so the values round doesn’t catch you reusing material.

Round-wise process

Round	Duration	What it tests
Recruiter screen	20-30 min	Background, motivation, comp expectations, logistics
Online Assessment (campus/grad)	90 min	2-3 coding problems on HackerRank
Technical screen (Karat, experienced hires)	45-60 min	Rapid-fire fundamentals (OS/networking) + 1-2 coding problems
Onsite - Coding (x2)	45-60 min each	DSA (LeetCode medium), code design, communication
Onsite - System design	45-60 min	Practical design: task list, job scheduler, notification system
Values interview	~45 min	Alignment with Atlassian’s 5 published values
Managerial / hiring manager	30-45 min	Team fit, career goals, closing

Real interview experiences

Experience 1: Software Engineer, Graduate Program (2025)

Profile: B.Tech CSE, ~8.2 CGPA, tier-2 college, one internship, applied through Atlassian’s rolling Graduate Program listing for the Bengaluru office

Online Assessment

• 90-minute HackerRank test, 3 problems of increasing weightage. The easiest was a straightforward string/array problem; the hardest needed a graph traversal.
• Shortlist result arrived within about a week.

Technical interviews (2 panelists each)

• Coding: longest substring without repeating characters, expected sliding window + hashmap; the interviewer pushed on edge cases (empty string, all-repeated characters) more than the first pass.
• A separate round mixed a binary tree level-order traversal (BFS) with OS/DBMS-flavoured questions - process vs thread, indexing basics.
• Both rounds included a project deep-dive: architecture choices, the hardest bug encountered, and what the candidate would rebuild differently.

Values interview

• “Tell me about a problem nobody asked you to fix, that you fixed anyway” (Be the change you seek)
• “Describe a time you gave direct feedback to a teammate instead of staying quiet” (Open company, no bullshit)
• Kept answers to a clear situation-action-result structure rather than a rehearsed speech.

Result: Selected What helped: Narrating the approach before coding, and having one values story ready per value rather than one generic “teamwork” story stretched across every question.

Experience 2: Senior Software Engineer, experienced hire (2024-2025)

Profile: ~4 years’ experience, applied off-campus via a referral for a P40-level backend role

What differed from the campus track

• Recruiter screen led straight into a Karat-run technical screen: a handful of rapid-fire fundamentals (TCP vs UDP, process vs thread) followed by one LeetCode-medium coding problem - the interviewer worked for Karat, not Atlassian.
• Onsite system design leaned into a job-scheduler-style problem: API shape, retry/failure handling, and data model, kept at a practical scope rather than a hyperscale distributed-systems discussion.
• A separate managerial round closed the loop: team fit, what kind of problems the candidate wanted next, and logistics.

Mistakes that hurt other candidates in the same hiring cycle

• Jumping into code before clarifying constraints on the Karat screen
• Treating the values round as a formality and reusing one story across every value
• System-design answers heavy on buzzwords with no concrete data model or failure mode

Result: Selected after the managerial round Takeaway: A clean, well-communicated DSA round plus five distinct, honest values stories mattered more than raw years of experience in this loop.

Questions that come up often

Coding / technical

1. Longest substring without repeating characters - sliding window + hashmap
2. Binary tree level order traversal - BFS
3. Detect cycle in a directed graph - DFS colouring / topological sort
4. Design an LRU cache
5. Merge intervals / overlapping intervals
6. Rapid-fire fundamentals on the Karat screen: OS, networking, complexity analysis

System design

1. Design a task list / simplified ticketing (Jira-style) board
2. Design a job scheduler or background-task queue
3. Design a notification system for a collaboration tool
4. Design a simple URL shortener or rate limiter

Values / behavioural

1. Describe a time you chose the customer’s interest over what was easiest for the business (Don’t #@!% the customer)
2. Tell me about a problem nobody asked you to solve, that you solved anyway (Be the change you seek)
3. Describe a time you gave or received direct, unfiltered feedback (Open company, no bullshit)
4. Tell me about balancing a hard deadline with your team’s wellbeing (Build with heart and balance)
5. Describe a time you put team success ahead of your own individual win (Play, as a team)

Practical tips for Atlassian

• Clear the Online Assessment or Karat screen first - a clean, fully-passing solution beats a clever but partial one.
• Narrate your reasoning out loud in coding rounds; Atlassian’s interviewers reportedly weigh communication and code structure about as heavily as correctness.
• Keep system design answers practical and scoped (a feature inside Jira/Confluence, not “design Twitter”) with a real data model and named trade-offs.
• Prepare five separate, professional values stories - one per value - so you’re never reusing material inside the values round.
• If you don’t know something, say so and outline how you’d find out - vague confidence reads worse than an honest gap.

HR interview

Atlassian’s closest equivalent to an “HR round” is the dedicated values interview plus the closing managerial conversation - motivation, logistics, and five values-based stories rather than a single generic chat. Prepare those answers on the dedicated page rather than cramming them into this hub.

HR interview questions→

Atlassian’s values-based HR questions, sample answer frames, and STAR tips.

Similar companies

Google · Microsoft · Amazon · Zoho · Freshworks · Salesforce