Business Operations Manager

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 must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info. We need to parse the job description. Given content: - Location: Guernsey - Schedule: Monday to Friday, 36.25 hours per week - Working Arrangement: Hybrid / On-Site - Contract Type: Permanent About The Role: paragraph. Key Responsibilities: list bullet points. Required Qualification/Experience: list bullet points. Preferred Qualification/Experience: list bullet points. About Us: paragraph about CSC. About The Team: paragraph. We need to map to sections: About the role (we have that), Responsibilities (Key Responsibilities), Requirements (maybe combine Required Qualification/Experience?), Qualifications (maybe Preferred?), Skills (maybe from required?), Benefits (maybe from About Us/Team mentions benefits?), Pay (none given), Schedule (we have schedule info). Also maybe Working Arrangement could be part of Schedule? But schedule section only if posting actually states them. It does state schedule: Monday to Friday, 36.25 hours per week. Also Working Arrangement: Hybrid / On-Site. Could include in Schedule? Probably schedule section should contain schedule details; working arrangement maybe also in schedule or separate? The instruction: include a section ONLY when posting has real, specific content for it. So we can include Schedule section with the schedule and maybe working arrangement. Benefits: we have mention of benefits in About Us and About The Team: "CSC colleagues have global career opportunities and excellent benefits, including annual success-sharing bonuses or commission plans based on individual performance." Also later: "CSC offers a competitive and comprehensive benefits package that includes annual leave, tuition reimbursement, referral bonuses, and more." So we have benefits details. So we can include Benefits section. Pay: no specific pay mentioned, so omit. Qualifications: we have Required Qualification/Experience and Preferred Qualification/Experience. Could combine into Qualifications section with subpoints? But we need to follow instruction: Use

for section headings. Use

• for any list of duties/requirements/benefits. So we can have a Qualifications section with list items (maybe separate required and preferred?). Could also have Requirements section for required qualifications, and Qualifications for preferred? But they said prefer a few substantive sections over many thin ones. So maybe combine required and preferred into one Qualifications section, but we need to preserve all info. Could separate into Required and Preferred as subheadings? But only allowed headings are those listed; we cannot add custom headings. So we must fit into the allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Thus we can put Required Qualification/Experience under Requirements, Preferred Qualification/Experience under Qualifications, and maybe Skills from required (communication, organisational, etc.) could go under Skills. But we also have skills listed in required: Strong organisational skills, Demonstrated capability working with KPI MI, Strong communication skills, Experience escalating risks/issues, People management experience. Those could be Skills. Thus: - About the role: paragraph from About The Role. - Responsibilities: list from Key Responsibilities. - Requirements: list from Required Qualification/Experience. - Qualifications: list from Preferred Qualification/Experience. - Skills: maybe extract skills from Required (organisational, KPI MI, communication, escalation, people management). Could also include from Preferred (accounting background, commercial awareness, etc.) but those are qualifications. We'll put skills as separate list. - Benefits: list from About Us/Team: annual success-sharing bonuses or commission plans based on individual performance; annual leave; tuition reimbursement; referral bonuses; etc. Also "global career opportunities". We'll list. - Schedule: Monday to Friday, 36.25 hours per week; Hybrid / On-Site working arrangement. We must not include boilerplate like "About Us", "About The Team" as headings; we can incorporate their content into Benefits or maybe omit if not needed. But we need to preserve ALL substantive information. So we need to include the info from About Us and About The Team somewhere. If we put them under Benefits, we might lose some info like "CSC is a global business...". That's substantive but maybe not required to preserve? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. Could we add a section "About the Company"? Not allowed headings. So we must fit into allowed headings. Perhaps we can put that info under About the role? But that's already used for role description. Could we add a paragraph under About the role that includes company info? That would be mixing but still preserving. However the About the role heading is meant for role description; but we can still include extra info there as long as we don't invent. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid adding other content under those headings beyond the example. So we can include company info under About the role or maybe under Benefits? But Benefits is for benefits; company description is not a benefit. Better to put under About the role? Might be odd but still preserves. Alternatively, we could create a section "About the Company" but not allowed. So we must embed within allowed sections. We could put the company info under "About the role" as a preceding paragraph before role description. That would preserve. Similarly, "About The Team" could go under "About the role" as well, or maybe under "Benefits"? Not ideal. Better: we could put company info under "About the role" and team info under "About the role" as well, maybe separate paragraphs. Thus we will have:

  About the role

  [Company overview paragraph from About Us] [Team paragraph from About The Team] [Role description paragraph from About The Role]

  Then Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. Check for any duplicate lines: we must remove duplicated lines. Ensure we don't repeat. Now craft content. Company overview from About Us: "CSC is a global business, legal, and financial services company based in Wilmington, Delaware, USA, providing knowledge-based solutions to clients worldwide. We have offices and capabilities in over 140 jurisdictions in the Americas, Europe, Asia Pacific, and the Middle East, and more than 8,000 colleagues. We are the business behind business.®" Team paragraph: "At CSC®, we’re always looking ahead, finding ways to innovate, challenge the status quo, and anticipate the needs of our clients. We exceed expectations by adapting client ambitions and goals as our own. This Fierce Client Spirit has helped us adapt and create solutions that have enabled businesses to run smoother and smarter for more than 125 years. It’s also the reason we’re the trusted partner of many of the world’s most successful organizations. CSC is committed to attracting, developing, and retaining talented people whose values align with ours. We empower our colleagues to bring the right solutions to market to meet client demand. That’s why we are the leading provider of business administration and compliance solutions. CSC is a great place to work with smart and dedicated people. We have won several employer recognition awards, including Top Workplace USA, Great Places to Work India, and Built In’s Best Places to Work. We offer fulfilling work and career opportunities. Most positions are filled with internal moves and employee referrals. Employees are eligible for Success Sharing, bonuses, or commission plans based on role and individual performance. CSC offers a competitive and comprehensive benefits package that includes annual leave, tuition reimbursement, referral bonuses, and more. As business needs allow, CSC offers hybrid or remote work schedules in alignment with local regulations. Specific details for this position will be discussed during the interview process." Note: The last sentence about specific details for this position will be discussed during interview process is somewhat generic; but it's substantive? Might be considered boilerplate? It's about the position details; but it's generic. Might be okay to keep. But we also have benefits info repeated: "CSC offers a competitive and comprehensive benefits package that includes annual leave, tuition reimbursement, referral bonuses, and more." Also earlier: "CSC colleagues have global career opportunities and excellent benefits, including annual success-sharing bonuses or commission plans based on individual performance." We'll combine. Now Role description paragraph from About The Role: "The Operations Manager – Guernsey reports to the Operations Director – Jersey and provides operational coordination, governance support, and delivery oversight across the Guernsey business. Acting as a central coordination point between Business Units and Shared Services, this role helps ensure operational matters, board reporting requirements, KPI MI inputs, and change initiatives are managed in a structured, consistent, and accountable way. You will work closely with operational leadership, the Data Metrics team, Business Units, and Shared Services to strengthen visibility, follow-through, and escalation across key operational activity. This role does not replace ownership within Business Units or Shared Services; it provides the structure, tracking, and escalation support that enables priorities to be delivered effectively." Now Responsibilities list (Key Responsibilities): - Coordinate preparation and delivery of board update reports, including gathering inputs across teams (with support from the Project Manager where applicable) and ensuring timely submission to the required standard - Partner with the Data Metrics team to coordinate accurate and timely inputs into KPI MI reporting suites, dashboards, and operational trackers - Track reporting actions, dependencies, and outstanding inputs; proactively follow up to maintain delivery discipline and quality - Identify, challenge, and escalate reporting gaps, inconsistencies, delays, and unresolved dependencies that require leadership input - Provide day-to-day operational oversight by tracking operational initiatives, agreed actions, and outcomes through to completion - Act as the central coordination and escalation point between Business Units and Shared Services to resolve cross-business operational issues - Identify recurring operational themes, dependencies, and blockers; translate insights into clear actions, risks, and escalation points - Participate as a member of the Policies and Procedures Committee and support governance standards and consistent ways of working - Lead and develop direct reports through regular check-ins, objective setting, prioritisation, and performance follow-up - Support structured project and change delivery by coordinating stakeholders, tracking risks/blockers, and ensuring operational follow-through after change activity Now Required Qualification/Experience list: - Proven experience in operations management, operational coordination, governance, or delivery oversight in a multi-stakeholder environment - Strong organisational skills with the ability to manage multiple priorities, deadlines, and dependencies across teams - Demonstrated capability working with KPI MI, operational data, dashboards, and reporting packs, with high attention to detail - Strong communication skills, including the ability to coordinate inputs, provide constructive challenge, and drive actions to closure - Experience escalating risks/issues appropriately and supporting resolution of cross-functional operational challenges - People management experience or clear capability to lead, prioritise work, and build accountability within a team Now Preferred Qualification/Experience list: - Accounting background (part-qualified or qualified) or strong commercial awareness and understanding of operational performance drivers - Experience coordinating board reporting inputs and governance routines (actions, minutes, committee packs, dependencies) - Experience supporting change initiatives, workstream tracking, and delivery governance across business units and shared services - Familiarity working alongside data/metrics teams to define, validate, and improve MI inputs and reporting quality Now Skills: we could extract from required: Strong organisational skills, Demonstrated capability working with KPI MI, operational data, dashboards, reporting packs, Strong communication skills, Experience escalating risks/issues, People management experience. But these are already in Requirements. To avoid duplication, maybe we should not duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put skills in both Requirements and Skills, that's duplication. Better to not duplicate. So we could move some items to Skills that are not already in Requirements? But all skills are in Requirements. Perhaps we can treat Requirements as qualifications/experience, and Skills as abilities (like