Atlassian
Values-driven execution, collaboration and craft over heroics.
Working here
Working at Atlassian
Culture
A strongly values-led culture that genuinely shows up in decisions and reviews. They build collaboration tools (Jira, Confluence, Trello), so the "play as a team" ethos is lived. Remote-friendly ("Team Anywhere"), balanced in pace, and low-ego, "open company, no bullshit" is a real operating value, not a slogan.
The type of work
APMs own features on collaboration products, working in tight cross-functional triads with a design lead and an eng lead. Lots of stakeholder coordination, customer-feedback synthesis, and pragmatic prioritization, with the values used explicitly to settle tradeoffs.
A day in the life
Your team is a triad (you, an engineering lead, a design lead), and you're the connector, not the builder: you lead with trust and influence, not authority. One hour you're weighing design options and timelines with your eng lead; the next you're in the numbers, digging past what a metric did into why it did it. You examine an experiment result, then write the product requirements that turn a hunch into something the team can commit to. When a tradeoff gets genuinely hard, the values do real work: 'open company, no bullshit' means you say the uncomfortable thing, and 'play as a team' settles more debates than seniority does. Most of this happens across timezones; Team Anywhere means your triad might span three of them, so much of the thinking lands in writing others pick up async. There's a weekly check-in with your manager, and a pace that's deliberately sustainable. The 'balance' value isn't decorative.
The interview process
Atlassian interview process
- 1
Recruiter screen
30 minA recruiter fit call: get-to-know-you, seriousness about PM and B2B SaaS, a values-based behavioral, a light favorite-product prompt. Screens values-fit and communication.
Behavioral - 2
Take-Home case
~48 to 72 hrs, asyncA written case of about 3 pages on a real Atlassian product: analyze it and propose a prioritized direction. Multi-day window, discussed later.
Product SenseExecutionAnalytical - 3
Product and Execution
45 minDesign or prioritize for a collaboration product.
Product SenseExecution - 4
Values interview
45 minA dedicated round mapping your stories to Atlassian's five values.
Behavioral - 5
Cross-functional & Behavioral
45 minWorking with eng and design, conflict, and stakeholders.
ExecutionBehavioral
What they weight & how to answer
What Atlassian weights and how to answer
Atlassianrewards structured thinking over a single “right” answer. These are its strongest signals, ordered from most weighted.
Execution
Most weightedPrioritization and cross-functional collaboration are central, backlog calls, working with eng and design.
Prioritization and cross-functional collaboration are central, expect backlog calls and "how would you work with eng and design." Prioritize on a clear axis, and use Atlassian's values explicitly to settle tradeoffs (they really do this in reviews). A pragmatic, team-first approach beats individual heroics.
Behavioral
A dedicated values round, bring stories that map cleanly to their five values.
There's a dedicated values round, so bring stories that map cleanly to their five values ("Open company, no bullshit", "Play as a team"). Name the value you're demonstrating and show low-ego, collaborative behavior. Authenticity matters, they can tell a retrofitted story.
Product Sense
Design for collaboration and teamwork use-cases.
Design prompts skew toward collaboration and teamwork use-cases (think Jira, Confluence, Trello). Center a real team workflow and its friction, and prioritize with the values in view. A pragmatic, customer-first call beats a clever but abstract one.
Analytical
Lighter than at the marketplace or dev-tools shops.
Analytics are lighter than at marketplace or dev-tools shops, so keep data answers clean and structured rather than deep. Define a sensible metric, reason from it, and move on, judgment and collaboration are what's really weighted.
Example questions
Example Atlassian interview questions
“Walk me through how you'd work with engineers and designers on a new feature from concept to launch.”
Execution
“How would you prioritize a backlog of 20 feature requests?”
Execution
“Describe a conflict with a teammate and how you resolved it.”
Behavioral
“Tell me about a time you led a team or project.”
Behavioral