Staff Product Designer

We need to output HTML fragment with sections: About the role (but note we already have "About SecurityScorecard" which is company description; we should not repeat job title heading. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. We need to include sections only when posting has real, specific content. The posting includes: About SecurityScorecard (company description). Should we include that as a section? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid "About the company". But they gave examples; we can include "About SecurityScorecard" as a heading? It might be considered a section. However they said "do NOT repeat the job title as a heading (the page already shows it)". The job title is "Staff Product Designer". Not repeated. So we can include "About SecurityScorecard" as a heading. But we need to decide which sections to include: About SecurityScorecard, About the Role (maybe "About the role" heading), Responsibilities (What You'll Do), Required Qualifications, Preferred Qualifications, Who You Are (maybe "Who you are" could be a section like "About you" but not in list; but we could treat as "Who you are" maybe as a section but not in examples. Could also combine into "Qualifications". However they said prefer a few substantive sections over many thin ones. We could have sections: About SecurityScorecard, About the Role, Responsibilities, Qualifications (combining required and preferred), Benefits (including Pay). Also maybe "Who you are" could be part of Qualifications or omitted. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated: "Specific to each country, we offer a competitive salary, stock options, Health benefits, and unlimited PTO, parental leave, tuition reimbursements, and much more! The estimated total compensation range for this position is $180,000 - $250,000 (base plus bonus)." So we can include Benefits section with that info. Pay is included within Benefits; we could still have Pay section but they said prefer few sections; we can include Benefits covering pay. Schedule: they mention hybrid work model: employees within 75 miles required onsite 1-2 days per week; outside eligible for fully remote. That's schedule info. So we could include a Schedule section. Thus sections: About SecurityScorecard, About the Role, Responsibilities, Qualifications (maybe split Required and Preferred but could combine), Benefits, Schedule. We must not include boilerplate like EEO, legal, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like company description, role description, responsibilities bullet points, qualifications bullet points, preferred qualifications bullet points, who you are bullet points, benefits details, schedule details. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must output only HTML fragment, no /, no markdown fences. Let's craft. First, maybe a short paragraph for metadata? Not needed. We'll start with

  About SecurityScorecard

  then

  with the company description. Then

  About the Role

  then

  with role description paragraph. Then

  Responsibilities

  then
  with each responsibility as
  • . The responsibilities are listed under "What You'll Do". We need to capture each bullet. List: - Master high-complexity workflows. Own the end-to-end design of deeply technical AI-enabled workflows, including third-party vendor risk assessments, automated security questionnaires, and continuous monitoring. - Ground decisions in evidence. Run usability tests, synthesize behavioral and product analytics (e.g., FullStory, Pendo), and fold research findings into your design iterations. - Design for enterprise constraints. Systematically design for complex B2B paradigms, including role-based access control, multi-tenant environments, and complex data-filtering mechanisms, treating these as design material rather than obstacles. - Bridge design and code with AI prototyping. Work directly against our codebase and design system, using Claude to produce interactive prototypes that are anchored in how our product actually works, not invented from scratch. Communicate design intent through prompting. - Work AI-native across your design process. Leverage AI to synthesize research, rapidly visualize concepts, explore edge cases, and validate functional prototypes to compress iteration cycles without lowering the craft bar. - Strengthen our design system. Contribute to our design system to ensure durable patterns and machine readability for AI prototyping at scale, with accessibility as a default (WCAG 2.2). - Build designer confidence with AI. Raise the product design team's AI fluency through collaborative prototyping workshops and shared AI prototyping techniques to elevate the team's collective technical skillsets. - Partner cross-functionally. Work alongside Product and Engineering to turn ambiguous briefs into defensible solutions, and push back with evidence when the brief is wrong. We'll keep each as separate
  • . Then

    Qualifications

    maybe split required and preferred but we can combine with subheadings? But we cannot use other heading levels? Only

    for section headings; we could still use

    but not specified. Safer to keep just

    Qualifications and then within that we can have

    for required qualifications prose and then

    for list? But required qualifications are a list of bullet points. We'll output
    • for each. Required qualifications list: - 7+ years of product design experience, with at least 3+ years designing B2B SaaS experiences in a platform environment. B2C design background does not translate to this role. - A proven portfolio demonstrating strong handling of high-complexity UI challenges, such as multi-dimensional data, analytics dashboarding, permissions management, or deep system nesting, plus a track record of turning ambiguous problems into shipped work without heavy oversight. - Demonstrated, hands-on use of AI in your own design practice, including prompting AI tooling such as Claude to build interactive prototypes in code that are grounded in an existing codebase and design system. Be prepared to show what you built, how you prompted it, and what it changed about the outcome. General familiarity with AI tools is not sufficient; we're looking for real practitioner experience. - Demonstrated experience working with and contributing to design systems. - Strong fluency with Figma and related AI-assisted design tooling. - A clear understanding of cognitive load, decision-making frameworks, and how to design interfaces that reduce user error in high-stakes security environments. - Hands-on experience integrating usability testing, product analytics, and accessibility standards (WCAG 2.2) into your process by default. Preferred qualifications list: - Experience with cybersecurity, Third-Party Risk Management (TPRM), or Governance, Risk, and Compliance (GRC). - Experience designing AI-enabled features that earn user trust, fail gracefully when the model is wrong, and keep users in control of the outcome. - Hands-on front-end capability beyond prototyping. You have written HTML, CSS, and component code that shipped, and you can contribute to a design system in the repo, not just in Figma. Who You Are bullet points: - You push yourself to do your best work. You hold a high craft bar and you're motivated by getting things right, not just getting them done. - You have a growth mindset. You actively seek out feedback and incorporate it, and understand how to give feedback. - You care about the people around you. You're committed to elevating your teammates. We don't hire for a "rockstar" mentality; we hire people who make the whole team better. - You lead with humility. You're confident in your craft and secure enough to stay open, curious, and collaborative. - You are someone that moves fast between prototypes, continually iterating using AI to validate your ideas. We could include Who You Are as a section, but not in examples. Could incorporate into Qualifications or maybe as a separate section "Who you are". Since they said prefer few sections, maybe we can incorporate Who You Are into Qualifications as a subsection but we don't have subheadings. Could just add as another
      under Qualifications with a preceding

      "Who you are:" but that might be okay. Better to have a separate section "Who you are" as

      Who you are

      with list. It's substantive. Then Benefits section:

      Benefits

      with

      containing the benefits description and compensation range. Then Schedule section:

      Schedule

      with

      describing hybrid work model. We must not include boilerplate like EEO, legal, etc. Remove those. Now ensure we preserve all substantive information: we have included company description, role description, responsibilities, qualifications (required, preferred, who you are), benefits, schedule. Check that we didn't miss any detail: The company description includes many details: over 12 million companies continuously rated, operating in 64 countries, founded 2013 by Dr. Alex Yampolskiy and Sam Kassoumeh, funded by world-class investors, patented rating technology used by over 25,000 organizations for self-monitoring, third-party risk management, board reporting, cyber insurance underwriting; making all organizations more resilient... Headquartered in NYC, culture recognized by Inc Magazine as a "Best Workplace”, by Crain’s NY as a "Best Places to Work in NYC," and as one of the 10 hottest SaaS startups in New York for two years in a row. Most recently, SecurityScorecard was named to Fast Company’s annual list of the World’s Most Innovative Companies for 2023 and to the Achievers 50 Most Engaged Workplaces in 2023 award recognizing “forward-thinking employers for their unwavering commitment to employee engagement.” SecurityScorecard is proud to be funded by world-class investors including Silver Lake Waterman, Moody’s, Sequoia Capital, GV and Riverwood Capital. We need to include all that. Role description paragraph: "We are seeking a highly technical Staff Product Designer to join our Product Design team at SecurityScorecard. In this role, you will design complex AI-powered cyber risk workflows touching on third-party risk assessments, automated security questionnaires, and continuous monitoring. You possess deep expertise in B2B SaaS user experience paradigms, such as dense data, complex permissioning, and multi-tenant workflows. You have deep experience leveraging AI in all phases of your design process, including grounding your prototypes directly in our codebase and design system rather than generating disconnected concepts, and you're comfortable building and scrapping fast rather than getting attached to a single direction. This role follows a hybrid work model based on proximity to our office locations. Employees who live within 75 miles of our Midtown NYC or Downtown Austin office are required to work onsite 1–2 days per week. Employees who live outside a 75-mile radius of both offices are eligible for fully remote work." We included hybrid info in schedule; but role description also includes that. We could keep it in role description and not duplicate in schedule. But schedule section should contain the schedule info; we can still keep it there and maybe remove from role description to avoid duplication? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay as long as we preserve. But we might want to avoid duplication but it's not prohibited. However better to keep role description without the hybrid details and put them in schedule. But role description currently includes that sentence; we could edit it out? That would be summarizing away detail (removing). We must preserve all substantive information; removing that sentence would lose detail. So we need to keep it somewhere. We could keep it