Academic snapshot
Marks: 7.5+ CGPA / 75% throughout (candidate-reported)
Degree: B.Tech / B.E. / M.Tech / MCA
Backlogs: None active
Year: Final-year and recent grads
Atlassian Placement Papers 2026
Atlassian is a global software company behind collaboration and developer tools including Jira, Confluence, and Bitbucket. In India, Atlassian recruits engineers in Bengaluru to build cloud products used by teams for project tracking, documentation, and software delivery.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Atlassian eligibility & CGPA (2026)
Who this hub is for
- For: Students targeting Software Engineer / Analyst roles at Atlassian India - product engineering on collaboration tools (Jira, Confluence, Bitbucket ecosystem), primarily Bangalore.
- Not the same track: Pure sales, support-only, or non-engineering roles. Those bars and processes do not map to this OA → DSA → design loop.
- Experienced hires: Mid-level loops may add deeper LLD, distributed-systems depth, or hiring-manager rounds and different CTC. Use fresher sections as a base, then read senior notes separately.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT timing, college CGPA list when printed | Coding bar, interview depth |
| Careers portal / referral | Resume screen volume; sometimes no hard published CGPA | Still expect OA + two tech rounds |
| Intern → full-time | Conversion interviews may skip a stage | You still defend projects and code |
Off-campus does not mean “easier coding.” It often means more applicants fighting the same ~90-minute filter. If your CGPA sits near 7.5, spend energy on mocks, not on hunting a mythical lower cutoff blog post.
Degree, projects, and “is 7.5 enough?”
Is 7.5 CGPA enough? It matches the commonly reported floor across 10th, 12th, and graduation. Selection still hinges on OA correctness and interview narration. A 7.6 with clean timed coding beats an 9.0 that freezes on edge cases.
Branches: CS/IT/ECE dominate shortlists. Related streams show up when DSA is solid. If your college lists only certain branches for a drive, read the notice.
Gaps and backlogs: Active backlogs are a hard blocker on most Atlassian fresher drives. A short education gap is easier to explain with a skills story than silence. Lying about CGPA or backlog status is an instant integrity fail in HR.
What helps the resume screen: One project you can defend end-to-end, open-source or contest signal when real, any internship with ownership language. Certificates are optional extras - DSA and OA mocks matter first. See certifications only after fundamentals are solid.
Branch & skills
Preferred: CS / IT / ECE and related
Languages: Java, Python, JavaScript, C++
Focus: DSA, system design, full-stack fundamentals
Differentiator: Collaboration product sense (Jira-like workflows)
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.5+ CGPA / ~75% across 10th, 12th, graduation | Consistently cited; verify every drive |
| Degree | B.Tech / B.E. / M.Tech / MCA | Related computing degrees on many posts |
| Branch | CS, IT, ECE (and related) | Strong DSA can help adjacent branches on some drives |
| Year | Final year + recent grads | Internship → conversion paths also appear |
| Backlogs | No active backlogs | Clear them before offer paperwork |
| Coding languages | Java, Python, JavaScript, C++ | Stick to one for OA + interviews |
Atlassian CGPA criteria
The minimum CGPA required is 7.5+ CGPA / 75% across 10th, 12th, and graduation (candidate-reported) - the commonly cited campus floor. Treat it as a shortlisting filter when printed - Atlassian still decides on OA correctness and interview narration.
| Academic Level | Minimum (typical) | Notes |
|---|---|---|
| 10th | 7.5+ CGPA / 75% | Consistently applied on many drives |
| 12th | 7.5+ CGPA / 75% | Diploma holders evaluated similarly |
| Graduation | 7.5+ CGPA / 75% | No active backlogs at hiring |
| Backlogs | None active | Cleared backlogs generally accepted |
Clearing CGPA only gets you into the funnel - coding speed decides whether you see an interviewer.
Atlassian placement papers - last few years
Download 2026 Atlassian placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Atlassian previous year papers actually train
Atlassian does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers for the first filter and early technical rounds - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed accuracy on Atlassian Online Assessment (~90 min): coding + aptitude speed |
| Technical 1 | Live coding narration: brute force → optimize → edge cases |
| Technical 2 | Prompts around Jira-like workflows, API design, concurrency, caching |
| HR | Why Atlassian?, Bangalore relocation, teamwork stories, integrity |
Themes that keep repeating (2024-2026)
- 2024 cycles: Medium DSA on OA with aptitude still present on many invites. Sliding-window and hash-map themes dominate practice sets. Students who skipped timeboxes lost easy aptitude marks.
- 2025 loops: Write-ups describe coding-heavy OAs (often 2-3 problems) on platforms like HackerRank, then DSA + project deep-dives. Domain chat around Jira-like workflows and concurrency shows up after you clear the code bar. Longest-substring / sliding window and graph BFS prompts keep returning.
- 2026 prep expectation: Keep both aptitude speed and medium-hard DSA warm. Expect design rounds to stay fresher-depth (actors, APIs, bottlenecks) - not staff-level distributed systems. Treat PDF packs as pattern catalogs. Own the sliding-window template, not the exact “longest substring without repeating characters” story.
Public write-ups on Atlassian India’s exact OA blueprint are thinner than for some FAANG loops - that is why this hub stresses pattern trainers and “verify your invite.” When in doubt, practice medium DSA under 90 minutes and keep a Jira-workflow sketch ready.
How to use one paper set in a single sitting
- Timed: run a full ~90-minute mock (aptitude block + coding) with the same language you will use on test day.
- Untimed review: rewrite the cleaner solution; list three edge cases you missed (empty string, single char, unicode).
- Map each coding miss to a theme (window / hash / tree / graph / heap) and pull two cousins from coding questions.
- Spend 15 minutes explaining a Jira issue state machine or API for comments out loud like a teammate.
- Log one STAR teamwork story the session reminded you of (conflict on a PR review, unclear requirements on a team project).
Related problems to practice
| Theme you saw in a set | What to drill next | Why Atlassian asks it |
|---|---|---|
| Sliding window / unique chars | Variable window, at-most-K variants | Text / search / filter UX intuition |
| Graph BFS / DFS | Connected components, shortest path | Dependency / workflow graphs |
| Hash map counting | Frequency, anagrams, two-sum family | Fast lookups in product features |
| Tree traversals | LCA, path sums | Nested page/space hierarchies intuition |
| Concurrency lite | Locks vs messages in plain words | Shared boards, simultaneous edits |
2025 PDFs often drill “longest substring without repeating characters.” Own the sliding-window template (left/right pointers + last-seen map), then drill “at most K distinct.” Interviews test the template, not memorised story text.
From application to offer at Atlassian
Atlassian hires freshers through campus placement cells, the careers portal, referrals, and occasional internship conversion paths. After resume screen, the shape is product-company style: timed OA, then two technicals, then HR.
Application methods
Campus recruitment
Through college placement cells - PPT, then OA and interviews on a batch timeline.
Online applications
Apply on atlassian.com careers for early-career / fresher tech roles; follow the invite mailer for platform and duration.
Referrals
Employee referrals improve visibility. You still need passing OA code and clear interviews.
1. Resume / eligibility screen
Placement cell or recruiter checks degree, CGPA floor when printed (7.5+ / 75% commonly reported across 10th/12th/grad), backlogs, and year of passing. Projects, open-source, and internships help when volumes are high. This is a gate, not the hard filter - coding is.
2. Online Assessment - Atlassian Online Assessment (~90 min)
Candidate reports commonly describe a ~90-minute assessment (some invites 90-120) mixing aptitude / reasoning with coding. Exact section splits vary by drive and year; treat the table as a working map, not a sealed blueprint.
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Aptitude / reasoning | ~15-30 | ~25-40 min | Quant, logic |
| Coding | 2-3 problems | Remaining window | Arrays, strings, hashing, trees, graphs |
| Technical MCQs | When present | Short block | CS basics |
Languages: Java, Python, JavaScript, C++. Platforms: HackerRank and similar appear in write-ups - confirm yours in the invite.
Pass bar in practice: Correct, fully passing solutions beat a brilliant half-answer. Aptitude, when present, punishes slow calculation more than exotic tricks.
Student tip: Spend 3-4 minutes skimming all coding prompts. Bank the solvable one first. Invent two edge cases before submit.
Example timing for a 90-minute OA
| Minute | Move |
|---|---|
| 0-5 | Skim full paper / all coding statements; mark easy wins |
| 5-30 | Aptitude / MCQ block if present - skip sticky puzzles, return later |
| 30-65 | Coding problem 1: restate → brute → optimize → code → sample tests |
| 65-85 | Coding problem 2 (and 3 if present) or harden edge cases |
| 85-90 | Quick revisit of flagged aptitude items |
Deeper OA notes and drills: Atlassian Online Assessment.
3. Technical interview round 1 - DSA (~60 min)
Video or onsite shared editor. Expect 1-2 DSA problems plus a short project warm-up. Patterns candidates report: sliding window, hash maps, tree/graph BFS, string manipulation.
You should:
- Clarify constraints (null inputs, duplicates, unicode)
- Narrate brute force → bottleneck → target complexity
- Code in your chosen language without syntax stalls
- Walk edge cases and complexity at the end
Interviewers care about debugging out loud. Silent staring after a failed mental test case is a common reject signal even when the idea was right.
Example narration shape (longest substring without repeating characters): “Brute force is check all substrings O(n²). Better: sliding window with last-seen index map, advance left when duplicate appears. Empty string returns 0; single char returns 1.” That 40-second plan already signals interview readiness.
4. Technical interview round 2 - design + product (~60 min)
Fresher depth, not staff-architect theater. Typical prompts:
- Jira-like issue workflow: states, transitions, who can move what
- API design for comments / attachments on an issue
- Concurrency on a shared board: two users edit the same field
- Search / filter for issues: indexes, pagination, empty results
Start with users → data → APIs → bottlenecks. Plain language beats “we will use Kafka and Redis” with no requirements. Tie one resume project to collaboration scale if it fits - without forcing it.
Worked mini-outline - issue state machine:
- Actors: reporter, assignee, reviewer, admin.
- States: To Do → In Progress → In Review → Done (plus Blocked).
- Rules: who can transition; what happens on reopen.
- Failure: invalid transition → clear error, no silent ignore.
- Scale later: only after the above is clear - caching issue lists is fine; do not lead with a buzzword diagram.
If the interviewer pivots to API design, talk resources, verbs, pagination, idempotency for creates, and auth at a fresher level.
5. HR / culture - ~30 min
Why Atlassian (not “cool brand” only), relocation to Bangalore, notice period / exams, teamwork and conflict STAR stories. Know the ₹30-40 LPA fresher band so CTC talk is grounded. Ask one real question about the team’s product surface (Jira Cloud, Confluence, Bitbucket) - it beats “what is the culture?”
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA (coding + aptitude) | ~90 min | Timed accuracy |
| 2 | Technical 1 (DSA) | ~60 min | Code + narration |
| 3 | Technical 2 (design + product) | ~60 min | Collaboration systems reasoning |
| 4 | HR | ~30 min | Fit, location, logistics |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT week then OA window |
| OA completion → shortlist | Few days common | Some batches move faster |
| Interview loop | ~1-2 weeks | Tech 1 → Tech 2 → HR |
| Offer / paperwork | Days after final round | Written offer wins over verbal |
| End to end | ~2-3 weeks campus batches often | Off-campus can be 2-4+ weeks |
OA pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Aptitude / logic | Speed + accuracy | Timed mock quiz |
| Coding Q1-Q2 | Windows, hashing, trees/graphs | Two timed mediums back-to-back |
| Domain follow-ups | Jira workflows, APIs, concurrency | Explain one flow in 3 minutes aloud |
| HR | Why Atlassian, Bangalore | Two STAR teamwork stories + relocation |
How Atlassian differs from a generic SaaS interview
Atlassian still filters hard on DSA, but the second technical often feels like a collaboration-product conversation:
- Jira-like workflows and API design show up more than retail or payments metaphors.
- Concurrency on shared boards is a favourite fresher-depth prompt.
- Culture interviews lean on teamwork and async collaboration harder than many product companies.
- Bangalore is the usual India hub story - treat relocation as a real HR question.
If you are also preparing for Microsoft or Adobe, keep DSA shared and customise the product sketches per company.
Where to practise for Atlassian
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
Atlassian preparation strategy that works
If a Atlassian invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Atlassian sits around ₹30-40 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Atlassian eligibility for freshers 2026 is candidate-reported. Common campus/SWE baseline: B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related fields; final-year students and recent graduates; typically 7.5+ CGPA / 75% across 10th, 12th, and graduation; no active backlogs. Strong DSA, system-design fundamentals, and collaboration stories matter after the resume screen. Always verify the drive notice or careers posting.
What you are training for: Atlassian fresher loops commonly run: Online Assessment (~90 min, coding/aptitude) → Technical Interview 1 (~60 min, DSA + projects) → Technical Interview 2 (~60 min, deeper design/API/concurrency) → HR (~30 min, culture and fit). Campus batches often finish in about 2-3 weeks from application to offer.
Short version of the prep split: Treat Atlassian like product hiring for collaboration tools. Split time roughly: 45% DSA, 20% system design / API / concurrency lite, 20% timed OA mocks + aptitude, 15% behavioral/teamwork stories. Clear the ~90-minute OA first. Languages: Java, Python, JavaScript, C++.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the Atlassian previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Atlassian drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Atlassian usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Atlassian?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Atlassian-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Atlassian story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Atlassian PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Atlassian papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Atlassian papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Atlassian-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed Atlassian paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Atlassian. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
What to carry into the interview room
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Atlassian, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
Tracking that does not become a second job
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Atlassian mistakes, you are collecting content, not preparing.
Extra drill block (1)
Sit one more mixed Atlassian set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Atlassian compensation & benefits
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on level, location (Bangalore), hiring year, and written components (base / bonus / equity).
Software engineer / analyst bands students ask about
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Software Engineer / Analyst (fresher) | ₹30-40 LPA | Primary band for this hub |
| Senior / mid-level (indicative) | Higher range | Not the fresher campus default |
Confirm base, joining bonus, and any equity or benefits language on the written offer. Do not treat blog midpoints as guarantees.
Benefits students actually care about
Policies vary by BU and year. Candidates commonly care about:
- Health insurance and wellness support
- Learning / certification sponsorship after joining (manager-dependent)
- Hybrid or office norms for Bangalore teams
- Relocation support when moving cities - ask HR, do not assume
How to talk CTC in HR without sounding lost
Know the ₹30-40 LPA fresher context, ask how the package splits (fixed vs variable vs equity), and clarify joining date vs final exams. One calm clarifying question beats aggressive negotiation with no market anchor.
Atlassian hiring updates for 2026
- Digital / off-campus assessments remain common alongside campus drives.
- DSA after resume screen stays the real filter - aptitude still appears on many OA invites, but weak coding rarely survives.
- Product awareness for Jira-like workflows, APIs, and concurrency shows up in Technical Round 2 more than in 2010s-style pure HR.
- HackerRank-style platforms appear in recent write-ups; always trust your invite for duration and section list.
- Treat ₹30-40 LPA as a reported fresher band, not a promise for every role or college.
- Teamwork / collaboration STAR stories matter more here than at many product companies - prepare them early, not the night before HR.
Common questions about Atlassian hiring
Process & papers
What is the Atlassian placement process for freshers?
Typical fresher path: Online Assessment (~90 min, coding + aptitude) → Technical 1 (DSA) → Technical 2 (design / product) → HR. Campus batches often finish in about 2-3 weeks; off-campus timelines vary. Confirm round names on your invite.
How many interview rounds does Atlassian usually have?
Most fresher SWE loops report four stages (OA + two technicals + HR). Some invites list OA as 90-120 minutes or merge managerial with HR. Count the mailer, not a random blog.
Can I download Atlassian placement papers PDF for free?
Yes. Free Atlassian placement papers PDF and 2024-2026 style practice sets are on this site - pattern trainers with solutions, not leaked live papers. No registration for the main downloads. Start with the 2026 PDF or the paper archive.
What does the Atlassian Online Assessment look like?
Candidate-reported OA is often ~90 minutes (sometimes 90-120) with aptitude/reasoning and 2-3 coding problems. Languages: Java, Python, JavaScript, C++. Platforms like HackerRank show up in write-ups - verify yours.
Eligibility & offer
What eligibility / CGPA do fresher SWE drives usually expect?
Commonly reported floor: 7.5+ CGPA / 75% across 10th, 12th, and graduation; CS/IT/ECE-related degrees; final-year or recent grads; no active backlogs. Atlassian does not publish one universal cutoff - your drive notice overrides this page.
What is Atlassian fresher salary in India?
Candidate-reported Software Engineer/Analyst fresher CTC often lands around ₹30-40 LPA (as of August 2026), mainly for Bangalore roles. The written offer letter is the only number that matters.
Do I have to relocate to Bangalore?
Bangalore is the main India hub candidates report for Atlassian engineering roles. HR usually checks relocation willingness and joining logistics. Be honest about constraints early.
Prep & Atlassian-specific
How should I prepare for Atlassian?
Split time roughly 45% DSA, 20% design/API/concurrency lite, 20% timed OA + aptitude, 15% behavioral/teamwork. Clear timed OA mocks first. Keep one coding language. Details: preparation guide.
Which programming languages are allowed?
Java, Python, JavaScript, and C++ are the usual set. Confirm on the invite. Do not switch languages the week of the drive.
What product topics should I revise?
Jira-like issue workflows, comments/attachments APIs, concurrency on shared boards, and search/filter at fresher depth: actors, data, bottlenecks, failure modes in plain language. Practice sketches beat memorised architecture diagrams.
How important are teamwork stories at Atlassian?
Very. Culture interviews lean on collaboration, conflict, and async work. Prepare STAR stories with metrics. Coding still decides whether you reach that round.
How is Atlassian different from Google or Microsoft for freshers?
All three care about DSA. Atlassian India loops often emphasise collaboration-product vocabulary (workflows, APIs, concurrency) with a Bangalore hub story and strong culture fit. Google/Microsoft bars differ by loop structure - prep DSA for all; customise product stories per company.
What certifications help before joining?
For campus SWE, DSA + OA mocks + one strong project beat certificate stacks. Cloud or domain certs are optional extras after fundamentals. See certifications.
Any pro tip that actually changes outcomes?
Bank solvable OA problems first, keep an error log, and rehearse one Jira-workflow or API explanation out loud before Technical Round 2. Correctness under time beats a half-finished clever solution.
Where can I read real interview experiences?
Start with Atlassian interview experience on this site, then cross-check recent community write-ups for your target level. Patterns shift by year - use them as maps, not scripts.
Atlassian - recent candidate experiences
Fresher SWE loops (2024-2025)
Profile patterns that got selected: B.Tech CSE/IT, roughly 7.5-8.5 CGPA, tier-2 and tier-1 mix, one internship or a strong project, steady DSA practice rather than last-week panic.
Online assessment: Timed coding on HackerRank or similar. Clean, fully passing solutions beat partial cleverness. Shortlist mail often arrived in a few days. Students who triaged prompts early kept both coding and aptitude (when present) alive.
Technical rounds: Coding such as longest substring without repeating characters (sliding window + hashmap), graph BFS, hash-map frequency problems. Domain chat around Jira-like workflows and concurrency - plain explanations worked better than buzzwords. Project deep dive: stack choice, hardest bug, what you would rebuild. Later rounds sometimes leaned into API design: resources, pagination, failure modes at fresher depth.
HR / managerial: Why Atlassian? Working with unclear requirements? Conflict on a team? Relocation comfort for Bangalore? Keep answers short: situation → what you did → result.
Takeaway candidates repeated: clear DSA plus a coherent workflow story beats a high CGPA with weak explanation. Talking through the approach before coding mattered as much as the final snippet.
What hurt other candidates in the same cycles: coding before clarifying constraints; treating HR as a formality; system-design jargon without a simple bottleneck story; optimising one hard OA item while leaving an easy problem incomplete; freezing when asked “what happens if two users edit the same issue?” with zero concrete answer.
Story-shaped notes students shared
Story 1 - Selected (CSE ~8.0): OA with fully passing solutions → Tech 1 sliding window with complexity narration → Tech 2 Jira state machine in plain English → HR teamwork STAR. What helped: connecting a college project to issue tracking without forcing the brand name.
Story 2 - Selected after a second tech lean into APIs (IT/ECE ~7.2): Weaker contest rating, stronger projects. Later round asked API design for comments. Takeaway: clear DSA plus coherent API story beat contest vanity metrics.
After you clear OA - what to do in the waiting week
- Re-solve every miss from your last two mocks cold.
- Speak two teamwork STAR stories and one conflict story without notes.
- Sketch a Jira-like state machine and a comments API on a blank doc.
- Warm one tree/graph medium in your interview language.
- Sleep and Bangalore logistics - do not open a new advanced DSA topic.
Mini design sketch students should rehearse
Two users edit the same issue field:
- Actors: User A, User B, issue service, audit log.
- Conflict: last-write-wins vs optimistic version check - pick one and say why for a fresher service.
- UX: show who edited last; avoid silent overwrite without a signal.
- Failure: version mismatch → refresh and retry with a clear message.
- Scale later: only after the above is clear - do not lead with Kafka.
That 90-second sketch beats a memorised microservices diagram.
More fresher narratives: Atlassian interview experience.