Strategy question
If you were the PM of Jira for mobile, what will be your roadmap?
- Atlassian
- Strategy
- Hard
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Tests roadmap prioritization for a mobile-specific version of an established desktop-first B2B product, requiring the candidate to identify mobile-native use cases rather than porting desktop features.
How to approach it
- Clarify the mobile use case: quick status checks and lightweight actions on the go, versus full project planning, since desktop remains better suited to the latter.
- Segment users by role: developers who mostly need to glance at and update ticket status, and managers who need approvals and quick triage from anywhere.
- Identify the highest-value mobile-native action: fast ticket triage and status updates (assign, comment, change status) during standups or while away from a desk.
- Prioritize roadmap items in that order: first, fast read and light-edit actions (status changes, comments, assignments); second, push notifications for mentions and blockers; third, lightweight approval flows for managers.
- Deprioritize complex features like full board configuration or detailed reporting, which are rare, precision-heavy tasks better suited to desktop.
- Define success as daily active mobile usage among users who also use desktop, and reduced time-to-response on mentions and blockers.
What a strong answer includes
- Identifies mobile-native, on-the-go use cases (status updates, mentions) instead of trying to replicate the full desktop feature set on mobile.
- Sequences the roadmap by usage frequency and mobile suitability, not by feature parity with desktop.
- Uses illustrative numbers as assumptions: assume the majority of desktop actions are read-only status checks, which mobile can serve well even without full editing parity.
- Explicitly deprioritizes complex configuration and reporting features, showing deliberate scope discipline for a mobile-first roadmap.
Common mistakes
- Proposing to port the full desktop feature set to mobile instead of prioritizing mobile-native use cases.
- Not segmenting by role (developer versus manager), missing that their mobile needs differ.
- Measuring success by feature count shipped instead of actual usage and responsiveness gains.
Likely follow-up questions
- What would you explicitly cut from the mobile roadmap and why?
- How would you handle notification overload on mobile?
- How would you measure if mobile usage is cannibalizing or complementing desktop usage?
More strategy questions
- What would be your roadmap if you were the PM of JIRA?Atlassian · Strategy · Hard
- Should Google build a food delivery app?Atlassian · Strategy · Hard
- If you were the CPO of Atlassian, what would be your strategy for company growth?Atlassian · Strategy · Hard
- It is your responsibility as the Product Manager at Atlassian to develop a plan for expanding into new markets. Investigate your opportunities.Atlassian · Strategy · Hard
- Google Keep is a free product to save, share notes etc. How would you make it a subscription product & monetize it?Google · Strategy · Hard
- How would you launch (roll out) Amazon Go?Amazon · Strategy · Hard
More questions from Atlassian
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 9: Prove it paid off: outcomes, economics, and pricing
- Chapter 14: Get the job: the AI PM interview loop