Atlassian SDE onboarding and first 90 days tips 2026

TL;DR

Atlassian SDE onboarding is not a passive orientation — it's a 6-8 week structured integration where your ability to ship code in your first sprint matters more than your interview performance. The first 90 days are a performance evaluation disguised as learning; your manager is already building a promotion or PIP case by day 60. Success depends on shipping early, building political capital with your immediate team, and understanding that Atlassian's "team health" metrics directly impact your performance review.

Who This Is For

This is for software engineers who have accepted an SDE offer at Atlassian (or are negotiating one) and want to understand the actual dynamics of the first 90 days — not the HR-approved version, but what determines whether you get a "meets expectations" or "exceeds" in your first performance cycle. If you're joining from a non-Agile shop, a smaller company, or haven't worked in Atlassian's specific brand of "team autonomy with corporate oversight," the cultural adjustment will be steeper than you expect.

What Is Atlassian SDE Onboarding Actually Like

The onboarding experience at Atlassian is designed to make you feel productive immediately — and that's the trap. It's not a gentle ramp-up; by week 2, you'll be in a sprint planning session expected to pick up stories. The company runs on a modified Scrum model across most teams, with 2-week sprints, backlog refinement every other week, and a "definition of done" that includes code review, testing, and documentation.

In a typical onboarding, you get 3 days of company-wide orientation in Sydney or San Francisco (depending on your hire location), then 2-3 days of org-specific setup — getting access to their internal tooling, Jira, Confluence, and the codebases. By day 10, you're expected to have your development environment running and have picked up at least one "good first issue" from your team's backlog.

The problem isn't the pace — it's that no one tells you which issues are political landmines. A senior engineer in your first team sync will casually mention "oh, that one's been in backlog for 6 months for a reason" — and you've just inherited technical debt that will tank your velocity for your first quarter.

Not the code quality matters most — but your judgment about which problems to solve and which to politely decline. Atlassian values "shipping over perfect" but there's an unspoken hierarchy of which shipping matters for promotion.

How Long Does Atlassian SDE Onboarding Take

The formal onboarding timeline is approximately 6-8 weeks, but the real integration period is 90 days. Here's the breakdown:

Days 1-5: Company orientation, org setup, tooling access
Days 6-14: Team integration, first code review, "good first issue" assignment
Weeks 3-6: First full sprint participation, initial feature work
Weeks 7-12: Independent feature ownership, first performance check-in
Days 60-90: First formal performance review cycle, promotion consideration window opens

The critical milestone is your first shipped code change hitting production — this should happen by week 4 at the latest. In hiring committee debriefs, I've seen managers flag engineers who haven't shipped anything by their 6-week mark as "integration concerns," even if they're doing extensive learning.

Not the length of onboarding matters — but whether you can demonstrate shipping velocity within the first month. Atlassian's promotion framework rewards "impact velocity," and the clock starts the day you accept your offer.

What Should I Expect in My First Week at Atlassian as an SDE

Your first week will feel like drinking from a firehose while being expected to look calm. You'll get access to roughly 15 different internal systems, 3-4 onboarding buddies (Atlassian's formal mentorship pairing), and a manager who will likely schedule exactly one 1:1 with you in that first week.

The first week typically includes:

Day 1-2: Badge pickup, laptop setup, HR paperwork, benefits enrollment
Day 3: Team introduction meeting, access to team Slack channels, first look at the codebase
Day 4: Development environment setup, first meeting with your onboarding buddy
Day 5: First 1:1 with manager, initial "good first issue" assignment

The culture shock for most new SDEs is the autonomy expectation. Atlassian operates on a "leadership at every level" principle — they don't hand-hold. If you don't understand something, you're expected to ask, but you're also expected to have tried to figure it out first. The worst signal you can send in your first week is passive confusion.

Not your technical questions matter most — but your ability to demonstrate ownership by coming to your manager with problems AND proposed solutions, even if the solutions are wrong. The intent signals "senior" more than the outcome signals "junior."

How Does Atlassian Evaluate SDE Performance in the First 90 Days

Atlassian uses a performance system called "Growth and Performance" (G&P) that happens twice yearly, with informal check-ins monthly. Your first formal review comes around the 90-day mark, but your manager is building that assessment from day one.

The evaluation criteria at Atlassian are publicly documented in their career framework and include:

Impact: Did you ship something that moved the needle?
Teamwork: Did you collaborate effectively, review others' code, contribute to team health?
Mastery: Did you demonstrate technical depth in your domain?
Enlightenment: Did you share knowledge, mentor others, or improve team processes?

In practice, for a new SDE in their first 90 days, "impact" is weighted 40%, "teamwork" 30%, and the other two categories make up the remaining 30%. The hiring committee perspective: if you shipped at least one meaningful feature (not just bug fixes) by day 90, you're on track for "meets expectations." If you shipped two or more and had positive code review feedback, you're in "exceeds" territory.

The catch: Atlassian's "team health" metrics — things like psychological safety scores, sprint velocity stability, and code review turnaround — are factored into your individual review. If your team is struggling, your individual rating can be capped regardless of your personal output.

Not your individual code output determines your review — but how your presence affected the team's overall performance. Atlassian explicitly penalizes "hero culture" and rewards engineers who lift their team's metrics.

What Are the Unwritten Rules for New SDEs at Atlassian

The written rules are in the onboarding docs. The unwritten rules are what get you promoted or pipped:

Don't touch the core platform code in your first month. The Jira and Confluence codebases have been around for 15+ years. There are engineers who have been at Atlassian for a decade who still don't touch certain modules. Picking up a "simple" bug in the core platform is the fastest way to become known as the person who broke production in their first week.

Your first code review sets your reputation. Atlassian has a thorough code review culture. If your first PR is sloppy — missing tests, unclear commit messages, no documentation — that reputation sticks. If it's excellent, people will seek you out for reviews. The standard expectation is at least 2 reviewers, 24-hour turnaround, and no pushback on feedback.

Attend the optional things. Atlassian has numerous optional engineering talks, hackathons, and team socials. Not attending isn't penalized directly, but in a company that values "team health," being the person who never shows up to optional events signals disengagement. This is especially true in your first quarter.

Use the tools the company sells. This sounds obvious, but new SDEs who don't use Jira for their own task management, Confluence for documentation, and Trello/Loom for async communication are seen as "not drinking the kool-aid." It's a cultural fit signal.

Don't compare your compensation publicly. Atlassian is relatively transparent about compensation bands (they publish salary ranges in job postings), but discussing your specific offer or your perceived fairness of your level creates unnecessary friction. The hiring committee has seen engineers who asked "why is this person at L4 and I'm at L3" get flagged for poor judgment.

Not your technical skills determine your success — but your ability to navigate the political and cultural expectations without being visibly political. Atlassian rewards engineers who seem genuinely aligned with the company's values, not those who perform alignment.

Preparation Checklist

Set up your development environment before day 1. Atlassian uses a specific tech stack (Java, Python, React for front-end) — get familiar with their open-source contributions on GitHub so the codebase doesn't look alien.

Read the Atlassian Engineering Blog and understand their engineering values. The "Team Health" monitor and "DevOps" maturity model are referenced constantly in performance conversations.

Prepare 3-5 questions for your first manager 1:1 that demonstrate strategic thinking: "What's the biggest technical debt the team is managing?" "What's the team's biggest bottleneck?" "What would success look like for me at 90 days?"

Review the Atlassian career framework for your level (L3/L4/L5). Know exactly what's expected for promotion to the next level — Atlassian makes this public for a reason.

Work through a structured preparation system (the PM Interview Playbook covers Atlassian-specific engineering leadership frameworks with real examples of how first-quarter performance reviews are structured).

Understand Atlassian's product suite deeply. You don't need to be a Jira expert, but knowing the difference between Jira Software, Jira Service Management, and Jira Work Management matters for context.

Set up your 30-60-90 day plan in your first week and share it with your manager. This demonstrates proactively and gives you a framework to reference when you feel lost.

Mistakes to Avoid

BAD: Waiting for your manager to tell you what to work on.

GOOD: Coming to your first 1:1 with a proposed 30-day plan based on your understanding of the team's backlog. Atlassian expects ownership, not task-following.

BAD: Volunteering to fix "easy" bugs in the core platform because they look simple in Jira.

GOOD: Asking your onboarding buddy which bugs are safe to pick up. The "easy" tickets are often traps left by engineers who know the code is a mess.

BAD: Skipping team social events because you're focused on "real work."

GOOD: Attending at least 60% of optional team events in your first quarter. The "team health" component of your review includes cultural fit signals that are subjective.

FAQ

How hard is Atlassian SDE compared to FAANG?

Atlassian's technical interviews are comparable to mid-tier FAANG (below Google/Meta, above Amazon in difficulty). The work-life balance is generally better — no mandatory pager duty for most teams, and the "no meetings on Wednesdays" policy is actually enforced in many orgs. The trade-off is slower career progression; promotions at Atlassian average 18-24 months versus 12-18 months at faster-growth companies.

What is the typical SDE salary at Atlassian in 2026?

Atlassian SDE compensation in US locations typically ranges from $180,000 to $350,000+ total compensation depending on level (L3-L6), with base salary $140K-$220K, equity vesting over 4 years, and annual bonuses of 10-20%. Sydney-based roles are 15-25% lower in absolute terms but competitive within the Australian market. Remote roles are compensated based on location tier.

Can I negotiate my SDE level at Atlassian after seeing the offer?

Yes, but the window is narrow. Atlassian is more flexible on level than Google or Meta — they have a formal "level calibration" process where you can provide evidence for a higher level within the first 2 weeks of seeing your offer. The strongest evidence is comparable offers from other companies or a detailed technical portfolio showing scope of work at your claimed level. The hiring manager has input, but final calibration goes to a committee.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.