Cloudflare · Primly Community

Cloudflare product designer and UX interview: portfolio review format and what they focused on

alex_design · 4 replies

went through cloudflare's product designer / UX interview process this spring. sharing because the design interview landscape at infra-focused companies is weird and i didn't find useful signal when i was prepping.

the context. cloudflare design is a small team relative to company size. you're designing for a very technical user base: developers, security engineers, network admins. that context shapes everything about how they evaluate you.

the process. recruiter screen, then a portfolio review + 45-min conversation, then a design challenge (take-home, one week), then a final round with 3 people.

portfolio review. they asked me to walk through 2-3 projects, targeting ones relevant to developer tooling or technical products. they pushed hard on the problem framing stage, not just the solution. questions like: how did you define the problem before designing anything? what did you learn from users that changed your initial direction? how did you scope what you wouldn't solve?

they did not care much about visual craft for its own sake. they cared about whether you had a point of view and could explain it.

take-home design challenge. they gave me a specific scenario involving a Cloudflare Workers dashboard feature. one week. my output was a figma file + 2-page written rationale. the written rationale mattered as much as the designs themselves. they want to see that you can articulate constraints and trade-offs.

final round. three conversations back to back: one with a product manager (all about prioritization and how you work with PMs), one with an engineer (they'll poke at technical feasibility of your designs, be prepared to defend), one with the design manager (culture, values, career ambitions).

a few things i'd highlight: know cloudflare's product surface at least at a high level. dashboard.cloudflare.com is worth spending time in. be ready to talk about designing for density and information architecture, not just pretty screens. their users want data, not delight. they asked about accessibility explicitly. not just 'did you consider it' but 'walk me through how you'd validate contrast ratios and keyboard navigation in your design system'.

i came out of it with an offer for a senior product designer role. the team seems solid and the work is genuinely interesting if you like complex technical products.

4 replies

ux_uma

the point about 'they don't care about visual craft for its own sake' is true of so many infra/developer-tools companies and i wish someone had told me earlier. i've seen really strong visual portfolios bomb at companies like this because the candidate couldn't explain the research that led there.

brand_ben

did they push on the design system side at all? cloudflare has a pretty mature component library (Cloudflare Design's open source stuff). i'm curious whether they wanted to talk about contributing to that or whether it was more product-design focused.

alex_design

they mentioned the design system a few times but it wasn't a deep focus in my loop. the PM conversation touched on it briefly when we talked about how design and eng collaborate. my sense is there are more system-design-focused roles that would go deeper, but for the product designer track it was background knowledge rather than a main topic.

director_dee

on the 'written rationale matters' point: this is the thing i look for when reviewing design candidates too. designers who can write clearly about trade-offs tend to be the ones who can hold their ground in a cross-functional conversation. the figma file is almost a formality at senior level.