Staff Product Designer, Design Systems

Bangalore, India Senior Posted 2026-04-16

Don't apply into the void — reach the hiring manager

ResuMail finds the recruiters and hiring managers behind this Staff Product Designer, Design Systems role at Ethos, drafts a personalised outreach email, and schedules the send — so your application actually gets seen.

Reach the hiring manager ›

About this role

<div class="content-intro"><h3>About Ethos</h3> 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.</div><h2>Design at Ethos</h2> 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. You'll help define how design gets made at Ethos as we grow, including how we adopt AI as a core part of the craft. <h2>About the Role</h2> We're 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 0→1 opportunity. Ethos is not yet "design-system mature," and we're deliberately building it in an AI-native way rather than retrofitting later.  You'll 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. <h2>Duties and Responsibilities</h2> <h3>Audit, Architect & Plan</h3> <ul> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Audit the current product UI and existing design artifacts; identify the highest-leverage opportunities to standardize, consolidate, and reduce inconsistency.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">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.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">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. </li> </ul> <h3>Design-to-Code Integration</h3> <ul> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">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.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Partner with Front-End engineers to translate the system into reusable, well-architected components with clear APIs, states, and accessibility built in.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Own the component lifecycle end-to-end: versioning, release notes, deprecations, and handoffs.</li> </ul> <h3>Adoption & Enablement</h3> <ul> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">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.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Create documentation that people (and agents) actually use: guidelines, do/don't examples, usage rationale, and decision records, structured so they're machine-readable as well as human-readable.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Drive pragmatic adoption: start where it matters most, ship iteratively, and build credibility through visible product impact.</li> </ul> <h3>AI Enablement & Prompt-to-Production</h3> This is the throughline across the three areas above. You won't build this alone, but you'll set the design foundations that make it work. <ul> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Design system AI integration and maintenance: Define how AI agents help audit, tag, and maintain the system's structure — and where human review gates belong (naming decisions, deprecations, new pattern introductions).</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Design-to-code (with a human in the loop): Shape the pipeline that takes a Figma frame or a PM's prompt through Cursor / Claude Code into Storybook-validated components, including the review checkpoints that keep quality, accessibility, and brand integrity intact.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">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.</li> </ul> <h3>Measurement & Iteration</h3> <ul> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">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.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Partner with Research and Data where useful to connect system changes to product outcomes (quality, user confidence, conversion efficiency).</li> </ul> <h2>Qualifications and Skills:</h2> <h3>Must-have</h3> <ul> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">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.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">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).</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Track record of driving adoption through pragmatic, builder-friendly processes rather than heavyweight governance.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Strong working knowledge of modern front-end concepts (tokens, components, states, responsive behavior) and comfort collaborating closely with engineers on tradeoffs.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Experience setting accessibility standards and shipping accessible components (WCAG-informed practices, inclusive design thinking).</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Genuine curiosity and hands-on experience with AI-assisted design and development workflows — you've used tools like Cursor, Claude Code, or equivalent, and have a point of view on where humans need to stay in the loop.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">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.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Ability to thrive in ambiguity and build structure where it doesn't yet exist — pragmatic, opinionated, iterative.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Clear communicator who can align diverse stakeholders and influence without formal authority.</li> </ul> <h3>Nice-to-have</h3> <ul> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Strong visual and interaction craft in Figma (component architecture, scalable patterns, high-quality specs). We value this, but the role's center of gravity is organization, integration, adoption, and AI enablement — not pixel-pushing.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Experience with Storybook or similar component documentation environments.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Experience with video, motion, illustration/iconography, or tone systems.</li> <li style="font-family: 'times new roman', times, serif; font-size: 12pt;">Prior experience shaping AI agent workflows, prompt scaffolding, or evals for design/front-end outputs.</li> </ul> #LI-Hybrid #LI-NG1  <div class="content-conclusion">Don’t meet every single requirement? If you’re excited about this role but your past experience doesn’t 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 our <a href="https://res.cloudinary.com/getethos/image/upload/v1684458868/00_CMS/CURRENT_CRPA_Privacy_Notice_for_Job_Applicants_05-23.docx_-_Google_Docs_lr4j43.pdf" target="_blank" data-saferedirecturl="https://www.google.com/url?q=https://res.cloudinary.com/getethos/image/upload/v1684458868/00_CMS/CURRENT_CRPA_Privacy_Notice_for_Job_Applicants_05-23.docx_-_Google_Docs_lr4j43.pdf&source=gmail&ust=1684616836493000&usg=AOvVaw2BlajerdOWoHawb8unUdI4">California Candidate Privacy Notice</a>. Recruitment Notice: Please be aware of recruitment scams. All legitimate communication from our team will only come from email addresses ending in @ethos.com or @getethos.com. 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.</div>

How to get this job at Ethos

Don't rely on the portal. Cold applications for a role like Staff Product Designer, Design Systems land in a pile of hundreds. A direct, personalised message to the hiring manager or a referrer is the fastest way in.
Find the right person. ResuMail surfaces the actual recruiters and hiring managers at Ethos — not a generic careers inbox.
Send tailored outreach. ResuMail drafts an email personalised to your resume and this role, then paces and schedules sends so you stay out of spam.
Follow up. One polite nudge after 5–7 days roughly doubles reply rates — scheduled for you.

Reach Ethos's hiring managers today.

Free to start. No credit card. Built for Indian job seekers.

Start free with ResuMail ›