Process Design Specialist

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, there is a lot of repeated "About Checkr" text. We need to remove boilerplate like navigation, legal, EEO, etc. Keep substantive info. The posting includes: - About Checkr (company description) – but we are told not to repeat job title as heading; we can include a short paragraph about company? The instruction: "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." It doesn't forbid including company description; but we need to decide if we include a section for "About Checkr". The allowed headings list includes only specific ones: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create other headings like "About Checkr". So we should embed company description maybe in a

before sections? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It doesn't say we cannot have a leading paragraph. Probably we can include a brief intro paragraph about the company, but not as a heading. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So only those headings allowed. So we can have a

for company overview, then sections. We need to extract: About the role: The section "About The Role" contains description: As Process Design Specialist, you'll assess how our operations processes work today and identify where they break down or fall short, using established process mapping methods to help design what should replace them. That includes taking customer experiences and turning them into concrete, standardized improvements to our support flows, with support from your manager and senior team members on the larger or more ambiguous calls. Our ideal candidate is a systems thinker who can look at a process end to end and pinpoint where it breaks down or stops scaling. You bring structure to ambiguity: you can take that understanding and help design something better, not just a cleaner version of the same process. You document what you find clearly, whether that's a process map, an SOP, or a runbook, and you know how to use current tools, including AI, to speed up discovery and documentation without cutting corners on rigor. We're not just documenting today's process — we're designing for a future where agents handle more of the execution. You'll help define where automation can run end to end and where a human-in-the-loop checkpoint is still required, setting the standard so our processes scale without losing rigor or compliance. This role reports to the Senior Manager, Operations Knowledge Systems & Process Design, and joins a growing team of knowledge and process specialists. It will require periodic travel ( headings and

• for lists,

  for prose. We need to avoid repeating job title. Not include any boilerplate like EEO, privacy, etc. We need to include company description? Could be a short

  before sections. Not required but could be included. The instruction says "Preserve ALL substantive information". The company description is substantive. So we should include it as a

  maybe without heading. Let's include a brief paragraph summarizing Checkr: "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..." etc. But we have duplicated paragraphs; we need to combine unique info. We have two About Checkr blocks with slightly different content. Let's merge: Established 2014, over 100,000 customers including DoorDash, Coinbase, Lyft, Instacart, Airtable. Also earlier: Over 140,000 companies and millions of people rely on Checkr for AI verification in moments: getting a new job, a new place to live, a car ride, childcare, even a date. Customers include Uber, Pennymac, Airbnb, Doordash, Anthropic. Recognized on Forbes Cloud 100 2025 List and Y Combinator 2024 Breakthrough Company. So we can combine. We'll output a

  with that. Now sections:

  About the role

  ... (the paragraph from About The Role)

  Responsibilities

  • ... each bullet

  Requirements

  • ... mandatory experience bullets (first 10)

  Qualifications

  • ... preferred: experience improving support operations workflows in a high-volume, customer-facing environment
  • ... preferred: Lean Six Sigma, BPM certification, or equivalent formal process improvement training
  Maybe also include "An A-player mindset..." as a skill or qualification? Could be under Skills.

  Skills

  • ... strong facilitation skills, with experience running working sessions to gather requirements from cross-functional stakeholders
  • ... excellent written communication skills; able to produce process documentation that's clear to both technical and non-technical audiences
  • ... experience quantifying a process's cost in time, volume, or rework before and after a change, using data from existing dashboards and reports; strong in spreadsheets, including pivot tables and lookups (SQL not required)
  • ... experience defining and tracking success metrics for a process change, and knowing when a metric improved but the underlying problem didn't
  • ... comfort working within support and knowledge systems (e.g., Zendesk, Salesforce, Confluence, or similar)
  • ... familiarity using AI tools to accelerate process documentation, gap analysis, or workflow audits, with the judgment to know where human review still matters
  But note some of these overlap with Requirements; we need to avoid duplication. We already put some of those in Requirements (like comfort with systems, familiarity using AI tools). Actually we listed those under Requirements earlier. Let's decide: Requirements = years of experience, process mapping experience, assessing current-state, translating tribal knowledge, comfort with support systems, familiarity using AI tools. That's 6 items. Then Skills =