Atlassian Program / Project Manager Interview Questions

1.Tell me about a time you had an idea to improve a project process and you just ran with it — built something scrappy, got it in front of people fast. How did you decide when it was good enough to share?

2.Walk me through a project you ran where the team was spread across at least two time zones. What was the hardest coordination problem and how did you solve it?

3.Tell me about a team ritual or working agreement you introduced that actually stuck. How did you get the team to adopt it, and how do you know it made a difference?

4.Tell me about a time you used a tool you were managing or supporting as a heavy daily user — not just to test it, but to get real work done. What did you discover that you wouldn't have caught otherwise?

5.Tell me about a time you proposed running a quick experiment to validate a program decision — maybe a pilot, a prototype process, or a limited rollout — when the default expectation was a full launch. How did you make the case and what happened?

6.Tell me about a time a distributed project started slipping and the root cause turned out to be a communication or coordination gap — not a technical one. How did you diagnose it and what did you change?

7.Estimate how many Jira projects are actively used across Atlassian's Cloud customer base right now. Walk me through how you'd get to a number.

8.A team using Jira to run their sprint process tells you their velocity metric has been climbing for three straight quarters — but they're shipping less. How do you make sense of that and where do you start?

9.Atlassian is launching a new Confluence feature to a subset of enterprise customers in a controlled rollout. Three weeks in, adoption is 12% against a 40% target. How do you diagnose what's happening and what do you recommend?

10.You're asked to estimate whether migrating Atlassian's internal program tracking from a mix of spreadsheets and Confluence pages to a unified Jira structure would save meaningful time across the 50-person PMO. How do you build that case?

11.Atlassian wants to reduce the average time-to-value for new Jira Cloud customers — defined as the number of days from sign-up to first completed sprint. Currently that's 47 days. You're asked to propose a program to get it to 30. Where do you start and what would you actually change?

12.You're running a critical program and halfway through you realize your program plan has been approved and staffed based on a quarterly roadmap that's about to be reshuffled by a senior leadership OKR change. Two of your four workstreams may no longer align to any company priority. What do you do and how fast do you move?

13.You're managing a Jira project for a cross-functional team and the board has become a mess — hundreds of open tickets, stale epics, and nobody trusts the data. How do you clean it up without losing real work?

14.How do you decide what goes in a Confluence project page versus what stays in a Jira ticket? Walk me through your actual mental model.

15.You're managing a program with four workstreams and you notice one team's velocity has dropped 40% over the last two sprints with no change in headcount. How do you diagnose it and what do you do?

16.You've been asked to build a program status dashboard that five different stakeholder groups — engineering, product, finance, exec team, and customers — all need to use. How do you design that without building five separate things?

17.You're six weeks from a major Jira Cloud milestone delivery and you discover the program's dependency map has three unresolved cross-team blockers that nobody flagged in status updates. How did they stay hidden, and how do you unblock the program without burning goodwill?

18.Atlassian Intelligence is getting embedded across Jira and Confluence. If you were asked to evaluate whether an AI-generated project summary feature is actually saving your team time, how would you measure it — and what would a convincing 'yes' look like?

19.You're two days into running a new program kickoff and you realize the project brief you inherited has a major scope gap — a whole workstream nobody planned for. The exec sponsor already announced the timeline externally. What do you do?

20.A teammate on your cross-functional program is consistently missing their commitments — not by a lot, but enough that it's starting to create downstream risk. You're not their manager. How do you handle it?

21.Your program is on track, but you just learned that a parallel team is about to ship a feature that directly overlaps with yours — and they're two weeks ahead of you. Nobody coordinated this. What do you do in the next 24 hours?

22.You're PM on a program that's been greenlit and staffed, but three weeks in you realize the core assumption the business case was built on is probably wrong — and if you're right, the program may not deliver the expected ROI. What do you do?

23.You're leading a program to migrate a large Jira Cloud customer off a legacy workflow configuration. Halfway through, their team lead tells you the new setup is creating friction for their developers and they want to pause the migration. Your engineering lead says pausing is technically risky and will cost two weeks of rework. How do you decide what to do?

24.Leadership asks you to cut 25% of your program's scope to hit a revised budget target — and they want your recommendation in 48 hours. Your program has four workstreams and all of them have at least one stakeholder who will push back hard on any cut. How do you approach this?

25.Tell me about a time you had to get a 'yes' from a team or partner you had no authority over. What was your approach?

26.Walk me through a time you had to give a stakeholder — a senior one — an update they clearly didn't want to hear. How did you frame it and how did they react?

27.Tell me about a time you had to align two teams that had fundamentally different definitions of success for the same initiative. How did you get them to a shared one?

28.You're running a cross-functional program and a finance or legal partner keeps deprioritizing your requests — they're not hostile, just genuinely stretched thin. Your timeline is at risk. How do you handle it?

29.Tell me about the most misaligned executive sponsor you've worked with — someone whose direction kept shifting or who was disengaged when you needed decisions. How did you manage them?

30.You're managing a program with a major external customer — think an enterprise Jira Cloud rollout — and they go dark for two weeks right before a critical sign-off you need. No response to emails, no response to Slack. What do you do?