Manager, Process Management & Controls

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (About Us maybe? Actually "About Us" is not a required heading; we can include as prose? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "About Us" could be considered "About the role"? Actually "About Us" is company description; maybe we can put under "About the role" or maybe we omit because not exactly role. But we need to preserve all substantive information. The "About Us" paragraph is substantive about company. Could be placed under a heading like "About the role"? Not ideal. Perhaps we can create a section "About the role" containing the Role Overview and maybe the About Us? The instruction says use those headings for section headings; we can also have other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Probably we should stick to those. So we need to map content: - About the role: could include Role Overview and maybe About Us? The Role Overview paragraph: "ClarityPay is seeking a Manager of Process Management & Controls to run and scale the operating system behind how we work..." That's role overview. Also maybe include "About Us" as company description but could be placed under About the role? Might be okay. - Responsibilities: list of key responsibilities bullet points. - Requirements: maybe qualifications? Actually Qualifications section separate. Requirements could be things like "Curious, energetic, positive..." but those are qualifications. The posting has "Qualifications:" list. So we can put that under Qualifications. Requirements maybe could be "Experience running a governance cadence..." etc. But we have both Qualifications and Requirements headings; we need to decide what goes where. The posting has "Qualifications:" with bullet-like sentences. Also "Nice to Have:" separate. Could treat "Qualifications" as required qualifications, and "Nice to Have" as optional. Could also have "Skills" section for skills like interviewing, writing, data fluency, SQL/Python, etc. We need to avoid filler headings. So we need to see what content we have for each potential section: - About the role: we have Role Overview paragraph and maybe About Us. That's substantive. - Responsibilities: we have Key Responsibilities list (multiple bullet-like sentences). Good. - Requirements: maybe we could put the "Curious, energetic, positive, solution-oriented, collaborative, trusted." plus the 5+ years experience etc. Those are qualifications. But we have a Qualifications heading; maybe Requirements is for mandatory experience/education? The posting doesn't have separate "Requirements". Could combine Qualifications and Requirements? But we need to only emit sections with real content. If we don't have distinct content for Requirements, we should not emit it. So we could omit Requirements. - Qualifications: we have the list after "Qualifications:" (Curious, energetic... etc). That's substantive. - Skills: we have "Exceptional interviewing and writing skills — able to get how work really runs out of busy people and write it so a new hire could follow it." Also "Data fluency: comfortable pulling answers out of a data warehouse using AI to draft the queries, and able to catch when the output is wrong." Also "Deep SQL or Python expertise is not required; willingness to work in the data is." Also maybe "Nice to Have" items could be considered skills? But we could put those under Skills. - Benefits: we have "What we offer: Competitive fixed and variable compensation package. Comprehensive benefits (medical, dental, vision). 401k program." That's benefits. - Pay: we have "Compensation Range: $120K - $170K". That's pay. - Schedule: no mention of schedule (full-time, hours, remote). Not present, so omit. Also we have "How You’ll Know This Role Is Right for You:" which is more like motivational; could be omitted or maybe put under About the role? It's not a standard heading but could be considered part of role overview. We could incorporate into About the role paragraph. We must not include boilerplate like equal opportunity employer, etc. Remove that. We must preserve all substantive information: need to ensure we don't lose any details from the posting. Let's extract all substantive content: About Us paragraph: "At ClarityPay, we’re redefining the point-of-sale credit market to bring more value to merchants. Based in NYC and Atlanta, our fast-growing fintech empowers large merchants with configurable “Pay-Over-Time” tools— including monthly installments, BNPL, and revolving products. We solve complex credit challenges with speed, precision, and intelligence. Our values guide everything we do: we put merchants first, stay data-driven, always know the why, learn relentlessly, and win together as a team." Role Overview paragraph: "ClarityPay is seeking a Manager of Process Management & Controls to run and scale the operating system behind how we work. That system exists: 108 documented processes, a taxonomy of 10 value streams and 65 capabilities, QA and register tooling, and a three-stage review chain. Your job is to raise it, so every process carries an owner, a trigger and closure, a KPI, a cost per run, and classified preventive and detective controls — the standard that lets ClarityPay optimize operations against its financial model." Key Responsibilities list (each sentence): - Run Process Office stage-2 review: check each submission for one accountable owner, correct taxonomy placement and duplicates, and confirm PROC- IDs. - Run QA and rebuild the register and dashboard on cadence, and administer change control. - Authority to add, rename or retire a value stream or capability stays with the Chief of Staff and the COO. - Document how work actually runs — interview process owners, capture steps, decisions, thresholds and handoffs, and hold the standard as coverage expands. - Tie every process to a quantifiable KPI and a cost per run (time, FTE, system spend). - Design preventive controls built into the process: approval thresholds and limits, segregation of duties, maker-checker steps, system validation. - Design detective controls — reconciliations, exception reports, variance thresholds, anomaly detection — sized to catch a break the same day, plus leading indicators that flag failure early. - Build the instrumentation yourself — pull the numbers out of our data warehouse and build the dashboards and alerting — and operate and extend the Process Office tooling that runs documentation, QA and the register. - Run root cause analysis on breaks; turn one-off fixes into permanent controls. - Supply documentation and control evidence to Compliance and IT Security on request, and report process health to executives in decision-ready terms. - Continually promote and apply ClarityPay values; be a role model of trust and integrity. Qualifications list (after "Qualifications:"): - Curious, energetic, positive, solution-oriented, collaborative, trusted. - 5+ years in management consulting or advisory (Big Four, Accenture, or a boutique operations or risk practice), or a comparable in-house process, controls, or business operations role. - Experience running a governance cadence — a review board, change control, or ownership of a register or inventory others submit into. - Evidence of owning and operating what you recommended — not handing over a deliverable and moving on. - Demonstrated experience designing preventive and detective controls, not only documenting processes. - Data fluency: comfortable pulling answers out of a data warehouse using AI to draft the queries, and able to catch when the output is wrong. - Deep SQL or Python expertise is not required; willingness to work in the data is. - Exceptional interviewing and writing skills — able to get how work really runs out of busy people and write it so a new hire could follow it. Nice to Have: - Fintech, lending, payments, banking, or another regulated environment. - Familiarity with control frameworks (COSO, SOC 2, PCI DSS) or supporting audits from the inside. - Has built or maintained LLM-based agents, skills, or workflows that other people rely on. How You’ll Know This Role Is Right for You: (four bullet-ish sentences) - You want to take over a working system and scale it — not start from a blank page. - You would rather fix the process than write the memo about the process. - You like being the person who noticed — the best outcome is a problem that never became an incident. - You think a company can have a real operating system, and you want to be the one who maintains it. What we offer: - Competitive fixed and variable compensation package. - Comprehensive benefits (medical, dental, vision). - 401k program. Compensation Range: $120K - $170K. Now we need to map to sections. About the role: Could combine About Us + Role Overview + How You’ll Know... maybe. But we need to avoid duplication. Let's put About Us and Role Overview under About the role. The "How You’ll Know..." could be considered part of role overview as well, but maybe we can put under About the role as a subsection? But we only have

headings; we could just include that paragraph as prose under About the role. Responsibilities: the Key Responsibilities list. Qualifications: the Qualifications list (including the bullet points). Could also include the Nice to Have under Skills? Or we could have Skills section for skills like interviewing, writing, data fluency, etc. But the Qualifications list already includes many skill-like items. However we have a separate Skills heading; we could put the "Exceptional interviewing and writing skills", "Data fluency", "Deep SQL or Python expertise is not required; willingness to work in the data is." under Skills. Also maybe the Nice to Have items could be under Skills as well (fintech experience, control frameworks, LLM-based agents). But we need to avoid duplication: if we put those under Skills, we should not also put them under Qualifications. However the Qualifications list includes those items already; we could keep them under Qualifications and not have a separate Skills section. But we have a Skills heading available; we could decide to not use Skills if content overlaps. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one Qualifications section. But we have both headings available; we can choose to omit Skills if not needed. However we have distinct skill items that are not strictly qualifications? The Qualifications list includes "Exceptional interviewing and writing skills", "Data fluency", etc. So they are qualifications. So we can put all under Qualifications. Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We must not include Requirements (no content), Skills (if we omit), Schedule (none). Also we must not include any filler like "commensurate with experience". Not present. Now we need to output HTML fragment: use

for each section heading, then content:

for prose,

• for lists. We need to ensure we preserve all substantive information. Let's craft: not needed; just output headings and content. We'll do:

  About the role

  At ClarityPay, we’re redefining the point-of-sale credit market to bring more value to merchants. Based in NYC and Atlanta, our fast-growing fintech empowers large merchants with configurable “Pay-Over-Time” tools— including monthly installments, BNPL, and revolving products. We solve complex credit challenges with speed, precision, and intelligence. Our values guide everything we do: we put merchants first, stay data-driven, always know the why, learn relentlessly, and win