Customer Program Manager, Louisiana

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate (EEOC, legal, etc). Must preserve all substantive info. We need to parse content: The posting includes: - Intro paragraph about Mojo AI, Safety Mojo, Series B, join us, seeking a driven, organized Customer Program Success Manager (CPSM) to own full customer journey across enterprise accounts — from initial deployment through scaled, sustained adoption. This is not a traditional account management role. You will serve as primary program owner and trusted advisor, managing multi-stakeholder engagements as structured programs of work. You'll embed Safety Mojo into core operations of customers' organizations, drive measurable safety outcomes, and contribute to expansion opportunities within your book of business. You won't just manage accounts — you'll build programs that save lives. If you want to operate at highest level of enterprise customer success and do work that genuinely matters, this is the role for you. Then "What You'll Own" bullet list (actually sentences with em dash). Then "What You Bring" bullet list. Then "More Details" with Division, Department, Reports To, Location, Role Type, Employment, Pay Type, Pay Elements, Compensation & Benefits (including base salary range, variable pay, benefits). Then "Important Notes" includes EEOC & Inclusion, ADA, At-Will Employment, Background Check Requirement, thank you note. We need to remove boilerplate: EEOC & Inclusion, ADA, At-Will Employment, Background Check Requirement, thank you note? The thank you note maybe not boilerplate but could be considered closing; but it's not a section heading; we can keep as prose maybe? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEOC & Inclusion, ADA, At-Will Employment, Background Check Requirement. The thank you note maybe not boilerplate but it's a closing; we could keep as prose but it's not required. Might be okay to keep but it's not a section. However we need to preserve all substantive information; the thank you note is not substantive for job details; but it's not prohibited. Safer to keep it as a paragraph maybe under a generic "About the company"? But we have no heading for that. Could just include as a

after sections. We need to structure sections: About the role (intro). Responsibilities (What You'll Own). Requirements/Qualifications/Skills (What You Bring). Benefits (Compensation & Benefits). Pay (Base Pay, Variable Pay). Schedule? Not mentioned. So we should not create Schedule section. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly combine Requirements and Qualifications? The instruction: Use headings for those specific labels if content exists. We have "What You Bring" includes experience, skills, etc. Could split into Requirements (years experience), Qualifications (maybe same), Skills (communication, organized). But we can just make a single "Requirements" section covering all. However we need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe combine into "Requirements" covering experience, skills, etc. Also we could have "Benefits" and "Pay" separate. Thus sections: - About the role (intro paragraph) - Responsibilities (What You'll Own) - Requirements (What You Bring) - Benefits (Compensation & Benefits) - Pay (Base Pay, Variable Pay) We need to ensure we don't include headings with filler text. All have content. Now we need to format lists: Use

• for any list of duties/requirements/benefits. For prose use

  . We need to extract details. Let's extract About the role paragraph: The first paragraph(s) before "What You'll Own". It includes multiple sentences. We'll combine into one

  . Responsibilities: The bullet list after "What You'll Own". It includes: - Own the program end-to end — design and run governance cadences (steering committees, exec reviews, working sessions), maintain master program plans, and manage RAID logs across all active workstreams - Lead deployment and adoption — drive implementations and build structured adoption programs that move customers from go-live to deeply embedded, organization-wide usage - Manage stakeholder relationships — navigate multi-level customer organizations from frontline safety managers to operational leadership, serving as the primary point of contact and escalation for your accounts - Coordinate across internal teams — align Engineering, Product, and Support to ensure the right resources are engaged at the right time; nothing falls through the cracks - Report with clarity — deliver executive-ready dashboards, status reports, and business reviews that surface ROI, risks, and next steps for both customers and internal leadership - Drive expansion — identify and develop growth opportunities within your accounts, partnering with Sales on renewals, upsells, and executive relationship development We need to preserve all detail. We'll make each as

• . Requirements: The bullet list after "What You Bring". It includes: - 5–7 years in Customer Success, Program Management, or a related customer-facing role — SaaS or industrial/safety verticals preferred - Experience managing multi-stakeholder customer engagements with structured program or project management approaches - Strong communication skills — comfortable presenting to operational leaders and adapting your style across different audiences - Organized and process-oriented with a working knowledge of program management fundamentals (meeting cadences, action tracking, status reporting) - Early track record of driving customer outcomes and supporting account growth - Ability to work independently and stay organized across multiple accounts in a fast-moving environment - Willingness to travel up to 50% of the time with weekly onsite requirements with major enterprise clients. We'll make each as
• . Benefits: The paragraph after "Compensation & Benefits": "Safety Mojo offers a strong combination of medical, dental, vision, life, disability, 401(k) with match, and generous PTO benefits. Please note that our medical insurance includes two options: traditional plan and HDHP with HSA with employer contributions." We'll make that as

  under Benefits. Pay: Base Pay: $100,000 to $130,000 per year. Variable Pay: A bonus of 5% of your annual salary will be prorated and payable quarterly for the achievement of certain milestones and metrics. We'll make two

  or maybe a

  . Since it's details, we can use

  each. We also have "More Details" includes Division, Department, Reports To, Location, Role Type, Employment, Pay Type, Pay Elements. Some of that is redundant with Pay section. We could incorporate those details into Pay or Benefits? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include Division, Department, Reports To, Location, Role Type, Employment, Pay Type, Pay Elements. Where to put? Could create a section "Details" but not in allowed headings list. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put Division/Department/Reports To/Location/Role Type/Employment under "About the role" maybe as extra prose. But we need to not lose info. We can embed them in a paragraph after the intro. Let's extract More Details: - Division: Operations - Department: Customer Success - Reports To: Sr Director of Customer Success - Location: Onsite at regional client facilities - Role Type: Individual Contributor - Employment: Full-Time - Pay Type: Salaried, exempt - Pay Elements: Salary + Bonus We already have Pay section covering base salary and bonus. So we can incorporate these details into About the role or a separate "Details" but not allowed. Perhaps we can add a short paragraph under About the role that includes these details. We must not repeat job title as heading. Already fine. We must not include Pay/Schedule/Benefits sections unless posting actually states them. We have Pay and Benefits. Now we need to output HTML fragment only, no /, no markdown fences. Let's craft:

  About the role

  Mojo AI is the standard for modern safety management in high-risk industries, including construction and oil & gas. Through Safety Mojo—our enterprise-grade, AI-powered platform—we empower frontline safety professionals to mitigate risk and prevent incidents in real time. We recently closed a Series B and are on an exciting trajectory. Join us! We are seeking a driven, organized Customer Program Success Manager (CPSM) to own the full customer journey across our enterprise accounts — from initial deployment through scaled, sustained adoption. This is not a traditional account management role. You will serve as the primary program owner and trusted advisor, managing multi-stakeholder engagements as structured programs of work. You'll embed Safety Mojo into the core operations of your customers' organizations, drive measurable safety outcomes, and contribute to expansion opportunities within your book of business. You won't just manage accounts — you'll build programs that save lives. If you want to operate at the highest level of enterprise customer success and do work that genuinely matters, this is the role for you. Division: Operations. Department: Customer Success. Reports To: Sr Director of Customer Success. Location: Onsite at regional client facilities. Role Type: Individual Contributor. Employment: Full-Time. Pay Type: Salaried, exempt. Pay Elements: Salary + Bonus.

  Then Responsibilities:

  Responsibilities

  • Own the program end-to end — design and run governance cadences (steering committees, exec reviews, working sessions), maintain master program plans, and manage RAID logs across all active workstreams
  • Lead deployment and adoption — drive implementations and build structured adoption programs that move customers from go-live to deeply embedded, organization-wide usage
  • Manage stakeholder relationships — navigate multi-level customer organizations from frontline safety managers to operational leadership, serving as the primary point of contact and escalation for your accounts
  • Coordinate across internal teams — align Engineering, Product, and Support to ensure the right resources are engaged at the right time; nothing falls through the cracks
  • Report with clarity — deliver executive-ready dashboards, status reports, and business reviews that surface ROI, risks, and next steps for both customers and internal leadership
  • Drive expansion — identify and develop growth opportunities within your accounts, partnering with Sales on renewals, upsells, and executive relationship development
  Then Requirements:

  Requirements

  • 5–7 years in Customer Success, Program Management, or a related customer-facing role — SaaS or industrial/safety verticals preferred
  • Experience managing multi-stakeholder customer engagements with structured program or project management approaches
  • Strong communication skills — comfortable presenting to operational leaders and adapting your style across different audiences
  • Organized and process-oriented with a working knowledge of program management fundamentals (meeting cadences, action tracking, status reporting)
  • Early track record of driving customer outcomes and supporting account growth
  • Ability to work independently and stay organized across multiple accounts in a fast-moving environment
  • Willingness to travel up to 50% of the time with weekly onsite requirements with major enterprise clients
  Then Benefits:

  Benefits

  Safety Mojo offers a strong combination of medical, dental, vision, life, disability, 401(k) with match, and generous PTO benefits. Please note that our medical insurance includes two options: traditional plan and HD