Atlassian has one of the more structured interview processes among product companies in India and one of the more genuinely varied ones. The rounds are consistent in format. The questions are not always what candidates expect, particularly the Karat screening that opens everything and the rapid-fire system design questions that appear in it.
Most candidates who do not clear Atlassian are rejected at the Karat round or at the system design stage. Both are addressable with the right preparation.
If you want to experience what an Atlassian interview feels like before yours, Intervue.io connects you with engineers who have been through real Atlassian hiring rounds for one-on-one mock interviews. Visit intervue.io.
The Atlassian Interview Process in India
The full process for software engineering roles (P40 and P50 bands) in Bengaluru runs 5 to 6 rounds and typically takes 2 to 4 weeks from first contact to offer decision. The average process duration on Glassdoor is listed at 19 days.
The standard sequence for P40 (equivalent to SDE2 at most companies):
- Karat Screening (1 hour, outsourced)
- Coding Round 1 or Data Structures Round (1 hour)
- Code Design or Low-Level Design Round (1 hour)
- System Design Round (1 hour)
- Values Round (45 minutes)
- Manager Round (1 hour)
P50 (Principal Engineer) candidates typically face an additional round and deeper probing on all technical rounds, particularly system design. Frontend-specific processes have been reported with three coding rounds covering JavaScript, React, and then system design.
All rounds are eliminatory. Atlassian does not carry partial scores forward.
The Karat Screening: The First Gate
The Karat round is conducted by Karat, an outsourced technical interviewing company, not by Atlassian engineers directly. This is the most commonly cited surprise for first-time Atlassian applicants.
What the Karat round contains varies slightly by role and band but the most common format reported by Bengaluru candidates in 2025 is:
Rapid-fire system design questions (20 to 25 minutes): 4 to 5 short system design scenarios in quick succession, 4 to 5 minutes each. These are not full system design exercises. They are situation-based debugging and improvement questions. A system is running slow: what do you check first? An API is returning inconsistent results under load: what are the possible causes? A smart freezer's electronic system is behaving unexpectedly: how do you approach diagnosis? The expectation is practical reasoning speed, not exhaustive design.
DSA coding problem (25 to 30 minutes): One medium-difficulty LeetCode problem, completed on Karat's coding platform. Standard DSA topics: arrays, hash maps, graphs, trees. Some candidates report being asked to discuss the pros and cons of multiple approaches before implementing one.
Quick Q&A: Brief conversation about past experience and how you approach technical problems.
The Karat round pass rate is not published but based on candidate reports, roughly 50 to 60% of candidates who reach Karat advance to the Atlassian-internal rounds. The most common rejection reasons: not being able to discuss multiple solution approaches for the coding problem, and not being able to reason quickly through the rapid-fire system design scenarios.
Real Atlassian Interview Experiences: P40 (SDE2)
Account 1: P40 Backend, Bengaluru, Offer Received
6 rounds total. Application via LinkedIn recruiter outreach. Timeline: approximately 5 weeks.
Round 1 (Karat): Karat interviewer, experienced. Rapid-fire system design questions first, then a DSA problem. Went well.
Round 2 (Coding/Data Structures): Standard DSA round with an Atlassian engineer. One medium-hard problem. Concurrency and synchronisation topics appeared. The interviewer expected the candidate to discuss multiple approaches before settling on the optimal one.
Round 3 (Code Design/LLD): Pair programming style. Asked to design a file storage system. Code structure and clean design mattered more than raw correctness. Interviewer assessed how the candidate organised code, named things, and separated concerns.
Round 4 (System Design/HLD): Design a tagging system for Atlassian products. The expectation was depth on the API design layer (URL structure, request/response format, data model) which the interviewer had to nudge for. Lesson from this candidate: do not stay at the whiteboard diagram level in Atlassian system design rounds. Go deep into the API contract, the data model, and the specific components.
Round 5 (Values): Atlassian-specific values interview. Questions mapped to Atlassian's five values: open company no bullshit, build with heart and balance, don't #@!% the customer, play as a team, and be the change you seek. STAR-format answers expected. Specific questions: tell me about a time you had to deliver difficult feedback to a colleague, describe a situation where you prioritised the customer's need over what was technically easier.
Round 6 (Manager): Projects discussion, primarily behavioural. How do you handle a situation where a team member is consistently missing delivery commitments. What is your approach when you disagree with a technical decision made by a more senior engineer.
Account 2: P40 Frontend, Bengaluru, 6 Rounds
Frontend-specific process. Three technical rounds with a clear skill progression.
Screening: Standard. Skills-based fitment conversation.
Round 1 (Coding, JavaScript): Live coding in JavaScript. Core JS questions beyond just syntax: closures, event loop behaviour, and DOM manipulation.
Round 2 (Coding, React): Core React coding. Component design, hooks, state management, performance considerations.
Round 3 (System Design): Frontend system design. Design a URL scraping system (same question as backend P40 experience above, from a frontend angle). The candidate was expected to think about the client-side aspects of data display, state management for large datasets, and performance.
Round 4 (Values): Standard Atlassian values round.
Round 5 (Manager): Behavioural and projects.
Real Atlassian Interview Experiences: P50 (Senior/Principal)
Account 1: P50 Backend, Bengaluru, July to August 2025, Offer Received
5 rounds. Contacted by recruiter. 6 years of experience, tier 2 college, prior MNC experience.
Karat Round: 5 rapid-fire system design questions. Broader and faster than the P40 Karat format. The candidate described these as "debugging rather than diagramming": you are presented with a broken or struggling system and asked what you would investigate.
Code Design Round: LLD-focused. Design something with clear class structure and clean interfaces.
Data Structures Round: Standard DSA, medium-hard difficulty.
HLD (System Design) Round: URL scraping system, same as P40. Expectation at P50 is significantly deeper: capacity estimation, failure modes, consistency guarantees, and scalability beyond the basic architecture.
Management Round: How do you handle team conflict. How do you approach a situation where you need to deliver something you disagree with technically.
Values Round: Atlassian values STAR questions.
Account 2: P60 (Principal Engineer), Bengaluru, September 2025, Rejected
6 rounds. Rejected at the design stage.
This account highlights something important about Atlassian: the system design round expectation at Principal level is categorically different. The interviewer reportedly expected the candidate to raise and discuss edge cases and failure modes that the candidate did not surface unprompted. The feedback was that the "system design round feedback was on the higher side."
The key signal: at P50 and P60, Atlassian expects you to drive the system design discussion. Waiting for the interviewer to redirect you to interesting areas is not enough at this level.
What Atlassian Values Round Specifically Tests
The Atlassian values round is the most distinct part of their interview process because it maps directly to their five published values, which are public and specific.
Open company, no bullshit: Questions about transparency and honesty in difficult situations. Tell me about a time you had information your team needed but that was uncomfortable to share.
Build with heart and balance: Questions about sustainable work practices and genuine care for quality. How do you handle a situation where meeting a deadline requires cutting corners you believe will create problems later?
Don't #@!% the customer: Questions about customer-first decision making. Tell me about a time you prioritised fixing a customer-facing issue over internal work that was important to you.
Play as a team: Questions about collaboration and collective success. Describe a situation where you helped a colleague succeed at the expense of your own short-term recognition.
Be the change you seek: Questions about proactive improvement. Tell me about something you changed at your company that no one asked you to change.
Prepare specific stories for each value. The Atlassian values are clearly documented and the questions map to them directly. Not preparing for this specific framework is the most avoidable reason candidates fail this round.
The System Design Questions Atlassian Asks Most Often
Based on reported experiences from Bengaluru candidates across P40 and P50 levels:
Design a URL scraping system. Design a tagging system for Atlassian products. Design a Confluence popular feed. Design a web crawler. Design a hierarchical data storage system. Design a color picker tool. Design a tag management system.
The Atlassian-flavoured system design questions often have a product or tooling context connected to Jira, Confluence, or Bitbucket. Knowing what these products actually do as a user gives you a natural starting point for framing your design in a way generic system design practice does not.
The rapid-fire Karat format: a system is running slow (plus details). What would you investigate? An API returns inconsistent results under load. What are the possible causes? These are not full designs. They are diagnostic reasoning questions. Practice reasoning out loud through system problems quickly.
What Separates Passes From Rejections at Atlassian
Based on the accounts above and broader candidate reports:
Passes drove the system design discussion. At P40 and above, waiting for the interviewer to direct you to interesting areas is not enough. Candidates who proactively surfaced API design depth, failure modes, and data model specifics without prompting consistently received stronger feedback.
Passes had specific Atlassian values stories. Not generic "I was a team player" stories. Specific situations mapped to specific Atlassian values with real details and outcomes.
Rejections at Karat happened because of the rapid-fire format. Most candidates prepare for long-form system design. Four to five 4-minute diagnostic scenarios in sequence is a different skill. Practicing timed, fast reasoning through system problems is specific preparation that pays off.
Rejections at system design at P50 and above happened because candidates were reactive rather than proactive. The design depth existed in the candidate's knowledge but they did not surface it until prompted.
How to Prepare for an Atlassian Interview
For the Karat round: Practice 5-minute verbal responses to "this system is broken or slow, what do you check?" scenarios. Depth is less important than speed of reasoning and clear communication under time pressure.
For the coding rounds: LeetCode mediums, particularly graphs, trees, hash maps, arrays, and concurrency-related problems. Clean code matters: Atlassian interviewers specifically note code structure and design quality, not just correctness.
For the LLD round: Practice designing small-scale systems at the class and interface level. The file storage system, a parking lot, a library management system. Clean separation of concerns and sensible naming matter.
For the HLD round: Know the standard system design framework (requirements, estimation, high-level design, deep dive) and practice going deep on API design specifically. URL structure, request/response format, data models. Atlassian interviewers probe here more than most companies.
For the values round: Read Atlassian's five values. Prepare one strong story per value using the STAR format. Know the values well enough that you can identify in real time which one a question is probing.
At Intervue.io, Atlassian mock interviews are one-on-one with engineers who have been through real Atlassian hiring rounds.
Visit intervue.io to book yours.
FAQs
How many rounds does an Atlassian interview have in India? 5 to 6 rounds for P40 and P50 roles. Karat screening, one to two DSA/coding rounds, an LLD code design round, a system design round, a values round, and a manager round. P60 Principal Engineer roles may have additional rounds.
What is the Karat round at Atlassian?A third-party technical interview conducted by Karat interviewers, not Atlassian engineers. It includes rapid-fire system design scenarios (4 to 5 questions in 20 to 25 minutes) and one DSA coding problem. It is the first eliminatory gate.
How long does the Atlassian interview process take in India? Average of 19 days per Glassdoor data. Typically 2 to 4 weeks from first contact to offer or rejection decision.
What system design questions does Atlassian ask? URL scraping system, tagging system, Confluence popular feed, web crawler, hierarchical data storage, and color picker tool. Questions frequently have a product context connected to Jira, Confluence, or Bitbucket.
Is the Atlassian values round eliminatory? Yes. All rounds at Atlassian are eliminatory. A weak values round can result in rejection regardless of strong technical performance.
I have an Atlassian interview coming up. How should I prepare? Prepare for each stage of the Atlassian interview process, especially the Karat screening, DSA, system design, LLD, and values round. If you want to experience the interview before the actual one, you can take an Atlassian mock interview on Intervue.io with an experienced interviewer and get detailed feedback on your performance.
