Risk Management Professional

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. No job title heading. No Job ID. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. First paragraph: "RK&K’s Construction Management Division is hiring a Risk Management Professional to support risk management activities across major capital programs and complex infrastructure projects. This position will be part of RK&K’s Project Controls practice and will work directly with clients, project teams, and technical disciplines to identify, assess, quantify, and manage project and program risks. The position will support the development and implementation of risk management processes, integrate risk with cost and schedule controls, and provide recommendations to project and program leadership. The Risk Management Professional will also contribute to the continued development of RK&K’s risk management practice, including methodologies, tools, processes, and staff capabilities. Depending on experience, the position may lead risk management teams, supervise junior professionals, and serve as a senior advisor to clients and project leadership." That's about the role. Could be "About the role". We'll put that in

About the role

then

with that paragraph. Next: "Essential Functions" list. Those are responsibilities. We'll put

Responsibilities

then

• each bullet. List items: - Lead the development and implementation of project and program risk management plans, processes, procedures, and governance frameworks. - Facilitate risk identification, assessment, and mitigation workshops with clients, project teams, contractors, and technical stakeholders. - Develop and maintain risk registers, risk matrices, risk management plans, mitigation strategies, and associated documentation. - Evaluate project risks across cost, schedule, scope, procurement, contracting, design, construction, funding, stakeholder, operational, and other areas. - Perform qualitative and quantitative risk analysis, including probabilistic cost and schedule analysis, contingency evaluation, and risk-adjusted forecasting. - Integrate risk management activities with project controls, including cost estimates, schedules, forecasts, contingency management, change management, and project performance reporting. - Monitor emerging risks, mitigation actions, residual risk, and overall program risk exposure; identify trends and communicate material risks to project and program leadership. - Prepare risk reports, dashboards, presentations, and recommendations for project teams, clients, and executive-level stakeholders using tools such as Power BI and other risk management and reporting software. - Support evaluation of project changes, claims, procurement strategies, delivery approaches, and other project decisions from a risk management perspective. - Lead or support the development of risk management methodologies, standards, tools, and best practices for RK&K and its clients. - Supervise, mentor, and provide technical direction to junior risk management and project controls staff, as applicable based on experience. Now "Required Experience" list: we can treat as Requirements (maybe also Qualifications). The instruction: Use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put each piece. "Required Experience" bullet list: we can put under Requirements (maybe also Qualifications). The bullet list includes: - Bachelor’s degree in engineering, construction management, project management, or a related field. - Demonstrated experience in project or program risk management, project controls, construction management, or a related discipline, with experience appropriate to a mid-career or senior professional. - Experience identifying, assessing, mitigating, and monitoring risks on complex projects or programs. - Experience working directly with clients and project stakeholders and presenting risk information, analysis, and recommendations to project and program leadership. - Experience integrating risk management with project cost, schedule, forecasting, and other project controls functions. - Experience with qualitative and quantitative risk analysis and familiarity with risk modeling methodologies. - Experience using Power BI and risk management or project controls software such as @RISK, Primavera Risk Analysis, Safran, Deltek Acumen, or similar software. - Strong analytical, organizational, communication, and leadership skills, with the ability to manage multiple assignments and work effectively with technical and nontechnical stakeholders. These are requirements/qualifications/skills. We could split: Requirements (education, experience), Qualifications (certifications), Skills (analytical etc). But we have also "Preferred Qualifications" list. Let's decide: - Requirements: education + core experience (maybe first 6 bullets). - Qualifications: Preferred Qualifications (certifications, etc). - Skills: maybe the strong analytical etc bullet (or we could include under Requirements). But we need to avoid duplication. Better: Use Requirements for education and experience bullets. Use Qualifications for preferred qualifications (certifications, etc). Use Skills for the strong analytical etc bullet (maybe also include software experience? but that is already in experience). However the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one? But they ask to use those headings if content exists. We have content for Requirements (education/experience). We have content for Qualifications (preferred certifications). We have content for Skills (analytical, organizational, communication, leadership). We have Benefits (listed). We have Pay (Pay Range: $60-$90/PH). We have Schedule? Not mentioned. So we omit Schedule. Also we have "What We Offer" section describing benefits. We'll put under Benefits. We also have "Why RK&K?" and other fluff; we should remove boilerplate like "Design your career at RK&K, Apply Today!" etc. Also remove "Other Duties" boilerplate. Also remove "Pay Range: $60-$90/PH" we keep as Pay. Now we need to ensure we don't include filler like "commensurate with experience" in Benefits? Actually benefits list includes "attractive compensation packages commensurate with experience". That's a phrase we should keep? The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". That's about headings with filler text. If we include a Benefits section, we must not have just filler text; we have actual list of benefits. The phrase "commensurate with experience" appears inside the benefits description; it's not a heading, it's part of prose. That's okay. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the benefits list exactly as given: Paid time off, Matching 401(k) plan, Student Loan Retirement Match Program, Paid Holidays, Tuition reimbursement, Health, dental, vision, life, and disability insurances, Paid parental leave, Wellness programs and employee resource groups, Career Development, Much, much more! Also "attractive compensation packages commensurate with experience". We'll include that as part of the benefits paragraph. Now "What We Offer RK&K offers excellent potential for career advancement and professional growth." That's also part of benefits? Could be under Benefits as well. Now "Why RK&K?" paragraph: we could consider that as part of About the role? But it's more about company culture. Might be considered boilerplate? It's not required to be removed unless it's boilerplate/legal/EEO etc. It's descriptive but could be considered fluff. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This is not exactly those. It's a marketing paragraph. Might be okay to keep? However they said "Prefer a few substantive sections over many thin ones." If we add another section like "About RK&K" we might be adding thin section. But we could incorporate into About the role? The About the role currently is about the position. The "Why RK&K?" is about the firm. Could be considered not essential to the job posting but still substantive. However we might decide to omit it to keep sections minimal. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it if it's substantive. But we need to decide where to place it. Could add a section "About RK&K" but not in the allowed headings list. The allowed headings are limited to those eight. So we cannot add a custom heading. We could put it under About the role as additional paragraph? That might be okay: About the role could include both role description and company info. But the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings, but they gave examples. It 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 stick to those. Thus we can incorporate the "Why RK&K?" paragraph into About the role as extra sentences. Now "Other Duties" boilerplate: remove. Now "Pay Range: $60-$90/PH" -> we need a Pay section. Now we need to ensure we don't include any duplicated lines. Now produce HTML. Structure:

  About the role

  ... (combined intro + Why RK&K? maybe)

  Responsibilities

  ...

  Requirements

  ... (education and experience bullets)

  Qualifications

  ... (Preferred Qualifications)

  Skills

  Strong analytical, organizational, communication, and leadership skills, with the ability to manage multiple assignments and work effectively with technical and nontechnical stakeholders.

  Benefits

  RK&K offers excellent potential for career advancement and professional growth. We also offer attractive compensation packages commensurate with experience and a comprehensive benefits package including: Paid time off Matching 401(k) plan Student Loan Retirement Match Program Paid Holidays Tuition reimbursement Health, dental, vision, life, and disability insurances Paid parental leave Wellness programs and employee resource groups Career Development Much, much more!

  But we need to format benefits as list? The instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. Benefits is a list, so we should use

    • . However the benefits list includes many items separated by commas and line breaks. We'll make each item a
    • . Also include the sentence about attractive compensation packages etc as part of prose maybe preceding list. Thus:

      Benefits

      RK&K offers excellent potential for career advancement and professional growth. We also offer attractive compensation packages commensurate with experience and a comprehensive benefits package including:

      • Paid time off
      • Matching 401(k) plan
      • Student Loan Retirement Match Program
      • Paid Holidays
      • Tuition reimbursement
      • Health, dental, vision, life, and disability insurances
      • Paid parental leave
      • Wellness programs and employee resource groups
      • Career Development
      • Much, much more!
      Now Pay section:

      Pay

      Pay Range: $60-$90/PH

      Now Schedule: omitted. Now ensure no extra whitespace issues. Now produce final HTML fragment. Check for any boilerplate left: We removed "Other Duties", "What We Offer RK&K offers excellent potential..." we kept that as part of benefits. We removed "Why RK&K?" paragraph? We didn't include it. Did we lose substantive info? It's about company culture and impact. Might be considered substantive but not covered by allowed headings. Could we incorporate into About the role? Let's add a sentence after the initial description: "