Scrum Master
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Key content:
Position Description: We are seeking an experienced Scrum Master to support multiple Agile Scrum teams within a Property & Casualty (P&C) insurance environment. The Scrum Master will serve as a servant leader, Agile coach, and delivery facilitator, enabling teams to deliver high quality solutions while promoting collaboration, transparency, accountability, and continuous improvement. This role requires strong experience working across business and technology teams, managing dependencies and impediments, and facilitating Agile delivery in a complex enterprise environment. This position must be performed at the client site in Webster, MA, however a hybrid working model is acceptable.
Then sections: "Your future duties and responsibilities" with subheadings: Agile Leadership & Ceremonies, Delivery, Backlog & Dependency Management, P&C Insurance & Stakeholder Collaboration, Agile Metrics & Continuous Improvement.
Then "Required Qualifications" list.
Then "Preferred Qualifications" list.
Then "What Success Looks Like" list.
Then "Other Information:" includes compensation range and benefits.
Also there is duplicate "Required Qualifications To Be Successful In This Role" repeated same list; we should not duplicate content; preserve all substantive info but avoid duplication. We need to include each piece only once.
We need to decide sections: About the role (intro paragraph). Responsibilities (duties). Requirements (maybe required qualifications). Qualifications (maybe preferred? Actually they have Required Qualifications and Preferred Qualifications; we could combine into Requirements and Qualifications sections? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map:
- About the role: intro paragraph (position description).
- Responsibilities: duties (Agile Leadership & Ceremonies etc.)
- Requirements: Required Qualifications (maybe also include location/hybrid? but location is part of About? Could include in About.)
- Qualifications: Preferred Qualifications.
- Skills: maybe we could extract skills from responsibilities? But we have no explicit Skills section; we could omit if no specific content. The instruction: include a section ONLY when the posting has real, specific content for it. So if we don't have a distinct Skills section, we should not create it.
- Benefits: we have benefits listed.
- Pay: we have compensation range.
- Schedule: we have location/hybrid model; maybe schedule? The posting mentions "This position must be performed at the client site in Webster, MA, however a hybrid working model is acceptable." That's about location/work arrangement, not schedule. No explicit schedule (e.g., full-time, part-time). So we should not create Schedule section unless there is specific schedule info. So omit Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to use
for each section heading.
Inside sections, use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information.
Let's extract content.
About the role: combine the initial paragraphs: "We are seeking an experienced Scrum Master to support multiple Agile Scrum teams within a Property & Casualty (P&C) insurance environment. The Scrum Master will serve as a servant leader, Agile coach, and delivery facilitator, enabling teams to deliver high quality solutions while promoting collaboration, transparency, accountability, and continuous improvement. This role requires strong experience working across business and technology teams, managing dependencies and impediments, and facilitating Agile delivery in a complex enterprise environment. This position must be performed at the client site in Webster, MA, however a hybrid working model is acceptable."
That's prose; we can put in
.
Responsibilities: we have multiple bullet-like paragraphs under headings: Agile Leadership & Ceremonies, Delivery, Backlog & Dependency Management, P&C Insurance & Stakeholder Collaboration, Agile Metrics & Continuous Improvement. Each contains several sentences; we can treat each as list items? The instruction: Use
- for any list of duties/requirements/benefits. So we can create a
with each duty as - . We need to preserve all substantive info; we can break down each bullet into separate
- items, but we must not lose detail. Could also keep each heading as part of
- text.
Let's extract each duty:
Agile Leadership & Ceremonies:
- Serve as Scrum Master for multiple Scrum teams simultaneously, ensuring effective Agile practices and delivery execution.
- Facilitate core Agile ceremonies, including Sprint Planning, Daily Stand Ups, Backlog Refinement, Sprint Reviews, and Retrospectives.
- Help teams establish clear Sprint Goals, manage capacity, and make realistic delivery commitments.
- Coach teams, Product Owners, and stakeholders on Scrum principles, Agile practices, servant leadership, and continuous improvement.
- Promote self-organizing, collaborative, high performing teams.
Delivery, Backlog & Dependency Management:
- Partner with Product Owners and Business Analysts to maintain prioritized, well defined, and Sprint ready backlogs.
- Facilitate backlog refinement to ensure stories have clear requirements, acceptance criteria, estimates, and identified dependencies.
- Monitor Sprint progress, velocity, capacity, scope, and delivery commitments; proactively identify and address risks.
- Identify, track, and remove impediments affecting team productivity and delivery.
- Manage cross team dependencies, integration points, and coordination with other technology teams.
- Support release planning, production readiness, and delivery coordination across dependent teams.
P&C Insurance & Stakeholder Collaboration:
- Apply Property & Casualty insurance domain knowledge to support delivery of business and technology initiatives.
- Work with teams supporting capabilities such as policy administration, underwriting, rating, claims, billing, agency/broker systems, customer portals, integrations, and regulatory initiatives.
- Understand the impact of insurance business rules, regulatory requirements, product changes, and downstream integrations on delivery.
- Partner effectively with Product Owners, business stakeholders, developers, QA, architects, DevOps, data teams, and technology leadership.
- Provide clear and timely communication on delivery progress, risks, issues, dependencies, and decisions.
Agile Metrics & Continuous Improvement:
- Maintain accurate delivery information in Jira.
- Monitor relevant Agile metrics such as velocity, burndown/burnup, cycle time, throughput, defects, and Sprint completion.
- Use metrics and team feedback to identify trends and opportunities for improvement.
- Facilitate meaningful retrospectives and ensure improvement actions are followed through.
- Promote sustainable delivery, quality, transparency, and continuous improvement across both teams.
We'll put each bullet as
- .
Requirements (Required Qualifications): list:
- 5+ years of experience as a Scrum Master in Agile software development environments.
- 5+ years of experience working in the Property & Casualty (P&C) insurance industry, with a strong understanding of P&C business processes and technology.
- Proven experience supporting and coordinating multiple Scrum teams simultaneously.
- Proven experience working in an onshore/offshore delivery model, effectively coordinating distributed teams across geographies, time zones, and working hours.
- Strong understanding of Scrum, Agile principles, servant leadership, and Agile coaching.
- Demonstrated experience facilitating Sprint Planning, Daily Stand Ups, Backlog Refinement, Sprint Reviews, and Retrospectives.
- Proven ability to manage impediments, risks, issues, and cross team dependencies.
- Experience working with Jira or similar Agile delivery tools.
- Strong stakeholder management, facilitation, communication, conflict resolution, and problem solving skills.
- Experience collaborating with Product Owners, Business Analysts, developers, QA, architects, and other cross functional teams.
- Ability to manage competing priorities and maintain delivery visibility across multiple teams.
- Active Scrum Master certification, such as CSM, PSM, SAFe Scrum Master (SSM), or equivalent.
- Bachelor's Experience Required (the text says "Bachelor's Experience Required" maybe means Bachelor's degree required? It says "Bachelor's Experience Required". Likely they meant Bachelor's degree required. We'll keep as "Bachelor's degree required.") Actually the original: "Bachelor's Experience Required". We'll preserve that phrase exactly? It's ambiguous but we must preserve substantive information; we can keep "Bachelor's Experience Required". We'll treat as a qualification item.
Qualifications (Preferred Qualifications): list:
- Experience working in SAFe, Scrum@Scale, or another enterprise Agile framework.
- Strong knowledge of P&C insurance functions including policy lifecycle, underwriting, rating, claims, billing, renewals, endorsements, and regulatory requirements.
- Experience supporting insurance application modernization, digital transformation, enterprise integrations, APIs, cloud, data, or automation initiatives.
- Experience coordinating releases across multiple applications, platforms, or Agile teams.
- Experience working with geographically distributed or offshore/onshore delivery teams.
- Additional Agile, Scrum, or Agile coaching certifications are a plus.
- Experience using Agile metrics and dashboards to support executive and program level reporting.
Benefits: from "Other Information:" after compensation: "CGI's benefits are offered to eligible professionals on their first day of employment to include: Competitive compensation Comprehensive insurance options Matching contributions through the 401(k) plan and the share purchase plan Paid time off for vacation, holidays, and sick time Paid parental leave Learning opportunities and tuition assistance Wellness and Wellbeing programs"
We need to list each as
- . Also note "Competitive compensation" is listed as a benefit but we also have Pay section; we can still include it.
Pay: compensation range: "A reasonable estimate of the current range for this role in the U.S. is $77,800.00 $172,400.00." Note there is a missing space between numbers? Actually it's "$77,800.00 $172,400.00". We'll preserve exactly.
We might also include note about CGI typically not hiring at top of range etc. That's also part of Other Information. Should we include that in Pay section? It's substantive info about compensation. We'll include as prose
under Pay section.
Thus Pay section:
A reasonable estimate of the current range for this role in the U.S. is $77,800.00 $172,400.00. To support the ability to reward for merit-based performance, CGI typically does not hire individuals at or near the top of the range for their role. Compensation decisions are dependent on the facts and circumstances of each case.
We need to avoid duplication: The "Other Information" block appears twice in the posting (duplicate). We'll only include once.
Now we need to ensure we don't include boilerplate like EEO etc. At the end there is a long EEO statement; we must remove.
Also remove duplicated lines like "Required Qualifications To Be Successful In This Role" repeated; we already captured Required Qualifications.
Now produce HTML fragment:
About the role
We are seeking
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key content: Position Description: We are seeking an experienced Scrum Master to support multiple Agile Scrum teams within a Property & Casualty (P&C) insurance environment. The Scrum Master will serve as a servant leader, Agile coach, and delivery facilitator, enabling teams to deliver high quality solutions while promoting collaboration, transparency, accountability, and continuous improvement. This role requires strong experience working across business and technology teams, managing dependencies and impediments, and facilitating Agile delivery in a complex enterprise environment. This position must be performed at the client site in Webster, MA, however a hybrid working model is acceptable. Then sections: "Your future duties and responsibilities" with subheadings: Agile Leadership & Ceremonies, Delivery, Backlog & Dependency Management, P&C Insurance & Stakeholder Collaboration, Agile Metrics & Continuous Improvement. Then "Required Qualifications" list. Then "Preferred Qualifications" list. Then "What Success Looks Like" list. Then "Other Information:" includes compensation range and benefits. Also there is duplicate "Required Qualifications To Be Successful In This Role" repeated same list; we should not duplicate content; preserve all substantive info but avoid duplication. We need to include each piece only once. We need to decide sections: About the role (intro paragraph). Responsibilities (duties). Requirements (maybe required qualifications). Qualifications (maybe preferred? Actually they have Required Qualifications and Preferred Qualifications; we could combine into Requirements and Qualifications sections? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map: - About the role: intro paragraph (position description). - Responsibilities: duties (Agile Leadership & Ceremonies etc.) - Requirements: Required Qualifications (maybe also include location/hybrid? but location is part of About? Could include in About.) - Qualifications: Preferred Qualifications. - Skills: maybe we could extract skills from responsibilities? But we have no explicit Skills section; we could omit if no specific content. The instruction: include a section ONLY when the posting has real, specific content for it. So if we don't have a distinct Skills section, we should not create it. - Benefits: we have benefits listed. - Pay: we have compensation range. - Schedule: we have location/hybrid model; maybe schedule? The posting mentions "This position must be performed at the client site in Webster, MA, however a hybrid working model is acceptable." That's about location/work arrangement, not schedule. No explicit schedule (e.g., full-time, part-time). So we should not create Schedule section unless there is specific schedule info. So omit Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to use
for each section heading.
Inside sections, use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information.
Let's extract content.
About the role: combine the initial paragraphs: "We are seeking an experienced Scrum Master to support multiple Agile Scrum teams within a Property & Casualty (P&C) insurance environment. The Scrum Master will serve as a servant leader, Agile coach, and delivery facilitator, enabling teams to deliver high quality solutions while promoting collaboration, transparency, accountability, and continuous improvement. This role requires strong experience working across business and technology teams, managing dependencies and impediments, and facilitating Agile delivery in a complex enterprise environment. This position must be performed at the client site in Webster, MA, however a hybrid working model is acceptable."
That's prose; we can put in
.
Responsibilities: we have multiple bullet-like paragraphs under headings: Agile Leadership & Ceremonies, Delivery, Backlog & Dependency Management, P&C Insurance & Stakeholder Collaboration, Agile Metrics & Continuous Improvement. Each contains several sentences; we can treat each as list items? The instruction: Use
- for any list of duties/requirements/benefits. So we can create a
with each duty as - . We need to preserve all substantive info; we can break down each bullet into separate
- items, but we must not lose detail. Could also keep each heading as part of
- text.
Let's extract each duty:
Agile Leadership & Ceremonies:
- Serve as Scrum Master for multiple Scrum teams simultaneously, ensuring effective Agile practices and delivery execution.
- Facilitate core Agile ceremonies, including Sprint Planning, Daily Stand Ups, Backlog Refinement, Sprint Reviews, and Retrospectives.
- Help teams establish clear Sprint Goals, manage capacity, and make realistic delivery commitments.
- Coach teams, Product Owners, and stakeholders on Scrum principles, Agile practices, servant leadership, and continuous improvement.
- Promote self-organizing, collaborative, high performing teams.
Delivery, Backlog & Dependency Management:
- Partner with Product Owners and Business Analysts to maintain prioritized, well defined, and Sprint ready backlogs.
- Facilitate backlog refinement to ensure stories have clear requirements, acceptance criteria, estimates, and identified dependencies.
- Monitor Sprint progress, velocity, capacity, scope, and delivery commitments; proactively identify and address risks.
- Identify, track, and remove impediments affecting team productivity and delivery.
- Manage cross team dependencies, integration points, and coordination with other technology teams.
- Support release planning, production readiness, and delivery coordination across dependent teams.
P&C Insurance & Stakeholder Collaboration:
- Apply Property & Casualty insurance domain knowledge to support delivery of business and technology initiatives.
- Work with teams supporting capabilities such as policy administration, underwriting, rating, claims, billing, agency/broker systems, customer portals, integrations, and regulatory initiatives.
- Understand the impact of insurance business rules, regulatory requirements, product changes, and downstream integrations on delivery.
- Partner effectively with Product Owners, business stakeholders, developers, QA, architects, DevOps, data teams, and technology leadership.
- Provide clear and timely communication on delivery progress, risks, issues, dependencies, and decisions.
Agile Metrics & Continuous Improvement:
- Maintain accurate delivery information in Jira.
- Monitor relevant Agile metrics such as velocity, burndown/burnup, cycle time, throughput, defects, and Sprint completion.
- Use metrics and team feedback to identify trends and opportunities for improvement.
- Facilitate meaningful retrospectives and ensure improvement actions are followed through.
- Promote sustainable delivery, quality, transparency, and continuous improvement across both teams.
We'll put each bullet as
- .
Requirements (Required Qualifications): list:
- 5+ years of experience as a Scrum Master in Agile software development environments.
- 5+ years of experience working in the Property & Casualty (P&C) insurance industry, with a strong understanding of P&C business processes and technology.
- Proven experience supporting and coordinating multiple Scrum teams simultaneously.
- Proven experience working in an onshore/offshore delivery model, effectively coordinating distributed teams across geographies, time zones, and working hours.
- Strong understanding of Scrum, Agile principles, servant leadership, and Agile coaching.
- Demonstrated experience facilitating Sprint Planning, Daily Stand Ups, Backlog Refinement, Sprint Reviews, and Retrospectives.
- Proven ability to manage impediments, risks, issues, and cross team dependencies.
- Experience working with Jira or similar Agile delivery tools.
- Strong stakeholder management, facilitation, communication, conflict resolution, and problem solving skills.
- Experience collaborating with Product Owners, Business Analysts, developers, QA, architects, and other cross functional teams.
- Ability to manage competing priorities and maintain delivery visibility across multiple teams.
- Active Scrum Master certification, such as CSM, PSM, SAFe Scrum Master (SSM), or equivalent.
- Bachelor's Experience Required (the text says "Bachelor's Experience Required" maybe means Bachelor's degree required? It says "Bachelor's Experience Required". Likely they meant Bachelor's degree required. We'll keep as "Bachelor's degree required.") Actually the original: "Bachelor's Experience Required". We'll preserve that phrase exactly? It's ambiguous but we must preserve substantive information; we can keep "Bachelor's Experience Required". We'll treat as a qualification item.
Qualifications (Preferred Qualifications): list:
- Experience working in SAFe, Scrum@Scale, or another enterprise Agile framework.
- Strong knowledge of P&C insurance functions including policy lifecycle, underwriting, rating, claims, billing, renewals, endorsements, and regulatory requirements.
- Experience supporting insurance application modernization, digital transformation, enterprise integrations, APIs, cloud, data, or automation initiatives.
- Experience coordinating releases across multiple applications, platforms, or Agile teams.
- Experience working with geographically distributed or offshore/onshore delivery teams.
- Additional Agile, Scrum, or Agile coaching certifications are a plus.
- Experience using Agile metrics and dashboards to support executive and program level reporting.
Benefits: from "Other Information:" after compensation: "CGI's benefits are offered to eligible professionals on their first day of employment to include: Competitive compensation Comprehensive insurance options Matching contributions through the 401(k) plan and the share purchase plan Paid time off for vacation, holidays, and sick time Paid parental leave Learning opportunities and tuition assistance Wellness and Wellbeing programs"
We need to list each as
- . Also note "Competitive compensation" is listed as a benefit but we also have Pay section; we can still include it.
Pay: compensation range: "A reasonable estimate of the current range for this role in the U.S. is $77,800.00 $172,400.00." Note there is a missing space between numbers? Actually it's "$77,800.00 $172,400.00". We'll preserve exactly.
We might also include note about CGI typically not hiring at top of range etc. That's also part of Other Information. Should we include that in Pay section? It's substantive info about compensation. We'll include as prose
under Pay section.
Thus Pay section:
A reasonable estimate of the current range for this role in the U.S. is $77,800.00 $172,400.00. To support the ability to reward for merit-based performance, CGI typically does not hire individuals at or near the top of the range for their role. Compensation decisions are dependent on the facts and circumstances of each case.
We need to avoid duplication: The "Other Information" block appears twice in the posting (duplicate). We'll only include once.
Now we need to ensure we don't include boilerplate like EEO etc. At the end there is a long EEO statement; we must remove.
Also remove duplicated lines like "Required Qualifications To Be Successful In This Role" repeated; we already captured Required Qualifications.
Now produce HTML fragment:
About the role
We are seeking
for prose. We need to preserve all substantive information. Let's extract content. About the role: combine the initial paragraphs: "We are seeking an experienced Scrum Master to support multiple Agile Scrum teams within a Property & Casualty (P&C) insurance environment. The Scrum Master will serve as a servant leader, Agile coach, and delivery facilitator, enabling teams to deliver high quality solutions while promoting collaboration, transparency, accountability, and continuous improvement. This role requires strong experience working across business and technology teams, managing dependencies and impediments, and facilitating Agile delivery in a complex enterprise environment. This position must be performed at the client site in Webster, MA, however a hybrid working model is acceptable." That's prose; we can put in
. Responsibilities: we have multiple bullet-like paragraphs under headings: Agile Leadership & Ceremonies, Delivery, Backlog & Dependency Management, P&C Insurance & Stakeholder Collaboration, Agile Metrics & Continuous Improvement. Each contains several sentences; we can treat each as list items? The instruction: Use
- for any list of duties/requirements/benefits. So we can create a
- with each duty as
- . We need to preserve all substantive info; we can break down each bullet into separate
- items, but we must not lose detail. Could also keep each heading as part of
- text. Let's extract each duty: Agile Leadership & Ceremonies: - Serve as Scrum Master for multiple Scrum teams simultaneously, ensuring effective Agile practices and delivery execution. - Facilitate core Agile ceremonies, including Sprint Planning, Daily Stand Ups, Backlog Refinement, Sprint Reviews, and Retrospectives. - Help teams establish clear Sprint Goals, manage capacity, and make realistic delivery commitments. - Coach teams, Product Owners, and stakeholders on Scrum principles, Agile practices, servant leadership, and continuous improvement. - Promote self-organizing, collaborative, high performing teams. Delivery, Backlog & Dependency Management: - Partner with Product Owners and Business Analysts to maintain prioritized, well defined, and Sprint ready backlogs. - Facilitate backlog refinement to ensure stories have clear requirements, acceptance criteria, estimates, and identified dependencies. - Monitor Sprint progress, velocity, capacity, scope, and delivery commitments; proactively identify and address risks. - Identify, track, and remove impediments affecting team productivity and delivery. - Manage cross team dependencies, integration points, and coordination with other technology teams. - Support release planning, production readiness, and delivery coordination across dependent teams. P&C Insurance & Stakeholder Collaboration: - Apply Property & Casualty insurance domain knowledge to support delivery of business and technology initiatives. - Work with teams supporting capabilities such as policy administration, underwriting, rating, claims, billing, agency/broker systems, customer portals, integrations, and regulatory initiatives. - Understand the impact of insurance business rules, regulatory requirements, product changes, and downstream integrations on delivery. - Partner effectively with Product Owners, business stakeholders, developers, QA, architects, DevOps, data teams, and technology leadership. - Provide clear and timely communication on delivery progress, risks, issues, dependencies, and decisions. Agile Metrics & Continuous Improvement: - Maintain accurate delivery information in Jira. - Monitor relevant Agile metrics such as velocity, burndown/burnup, cycle time, throughput, defects, and Sprint completion. - Use metrics and team feedback to identify trends and opportunities for improvement. - Facilitate meaningful retrospectives and ensure improvement actions are followed through. - Promote sustainable delivery, quality, transparency, and continuous improvement across both teams. We'll put each bullet as
- . Requirements (Required Qualifications): list: - 5+ years of experience as a Scrum Master in Agile software development environments. - 5+ years of experience working in the Property & Casualty (P&C) insurance industry, with a strong understanding of P&C business processes and technology. - Proven experience supporting and coordinating multiple Scrum teams simultaneously. - Proven experience working in an onshore/offshore delivery model, effectively coordinating distributed teams across geographies, time zones, and working hours. - Strong understanding of Scrum, Agile principles, servant leadership, and Agile coaching. - Demonstrated experience facilitating Sprint Planning, Daily Stand Ups, Backlog Refinement, Sprint Reviews, and Retrospectives. - Proven ability to manage impediments, risks, issues, and cross team dependencies. - Experience working with Jira or similar Agile delivery tools. - Strong stakeholder management, facilitation, communication, conflict resolution, and problem solving skills. - Experience collaborating with Product Owners, Business Analysts, developers, QA, architects, and other cross functional teams. - Ability to manage competing priorities and maintain delivery visibility across multiple teams. - Active Scrum Master certification, such as CSM, PSM, SAFe Scrum Master (SSM), or equivalent. - Bachelor's Experience Required (the text says "Bachelor's Experience Required" maybe means Bachelor's degree required? It says "Bachelor's Experience Required". Likely they meant Bachelor's degree required. We'll keep as "Bachelor's degree required.") Actually the original: "Bachelor's Experience Required". We'll preserve that phrase exactly? It's ambiguous but we must preserve substantive information; we can keep "Bachelor's Experience Required". We'll treat as a qualification item. Qualifications (Preferred Qualifications): list: - Experience working in SAFe, Scrum@Scale, or another enterprise Agile framework. - Strong knowledge of P&C insurance functions including policy lifecycle, underwriting, rating, claims, billing, renewals, endorsements, and regulatory requirements. - Experience supporting insurance application modernization, digital transformation, enterprise integrations, APIs, cloud, data, or automation initiatives. - Experience coordinating releases across multiple applications, platforms, or Agile teams. - Experience working with geographically distributed or offshore/onshore delivery teams. - Additional Agile, Scrum, or Agile coaching certifications are a plus. - Experience using Agile metrics and dashboards to support executive and program level reporting. Benefits: from "Other Information:" after compensation: "CGI's benefits are offered to eligible professionals on their first day of employment to include: Competitive compensation Comprehensive insurance options Matching contributions through the 401(k) plan and the share purchase plan Paid time off for vacation, holidays, and sick time Paid parental leave Learning opportunities and tuition assistance Wellness and Wellbeing programs" We need to list each as
- . Also note "Competitive compensation" is listed as a benefit but we also have Pay section; we can still include it.
Pay: compensation range: "A reasonable estimate of the current range for this role in the U.S. is $77,800.00 $172,400.00." Note there is a missing space between numbers? Actually it's "$77,800.00 $172,400.00". We'll preserve exactly.
We might also include note about CGI typically not hiring at top of range etc. That's also part of Other Information. Should we include that in Pay section? It's substantive info about compensation. We'll include as prose
under Pay section. Thus Pay section:
A reasonable estimate of the current range for this role in the U.S. is $77,800.00 $172,400.00. To support the ability to reward for merit-based performance, CGI typically does not hire individuals at or near the top of the range for their role. Compensation decisions are dependent on the facts and circumstances of each case.
We need to avoid duplication: The "Other Information" block appears twice in the posting (duplicate). We'll only include once. Now we need to ensure we don't include boilerplate like EEO etc. At the end there is a long EEO statement; we must remove. Also remove duplicated lines like "Required Qualifications To Be Successful In This Role" repeated; we already captured Required Qualifications. Now produce HTML fragment:About the role
We are seeking