Find a lesson, question or project

Start typing to search published content and planned structures.

↑ ↓ moveEnter openEsc close

Atlassian interview research

Candidate accounts · 1 scoped account · 5 reported questions/topics

Snapshot: 1 October 2026 · Software/backend focus · No live fetching

Self-reported accounts, not employer-confirmed. Preserve the stated role, team and location; this sample does not establish company-wide patterns or question frequency.

Questions people reported

Named problems, reported variants and broad topics are different kinds of evidence. Related practice links are not proof that the exact problem was asked. Some prompts were withheld; we do not invent their details.

Topics in these accounts: Coding · Practical coding · System design · Behavioral

P50; location not stated

Interview period ended Aug 2025; see source notes for the full period

Read the original candidate account

Scope and source limitations

July–August 2025 loop. Preserve the employer's P50 title instead of applying it to every senior role.

  • Two Sum-like screen and an unnamed BFS problem

    Coding · Reported variant

  • Rank support agents by their average customer rating

    Practical coding · Reported topic

  • Find a shared department in an organizational hierarchy

    Coding · Reported topic

  • Tag discovery and popular-tag search

    System design · Reported topic

  • End-to-end ownership, mentoring and company values

    Behavioral · Reported topic

Additional independent, matching role/level/region reports are needed before claiming recurring patterns.

A suggested 14-day preparation plan

Authored practice, not the company’s syllabus. This general track is an editorial starting point, not a pattern inferred from all these reports. Confirm the format with your recruiter and adapt it to your actual level.

Practical coding and maintainable design

Implement small services incrementally, test them, read unfamiliar code and explain concurrency or schema decisions.

  • Days 1–2: implement an iterator, parser or small key/value store with tests.
  • Days 3–4: add one new requirement without breaking the existing API.
  • Days 5–6: reproduce and fix bugs in unfamiliar code; explain the tests.
  • Days 7–8: DSA fundamentals and one timed graph/hash-map exercise.
  • Days 9–10: object design, database schema and safe state transitions.
  • Days 11–14: a service-design mock, project deep dive and coding review.
Practise an original design exercise

Design an issue tracker with searchable comments and permissions.

This exercise is written for practice, not reported by a candidate. Define requirements, implement the smallest useful version, then test concurrency, retries and failure recovery where relevant.

Customize a timed role/level prep brief

The timed brief uses a narrower, date/level-filtered dataset. Broader accounts on this page are deliberately not substituted into those filters.

How this research was collected

Public candidate accounts, official guides and original editorial practice are kept separate. We did not copy paid question banks or scrape all of the internet. Cross-posts are not independent evidence; one source can describe more than one company. Unknown or index-only dates are not used to claim recency. Future expansion needs permitted fetching, deduplication and metadata review; this version remains a static snapshot.