Staff Product Designer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only if posting has real specific content. We have content: About SecurityScorecard (company overview) maybe not needed? The instruction says "About the role" heading for role description. We have "About the Role:" section. So we can put that under About the role
. Then we have "What You'll Do" which is responsibilities. So Responsibilities
with list.
Then "Required Qualifications" and "Preferred Qualifications" maybe combine into Qualifications? Could have Qualifications
with sublists? But instruction says use headings for sections; we could have Required Qualifications and Preferred Qualifications as separate sections? They didn't list those as example headings but we can still use Required Qualifications
and Preferred Qualifications
. However they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "Qualifications" is acceptable. We could put both required and preferred under Qualifications with maybe two lists: Required and Preferred. But we need to preserve all substantive info; we can separate.
We also have "Who You Are" which could be Skills? Or maybe "Skills". Could treat as Skills section.
We have Benefits section with details.
We have Pay: "estimated total compensation range for this position is $180,000 - $250,000 (base plus bonus)." Also mention performance-based incentive, equity. So we can include Pay section.
Schedule: hybrid work model details. So we can include Schedule.
We must not include boilerplate like EEO, immigration sponsorship, etc. Remove those.
We must not include repeated lines.
We must not include cookie/navigation/legal/EEO etc.
We must not include application instructions.
We must not include duplicated lines.
We must not include minor metadata like Job ID.
We must not create sections with filler like "commensurate with experience". We have actual content.
Now produce HTML fragment.
Structure:
About the role
... (the About SecurityScorecard paragraph? Actually "About the Role:" includes description of role and hybrid work model. We'll put that in About the role.) Then Responsibilities: list of bullet points from "What You'll Do". Each bullet as
Required Qualifications
andPreferred Qualifications
. But instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't forbid other headings but we should prefer those. However we can still use Required Qualifications as a heading under Qualifications? Might be okay. But to be safe, we can haveQualifications
and inside have two- with headings? But we cannot have headings inside
- .
For About the role: we have two paragraphs: company overview and role description. Could combine into one
with two sentences? Better to keep as
containing both paragraphs separated by
? But we can just put them in onewith line break. However we should preserve substantive info; we can have two
elements under the heading? The instruction: Use
for prose. So we can have multiple
under heading. Thus:
About the role
SecurityScorecard is the global leader in cybersecurity ratings, with over 12 million companies continuously rated, operating in 64 countries. Founded in 2013 by security and risk experts Dr. Alex Yampolskiy and Sam Kassoumeh and funded by world-class investors, SecurityScorecard’s patented rating technology is used by over 25,000 organizations for self-monitoring, third-party risk management, board reporting, and cyber insurance underwriting; making all organizations more resilient by allowing them to easily find and fix cybersecurity risks across their digital footprint. Headquartered in New York City, our culture has been 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 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
- . Could use
Required:
then list. But that adds extra markup not prohibited. Simpler: UseRequired Qualifications
andPreferred Qualifications
. The instruction didn't forbid those; they just gave examples. I think it's fine. Then Skills: maybe "Who You Are" could be Skills. We'll put that asSkills
with list. Then Benefits:Benefits
with list. Then Pay:Pay
with paragraph. Then Schedule:Schedule
with paragraph. We must not repeat job title as heading. Not include "About SecurityScorecard" as heading? Could be part of About the role paragraph. Let's extract content. About SecurityScorecard paragraph: first paragraph about company. We'll include that in About the role? Actually About the role section should contain role description, not company overview. But we have "About SecurityScorecard:" then "About the Role:" We could combine both under About the role heading: first paragraph about company, then role description. That preserves all info. Thus About the role: include company overview paragraph and role description paragraph. Now Responsibilities: list from "What You'll Do". Let's extract each bullet: - 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. Now Required Qualifications: - 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: - 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 (Skills): - 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. Benefits: - Specific to each country, we offer a competitive salary, stock options, Health benefits, and unlimited PTO, parental leave, tuition reimbursements, and much more! Pay: - The estimated total compensation range for this position is $180,000 - $250,000 (base plus bonus). Actual compensation for the position is based on a variety of factors, including, but not limited to affordability, skills, qualifications and experience, and may vary from the range. In addition to base salary, employees may also be eligible for annual performance-based incentive compensation awards and equity, among other company benefits. Schedule: - 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. Now we need to output HTML fragment only. We'll wrap each section inheading and then
or