Senior Product Designer, Verifications

We need to output HTML fragment with sections: About the role, Responsibilities (What You'll Do), Requirements/Qualifications (What You Bring), Benefits (What We Offer), Pay (salary ranges), Schedule (in-office expectation). Also maybe include About Checkr? 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. So we can include About the role? The posting includes "About The Role" heading. That is a section heading we can use. Then "What You'll Do" corresponds to Responsibilities. "What You Bring" corresponds to Requirements/Qualifications. "What We Offer" corresponds to Benefits. Pay: we have salary ranges for locations. Schedule: in-office expectation (3+ days a week). Also maybe include "About Checkr"? Not required but could be included as a section? The instruction: include a section ONLY when the posting has real, specific content for it. About Checkr is present, but not listed as a standard heading; but we could include as a section maybe "About Checkr". However they gave examples of headings but not limited to those. Probably we should include About Checkr as a section? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. Might be safe to include About Checkr as a heading? It's not in the list but could be considered similar to "About the role". However they said "Do NOT repeat the job title as a heading (the page already shows it)". About Checkr is not job title. Could include. But they said "Prefer a few substantive sections over many thin ones." So maybe combine About Checkr into About the role? But About the role already exists. Could we include About Checkr as a paragraph under About the role? Probably better to keep About Checkr as a brief intro paragraph before sections. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should strip EEO etc. Also remove Applicant Privacy Policy etc. Also remove Equal Employment Opportunities etc. Also remove "Legitimate Checkr emails..." etc. Also remove "At Checkr, we believe an in office work environment..." maybe that's schedule info, we keep that. We need to preserve all substantive information. So we need to keep details about Checkr mission, customers, recognition, etc. That's substantive. So we should include that as a section maybe "About Checkr". But they didn't list that as example but it's okay. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exhaustive. So we can add About Checkr. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About Checkr

... (mission, customers, recognition)

About the role

... (summary)

Responsibilities

• ... each bullet from "What You'll Do"

Requirements

• ... each bullet from "What You Bring"

Maybe also "Nice to have" could be included under Requirements as separate list? Could be separate "Preferred qualifications". But we can incorporate into Requirements as separate list with heading "Preferred qualifications". However instruction: Use headings from list; we could add "Preferred qualifications" as a heading? Not in list but could be okay. But to keep few sections, we could merge nice-to-have into Requirements list with note. But better to separate: maybe have "Qualifications" for required, and "Preferred qualifications" for nice to have. They listed Qualifications as possible heading. So we can have:

Qualifications

Required:

... required bullets

Preferred qualifications

... nice to have bullets

But that adds more sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine required and preferred into one list with indication? Could be okay to keep separate but it's many sections. Let's think: We have About Checkr, About the role, Responsibilities, Requirements (including both required and preferred), Benefits, Pay, Schedule. That's 7 sections. That's okay. We can put required under "Requirements" and preferred under "Preferred qualifications" as subheading maybe

but they only said use

for section headings. Could use

for both, but that would be many sections. Maybe we can combine: Under Requirements list, we can include both required and preferred, but we can differentiate by phrasing. However the instruction says preserve ALL substantive information; we can keep both but we need to show distinction. Could do:

Requirements

Required:

... required

Preferred (nice to have):

... preferred

That's still one section. Now Benefits: list from "What We Offer". Also include in-office perks etc. Pay: include salary ranges for SF and Denver. Also mention geographic cost of labor etc. Keep that. Schedule: include expectation to work from office 3+ days a week, hub locations, in-office perks, relocation stipend. Now we need to remove boilerplate: EEO, Applicant Privacy Policy, Legitimate Checkr emails, etc. Also remove "Equal Employment Opportunities at Checkr" etc. Also remove "Applicant Privacy Policy". Also remove "Legitimate Checkr emails..." etc. Also remove "At Checkr, we believe an in office work environment strengthens collaboration, drives innovation, and encourages connection." Actually that is relevant to schedule/office expectation, we keep that part but maybe we can keep the sentence about in-office expectation and perks. The sentence includes "Individuals are expected to work from the office 3+ days a week. In-office perks are provided, such as lunch five times a week, a commuter stipend, and an abundance of snacks and beverages. A relocation stipend may be available for those willing to relocate to a Checkr hub location." That's schedule/benefits. We'll keep. Now we need to ensure we don't include duplicated lines. Also remove "On-target Earnings OR Base Salary range (San Francisco, CA) $169,000—$199,000 USD" and same for Denver. Keep both. Now produce HTML. Let's craft content. About Checkr paragraph: "Checkr is building the data platform to power safe and fair decisions. Over 140,000 companies and millions of people rely on Checkr for AI verification in the moments that matter most: getting a new job, a new place to live, a car ride, childcare, even a date. Customers include Uber, Pennymac, Airbnb, Doordash, and Anthropic. We’re a team that thrives on solving complex problems with innovative solutions that advance our mission. Checkr is recognized on Forbes Cloud 100 2025 List and is a Y Combinator 2024 Breakthrough Company." About the role paragraph: "We’re looking for a Senior Product Designer to help shape the end-to-end experiences that power Checkr’s Verifications products—spanning employment, education, criminal record, and driving record verifications, with a key focus on drug & occupational health testing. You’ll partner closely with Product, Engineering, and cross-functional stakeholders to design intuitive workflows for complex, high-trust domains—balancing candidate ease, employer clarity, and operational realities. This is a hands-on product design role with high ownership: you’ll drive discovery through execution, bring strong craft, and help the team make great decisions through clear thinking and excellent communication." Responsibilities bullets: list each sentence from "What You'll Do". Let's extract: - Own design for key Verifications product areas—including drug & occupational health testing—across candidate, employer, and internal operational experiences (as applicable), from discovery through launch and iteration. - Partner with Product and Engineering to define problems, shape roadmaps, and deliver high-quality solutions that align user needs with business outcomes. - Simplify complex workflows (verification requests, document collection, consent/authorization, appointment scheduling, status visibility, exception handling) into clear, user-friendly experiences. - Use AI-assisted design and development tools to rapidly prototype, validate, and—when appropriate—implement lightweight UI changes in code to improve iteration speed and overall product quality. - Design for trust and clarity in a sensitive, regulated domain—prioritizing transparency, error prevention, accessibility, and confidence-building UI patterns. - Translate insights into outcomes by combining qualitative research, stakeholder input, and product data to propose, test, and refine solutions. - Create thoughtful interaction and visual design across responsive web and/or platform surfaces, producing clear specs and assets for engineering. - Facilitate alignment with workshops, design reviews, and strong storytelling—helping teams move from ambiguity to decisions. - Collaborate cross-functionally with partners such as Customer Success, Sales, Compliance/Legal, Data, and Operations to ensure designs work in the real world. - Contribute to design systems and standards to improve consistency, speed, and quality across Checkr. That's 10 bullets. Requirements (required) bullets from "What You Bring" required part: - You have 5–8+ years of product design experience (or equivalent), with a strong track record of shipping high-quality work. - Your portfolio demonstrates end-to-end thinking: problem framing, exploration, rationale, collaboration, iteration, and measurable impact. - You’re comfortable working in complex domains where edge cases matter, and you can distill that complexity into simple, usable flows. - You have strong product instincts—you know how to balance user needs, business goals, technical constraints, and timeline realities. - You’re experienced in collaborative, cross-functional environments, influencing decisions through clarity rather than authority. - You can independently plan and execute lightweight research (interviews, usability testing, concept validation) and partner effectively with researchers when available. - You sweat the details: interaction patterns, content clarity, information hierarchy, and accessibility best practices. - An A-player mindset with a strong bias for action: you raise the bar, move with urgency, stay resilient through ambiguity, and take ownership to deliver meaningful outcomes. That's 8 bullets. Preferred (nice to have) bullets: - Experience in background screening, HR tech, healthcare, identity, compliance-heavy, or other high-trust regulated spaces. - Experience designing B2B / B2B2C products, especially workflows used by operations teams or external partners. - Familiarity with design systems, documentation, and scalable component thinking. - Experience designing for secure data, consent, and privacy-forward user experiences. That's 4 bullets. Benefits bullets from "What We Offer": - A fast-paced and collaborative environment - Learning and development allowance - Competitive cash and equity compensation, and opportunity for advancement - 100% medical, dental, and vision coverage - Up to $25K reimbursement for fertility, adoption, and parental planning services - Flexible PTO policy - Monthly wellness stipend Also we have in-office perks: lunch five times a week, commuter stipend, abundance of snacks and beverages, relocation stipend may be available for those willing to relocate to a Checkr hub location. Also hub locations: Denver, CO; San Francisco, CA; Nashville, TN; Santiago, Chile. Also expectation to work from office 3+ days a week. We could include those under Benefits as additional bullets, or under Schedule. Probably schedule section includes expectation and hub locations. Benefits includes perks like