[Hiring] Senior Product Designer @360 Privacy

Role Description

The Senior Product Designer, Design Systems owns UX across 360 Privacy’s product. This role will own UX work and decisions for our platform. It needs business context, design taste, and technical understanding in equal measure, and it is an AI-native role for a designer who works through a design system. 360 Privacy already has a complete system built in Claude: design tokens, a full component set, and documented rules for how each component should be used. This role takes it over, evolves it, and uses it every day to turn product ideas, roadmaps, and leadership updates into polished mockups, customer-facing PDF report designs, slides, and documents. Using the existing design system, AI tools draft quickly and this role’s time goes to judgment, refinement, and craft.

This is the company’s only design role, and its work is prioritized in this order: product UX ownership, the design system that supports it, the digital exposure risk reports, then leadership and enablement materials as capacity allows. This is not a front-end engineering role; it does not own production code. It is also not a role that solves each feature with new layouts. Engineers build from what this role specifies, AI tools draft from what it documents, and the job is to make reinvention unnecessary.

Qualifications

• 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.

Requirements

• 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.

Success Measures

Success in this role includes:

First 90 Days

• Making day-to-day UX decisions independently, with the CTO out of the critical path for routine UX work.
• Full command of 360 Privacy’s design system: you can explain any rule and the reason behind it.
• Deep fluency in the problem 360 Privacy exists to solve, the work the company actually delivers, and the broader ecosystem in which it operates. By the end of your first 90 days, you should be able to explain the company’s value, and the genuine complexity behind that value, to anyone you encounter in the course of your work.
• At least one feature carried from discovery to launch with a PM, built entirely from system components.
• Executive exposure risk report template live with customers.

By End of Year One

• Product, engineering, and leadership treat you as the owner of UX.
• The full report family (executive, analyst, action-oriented) in customer use.
• Engineers build new features from existing patterns, and custom styling is rare.
• Marketing, sales, and CX produce on-brand materials from your templates without needing you.
• AI tools produce drafts the team uses with light edits, not rework.