Associate Director / Director, Advisory

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Company description: "Work with Us. Change the World..." That's likely "About the company" but not requested. We can include maybe "About AECOM" but not required. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include sections that exist: About the role (maybe from Job Description?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to preserve all substantive info, not invent. Let's extract: - About the role: The job description includes description of role: "As a Director or Associate Director in AECOM Advisory’s US West Region, your day-to-day role will include driving business development, overseeing engagement delivery and supporting practice development." Also earlier: "We are seeking talented management consultants to join AECOM Advisory who are mission-driven for the role of our clients in supporting economic, environmental and social vibrancy." Might be considered about the role. - Responsibilities: The bullet list after "These tasks will include, but not be limited to:" includes many items. We need to format as

• . - Requirements: Possibly "Required competencies include:" list. Also "Domain expertise in at least two of the following areas:" list. Also "Strong interpersonal skills..." etc. Might be considered requirements. - Qualifications: The "Minimum Required:" and "Preferred:" sections. - Skills: Could be part of required competencies? Might be separate but we can combine. - Benefits: The "About AECOM" paragraph about benefits: "AECOM is proud to offer comprehensive benefits..." includes list of benefits. Also later "What makes AECOM a great place to work" includes benefits but we can include benefits section. - Pay: The compensation range: "$155000 to $190000". Also "Offered rate of compensation will be based on individual education, qualifications, experience, and work location." So we have pay. - Schedule: Not mentioned. No schedule info. So we should not create Schedule section. We must not include boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "ReqID: J10159627 Business Line: Advisory Business Group: DCS Strategic Business Unit: West Career Area: Consulting Services Work Location Model: Hybrid Compensation: USD 155000 - USD 190000 - yearly". That's metadata; we can fold minor metadata into a short

  or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could include a short paragraph with location model hybrid and maybe req ID? Probably drop it. We must not repeat the job title as a heading. The job title is "Director or Associate Director". Not to be used as heading. We need to output only HTML fragment, no /, no markdown fences. Let's craft sections:

  About the role

  As a Director or Associate Director in AECOM Advisory’s US West Region, your day-to-day role will include driving business development, overseeing engagement delivery and supporting practice development. You will join a fast‑paced, supportive team of diverse consulting professionals, contributing to mission‑driven work that supports clients’ economic, environmental and social vibrancy.

  But need to preserve all substantive info; we can combine the earlier description about seeking talented management consultants etc. Let's include that. Better: "AECOM Advisory is seeking a dynamic Director or Associate Director to expand our growing global Advisory business line. We are seeking talented management consultants to join AECOM Advisory who are mission‑driven for the role of our clients in supporting economic, environmental and social vibrancy." Then the role description. We'll include that.

  Responsibilities

  • Being present in industry conversations and professional networks to identify and originate business development opportunities.
  • Leveraging industry expertise and commercial acumen to proactively target, define and shape business development campaigns.
  • Managing all aspects of proposal responses as Capture Manager, including: narrative development, coordinate across multiple teams to develop technical solutions, pricing, team definition, subcontractor engagement, internal risk review, and compliance procedures.
  • Driving (outline, supervise, and provide quality control over) multiple delivery teams comprised of 5‑8 Consultants and Senior Consultants across multiple and inter‑dependent workstreams:
  • Lead client interactions on delivery progress and insight validation and plan interactions including with C‑suite clients and senior management stakeholders.
  • Upwardly and laterally manage the inputs from regional leadership, Directors, Client Account Managers and technical experts to flag key delivery choices, considerations and risks as they relate to technical scope, client satisfaction, and commercial constraints.
  • Design analytical workstreams and share guidance to engagement teams.
  • Provide timely quality assurance and control over scope, assumptions, analyses and insights.
  • Lead in narrative formulation and highly‑polished deliverable production to meet client expectations and firm standards.
  • Responsibility for project financial performance and supporting overall practice area operational performance improvement, thought leadership and IP generation.
  • Proactively coach and mentor junior staff on developing core consulting skills.
  But note nested lists: The spec says use
  • for any list of duties/requirements/benefits. It didn't forbid nested lists, but we could flatten. However the responsibilities list includes sub-items; we could keep them as separate
  • with indentation via text. Simpler: flatten all items as separate
  • . Let's list each bullet as separate
  • . We'll include the sub-items as separate
  • but maybe prefix with "-". We'll just list them. Thus:
    • Being present in industry conversations and professional networks to identify and originate business development opportunities.
    • Leveraging industry expertise and commercial acumen to proactively target, define and shape business development campaigns.
    • Managing all aspects of proposal responses as Capture Manager, including narrative development, coordinating across multiple teams to develop technical solutions, pricing, team definition, subcontractor engagement, internal risk review, and compliance procedures.
    • Driving (outline, supervise, and provide quality control over) multiple delivery teams comprised of 5‑8 Consultants and Senior Consultants across multiple and inter‑dependent workstreams.
    • Lead client interactions on delivery progress and insight validation and plan interactions including with C‑suite clients and senior management stakeholders.
    • Upwardly and laterally manage the inputs from regional leadership, Directors, Client Account Managers and technical experts to flag key delivery choices, considerations and risks as they relate to technical scope, client satisfaction, and commercial constraints.
    • Design analytical workstreams and share guidance to engagement teams.
    • Provide timely quality assurance and control over scope, assumptions, analyses and insights.
    • Lead in narrative formulation and highly‑polished deliverable production to meet client expectations and firm standards.
    • Responsibility for project financial performance and supporting overall practice area operational performance improvement, thought leadership and IP generation.
    • Proactively coach and mentor junior staff on developing core consulting skills.
    Now Requirements: Could be "Required competencies include:" list. Also "Domain expertise in at least two of the following areas:" list. Also maybe "Strong interpersonal skills..." etc. Let's extract. From text: "Required competencies include: - Strong interpersonal skills, client-service mindset and ability to act as a trusted adviser to clients. - Work in a high-tempo, high-context client-facing environment, with the ability to maintain poise, maturity and work well under pressure. - Able to be self-directed, anticipatory and comfortable working across a highly-matrixed consulting organization. - Solid verbal communication and narrative development skills, with the ability to summarize and convey key insights to C-suite and senior management audiences. - Strong commercial acumen and willingness to have an informed point-of-view, grounded in an interest in enterprise challenges (people, process, technology) and advanced understanding of client industries and their context. - Collegial team-player who can work within a small, motivated team of diverse consulting professionals. - Domain expertise in at least two of the following areas: * Corporate or enterprise strategy, market analysis and target operating model design. * Organizational assessment, business transformation and performance improvement. * Capital projects advisory, including project finance and/or infrastructure investment appraisal, capital improvement planning, asset management, portfolio strategy. * Decarbonization, climate action implementation, resilience strategies and frameworks incl. non-financial valuation methodologies. * Economic development, industrial policy, broadband & digital equity, and market transformation. * Technology-led business transformation. * Corporate finance, valuations, M&A, divestitures, divestments and privatizations." Thus we can treat "Required competencies" as Requirements. Also "Domain expertise..." is part of required competencies. We'll create a

    Requirements

    with
    • for each bullet. For the domain expertise sub-bullets, we can either nest or flatten. We'll flatten: each domain area as separate
    • maybe preceded by "Domain expertise in at least two of the following areas:" as a
    • then sub-items as separate
    • . But that might be odd. Better to keep as separate
    • for each domain area, and include a preceding note that you need expertise in at least two of them. We'll include a
    • stating "Domain expertise in at least two of the following areas:" then list each area as separate
    • . That's acceptable. Now Qualifications: Minimum Required: BA/BS + 10 YORE or demonstrated equivalency of experience and/or education, including 2 years of leadership Typically at least 8 years Management Consulting or equivalent experience Preferred: 12 years of related industry experience MBA, or other Master’s degree in Operational Research, Management, Management Science, Finance, Economics, Systems Engineering and/or related fields. Fluency with Microsoft Office Suite, especially Excel Strong technical skills, including experience with one or more of the following software packages: ArcGIS and other spatial analysis tools Quantitative/statistical programs such as R or Python Evaluation of financial cashflows, particularly public finance, via Excel. We'll create

      Qualifications

      with
      • . We'll separate minimum and preferred maybe as separate
      • but we can combine. List: - BA/BS + 10 years of experience or demonstrated equivalency of experience and/or education, including 2 years of leadership. - Typically at least 8 years of Management Consulting or equivalent experience. - Preferred: 12 years of related industry experience. - Preferred: MBA, or other Master’s degree in Operational Research, Management, Management Science, Finance, Economics, Systems Engineering and/or related fields. - Fluency with Microsoft Office Suite, especially Excel. - Strong technical skills, including experience with one or more of the following software packages: ArcGIS and other spatial analysis tools; quantitative/statistical programs such as R or Python; evaluation of financial cashflows, particularly public finance, via Excel. We could also list the software packages as separate
      • but we can keep within one. Now Skills: Could be derived from required competencies but we already have them in Requirements. Might not need separate Skills section. However we could create a Skills section for technical skills: "Fluency with Microsoft Office Suite, especially Excel; experience with ArcGIS, R/Python; evaluation of financial cashflows via Excel." But that's already in Qualifications. To avoid duplication, we could omit Skills section. The instruction: Prefer a few substantive sections over many thin ones. So we can skip Skills if content overlaps. Benefits: From "About AE