Product Designer

Required Qualifications

• Visual Craft for Data-Dense UI: A portfolio that holds up to detailed scrutiny — strong colour theory, deliberate visual hierarchy, considered information architecture for complex workflows. This is the bar, not a nice-to-have. Your interview will dig into specific design choices and why you made them.
• Product Design Track Record: 4-7 years of professional product design experience, with shipped work in B2B SaaS. We’re flexible on years; demonstrated craft and clear ownership matter more than time served.
• Data-Heavy B2B Interfaces: Direct experience designing for complex workflows, dense data, and technical audiences. Dashboards, investigation tools, developer products, security platforms — the kind of UI where information density and decision support actually matter.
• AI as Tool, Not Crutch: You use AI tools (Figma AI, Cursor, v0, Midjourney, ChatGPT/Claude, etc.) as part of your daily workflow and can speak credibly to what they’re good for and where they break down. Critically, every design choice you ship should hold up on its own — AI accelerates your work, it doesn’t substitute for foundational craft.
• Product-Strategic Thinking: Track record of driving product direction, not just executing on briefs. You’ve influenced what to build with research, framed problems for leadership, and made business-impact calls — ideally in environments where you operated without a dedicated PM.
• Deep Engineering Collaboration: Demonstrable history of shipping work in tight partnership with engineers — including backend. Pairing on implementation, working in design tokens, understanding the systems your designs land in, building consensus rather than shipping around resistance.
• Design Systems Experience: Background building or meaningfully contributing to a design system in a production product. You think in components, tokens, and patterns, not one-off screens.
• Customer-Led Approach: Comfortable running discovery directly with users, synthesising what you hear, and using that to make calls about what to build. You don’t wait for research to be handed to you.
• Nice to haves: Experience designing for cybersecurity, developer tools, or other technical product domains Background designing agentic or AI-native product experiences (not just AI features bolted onto existing products) Early-stage startup experience where you’ve operated without a manager or established design function
• Experience designing for cybersecurity, developer tools, or other technical product domains
• Background designing agentic or AI-native product experiences (not just AI features bolted onto existing products)
• Early-stage startup experience where you’ve operated without a manager or established design function
• Visual Craft for Data-Dense UI: A portfolio that holds up to detailed scrutiny — strong colour theory, deliberate visual hierarchy, considered information architecture for complex workflows. This is the bar, not a nice-to-have. Your interview will dig into specific design choices and why you made them.
• Product Design Track Record: 4-7 years of professional product design experience, with shipped work in B2B SaaS. We’re flexible on years; demonstrated craft and clear ownership matter more than time served.
• Data-Heavy B2B Interfaces: Direct experience designing for complex workflows, dense data, and technical audiences. Dashboards, investigation tools, developer products, security platforms — the kind of UI where information density and decision support actually matter.
• AI as Tool, Not Crutch: You use AI tools (Figma AI, Cursor, v0, Midjourney, ChatGPT/Claude, etc.) as part of your daily workflow and can speak credibly to what they’re good for and where they break down. Critically, every design choice you ship should hold up on its own — AI accelerates your work, it doesn’t substitute for foundational craft.
• Product-Strategic Thinking: Track record of driving product direction, not just executing on briefs. You’ve influenced what to build with research, framed problems for leadership, and made business-impact calls — ideally in environments where you operated without a dedicated PM.
• Deep Engineering Collaboration: Demonstrable history of shipping work in tight partnership with engineers — including backend. Pairing on implementation, working in design tokens, understanding the systems your designs land in, building consensus rather than shipping around resistance.
• Design Systems Experience: Background building or meaningfully contributing to a design system in a production product. You think in components, tokens, and patterns, not one-off screens.
• Customer-Led Approach: Comfortable running discovery directly with users, synthesising what you hear, and using that to make calls about what to build. You don’t wait for research to be handed to you.
• Nice to haves: Experience designing for cybersecurity, developer tools, or other technical product domains Background designing agentic or AI-native product experiences (not just AI features bolted onto existing products) Early-stage startup experience where you’ve operated without a manager or established design function
• Experience designing for cybersecurity, developer tools, or other technical product domains
• Background designing agentic or AI-native product experiences (not just AI features bolted onto existing products)
• Early-stage startup experience where you’ve operated without a manager or established design function