Product Manager - Intelligent Network Operations Control

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, disclaimer, etc. Must not include placeholder text. We need to parse the posting. Key sections: - Location: "This is a hybrid role based in Irvine, CA with an expectation of 4 days onsite each week." That's schedule info? Could be Schedule section: hybrid, 4 days onsite. - About The Job: description of role. - Your Role: bullet list of responsibilities. - Your Skills And Experience: qualifications/skills. - Compensation: base compensation range $101,140- $182,624/year. Also mention variable incentives, bonuses, commissions. Benefits: comprehensive non-negotiable benefits package, list of benefits. Thus we can have sections: - About the role (maybe "About the role" heading) containing the paragraph about the job. - Responsibilities: list from "Your Role" bullet points. - Qualifications: maybe combine "Your Skills And Experience" includes required qualifications (Bachelor's degree, 8+ years, etc.) and preferred experience. - Skills: maybe separate but we can combine. But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to include based on content. We have content for: - About the role: yes. - Responsibilities: yes (Your Role bullet list). - Qualifications: yes (Bachelor's degree, 8+ years, etc.) - Skills: maybe we can include "Skills" heading for technical skills like SAFe, MRO, aviation regulatory, data science, etc. But the qualifications already include many skills. Could split: Qualifications for education/experience, Skills for technical competencies. But we must not create thin sections; prefer few substantive sections. Could combine Qualifications and Skills into one "Qualifications" section that includes both education/experience and skills. However the instruction list includes both Qualifications and Skills as possible headings; we can choose to include only Qualifications if we put all there. That's acceptable. - Benefits: yes (benefits package list). - Pay: yes (base compensation range). - Schedule: yes (hybrid, 4 days onsite). We should not include Requirements heading if we don't have separate content; we can omit. Thus output HTML with sections:

About the role

...

,

Responsibilities

...

,

Qualifications

...

(or mix of

and

),

Benefits

...
,

Pay

...

,

Schedule

...

. Need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, disclaimer, etc. We must extract the responsibilities bullet points exactly as in text. Let's extract: From "Your Role": - Own the vision, strategy and multi-quarter roadmap for the Control Tower platform across all three capability pillars, aligned to business objectives and customer outcomes. - Define and prioritise Priority EPICs and features (Planning & Scheduling, Incident & Case Management, Reporting & Dashboarding); own and groom the backlog, balancing value, effort, compliance and commercial impact. - Operate within a SAFe Agile Release Train — contribute to PI planning, write clear user stories and acceptance criteria, and partner with engineering and UX to deliver rapid, relevant increments of value. - Work with data science teams to shape optimization/ML-driven scheduling and predictive maintenance capabilities, defining data requirements, success metrics and guardrails. - Engage operations teams, engineers and customers to translate maintenance and network-operations workflows into product requirements. - Ensure the product supports airworthiness and operational compliance (e.g. ADs, SBs, traceability, audit trails) and relevant regulatory frameworks (EASA / FAA). - Define and track KPIs — turnaround time, deferrals, utilization, downtime, SLA compliance and CSAT — and use analytics and feedback to steer the roadmap. - Act as the central coordination point across internal teams and customers, communicating progress and managing expectations. - Own the end-to-end product lifecycle from concept and design through operation, iteration and retirement. We need to keep punctuation as is. Now Qualifications/Skills: From "Your Skills And Experience": Required: - Bachelor’s degree in engineering, Computer Science, Information Systems, Aviation/Aeronautics or a related field (or equivalent experience). - 8+ years of relevant experience, including 3+ years in a product management or product owner role for a B2B software / SaaS product. - Hands-on experience delivering software in a SAFe or scaled agile environment (PI planning, user stories, backlog management). - Working knowledge of MRO / network operations — maintenance planning, scheduling, incident management or operations control. - Familiarity with aviation regulatory frameworks (EASA, FAA) and compliance concepts such as ADs, SBs and traceability. - Comfort partnering with data science on AI/ML and optimization features; strong data-driven prioritization skills. - Excellent communication, stakeholder management and leadership skills across technical and non-technical audiences. Preferred: - Experience with MRO/operations-control platforms (AMOS, Trax, Traxxall, TrustFlight, Ramco, or similar), aviation operations or maintenance environments, and knowledge of optimization, scheduling, predictive maintenance, and reliability analytics. - Experience delivering cloud-based SaaS products, dashboards/BI solutions, APIs, and system integrations, with SAFe/Scrum product certifications (POPM, CSPO, or equivalent) and the ability to translate complex requirements into clear direction for delivery teams. We should preserve all that. We could format as
• ... each bullet. Now Benefits: From paragraph: "Capgemini offers a comprehensive, non-negotiable benefits package to all regular, full-time employees. In the U.S. and Canada, available benefits are determined by local policy and eligibility and may include: Paid time off based on employee grade (A-F), defined by policy: Vacation: 12-25 days, depending on grade, Company paid holidays, Personal Days, Sick Leave Medical, dental, and vision coverage (or provincial healthcare coordination in Canada) Retirement savings plans (e.g., 401(k) in the U.S., RRSP in Canada) Life and disability insurance Employee assistance programs Other benefits as provided by local policy and eligibility" We need to preserve as list items maybe. We can create
  • Paid time off based on employee grade (A-F), defined by policy: Vacation: 12-25 days, depending on grade
  • Company paid holidays
  • Personal Days
  • Sick Leave
  • Medical, dental, and vision coverage (or provincial healthcare coordination in Canada)
  • Retirement savings plans (e.g., 401(k) in the U.S., RRSP in Canada)
  • Life and disability insurance
  • Employee assistance programs
  • Other benefits as provided by local policy and eligibility
  Now Pay: From: "The base compensation range for this role in the posted location is: $101,140- $182,624/year Capgemini provides compensation range information in accordance with applicable national, state, provincial, and local pay transparency laws. The base compensation range listed for this position reflects the minimum and maximum target compensation Capgemini, in good faith, believes it may pay for the role at the time of this posting. This range may be subject to change as permitted by law. The actual compensation offered to any candidate may fall outside of the posted range and will be determined based on multiple factors legally permitted in the applicable jurisdiction. These may include, but are not limited to: Geographic location, Education and qualifications, Certifications and licenses, Relevant experience and skills, Seniority and performance, Market and business consideration, Internal pay equity. It is not typical for candidates to be hired at or near the top of the posted compensation range. In addition to base salary, this role may be eligible for additional compensation such as variable incentives, bonuses, or commissions, depending on the position and applicable laws." We need to preserve all substantive info. However we must avoid boilerplate? The instructions say remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The pay transparency law statement might be considered legal boilerplate? It's about compensation range disclosure; it's part of the posting but maybe considered legal. However the instruction says "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". This is legal boilerplate about pay transparency. Might be considered legal and should be removed? The instruction says remove legal boilerplate. So we should strip out the sentences about Capgemini provides compensation range information in accordance with applicable laws, etc. But we must keep the base compensation range and mention of variable incentives etc. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The legal disclaimer about compensation range may be considered not substantive? It's about legal compliance; might be considered boilerplate. I'd lean to remove it to follow instruction. Keep the base compensation range and note about variable incentives etc. Thus Pay section:

  The base compensation range for this role in the posted location is: $101,140- $182,624/year. In addition to base salary, this role may be eligible for additional compensation such as variable incentives, bonuses, or commissions, depending on the position and applicable laws.

  We could also include note that it's not typical to be hired at top of range, but that might be considered boilerplate? It's still substantive? Might be considered extra detail; but we can keep if not too boilerplate. However it's a general statement; maybe keep. But to be safe, include it: "It is not typical for candidates to be hired at or near the top of the posted compensation range." That's substantive? It's a note; could keep. Thus Pay paragraph: include base range, note about typical hiring, variable incentives. Now Schedule: From location: "This is a hybrid role based in Irvine, CA with an expectation of 4 days onsite each week." Thus Schedule section:

  This is a hybrid role based in Irvine, CA with an expectation of 4 days onsite each week.

  Now About the role: paragraph from "About The Job You’re Considering" plus maybe first sentence about Capgemini? The opening paragraph about Capgemini Engineering is generic marketing; might be considered boilerplate? It's about company description; could be considered not specific to role. The instruction says preserve ALL substantive information; do not invent or summarize away detail. The company overview might be considered substantive? It's generic but still part of posting. However we might keep it as part of About the role. But we could also trim to just role-specific description. The instruction says "Prefer a few substantive sections over many thin ones." The company overview is not role-specific; maybe we can omit as it's not essential to role. However it's part of the posting; but we could consider it boilerplate? It's not legal/EEO; it's marketing. The instruction didn't explicitly say to remove marketing boilerplate, only cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should keep it. Thus About the role paragraph: combine first two sentences: "At Capgemini Engineering, the world leader in engineering services, we bring together a global team of engineers, scientists, and architects to help the world’s most innovative companies unleash