Staff Product Designer, Design Systems

About Ethos

Ethos is a leading life insurance technology company on a mission to protect families by democratizing access to life insurance and empowering agents at scale. With its robust three-sided technology platform Ethos is transforming the life insurance experience for consumers agents and carriers alike. Ethos offers instant accessible products and a seamless online process that requires no medical exams and just a few health questions; it eliminates traditional barriers making it easier than ever for everyone to protect their families. Ethos is redefining how life insurance is bought sold and underwritten.

Design at Ethos

Design at Ethos plays a meaningful role in shaping our product and customer experience end-to-end. We work cross-functionally to solve hard problems build products that matter and raise the bar for craft in a highly regulated decision-heavy domain. Youll help define how design gets made at Ethos as we grow including how we adopt AI as a core part of the craft.

About the Role

Were looking for Ethos first Staff Design Systems Designer to build the foundations that let designers PMs and engineers reliably produce on-brand accessible high-quality UI and to stand up the prompt-to-production pipeline that turns those outputs into shipped products.

This is a true 01 opportunity. Ethos is not yet design-system mature and were deliberately building it in an AI-native way rather than retrofitting later.

Youll partner closely with Product Design Engineering Brand/Creative Content Design and our AI tooling efforts to build a system where Figma Cursor / Claude Code and Storybook form one coherent pipeline with the right human checkpoints in the loop.

Duties and Responsibilities

Audit Architect & Plan

• Audit the current product UI and existing design artifacts; identify the highest-leverage opportunities to standardize consolidate and reduce inconsistency.
• Define the information architecture of the system itself naming taxonomy component hierarchy and documentation structure so that both humans and AI agents can find reason about and correctly apply the right primitives.
• Create a concrete step-by-step plan by partnering with design engineering and leadership to correctly prioritize pieces of this effort balancing long-term scalability with near-term product needs.

Design-to-Code Integration

• Define and ship a scalable token strategy (color typography spacing elevation motion) with a pipeline that keeps Figma variables code tokens and Storybook in sync.
• Partner with Front-End engineers to translate the system into reusable well-architected components with clear APIs states and accessibility built in.
• Own the component lifecycle end-to-end: versioning release notes deprecations and handoffs.

Adoption & Enablement

• Build a lightweight builder-friendly contribution process designers engineers and PMs should be able to propose review and add to the system without a heavy governance tax.
• Create documentation that people (and agents) actually use: guidelines do/dont examples usage rationale and decision records structured so theyre machine-readable as well as human-readable.
• Drive pragmatic adoption: start where it matters most ship iteratively and build credibility through visible product impact.

AI Enablement & Prompt-to-Production

This is the throughline across the three areas above. You wont build this alone but youll set the design foundations that make it work.

• Design system AI integration and maintenance: Define how AI agents help audit tag and maintain the systems structure and where human review gates belong (naming decisions deprecations new pattern introductions).
• Design-to-code (with a human in the loop): Shape the pipeline that takes a Figma frame or a PMs prompt through Cursor / Claude Code into Storybook-validated components including the review checkpoints that keep quality accessibility and brand integrity intact.
• Adoption in the AI canvas: Make the system legible to agents. Ensure components tokens and patterns are documented named and structured so that when a designer or PM prompts an agent to build the post-intent screen the agent reaches for the right primitives and produces something shippable not something that needs to be rebuilt.

Measurement & Iteration

• Define what success looks like and track meaningful signals: adoption UI consistency design/dev cycle time accessibility improvements and the quality of AI-generated output against the system.
• Partner with Research and Data where useful to connect system changes to product outcomes (quality user confidence conversion efficiency).

Qualifications and Skills:

Must-have

• Has owned a design system end-to-end at a product company including the organizational work of getting it adopted not just the design artifact.
• Deep fluency with design-to-code integration: tokens pipelines component APIs versioning and keeping design and code in sync in practice (not just in theory).
• Track record of driving adoption through pragmatic builder-friendly processes rather than heavyweight governance.
• Strong working knowledge of modern front-end concepts (tokens components states responsive behavior) and comfort collaborating closely with engineers on tradeoffs.
• Experience setting accessibility standards and shipping accessible components (WCAG-informed practices inclusive design thinking).
• Genuine curiosity and hands-on experience with AI-assisted design and development workflows youve used tools like Cursor Claude Code or equivalent and have a point of view on where humans need to stay in the loop.
• Sets direction for peers and partner teams. Comfortable making opinionated calls on ambiguous tradeoffs (governance vs. speed system purity vs. product reality human review vs. agent autonomy) and defending them with evidence.
• Ability to thrive in ambiguity and build structure where it doesnt yet exist pragmatic opinionated iterative.
• Clear communicator who can align diverse stakeholders and influence without formal authority.

Nice-to-have

• Strong visual and interaction craft in Figma (component architecture scalable patterns high-quality specs). We value this but the roles center of gravity is organization integration adoption and AI enablement not pixel-pushing.
• Experience with Storybook or similar component documentation environments.
• Experience with video motion illustration/iconography or tone systems.
• Prior experience shaping AI agent workflows prompt scaffolding or evals for design/front-end outputs.

#LI-Hybrid
#LI-NG1

Dont meet every single requirement If youre excited about this role but your past experience doesnt align perfectly with every qualification in the job description we encourage you to apply anyway. At Ethos we are dedicated to building a diverse inclusive and authentic workplace.

We are an equal opportunity employer.. We do not discriminate on the basis of race religion color national origin gender sexual orientation age marital status veteran status or disability status. Pursuant to the SF Fair Chance Ordinance we will consider employment for qualified applicants with arrests and conviction records.

To learn more about what information we collect and how it may be used please refer to ourCalifornia CandidatePrivacy Notice.

Recruitment Notice: Please be aware of recruitment scams. All legitimate communication from our team will only come from email addresses ending in @ or @.
We will never ask for payment banking details or sensitive personal information during the hiring process. If you are contacted by someone claiming to represent us from a different email address please treat it as fraudulent.