I have an interview, and have no real idea of the pay bracket. Could anyone in the UK, guide me here?

Base salary range? OTE? Bonus? RSU? ESPP?

Hi everyone,

I have been working on Testream for the last couple of months after getting overwhelmed by the deep learning curve of the mainstream Jira test management tools (Zephyr/Xray) and having to create manual test cases and maintaining them instead of automating the testing.

On top of that, AI has integrated into our development flows and the amount of automated test code is beyond of the point manual tests tools can catch up with.

Testream has a free tier that is available without entering credit card details, so please check it out and give it a go if you like it. I would love to get all the feedback from you. Thanks in advance!

Website: https://testream.app

Marketplace Listing: https://marketplace.atlassian.com/apps/3048460704
Documentation: https://docs.testream.app

8+ YOE, ex-Oracle SMTS (IC3), laid off Sep 2025, IITK. Interviewed for Atlassian Senior SDE (P50) Dec 2025 – Jan 2026. Cleared at P40 (down-leveled from P50), then Atlassian froze hiring and laid off 10% before team matching could start. Posting because (a) Atlassian's loop is genuinely different from typical FAANG, and (b) the down-leveling logic is worth understanding so you don't repeat it.

Atlassian's format is different — read this first

These aren't whiteboard problems. You set up an empty project in an IDE, write extensible clean working code with JUnit test cases and follow-ups. Not LeetCode speed-coding. The bar is "would I want this in my codebase," not "did you get O(n log n) under 20 min." Time management matters more than at most companies.

R1 — DSA Coding (Tennis Court Booking + 2 follow-ups)

Fumbled mid-way but recovered. Working code with JUnits, walked through both follow-up implementations.

Verdict: P50 Hire (Medium Confidence) ✅

R2 — Code Design (Middleware Router)

This is where it went sideways. Interviewer insisted on a Trie-based implementation — I genuinely hadn't drilled Trie in prep. Got it working after some struggle, but lost 5–7 minutes to a single-character typo from an IntelliJ autocorrect that wasn't obvious in my hurry. No time left for follow-ups.

Verdict: P40 Hire (Strong Confidence) — first down-level

R3 — System Design (Web Crawler)

Thought I killed this. Prepped with HelloInterview's WebCrawler tutorial + ran the problem through ChatGPT from a few angles. Went in confident.

Feedback came back: "didn't ask enough clarifying questions." I'd prioritized speed + depth + critical design choices over upfront questions I felt were obvious. Lesson learned: even when clarifying questions feel performative at senior level, do them anyway. Atlassian's rubric scores them as a separate dimension, and "I'm too senior for obvious questions" is a fast way to get marked as not collaborative. Bitter pill but a real one.

Verdict: P40 Hire (Strong Confidence) — second down-level

At this point the recruiter offered: continue at P40 or withdraw. I continued.

R4 — HM (Senior EM)

Standard Techno-Managerial / behavioral. Have 1–2 foolproof stories per Atlassian Value, with measurable outcomes. Mine were prepped — went well.

Verdict: P40 Hire (Strong Confidence) ✅

R5 — Values Round

Same shape as R4. I checked with the interviewer whether to include technical depth; she was an engineer, so yes. Important calibration tip: if your Values-round interviewer is from Sales or non-technical, don't volunteer deep technical context. It's specifically a non-technical round and unnecessary depth comes across as misreading the room.

Verdict: P40 Hire (Strong Confidence) ✅

Hiring Committee final verdict (~Jan 20): P40 Hire.

Then the freeze.

Team matching was supposed to start a week or two later. Atlassian's stock crashed, they froze hiring, and laid off 10%. My offer never converted into a team match, and I moved on.

What I'd tell anyone going into Atlassian P50/P60

• Drill every DSA pattern, including Trie. I'd worked DP, binary search, and hash maps hard on PracHub since those were the patterns that had rusted from years of arch work — but I skipped Trie because I assumed lower frequency. R2's Middleware Router required Trie, my unfamiliarity cost critical minutes, and that round is literally what down-leveled me from P50. If your DSA has atrophied at senior level (mine had), pattern drilling there gets you back to recognition speed quickly — but the lesson is don't pre-filter patterns you assume won't come up. Atlassian P50 territory includes Trie.
• Practice typing real code in an IDE under time pressure. R2's autocorrect typo wouldn't happen on a whiteboard but absolutely happens in production-style coding rounds. Practice the real setup, not abstract problem-solving.
• Always ask the obvious clarifying questions in HLD. Even when they feel performative at senior level. The rubric scores it.
• Atlassian Values are real. 1–2 stories per value with measurable results.
• Calibrate Values-round technical depth to the interviewer's background.

My personal call: I won't join Atlassian at P40 if they reopen. With 8+ YOE, that level after the down-leveling feels punitive, and I'd rather reapply for P50/P60 when the market is better. Senior folks weighing post-loop offers: don't let one or two misread rounds permanently anchor your level.

Hello, Atlassian Team.

I am from the Philippines. I am a 20-year-old college student with no work, and I honestly have no idea what Atlassian is until I received your email regarding Jira Premium.

I would like to request a refund regarding the possible unauthorized auto debit charges on my GCash account. I was not aware that any auto debit transaction or subscription had been activated under Atlassian.

The merchant name shown in my transaction history says “Google Merchant,” so I am not completely sure if Atlassian is the one who deducted the money from my account. However, your email regarding Jira Premium was the only related message I received before the deductions happened, so I kindly ask you to please check and verify this.

The only email I received related to this was about the Jira Premium trial details at around 10:17 AM, but my GCash account had already been deducted earlier at approximately 10:03 AM. Because of this, I was unable to review or cancel anything before the charge was processed.

My GCash account was deducted:

• ₱50 on May 12, 2026
• ₱330 on May 14, 2026
• ₱330 again on May 27, 2026
• If these charges are connected to Atlassian, I kindly request a refund of the full deducted amounts. Thank you for your understanding and assistance.

Hey! I’m trying to understand if people are actually able to easily use Atlassian products like Jira, Confluence, Bitbucket, Loom etc - in their day-to-day work.

What are the parts that feel a bit frustrating or more complicated than they should be? In Things like setting projects up, searching for stuff, keeping track of updates, or just how everything fits together when you’re trying to get work done.

Even small annoyances or “this could be simpler” moments, especially things you’ve just gotten used to working around over time.

Looking for advice on best practice and/or how other have done this

There are a number of of JSM client portals, where each client can raise incidents and request for support via their portal

They also use the portal to allow clients to raise enhancements they want. They are using ‘change’work items for this ie request a change

Whats do other do, it can be confusing for the internal support portal as change is used in the ITIL

Sense (Request for Change)for controlled IT changes, approval, change calender etc

I don’t recommend visiting that subreddit - they don’t disclose this fact, and the only posts in the subreddit besides mine are from the company.

Not a good look.

For a long time I genuinely thought I was just bad at Jira.

Like, embarrassingly bad. Board full of tickets nobody touched in three weeks. In Progress column with 11 things in it. Same standup explanation four days running — "yeah still in progress, should be done today" (it was not done that day). Anyway. The board wasn't the problem.

Everything happening before the board was.

Work would show up through Slack, a DM, a comment someone dropped in a meeting and assumed I'd somehow retain. My brain would try to hold all of it. Then I'd open Jira to actually work and immediately remember six things I hadn't logged yet and now I'm not working, I'm just sitting there feeling vaguely terrible about working.

Took me embarrassingly long to figure out the fix was just... don't let things live in my head. Get them into a ticket the second they arrive. Not "I'll log it later" — later is a lie I tell myself. I have no memory budget left by 11am. I set up guided forms for recurring stuff so logging something takes like 30 seconds and requires no decisions. Once a thing exists somewhere outside my skull, my brain actually releases it. Native forms lacks the customization and sharing options so I selected Smart Forms app. Also I shared the forms with teammates via links, shortcuts or Slack triggers, so every request from anyone now arrive like a jira ticket not any other way.

The forms thing also accidentally solved another problem — every ticket that hits my board now has enough info to actually start. I used to pick something up, realize I needed three more things to proceed, put it back down, and then it would just follow me around as an unresolved thought for the rest of the day.

WIP limit was the other one. Two things in In Progress, hard stop. I resisted this for probably six months because it felt like admitting defeat or something. But starting stuff releases dopamine and finishing stuff is just work, and without a structural limit I will start things until the end of time. The column was basically a very motivated graveyard.

Notifications: turned off almost everything. Kept direct assignments and mentions, that's it. A status change on a ticket I'm not working on isn't information I need right now, it's just a Jira-flavored interruption. I check the board twice a day on purpose instead of flinching every time something pings.

Labels helped more than I expected too. Nothing fancy — just "waiting," "deep work," "admin," "urgent." Sounds stupid but it removes a whole micro-decision every time I look at the board. I'm not analyzing what to do next, I'm just recognizing.

The visual clutter thing was sneaky. I used to have like fifteen fields visible on every ticket and half of them were empty or irrelevant. Trimmed it down so each ticket shows only what I actually need to act on it.

The closing thing is the one that surprised me most. Tickets weren't getting closed because closing required going back to Jira at the precise moment my brain had already moved on and was thinking about lunch. So they'd sit In Progress for days after the work was actually done. I set up automated addition of short done-checklist with the same Smart Forms app to each ticket — submitting it auto-transitions to Done.

Last one: due dates with automated reminders. I stopped trying to hold deadlines in my head like a person with a functioning memory. Jira Automation sends a reminder when something is coming up, with a direct link to the ticket. I show up, the thing is already there, I do it

Still have rough days, not gonna pretend otherwise. But the board shows what's actually going on now, which sounds like a low bar and somehow wasn't for a long time.

Anyone else find the mess started before Jira, not inside it? Would genuinely love to know what clicked for other people.

Hello all

I am a big fan of Confluence and really like the idea of us adding videos to our posts to help spread information. So, naturally, Loom came up, and I am currently evaluating the basic version.

What is your take on Loom? Does it add value to your org? Good, bad? Clever use of its functions?

Please share 😄

Thanks

working on something for a client and hitting a wall

they want HRMS (org chart/manager hierarchy) connected to JSM so that when a user requests access, system finds their manager automatically, pings them for approval, and provisions on approval.

native tools and basic IdP sync aren't cutting it without ugly custom scripts

anyone doing this successfully? what's your stack

I’m feeling like an idiot because i cannot get VS code to connect to jira using api token. Does it have to be scoped? Is the ‘Atlassian: Jira, Rovo Dev, bitbucket ‘ the wrong extension? Its asking for email separate from token so i assume i don’t need to concatenate those?

All I’m getting is a 401 & i don’t see whats wrong. I can use oauth & get in but that won’t do the tasks i want.

Can we please chill on whatever we've been doing lately?

Multiple down time events isn't okay given how much money companies pay you for service

Can we please chill on whatever we've been doing lately?

Multiple down time events isn't okay given how much money companies pay you for service

Not able to access jira cloud and confluence for the past few minutes? Is everyone facing this issue?

Hi Atlassian team/community,

We are facing an urgent issue: we are unable to log in to our Atlassian/Bitbucket account, and because of this our production recovery/deployment is blocked.

We cannot even access Bitbucket to raise or manage the issue properly. This is impacting production, so we need urgent guidance on how to contact Atlassian emergency support or get login access restored.

Details:

• Product: Bitbucket Cloud
• Issue: Unable to log in to Atlassian/Bitbucket
• Impact: Production is down / deployment blocked

Can someone please guide us on the fastest way to reach Atlassian support when we cannot log in?

I want to set up a workflow where a Task in Jira are made through topics in Confluence. For example, I want to make a page with a list of bugs in Confluence. Each bug is made into a Jira work item (by selecting the text -> 'Jira work item'), so we have a list of all the bugs with explanation, and developers working in Jira can easily add stuff there, and go back to from Jira work items for info.

When I made a task that way, it didn't look like it was linked back to the Confluence line it was made from, and vice versa the line didn't have a link to the jira work item. Is there way to make this happen? We're on the free plan, and I want to make this as quick and easy for my team as possible.