Atlassian · Primly Community

Atlassian product designer / UX interview and portfolio review: what they're really looking for

brand_ben · 5 replies

just wrapped up the atlassian product designer loop and wanted to share a real account because the info out there is thin.

i applied for a senior product designer role on the Jira product team. atlassian's design org is sizable and fairly mature, there's a clear difference between what they want vs a startup or agency.

process overview recruiter call. hiring manager intro call. portfolio review (separate 30 min session). then a 4-5 hour virtual onsite.

the portfolio review this was earlier in the process than i expected. 30 minutes, i presented 2 case studies. they were less interested in aesthetics and much more interested in: how did you frame the problem, who did you involve, what did you cut and why, what shipped and what happened. my usual agency portfolio framing (problem, process, outcome) worked fine but i had to sharpen the "outcome" part with real metrics. design without measurement is a weaker story here.

the onsite Design exercise: they gave me a prompt about redesigning a specific Jira workflow and 30 minutes to think through it, then i presented to two designers. no expectation of polish, they were watching how i thought: did i identify assumptions, did i ask questions, did i consider edge cases and different user types. Cross-functional round: a PM and an engineer asked behavioral questions specifically about working across functions. conflict stories came up. Research and craft round: questions about how i do user research, how i communicate findings, a few "how would you approach X" scenarios. Behavioral: atlassian values. same as every other track.

what clicked for me treating the design exercise like a collaborative thinking session, not a performance. and being really honest about what didn't work in past projects instead of spinning everything into success. they pushed back pretty directly when i glossed over a rough patch in a project.

long process but felt rigorous in a good way.

5 replies

ux_uma

the early portfolio review is interesting, most companies do that at the onsite. makes me think they're using it as a filter before investing in the full loop. did you feel like the portfolio review determined whether you moved on?

brand_ben

100% felt like a filter. the hiring manager specifically said something like "we want to make sure there's alignment before we bring you in for the full day." i'd treat it as seriously as an onsite round.

alex_design

the "what did you cut and why" question is so underrated for senior design roles. at staff+ level that's probably 40% of your job. good to know atlassian actually asks about it.

returner_ren

i'm considering applying for a mid-level designer role after a gap. the portfolio piece is what worries me most, my most recent shipped work is 2 years old. how much did recency matter vs the quality of the thinking in the case studies?

brand_ben

ren, honest answer: they cared about depth of thinking more than recency in my experience. one of my two case studies was 3 years old but i could speak to it fluently and it had strong outcomes. i'd pick your best work, not your newest. that said, if you can add any context about what you've been doing or thinking about during the gap, weave it in.