Senior Project Manager - Customer Experience (CX) Technology

We need to produce HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove the "Omilia Note" maybe? The note includes "Contribute actively and effectively as an integrated team member Act as an Omilia ambassador in all interactions". That seems like a value statement; maybe it's part of Benefits? Actually it's under "Omilia Note". Might be considered part of company culture; but we can treat as part of Benefits? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to extract content for each possible heading. Let's parse the posting: - About The Company: description of Omilia. That's about the company, not role. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't list About the Company. So we should not include a heading for About the Company? The instruction says use those headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not include About the Company. However we need to preserve ALL substantive information. If we omit About the Company, we lose that info. But maybe we can incorporate it under About the role? The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings like About the Company, but they gave examples. Might be okay to include About the Company as a heading? But they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. Safer to follow that and only include those headings. Then we need to embed company info somewhere else, maybe in a

under About the role? But that would be mixing. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep company description. If we cannot create a heading for it, we could put it as a

before any headings, as introductory paragraph. That's allowed: we can have prose outside headings. The instruction didn't forbid that. So we can start with a

containing the About The Company paragraph. Then we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content for each. Let's parse the posting for each. **About the role**: The posting includes "Role Purpose" paragraph: "Omilia is looking for a Senior Project Manager to lead complex, enterprise and mid-market implementations of Omilia's conversational solutions for contact centers, including Omilia's Agentic AI Solutions. The role keeps large, multi-stakeholder deployments on track, coordinating across Omilia's engineering, solutions, professional services, and customer success teams while owning the client relationship end to end. It suits someone who has already run enterprise-scale CX or contact centre technology projects, thinks analytically under pressure, and wants to grow into a bigger scope as the company scales." That's about the role. So we can put that under

About the role

with

. **Accountabilities**: list of bullet points (though not formatted as bullet). They are sentences separated by line breaks? In the text: "Own the full lifecycle of enterprise and mid-market implementations end-to-end — from scoping and planning through go-live and closure — delivering on time, on budget, and to quality standardsServe as the primary point of contact for enterprise and mid-market clients, building relationships that support renewal and expansionAct as the connective tissue between Omilia's internal teams and client stakeholders, resolving blockers before they become delaysIdentify risks early and drive mitigation plans proactively across all engagementsManage project teams effectively, keeping delivery teams aligned to project goalsBring back lessons learned from each engagement and drive continuous process improvement across the PMO" These are accountabilities/duties. Could be placed under Responsibilities. **Key Responsibilities**: a list of bullet-like sentences: "Define project scope and objectives with stakeholders, validate technical feasibility with delivery teams, and maintain a detailed, living project planAnticipate and resolve technical, operational, and organizational issues as they arise, applying structured, analytical thinking rather than escalating every problem upwardUnderstand the technical tasks behind each deliverable well enough to plan, sequence, and challenge estimatesTrack technical progress at task level, not just milestone level, and identify slippage earlySupport the requirements and design process, contributing to the gathering, clarification, and validation of technical and functional requirements, and their translation into implementable specificationsCoordinate across Omilia's engineering, solutions architecture, professional services, and support teams to keep delivery on trackPrepare and present clear status reports and metrics to both internal leadership and client stakeholders" These are responsibilities. Thus we can combine Accountabilities and Key Responsibilities into a Responsibilities section with

• items. **Requirements**: The posting has a "Requirements Knowledge, Skills & Experience Required:" then a list of items separated by line breaks? Let's extract: - 8+ years of customer-facing Project Management experience delivering complex, enterprise or mid-market IT/software projects, with demonstrated ownership rather than task execution - Working knowledge of the Conversational AI / Agentic CX space, ideally including Conversational Voice technology (IVR modernization, voice agents, voice biometrics, or similar) - Deep understanding of enterprise CX technology, contact centre operations, and the CCaaS/CPaaS vendor landscape - Strong analytical and structured problem-solving ability, comfortable diagnosing root causes across technical and organizational issues - Excellent communication and presentation skills, with the credibility to manage senior client stakeholders directly - Proven ability to coordinate effectively across cross-functional and cross-departmental teams - Expertise in Project Management methodologies and tools (PMP/PRINCE2 principles, Agile/Scrum, or equivalent experience) - Bachelor's degree in Computer Science, IT, Business, or a related field - Proactive, initiative-taking operator who identifies what needs to happen next without being told - Detail-oriented and results-driven, with the ability to zoom out and think strategically about the client relationship - Comfortable in a fast-moving, dynamic environment managing multiple concurrent engagements Then "Nice to have: PMP or PRINCE2 certificationFamiliarity with APIs and system integrations" Thus we have Requirements (mandatory) and Nice to have (preferred). The instruction includes Qualifications and Skills sections. We need to decide where to put what. Typically Requirements could be split into Qualifications (education, experience) and Skills (technical/soft). But we can also just put all under Requirements. However we must follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Requirements for the mandatory experience/knowledge, Qualifications for education/degree, Skills for specific abilities, and Benefits for benefits. But we need to ensure we don't create empty sections. Let's map: - Requirements: maybe the core experience: "8+ years of customer-facing Project Management experience delivering complex, enterprise or mid-market IT/software projects, with demonstrated ownership rather than task execution" plus maybe "Working knowledge of the Conversational AI / Agentic CX space..." etc. Could be considered requirements. - Qualifications: Bachelor's degree in Computer Science, IT, Business, or a related field. - Skills: The rest: analytical/problem-solving, communication, coordination, expertise in PM methodologies, proactive, detail-oriented, comfortable in fast-moving environment, etc. Also maybe "Working knowledge of Conversational AI" could be skill. But we need to avoid duplication. Let's think: The posting lumps them together; we can split arbitrarily as long as we preserve all info. We'll create:

  Requirements

  • 8+ years of customer-facing Project Management experience delivering complex, enterprise or mid-market IT/software projects, with demonstrated ownership rather than task execution
  • Working knowledge of the Conversational AI / Agentic CX space, ideally including Conversational Voice technology (IVR modernization, voice agents, voice biometrics, or similar)
  • Deep understanding of enterprise CX technology, contact centre operations, and the CCaaS/CPaaS vendor landscape

  Qualifications

  • Bachelor's degree in Computer Science, IT, Business, or a related field

  Skills

  • Strong analytical and structured problem-solving ability, comfortable diagnosing root causes across technical and organizational issues
  • Excellent communication and presentation skills, with the credibility to manage senior client stakeholders directly
  • Proven ability to coordinate effectively across cross-functional and cross-departmental teams
  • Expertise in Project Management methodologies and tools (PMP/PRINCE2 principles, Agile/Scrum, or equivalent experience)
  • Proactive, initiative-taking operator who identifies what needs to happen next without being told
  • Detail-oriented and results-driven, with the ability to zoom out and think strategically about the client relationship
  • Comfortable in a fast-moving, dynamic environment managing multiple concurrent engagements
  • Nice to have: PMP or PRINCE2 certification
  • Nice to have: Familiarity with APIs and system integrations
  But we need to ensure we don't create sections with filler like "Nice to have" maybe okay as it's specific content. It's not placeholder. Now Benefits: The posting includes "Omilia Note Contribute actively and effectively as an integrated team member Act as an Omilia ambassador in all interactions Benefits Fixed compensation;Long-term employment with the working days vacation;Development in professional growth (courses, training, etc);Being part of successful cutting-edge technology products that are making a global impact in the service industry;Proficient and fun-to-work-with colleagues;Apple gear". This is a bit messy. Let's parse: After "Omilia Note" there is "Contribute actively and effectively as an integrated team member Act as an Omilia ambassador in all interactions Benefits Fixed compensation;Long-term employment with the working days vacation;Development in professional growth (courses, training, etc);Being part of successful cutting-edge technology products that are making a global impact in the service industry;Proficient and fun-to-work-with colleagues;Apple gear" Thus benefits list: Fixed compensation; Long-term employment with the working days vacation; Development in professional growth (courses, training, etc); Being part of successful cutting-edge technology products that are making a global impact in the service industry; Proficient and fun-to-work-with colleagues; Apple gear. Also maybe "Contribute actively and effectively as an integrated team member Act as an Omilia ambassador in all interactions" could be considered part of benefits or culture; but we can include as a benefit item. Thus we can create Benefits section with
  • items. Pay and Schedule: The posting does not mention specific pay or schedule. So we should NOT include Pay or Schedule sections because they would be empty/filler. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits we have, so include Benefits. Pay and Schedule: omit. Now we need to ensure we didn't miss any substantive info: The "Accountabilities" and "Key Responsibilities" we moved to Responsibilities. Also we need to include the "Role Purpose" under About the role. Also maybe we need to include the "Omilia Note" about contributing