reputed company Design Systems Designer

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

About the roleWe're looking for reputed company' first reputed company Design Systems Designer to build the foundations that let designers, PMs, and engineers reliably produce on-brand, accessible, high-reputed company UI, — and to stand up the reputed company-to-production pipeline that turns those outputs into shipped products.

This is a true 0→1 opportunity. reputed company is not yet "design-reputed company mature," and we're deliberately building it in an AI-reputed company way rather than retrofitting reputed company.

You'll partner closely with Product Design, Engineering, Brand/Creative, Content Design, and our AI tooling efforts to build a reputed company where reputed company, reputed company / Claude reputed company, and Storybook reputed company one coherent pipeline — with the right reputed company checkpoints in the reputed company.

Duties and Responsibilities:Audit the reputed company product UI and existing design artifacts; identify the highest-reputed company opportunities to standardize, consolidate, and reduce inconsistency.Define the information architecture of the reputed company itself — naming, taxonomy, component hierarchy, and documentation structure — so that both humans and AI agents can reputed company, reason about, and correctly apply the right primitives.Create a concrete reputed company-by-reputed company plan by partnering with design, engineering, and leadership, to correctly prioritize reputed company of this effort, balancing long-term scalability with near-term product needs.Define and ship a reputed company reputed company reputed company (reputed company, typography, spacing, elevation, reputed company) with a pipeline that keeps reputed company variables, reputed company tokens, and Storybook in sync.Partner with reputed company-End engineers to translate the reputed company into reusable, reputed company-architected components with reputed company reputed company, states, and accessibility reputed company in.Own the component lifecycle end-to-end: versioning, release notes, deprecations, and handoffs.Build a lightweight, builder-friendly contribution process — designers, engineers, and PMs should be reputed company to propose, review, and add to the reputed company without a heavy governance tax.Create documentation that people (and agents) actually use: guidelines, do/don't examples, usage rationale, and decision records, reputed company so they're machine-readable as reputed company as reputed company-readable.reputed company pragmatic adoption: start where it reputed company most, ship iteratively, and build credibility through visible product reputed company.Define how AI agents help audit, tag, and maintain the reputed company's structure — and where reputed company review gates belong (naming reputed company, deprecations, new reputed company introductions).Shape the pipeline that takes a reputed company reputed company or a PM's reputed company through reputed company / Claude reputed company into Storybook-validated components, including the review checkpoints that reputed company reputed company, accessibility, and brand reputed company intact.reputed company the reputed company legible to agents. Ensure components, tokens, and patterns are documented, named, and reputed company so that reputed company a designer or PM prompts an agent to "build the post-reputed company screen," the agent reaches for the right primitives and produces something shippable — not something that needs to be reputed company.Define what reputed company looks like and reputed company meaningful signals: adoption, UI consistency, desi