Senior Product Designer, Design Systems

360 Privacy develops digital exposure reduction products for enterprises, executives, and high-profile individuals. The Senior Product Designer, Design Systems owns product UX and evolves the design system, while creating customer risk reports and other team materials using the system and AI tools.

Responsibilities:

• Own UX decisions across the product, from flows and information architecture to interaction details, and make the call rather than waiting for sign-off
• Ground each design in the business goal, the customer’s context and what engineering can realistically build
• Be the central point for all things UX: the person product, engineering and leadership go to for UX answers, bringing in the CTO only for decisions with major business or technical impact
• Maintain design tokens for color, typography, spacing, elevation and radius, with semantic names that engineers and AI tools can apply without guessing
• Keep the component set small and deliberate so engineers pick from known variants, and extend core view patterns (explorer, detail and dashboard views; panels, widgets, drill-downs and edit modals) so new features slot into an existing pattern
• Keep the system’s rules in plain language and its documentation machine-readable (token files, component reference, usage rules), so people and AI tools follow it reliably
• Build high-fidelity, interactive prototypes in Claude to test flows and features, using only system components and tokens
• Turn roadmaps, strategy notes and status updates into polished, on-brand slides and documents for leadership and customers, and build enablement materials (one-pagers, feature explainers, battle cards, support guides) for marketing, sales and CX
• Review AI-generated output for off-system colors, one-off styles and pattern drift, and fix the documentation when a tool keeps getting something wrong
• Build reusable templates, example artifacts and prompt patterns so anyone on the team can produce on-brand work
• Design a family of PDF report templates, each tuned to its reader: an executive summary of risk level, trend and decisions; an analyst view of findings, evidence and severity; and an action-oriented checklist of what to fix, who owns it and how to verify it
• Turn complex risk data into charts, scores and summaries a non-technical reader understands in under a minute
• Design for print and PDF (page breaks, readable density, accessible severity colors, layouts that hold up in grayscale), and build report layouts, chart styles and severity language into the system
• Join product discovery early with your PM and carry the work through feedback and launch
• Hand engineers specs that name patterns and variants, not pixel-tuned one-offs, and flag when feature work reaches for custom styling, a sign the system is missing something
• Keep accessibility (contrast, focus states, readable data density) built into the system from the start

Requirements:

• 5+ years of product design, including at least 2 owning or co-owning a design system (tokens, components, documentation)
• A track record of owning UX decisions for a product end to end, not just executing someone else's direction
• Business context, design taste and technical understanding: you connect design decisions to business goals, hold a strong, well-reasoned point of view on what good looks like, and understand enough about how software is built to design what engineering can ship
• AI-native way of working: AI tools are how you design, not an add-on to a Figma workflow. Your portfolio shows work you produced with AI tools, the prompts, templates or documentation you wrote to get consistent output, and how you caught and fixed what the tools got wrong
• A track record of getting a design system adopted by engineers and other teams, not just built
• Strong visual craft for dense, data-heavy interfaces such as dashboards, tables and admin tools, carried across product UI, decks and documents
• Information design for reports: a portfolio piece that turns dense or technical data into a document tailored to a specific audience, such as executives versus practitioners
• Clear technical writing: you can explain a rule, its reason and its exceptions in a few sentences that both people and AI tools follow
• Working knowledge of how design tokens map to implementation (for example, Tailwind or CSS variables) so your specs are buildable. Reading code is helpful; writing it isn't required
• User experience first, with system discipline: you tailor each flow to the persona using it, work within the system, and weigh the engineering impact of every decision before you propose it
• Speed and product partnership: you complete design and feedback loops for features and decks in 1 to 2 weeks, run larger work like the report family on a milestone plan, and treat PM feedback as part of the process rather than a final review
• This position must be performed from within the United States
• Background in B2B security, privacy or data products; you can hold a substantive conversation about severity and remediation, not just the interface
• Familiarity with headless component libraries (such as Radix) and how a visual layer sits on top of them
• Motion and data visualization chops for charts, widgets and status indicators