Engineering at Atlassian runs distributed-first through Team Anywhere: roughly 40% of employees live outside commutable distance of an office, so async is the default, not the exception. Work is organized around structured decision docs, recorded design reviews, and deliberately fewer meetings — Atlassian's own experiments cut meeting time about 13% and reported that 70%+ of participants made more progress on their most important work. Days are anchored by focused build time on the core stack (Java/Kotlin services, React/TypeScript front ends on AWS) with a code-review culture that prizes clear thinking and justified trade-offs over line-perfect code. Collaboration is intentional rather than incidental: teams gather in person periodically (about 80% of staff visit an office quarterly, and intentional gatherings boosted team connection ~27% for several months), and ShipIt hackathons give 24 hours to build something outside the roadmap. The five values are not posters — they surface in how decisions are argued ('Open company, no bullshit'), how customer feedback is treated ('Don't #@!% the customer'), and how credit is shared ('Play as a team'). Junior engineers ship well-scoped features; senior engineers lead cross-team projects through written decisions; principals set technical direction across an org.

Reciting values instead of showing them

The values interview scores lived examples, not vocabulary. A resume that name-drops 'transparency' or 'collaboration' as buzzwords — with no concrete story of directness, customer focus, or team play — gives the interviewer nothing to grade and reads as a values miss.

Corporate buzzwords that violate 'Open company, no bullshit'

Inflated phrasing like 'synergized cross-departmental initiatives' is exactly the corporate-speak the signature value rejects. Atlassian reads plain, honest specificity as a strength and buzzword vagueness as a red flag.

Solo-hero framing

Atlassian hires engineers who 'elevate the team, not just the code.' An all-'I' resume with no collaboration, mentoring, or shared credit misses 'Play as a team' — a scored dimension, not a nice-to-have.

No distributed or async-work evidence

With Team Anywhere the default and ~40% of staff non-commutable, async-across-time-zones experience is a direct fit signal. Hiding it (when you have it) forfeits an easy point of alignment with how Atlassian actually operates.

A tool-proficiency wall over how you think

Atlassian screens for broad distributed-engineering skill and learning agility, and in coding says 'what's most important is how you think.' A keyword wall of frameworks with no reasoning about trade-offs signals the opposite of what they select for.

1Reciting values instead of showing them

Every Atlassian loop includes a values interview that scores how you have lived the five values in real situations, not whether you can name them. A resume that name-drops 'transparency' and 'teamwork' as buzzwords, with no concrete story of directness, customer focus, or team play, hands the interviewer nothing to grade. Seed specific values-in-action examples into your experience bullets so the values interview has evidence to build on.

2Corporate buzzwords that violate 'Open Company, No Bullshit'

'Open company, no bullshit' is a literal company value and it extends to how resumes read. 'Synergized cross-departmental initiatives' or 'leveraged best-in-class methodologies' is exactly the inflated corporate-speak the value rejects. Be direct: what you did, how, and what happened. Plain, honest specificity beats impressive-sounding vagueness at Atlassian more than almost anywhere.

3Presenting yourself as a solo hero

Atlassian explicitly hires engineers who 'elevate the team, not just the code,' and 'Play as a Team' is deeply embedded. A resume of 'I built / I designed / I decided' with no collaboration, mentoring, or shared credit reads as a values miss. Show how you amplified teammates and contributed to team outcomes, not just individual output.

4No distributed or async-work evidence

Team Anywhere is the default — roughly 40% of Atlassians live outside commutable distance of an office. If you have experience working async across time zones, running structured decision docs, or building for distributed teams, make it explicit. Omitting it, especially when you have it, misses a direct signal of fit with how Atlassian actually operates.

5A tool-proficiency wall instead of how you think

Atlassian's own interview guide says it screens for broad distributed-engineering skill and learning agility over proficiency in one language, and that in coding 'what's most important is how you think.' A resume that's a keyword wall of 20 frameworks with no reasoning about trade-offs, reliability, or design decisions signals the opposite of what they select for.