Contractual Risk Manager

We need to output HTML fragment with headings

for sections: 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. No metadata like Job ID. Remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, cookie/navigation/legal. Also remove duplicated lines. We need to preserve all substantive information. Let's parse the posting. Sections present: - About The Role (intro paragraph). Should be under

About the role

with

content. - Key Responsibilities Include ... list of responsibilities. Should be under

Responsibilities

with

• items. - Skills & Experience That Lead To Success: includes qualifications (JD, experience, knowledge, abilities). Could be split into Requirements/Qualifications/Skills. The instruction: use headings for Requirements, Qualifications, Skills. We need to decide where to place content. The posting has "Skills & Experience That Lead To Success" which includes Juris Doctor, proven relevant legal experience, deep knowledge, ability to identify, strong written/verbal communication, collaborative approach, intellectual curiosity. That's a mix of qualifications and skills. We could put under

  Qualifications

  for JD and experience, and

  Skills

  for abilities etc. But we must not create thin sections; prefer few substantive sections. Could combine into one

  Skills & Experience

  but headings must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot create custom heading. So we need to map content to those headings. We could put all under

  Qualifications

  (since includes JD, experience, knowledge). Or split: Requirements (maybe JD) and Skills (abilities). But we need to avoid thin sections. Let's see if we have content for Requirements: maybe "Juris Doctor (JD) or equivalent legal qualification." That's a requirement. Also "Proven relevant legal experience within a construction or engineering company, or a law firm with a focus on construction, infrastructure, or energy." That's also requirement/experience. Could be under Requirements. Then Qualifications could be "Deep knowledge of contract analysis, negotiation, indemnification, and risk allocation within the construction or infrastructure sector." Ability to identify complex exposures etc. That's more qualifications. Skills could be "Strong written and verbal communication skills... Collaborative and consultative approach... Intellectual curiosity..." That seems appropriate. Thus we can have three sections: Requirements, Qualifications, Skills. Now Benefits: The posting includes "What You Can Expect From Us" with bullet list: Comprehensive Benefits Package, Collaborative and innovative environment, Culture of continuous learning and professional development, Competitive salary package, 401k with above-average employer match of up to 5% of your salary, Leadership training and support, Work/Life Balance (Summer Fridays, flexible work arrangements and mental health services), Education and Student Loan Assistance. Also later mentions salary range varies etc. That's not a specific number, so we should not create Pay section because no specific salary figure. Benefits section we can include those items as list. Schedule: Not mentioned. No schedule info. So we omit Schedule. Pay: Not specific; we should not create Pay section because no specific salary. The posting says "Competitive salary package" but that's vague; also "The salary range for this position (intended for U.S. applicants) will vary based on applicant’s education, experience, skills, and abilities, as well as internal equity and alignment with market data. The salary may also be adjusted based on applicant’s geographic location." That's not a specific number or range; we should not create Pay section per instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have specific items, so we can include Benefits. Pay we should omit. Now we need to remove boilerplate: EEO statement, "American Global is proud to be an equal opportunity workplace..." etc. Also "Who We Are" paragraph maybe considered boilerplate? It's descriptive of company; but it's substantive? It's about the company, not role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Who We Are" might be considered boilerplate but it's not EEO; it's company description. Might be considered part of posting but not essential? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "Who We Are" is substantive about the company. However, we might keep it under About the role? But we already have About the role paragraph. The "Who We Are" is separate; could be considered part of About the role? Might be okay to include as additional paragraph under About the role. But we need to avoid duplication. The "Who We Are" includes details about American Global being largest privately held insurance and surety brokerage firm etc. That's substantive. We'll include it as part of About the role (maybe as second paragraph). Ensure we don't include EEO boilerplate. Also remove "If you would like to learn more about the reasonable accommodations we provide, email info@americanglobal.com." That's application instruction? It's about accommodations; could be considered part of EEO but it's still instruction. Likely remove. Also remove "The salary range for this position (intended for U.S. applicants) will vary..." because it's vague and not specific; but it's substantive about salary variability. However we are not creating Pay section; we could mention it in Benefits? Not appropriate. Could we include it under Benefits as a note? The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range will vary; but not a specific range. Might still be considered Pay info. Safer to omit Pay section entirely, and not include that sentence anywhere else because it's about Pay. But we might lose substantive info. However the instruction says preserve ALL substantive information; but also says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state something about salary (that it will vary). That's still Pay info. But we cannot create Pay section; maybe we can incorporate that sentence into Benefits? Not ideal. Could we include a

  under About the role about compensation? The instruction didn't forbid mentioning pay in other sections; just said not to create Pay/Schedule/Benefits sections unless posting actually states them. It does state something about salary (that it will vary). So we could include that as a paragraph under Benefits? But Benefits is for benefits; maybe we could add a note about compensation under Benefits as a bullet? However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about salary (that it will vary). So we could create a Pay section? But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state something about salary (that it will vary). So we could create a Pay section with that statement. However they also said "Prefer a few substantive sections over many thin ones." The Pay section would be thin (just a sentence about variability). Might be better to incorporate into Benefits or About the role. But the instruction about not creating Pay section unless posting actually states them suggests we can create Pay section if there is any salary info. There is salary info (competitive salary package, 401k match, etc). Actually 401k is benefit. Competitive salary package is vague but still salary info. So we could create Pay section with that statement. But they also said "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can create Pay section because posting does state something about salary (competitive salary package, 401k match, salary may vary). However they also said "Prefer a few substantive sections over many thin ones." If we create Pay section with just a sentence, it's thin. Maybe we can combine Pay with Benefits? But they are separate headings allowed. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings. It didn't forbid combining. It said "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. If we have Benefits already with several items, adding Pay with just a sentence might be thin. Could we incorporate the salary info into Benefits as a bullet? Eg "Competitive salary package" and "401k with above-average employer match of up to 5% of your salary" are already benefits? Actually 401k is benefit; competitive salary package is pay. Could we treat "Competitive salary package" as a benefit? It's compensation, but could be considered benefit. However the instruction distinguishes Benefits and Pay. Might be okay to put salary info under Benefits as a bullet? Might be stretching. Better to create Pay section with the salary variability statement and maybe also mention competitive salary package. That would be a few sentences; not extremely thin. Let's do that. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We'll omit Schedule. Now we need to extract content for each. About the role: combine the introductory paragraph(s) before "Key Responsibilities Include". The posting starts: "About The Role We are seeking a Contractual Risk Manager to join our Infrastructure team. In this role, you will analyze contractual risk and help clients navigate the complex risk allocation issues associated with major construction and infrastructure projects. Working alongside senior risk professionals, you will review and advise on construction contracts, including alternative delivery projects such as design-build and public-private partnerships (P3), as well as joint venture agreements, design agreements, subcontractor agreements, and other project-related contracts. You will collaborate with contractors, legal teams, and insurance and surety professionals to evaluate contractual risk allocation, support contract negotiations, and help develop practical strategies for managing and transferring risk. This is an opportunity to work on significant projects across sectors including heavy civil, buildings, data centers, and water infrastructure, while developing deeper expertise in insurance and surety. You will also have the opportunity to contribute to client strategy, business development, and thought leadership as you grow within the role. This position can be located near any of our offices in the US or Canada." Then after that, "Key Responsibilities Include". So About the role includes all that. We may also include "Who We Are" paragraph? It's after the EEO stuff. Let's see if we should include it. It's substantive about company. Could be added as another paragraph under About the role. However the instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The "Who We Are" is not boilerplate; it's company description. I'd include it. Thus About the role will have two paragraphs: first the role description, second the company description. Now Responsibilities: list items from "Key Responsibilities Include". Let's extract each bullet: - Contractual Risk Analysis: Analyze major construction and infrastructure agreements with a focus on risk allocation, indemnification, insurance requirements, and other key contractual provisions. - Contract Negotiation & Client Advisory: Support clients throughout contract negotiations by identifying key exposures and providing practical guidance on risk allocation, indemnities, and insurance terms. - Insurance & Risk Advisory: Evaluate contractual requirements and project risk profiles to help develop comprehensive risk management and insurance strategies. Contribute to risk reports that combine contractual analysis with technical risk assessments provided by other specialists. - Insurance Policy Analysis: Partner with colleagues and clients to evaluate insurance coverages, exclusions, limitations, and areas of uncertainty, including how relevant claims and coverage issues have historically been addressed. - Cross-Functional Risk Guidance: Serve as a bridge between contractors, legal teams, and insurance professionals, translating complex contractual provisions into practical risk considerations and identifying where insurance or surety solutions may mitigate exposure. -