CVP of Design

We need to produce HTML fragment with sections: About the role? The posting includes "Who is Sonar?" then description, then "Position Description", then "What You Will Do", then "Experience And Qualifications", then "Additional Comments". We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. We have content for About the role (company description), Responsibilities (What You Will Do), Requirements/Qualifications (Experience And Qualifications). Possibly Skills could be part of Qualifications. Benefits, Pay, Schedule not present, so we should not include those sections. Also we should not repeat job title as heading. The job title is "CVP of Design". Not to be used as heading. We need to preserve all substantive information, remove boilerplate like EEO etc. The Additional Comments includes location, relocation, diversity statement, EEO, accommodation, background check, agency statement, AI tools usage. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Additional Comments includes diversity statement and EEO which is boilerplate; we should remove that. Also location info is substantive: "This role is based in Austin. We are unable to consider candidates unwilling to be in Austin, but we are willing to relocate the right candidate." That's location/relocation info, we can keep. Also maybe we keep "Additional Comments" as a section? But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "Additional Comments". We could incorporate location info into About the role or maybe a separate section like "Location". But not allowed headings beyond those? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but we should use those headings when appropriate. It also says "include a section ONLY when the posting has real, specific content for it". So we can create sections with those headings if we have content. For location, there is no heading like Location in the list, but we could put it under About the role as a paragraph. Or we could create a custom heading? Probably better to stick to the given headings. So we will have:

About the role

with company description and location info.

Responsibilities

with What You Will Do bullet list.

Requirements

maybe combine Experience And Qualifications. We could also have

Qualifications

separate but we have only one block; we could split into Requirements and Qualifications but risk thin sections. Better to combine into one section, maybe "Requirements". Or we could have both Requirements and Qualifications with similar content but that would be duplicate. The instruction: "Prefer a few substantive sections over many thin ones." So we will have About the role, Responsibilities, Requirements (or Qualifications). Choose Requirements. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities we list each bullet as
• . For Requirements we list each bullet as
• . We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the sections. Let's extract About the role content: The "Who is Sonar?" paragraph plus maybe the mission etc. Also location info from Additional Comments. We need to remove boilerplate: diversity statement, EEO, accommodation, background check, agency statement, AI tools usage. Also "We value diversity, equity, and inclusion ..." etc. Also "All offers of employment ..." etc. Also "Applications that are submitted through agencies ..." etc. Also "We may use artificial intelligence (AI) tools ..." etc. Also "If you would like more information about how your data is processed, please contact us." All that is boilerplate; remove. We keep: "This role is based in Austin. We are unable to consider candidates unwilling to be in Austin, but we are willing to relocate the right candidate." Also maybe we keep "We move with a mindset we call CODE: Committed to our customers and community. Obsessed with quality. Deliberate in our decisions. Effective as one team." That's part of company description; keep. Also "With over $400M in revenue and profitable, fast-paced growth, we are building the backbone of the AI software revolution." Keep. Also "If you’re hungry to have an impact, want to build at a fast pace, and ready to work at the forefront of AI, we want to hear from you." Keep? That's a call to action; maybe considered boilerplate? It's more like marketing but still substantive? It's not a duty/requirement. It's part of About the role; we can keep. Now Responsibilities: "What You Will Do" bullet list: - Own the end-to-end product design vision, including visual design, interaction design, workflows, and overall platform evolution across Sonar's product line. - Define and drive a design strategy that ties directly to measurable business outcomes, working with Product and Engineering leadership to prioritize investments. - Track and report on design's impact on key business and product metrics. - Build, scale, and lead a global design organization, including hiring, mentoring, and developing design talent to foster a high-performing, creative, and inclusive team culture. - Champion and evolve Sonar's design systems and UX best practices, ensuring consistency and quality across a complex, technical, developer-facing product suite. - Guide the design approach for agentic and AI-driven features, ensuring the team understands emerging patterns and best practices in this space. - Engage directly with customers, users, and industry leaders to gather insights, and translate those insights into actionable, high-impact design solutions. - Represent design at the executive level, communicating strategy, trade-offs, and progress to executive leadership and cross-functional, global stakeholders. - Partner with Product Management and Engineering to ensure design is embedded early in the product development process, not bolted on at the end. We need to keep all. Experience And Qualifications bullet list: - 7+ years of management experience in product design, UX, or a related field, with a proven track record of leading and scaling teams globally. - Demonstrated success in end-to-end product design leadership, including visual design, interaction design, workflows, strategic product thinking, and platform evolution. - Deep expertise in design systems and UX best practices, including experience designing for developer tools, API based tools, or similar technical/complex products. - Good understanding of the agentic domain and how it shapes product and design decisions. - Experience defining design strategy that drives measurable business outcomes. - Exceptional collaboration and communication skills, with the ability to work effectively across executive leadership, cross-functional teams, and global stakeholders. - Proven ability to mentor and develop design talent, fostering a high-performing, creative, and inclusive global design culture. - Deep understanding of customer needs and market trends, with experience engaging directly with users and industry leaders to translate insights into actionable, high-impact design solutions. We keep all. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce:

  About the role

  Who is Sonar? Sonar is driving the future of agent-centric software development. As the leader in AI code review and verification, we solve a critical problem: ensuring that software generated by AI-assisted developers or autonomous agents is reliable, secure, and maintainable. Integrating seamlessly with Claude Code, Codex, Cursor, GitHub Copilot, Gemini, and Devin, we help over 75% of the Fortune 100 build trusted, reliable, compliant software. Customers who use Sonar are 44% less likely to report an outage due to AI-generated code. We believe code verification is the critical missing link in the Agent-Centric Development Cycle (AC/DC). Industry giants like Nvidia, ServiceNow, Booking.com, Goldman Sachs, AstraZeneca, and Ford Motor Company count on us to provide independent, explainable, consistent review and governance of their AI-generated code via products like: SonarQube: The world’s leading AI code review and verification platform. SonarQube Foundation Agent: Currently topping the leaderboards for agentic software repair. SonarSweep & Sonar Context Augmentation: Providing the enterprise-grade context and constraints agents need to be truly effective. Our team operates across global hubs in Austin, Bochum, Dubai, Geneva, London, Singapore, Tokyo, and Washington D.C. We move with a mindset we call CODE: Committed to our customers and community. Obsessed with quality. Deliberate in our decisions. Effective as one team. With over $400M in revenue and profitable, fast-paced growth, we are building the backbone of the AI software revolution. If you’re hungry to have an impact, want to build at a fast pace, and ready to work at the forefront of AI, we want to hear from you. This role is based in Austin. We are unable to consider candidates unwilling to be in Austin, but we are willing to relocate the right candidate.

  Responsibilities

  • Own the end-to-end product design vision, including visual design, interaction design, workflows, and overall platform evolution across Sonar's product line.
  • Define and drive a design strategy that ties directly to measurable business outcomes, working with Product and Engineering leadership to prioritize investments.
  • Track and report on design's impact on key business and product metrics.
  • Build, scale, and lead a global design organization, including hiring, mentoring, and developing design talent to foster a high-performing, creative, and inclusive team culture.
  • Champion and evolve Sonar's design systems and UX best practices, ensuring consistency and quality across a complex, technical, developer-facing product suite.
  • Guide the design approach for agentic and AI-driven features, ensuring the team understands emerging patterns and best practices in this space.
  • Engage directly with customers, users, and industry leaders to gather insights, and translate those insights into actionable, high-impact design solutions.
  • Represent design at the executive level, communicating strategy, trade-offs, and progress to executive leadership and cross-functional, global stakeholders.
  • Partner with Product Management and Engineering to ensure design is embedded early in the product development process, not bolted on at the end.

  Requirements

  • 7+ years of management experience in product design, UX, or a related field, with a proven track record of leading and scaling teams globally.
  • Demonstrated success in end-to-end product design leadership, including visual design, interaction design, workflows, strategic product thinking, and platform evolution.
  • Deep expertise in design systems and UX best practices, including experience designing for developer tools, API based tools, or similar technical/complex products.
  • Good understanding of the agentic domain and how it shapes product and design decisions.
  • Experience defining design strategy that drives measurable business outcomes.
  • Exceptional collaboration and communication skills, with the ability to work effectively across executive leadership, cross-functional teams, and global stakeholders.
  • Proven ability to mentor and develop design talent, fostering a high-performing, creative, and inclusive global design culture.
  • Deep understanding of customer needs and market trends, with experience engaging directly with users and industry leaders to translate insights into actionable, high-impact design solutions.
  We should ensure no extra whitespace issues. Also ensure we didn't include any boilerplate like "We value diversity, equity, and inclusion". We removed that. Check if any duplicated lines: The "Who is Sonar?" paragraph includes some repeated content? It's fine. We need to ensure we didn