UX: Staff Product Designer, Design Systems - Visual

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "About This Role" which is description of role; we can map to "About the role". Then responsibilities list: bullet points under "Role We’re looking for..." Actually that's responsibilities. Then "Who We’re Looking For" is qualifications/requirements/skills. We need to separate into Requirements, Qualifications, Skills maybe. The instruction: use headings for those categories. We need to decide what content fits each. We have: - About The Team (but we shouldn't repeat job title; we can include About the team? Not in list of allowed headings. Only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not include About The Team unless we map to About the role? Probably we should include About the role covering the description of role and team context. - Responsibilities: bullet list under "Role We’re looking for a strategically-minded...". Those are responsibilities. - Requirements: maybe the "Who We’re Looking For" bullet points (the list of qualifications). Could split into Requirements (must-have) and Qualifications (preferred) but not clear. The posting lumps them as "Who We’re Looking For". We could treat that as Requirements (or Qualifications). Since we need to avoid thin sections, maybe combine into one section "Requirements". But we have also Skills heading; we could extract skills from that list (e.g., expert-level design craft, leading multiple projects, presenter, relationships, vision, prior hands-on ownership of multi-tier token architecture, etc.) Might be redundant. Better: Use "About the role" for narrative description. Use "Responsibilities" for bullet list of duties. Use "Requirements" for the bullet list under "Who We’re Looking For". Possibly also "Skills" could be omitted if same as Requirements. But we need to avoid empty sections. We could put "Skills" as a subsection of Requirements? But instruction: use headings only when posting has real specific content for it. If we put Skills with same content as Requirements, it's duplicate; better to not include Skills if not distinct. Benefits: The posting includes "Pay & Benefits" section with description of benefits and compensation. It mentions Annual Cash Compensation Range and benefits description. So we can include Benefits and Pay sections. Schedule: Not mentioned; no schedule info. So omit Schedule. Thus output:

About the role

... (combined About The Team and About This Role narrative)

Responsibilities

• ... each bullet from Role We’re looking for...

Requirements

• ... each bullet from Who We’re Looking For...

Benefits

... description of benefits and perks...

Pay

Annual Cash Compensation Range $190,100—$304,200 USD ... maybe also mention equity, RSUs, overtime, etc.

We must not include boilerplate like EEO, legal, etc. Also remove duplicated lines. We need to preserve all substantive information. Let's extract. First, About The Team paragraph: "People love using HubSpot because it’s an essential product that gives them the tools and insights they need to grow their business. Trellis is HubSpot's enterprise design system — the shared foundation that powers every product surface across CRM, Marketing Hub, Sales Hub, Service Hub, Commerce Hub, Breeze AI, and the growing portfolio of agentic experiences. Trellis is not a style guide or a Figma library. It is the connective tissue between design intent and product reality at scale: a living system of tokens, components, patterns, documentation, and tooling that thousands of designers and engineers across HubSpot depend on every day to build with speed, quality, and consistency. We are at a defining inflection point. AI is fundamentally expanding what a design system is. In the AI-native era, Trellis must be machine-readable as well as human-readable: tokens need semantic structure that AI tools can reason about, documentation needs to serve both the designer using Figma and the AI coding tool generating product UI. This is the environment you're stepping into, and it is exactly the right moment to shape how HubSpot builds." About This Role paragraph: "The Staff Product Designer — Tokens & Visual Language is the foundational design role on the Trellis team. You are the DRI for the token architecture that every component, every pattern, and every product surface built on Trellis depends on. You are also the steward of HubSpot's product design language — the visual grammar of color, typography, spacing, iconography, and motion that makes HubSpot's product experiences feel coherent, polished, and distinctly HubSpot. This is not a role where you maintain what exists. You will inherit a token foundation and evolve it to meet requirements that didn't exist when it was built: multi-theme support, dark mode, density scaling, AI-generated product surfaces that need token constraints baked into their toolchain, and a platform that is migrating five major product surfaces simultaneously. You will make architectural decisions that cascade across the entire system — decisions that require the judgment to be right, the craft to be defensible, and the authority to hold the quality bar when product team urgency pushes against it." We can combine these into About the role. Responsibilities bullet list (under "Role We’re looking for a strategically-minded, outcomes-oriented design leader to own and evolve our Design System. In this role, you’ll:" then bullet points): - Design and steward the three-tier token graph — global, semantic, and component-specific — ensuring it scales to meet multi-theme, multi-platform, and multi-density requirements across the full HubSpot product surface - Make and defend architectural token decisions: naming conventions, tier boundaries, semantic abstraction levels, and the tradeoffs between flexibility and constraint that determine how well the system scales - Manage token migrations without breaking downstream consumers — designing safe, phased rollout processes and the governance model that keeps consuming teams aligned - Own the visual language of Trellis: the system-level decisions in color, typography, spacing, iconography, and motion that make HubSpot's product experiences feel intentional, cohesive, and distinctly HubSpot - Serve as the "final eye" on visual quality: hold the aesthetic quality bar for a system consumed by hundreds of designers, and navigate disagreements about visual direction with clarity, craft evidence, and authority - Develop and communicate design principles and tenets that give your team and consuming designers a framework for navigating visual decisions without requiring alignment overhead on every choice - Lead the effort to make the Trellis token layer machine-readable: structuring token names and documentation in formats that AI coding tools, MCP integrations, and generative UI systems can consume and apply correctly - Partner with product teams across Hubspot as the token and visual language authority — helping them build on the system correctly and surfacing friction points that indicate the system needs to evolve - Collaborate with engineers on implementation fidelity: understand the technical constraints that shape token decisions, and advocate for design intent within those constraints credibly and practically - Contribute to Trellis governance: participate in the contribution review process, hold the quality standard for design language decisions that originate in product teams, and help shape the policies that prevent token drift across the platform Now "Who We’re Looking For" bullet list: - You’re known for your expert-level design craft and ability to lead multiple projects at a time. - You’ve worked hands-on leading teams to evolve the content, visual, interaction, motion and illustration assets and patterns that bring a brand ethos to life in our digital product ecosystem. - You’re a compelling presenter with a clear and informed POV. - You’ve built solid relationships with your cross-functional partners, demonstrating a deep understanding of strategy and business goals. - You're well-known for your vision and thought leadership and everyone on the team looks to you for long-term thinking. - Prior hands-on ownership of a multi-tier token architecture at enterprise scale — has designed and shipped a token system for a multi-product or multi-platform environment, not just implemented tokens within one - Demonstrated track record of making consequential token architecture decisions and owning their downstream effects: naming, tier structure, semantic abstraction, and breaking change management - Full command of visual design as a systems discipline — understands how color, typography, spacing, iconography, and motion function as a unified language rather than independent decisions, and can articulate the principles behind each - Experience evolving a mature design language: knows how to push it forward without breaking it, has navigated the tension between brand evolution and system consistency, and can make those tradeoffs visible to stakeholders - Portfolio that demonstrates the aesthetic output of their token and systems work — not just technically correct token architecture, but a coherent, high-quality visual product - Has formed their own design tenets and can deploy them to navigate ambiguous visual decisions without extensive alignment overhead - Working knowledge of or demonstrated interest in machine-readable design systems — understands W3C DTCG token format, the role of semantic naming as machine-readable intent, and how token documentation can be structured for AI tool ingestion - Stays engaged with the evolution of design token standards and tooling: Tokens Studio, Style Dictionary, Figma Variables API, and emerging MCP/AI integrations — and can make informed Trellis pipeline decisions as the ecosystem evolves - Approaches the AI tooling layer with both curiosity and rigor: excited about what becomes possible, clear-eyed about what needs to be designed deliberately - Operates with Staff-level autonomy: capable of identifying the right problem, proposing the right solution, and driving it to resolution without requiring close direction - Comfortable partnering with engineering on implementation fidelity — understands technical constraints well enough to advocate for design intent credibly, and to recognize when design decisions need to adapt to engineering reality - Can communicate token architecture decisions to non-specialist stakeholders — makes the invisible infrastructure of a design system legible to product leadership without oversimplifying it - Has experience as a quality bar holder: has held the visual standard for a system used by many designers, navigated disagreement with clarity, and done so in a way that builds trust rather than creating friction Now Benefits and Pay section: From "Pay & Benefits": "The cash compensation below includes base salary, on-target commission for employees in eligible roles, and annual bonus targets under HubSpot’s bonus plan for eligible roles. In addition to cash compensation, some roles are eligible to participate in HubSpot’s equity plan to receive restricted stock units (RSUs). Some roles may also be eligible for overtime pay. Individual compensation packages are tailored to your skills, experience, qualifications, and other job-related reasons. This resource will help guide how we recommend thinking about the range you see. Learn more about HubSpot’s compensation philosophy. Benefits are also an important piece of your total compensation package. Explore the benefits and perks HubSpot offers to help employees grow better. At HubSpot, fair compensation practices aren’t just about checking off the box for legal compliance. It’s about living out our value of transparency with our employees, candidates, and community. Annual Cash Compensation Range $190,100—$304,200 USD" Then later: "At HubSpot, we value both flexibility and connection. Whether you’re a Remote employee or work from the Office, we want you to start your journey here by building strong connections with your team and peers. If you are joining our Engineering team, you will be required to attend a regional HubSpot office for in-person onboarding. If you join our broader Product team, you’ll also attend other in-person events, such as your Product Group Summit and other gatherings, to continue building on those connections. If you require an accommodation due to travel limitations or other reasons, please inform your recruiter during the hiring process. We are committed to supporting candidates who may need alternative arrangements" That's more about work arrangement (flexibility). Could be considered Schedule? Not exactly schedule but location flexibility. The instruction says include Schedule only if posting actually states them. It mentions flexibility: Remote employee or work from Office, in-person onboarding required