L0st Pérs0n
5.9K posts



Atlassian interview (end to end). Real questions I got. 1. Recruiter screen (20 min) “Why Atlassian?” “What’s your notice period, location, comp?” 2. DS/Algo (60 min) - “Given an array, find the shortest subarray with sum ≥ K.” (sliding window + prefix) - “Design an LRU cache.” (HashMap + doubly linked list) - Follow ups: time, space, edge cases, tests 3. Coding round 2 (60 min) - “Merge intervals, return non overlapping result.” - “Top K frequent elements.” - Follow ups: complexity, alternative approaches, input constraints 4. System design (90 min) “Design a Jira like issue tracking system.” Covered: - data model (Project, Issue, Comment, Status, Assignee) - APIs (create/update/search) - search (filters, pagination, indexes, Elastic) - scale numbers (QPS, storage), hot partitions - consistency (status transitions), idempotency - async work (notifications, webhooks), retries, DLQ - caching, rate limits, audit log - observability (SLOs, traces) 5. Hiring manager (45 min) “Biggest project you owned end to end?” “Tell me about a prod incident you caused.” “How do you handle disagreements in design reviews?” “What would your ex manager say you need to improve?” So if you’re prepping: don’t just grind LeetCode. Be sharp on tradeoffs, failure modes, and how you debug under pressure.




















