Senior Manager, Critical Account Programs - United States

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule, Skills etc. Only include sections that have real specific content. We must remove boilerplate: EEO, legal, navigation, cookie, application instructions, duplicated lines. Also remove "Check us out on LinkedIn..." etc. We need to preserve all substantive information. Let's parse the posting. Title: Senior Manager, Critical Account Programs - United States (Remote, United States). Not to repeat as heading. First paragraph: "We're looking for a Senior Manager, Critical Account Programs - United States This role is Remote, United States Cornerstone is building a more connected, proactive Customer Organization designed to help customers realize value faster and navigate complexity with confidence. As part of that evolution, we are establishing a dedicated Critical Account Programs capability to change how we manage our most complex, high-impact customer situations. The Senior Manager, Critical Account Programs will build this capability from the ground up and operate it in practice. You will own the situations that matter most: the largest, heaviest, cross-functional customer problems where our own Executive Leadership Team needs a single leader to coordinate the company's response. When a strategic account is at risk and the path forward spans Sales, Services, Product, Partners, Support, and Customer Success, this is the person who brings structure, drives resolution, and gives leadership a clear line of sight into what is happening and what we are doing about it. This is not a role for someone looking to inherit an established program. We are looking for a builder and operator who can bring structure to ambiguity, create momentum across organizational boundaries, and remain calm and decisive when the stakes are high. You will define what constitutes a Critical Account situation at Cornerstone, establish the operating model and governance, and personally lead our highest-priority situations while the function matures." Then "In this role you will..." enumerated list with numbers 1. etc. That's responsibilities. Then after enumerated list, there is a paragraph: "Turn situations into systemic improvement..." etc. That's also responsibilities. Then "Design a capability built to scale..." also responsibilities. Then "SrDrive accountability: ..." maybe a bullet? Actually looks like a continuation: "SrDrive accountability: establish ownership, challenge stalled progress, and escalate thoughtfully when needed.Build while operating: solve today's customer problem while improving the system used to solve tomorrow's.Balance customer and enterprise needs: advocate for the customer while considering commercial, product, operational, and business realities." Then "You’ve got what it takes if you’ve got…" list of requirements/qualifications. Then "What success looks like In the first 12 to 18 months, this leader will have:" list of outcomes. Then "Our Culture Spark Greatness..." fluff, maybe not needed? It's culture description but maybe not required? It's not a specific section like Benefits, Pay, Schedule. Could be omitted as boilerplate? It's not EEO but still fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Culture description maybe not boilerplate but could be considered fluff. However we need to preserve ALL substantive information; culture might be considered substantive? The instruction says "Prefer a few substantive sections over many thin ones." Could include a "Culture" section? Not listed as allowed headings; allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those. Thus: - About the role: introductory paragraph describing role, purpose, remote, etc. - Responsibilities: the enumerated list and subsequent paragraphs about building model, leading situations, communication, systemic improvement, scaling, accountability, etc. - Requirements/Qualifications: the "You’ve got what it takes if you’ve got…" list (10+ years experience etc.) plus maybe also "What success looks like" could be considered expectations but could be under Responsibilities? Actually success looks like outcomes; could be under "What success looks like" but not a standard heading. Could be placed under Responsibilities as expected outcomes, but maybe better as a separate section? Not allowed. Could incorporate into Responsibilities or Qualifications. I'd put under Responsibilities as expected outcomes. - Skills: maybe extract from requirements: exceptional executive communication skills, technical fluency, judgment, etc. Could be a Skills section. - Benefits: The posting mentions Total Rewards: compensation strategy, salary range, bonuses, benefits. There's a paragraph about Total Rewards: "At Cornerstone, we are dedicated to inspiring excellence... compensation strategy... listed salary range is just one element... may also include annual bonuses, short- and program-specific awards... comprehensive benefit offering." Also "The disclosed salary range reflects the geographic differential..." and "The starting salary for the successful applicant will depend on several job-related factors..." and "This range is based on a full-time position..." So we have Pay info: BASE salary range: 130800 - 209300 USD. Also mention bonuses etc. So we can create Pay section with salary range and note about bonuses etc. Benefits section: mention comprehensive benefit offering (but not specific). Could we include Benefits? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does mention benefits generally, but not specific. It says "comprehensive benefit offering." That's vague but still states there is a benefit offering. So we can include Benefits section with that statement. - Schedule: Not mentioned (remote, but no schedule specifics). So omit Schedule. - Skills: Could be separate but we might combine with Requirements/Qualifications. However we have both Requirements and Qualifications allowed headings. We could put experience requirements under Requirements, and skills under Skills. Let's do: Requirements: 10+ years of experience in customer escalations, critical account or program management, customer success, technical program management, services, or comparable enterprise environment. Experience building systems & processes to improve customer experience Experience personally leading complex, executive-visible customer situations involving technical and business stakeholders. Experience partnering closely with Product, Engineering, Services, and Support, with enough technical fluency to navigate complex issues and translate across technical and non-technical audiences. Experience turning root-cause findings into durable process or operating-model improvements. Strong judgment, organizational discipline, and the ability to remain calm and action-oriented under pressure. The ability to influence outcomes without relying on direct authority. A builder mindset and curiosity to deeply understand our customers, products, and organization. A clear point of view on how AI, automation, and new operating models can reinvent situation management and move organizations from reactive response toward earlier detection, faster decisions, and scalable intervention. Skills: Exceptional executive communication skills, including a proven ability to manage up to senior leadership and lead executive-level communication with customers under pressure. A track record of bringing structure and momentum to ambiguous, cross-functional problems. Maybe also "executive communication skills" etc. But we might double-count. Better to keep Requirements as experience, Skills as abilities. Let's extract: From "You’ve got what it takes if you’ve got…" list: - 10+ years of experience in customer escalations, critical account or program management, customer success, technical program management, services, or a comparable enterprise environment. - Experience building systems & processes to improve customer experience - Experience personally leading complex, executive-visible customer situations involving technical and business stakeholders. - Exceptional executive communication skills, including a proven ability to manage up to senior leadership and lead executive-level communication with customers under pressure. - A track record of bringing structure and momentum to ambiguous, cross-functional problems. - Experience partnering closely with Product, Engineering, Services, and Support, with enough technical fluency to navigate complex issues and translate across technical and non-technical audiences. - Experience turning root-cause findings into durable process or operating-model improvements. - Strong judgment, organizational discipline, and the ability to remain calm and action-oriented under pressure. - The ability to influence outcomes without relying on direct authority. - A builder mindset and curiosity to deeply understand our customers, products, and organization. - A clear point of view on how AI, automation, and new operating models can reinvent situation management and move organizations from reactive response toward earlier detection, faster decisions, and scalable intervention. We can split: Requirements = experience items (first three bullet points maybe). Skills = the rest (communication skills, track record, partnering, turning root-cause, judgment, influence, builder mindset, AI point of view). But it's arbitrary. Simplify: Have Requirements section with the experience bullets (10+ years, building systems, leading situations). Skills section with the rest (communication skills, track record, partnering, root-cause, judgment, influence, builder mindset, AI viewpoint). That seems reasonable. Now About the role: combine initial paragraphs up to "In this role you will..." maybe before the enumerated list. Let's craft About the role: "We're looking for a Senior Manager, Critical Account Programs - United States. This role is Remote, United States. Cornerstone is building a more connected, proactive Customer Organization designed to help customers realize value faster and navigate complexity with confidence. As part of that evolution, we are establishing a dedicated Critical Account Programs capability to change how we manage our most complex, high-impact customer situations. The Senior Manager, Critical Account Programs will build this capability from the ground up and operate it in practice. You will own the situations that matter most: the largest, heaviest, cross-functional customer problems where our own Executive Leadership Team needs a single leader to coordinate the company's response. When a strategic account is at risk and the path forward spans Sales, Services, Product, Partners, Support, and Customer Success, this is the person who brings structure, drives resolution, and gives leadership a clear line of sight into what is happening and what we are doing about it. This is not a role for someone looking to inherit an established program. We are looking for a builder and operator who can bring structure to ambiguity, create momentum across organizational boundaries, and remain calm and decisive when the stakes are high. You will define what constitutes a Critical Account situation at Cornerstone, establish the operating model and governance, and personally lead our highest-priority situations while the function matures." That seems good. Now Responsibilities: start with "In this role you will..." then the enumerated list (1.) and subsequent paragraphs. We need to capture all responsibilities text. Let's extract the enumerated list items: 1. Build the Critical Account Programs operating model - Define Cornerstone's end-to-end framework for managing the highest-impact, cross-functional customer situations, including qualification criteria, severity levels, entry and exit requirements, escalation paths, decision rights, and roles. - Build repeatable mechanisms for intake, prioritization, ownership, action tracking, communication, and closure. - Establish how Critical Account Programs connects with existing customer, product, support, and executive escalation processes so situations are surfaced early and routed to the right owner. - Continuously evolve the model based on what we learn. 2. Lead Cornerstone's most complex customer situations - Serve as the single point of accountability for the overall outcome of situations involving significant customer, retention, financial, operational, or reputational risk that span more than one function. - Rapidly assess customer impact, urgency, and business risk, and establish the right cross-functional response across Sales, Services, Product, Partners, Support, and Customer Success. - Marshal company-wide resources, align stakeholders around clear ownership, decisions, timelines, and actions, and identify where leadership intervention or executive decisions are required. - Drive situations through stabilization, resolution, and closure, remaining hands-on particularly as the capability is being established. 3. Communicate with, and manage up to, internal executives and customers - Expert-level communication is central to this role. This leader must be equally strong at managing up to Cornerstone's senior leaders and at leading high-stakes communication with customers. - Manage up to the ELT with confidence and clarity: give our senior leaders a candid, objective view of impact, progress, risks, decisions needed, and recovery plans, and prepare executive-level readouts and recommendations that support fast, informed decisions. - Anticipate what leadership needs to know before they ask, translate complex technical and operational detail into concise executive narratives, and keep leaders appropriately engaged without over-escalating