Portfolio and Outcomes
This is the core artifact for assessing your craft, product thinking, and impact. Interviewers expect 2–3 strong case studies with clarity around problem framing, constraints, options considered, and business/user results. Strong performance shows sensible trade-offs, clear rationale, and specific metrics.
Be ready to go over:
- Problem framing and scope – How you aligned on the problem statement and constraints.
- Before/after flows – What changed in the user journey and why.
- Impact metrics – Activation, task success, adoption, retention, support volume, or related KPIs.
Advanced concepts (less common):
- North Star metric design and diagnostic sub-metrics.
- Cohort-based analysis and funnel breakouts.
- Experimentation design (A/B, holdouts, guardrail metrics).
Example questions or scenarios:
- “Walk me through two portfolio case studies end-to-end—what did you ship and what changed?”
- “Which KPIs moved, by how much, and how did you measure causality versus correlation?”
- “What trade-offs did you make to ship v1, and what did you defer?”
Product Discovery and Research
Discovery de-risks bets and focuses the roadmap. Interviewers look for hypothesis-driven work that uses appropriate methods and results in clear decisions. Strong candidates synthesize research into design principles and opportunity areas, not just findings.
Be ready to go over:
- Assumption mapping and prioritization.
- Method selection – When you used interviews, usability tests, surveys, or analytics.
- Insight-to-decision – How research drove a pivot or sharpened scope.
Advanced concepts (less common):
- JTBD framing to anchor solution spaces.
- Mixed-method triangulation to resolve conflicting signals.
- Diary or longitudinal studies for complex workflows.
Example questions or scenarios:
- “Describe a time research changed your solution direction—what signal convinced you?”
- “How do you choose between qualitative and quantitative methods under time pressure?”
- “Show me how you defined success and validated it post-launch.”
Interaction Design and Design Systems
Atlassian expects strong interaction fundamentals and system thinking. You’ll be evaluated on information architecture, states and edge cases, and effective use of a design system. Strong performance shows component-level reasoning, accessibility, and consistency across screens.
Be ready to go over:
- IA and navigation for complex hierarchies and permissions.
- States and error handling across empty, loading, success, and failure states.
- Design system use and when to extend or propose new components.
Advanced concepts (less common):
- Token-driven theming and cross-product consistency.
- Accessibility audits (WCAG 2.1 AA) and semantic fidelity.
- Performance-aware design for heavy data tables and dashboards.
Example questions or scenarios:
- “Whiteboard a flow to create and manage a shared project in Jira—include edge cases.”
- “How would you extend the system to support a new pattern without breaking consistency?”
- “What accessibility considerations guided your decisions here?”
Collaboration in the Triad and Stakeholder Management
Success hinges on alignment with PM and Engineering while partnering with Content Design and Research. Interviewers probe your facilitation, conflict resolution, and decision clarity. Strong candidates show how they keep teams moving and make decisions transparent.
Be ready to go over:
- Working agreements and operating rhythms with PM/Eng.
- Decision logs and trade-off documentation.
- Feedback loops with content, research, and support.
Advanced concepts (less common):
- RICE or impact/effort frameworks for prioritization.
- Design reviews that scale across multiple pods.
- Partnering with enterprise customers for early feedback.
Example questions or scenarios:
- “Tell us about a disagreement with PM/Eng—what was the decision and outcome?”
- “How do you run efficient design critiques that lead to decisions?”
- “Describe a cross-team dependency you unblocked.”
Execution, Delivery, and Quality
You will be assessed on how you get from concept to shipped product. Interviewers look for clarity in specifications, collaboration during implementation, and post-launch iteration. Strong performance includes design QA, change logs, and measurable improvements after release.
Be ready to go over:
- Specs and dev handoff—what you write and how you collaborate.
- Design QA and how you track and resolve defects.
- Post-launch iteration—what you learned and what you changed.
Advanced concepts (less common):
- Feature flagging and staged rollouts.
- Experimentation platforms and guardrails.
- Operational metrics linked to design (support tickets, time-to-resolution).
Example questions or scenarios:
- “Show a spec you wrote—how did you ensure no ambiguity for engineers?”
- “Describe a launch that underperformed—what did you learn and change?”
- “How do you balance velocity and quality under tight deadlines?”
Content Design and UX Writing Collaboration
Many teams integrate content design in interviews and assignments. Interviewers evaluate whether your UI language reduces cognitive load and drives task success. Strong candidates partner early with content to align terminology, hierarchy, and help patterns.
Be ready to go over:
- Microcopy and empty states that guide users.
- Terminology decisions across product and docs.
- Localization and tone for enterprise contexts.
Advanced concepts (less common):
- Content testing for comprehension and action rates.
- Glossary frameworks for multi-product consistency.
- In-product education versus external docs trade-offs.
Example questions or scenarios:
- “How did you collaborate with content design on this flow?”
- “Rewrite this dialog to reduce friction—what changed and why?”
- “Walk us through your approach to empty states in onboarding.”
