AI Project Manager (Hybrid - NYC)

We need to output HTML fragment with sections: About the role? The posting includes description about customer, role summary, responsibilities, qualifications, benefits. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. We have: - About the role: could be the description of the customer and role summary? The posting includes "With roots dating back..." describing customer, then "We are seeking an AI Project Manager on a contract basis..." then "Role Summary". So we can put an About the role section containing that description (customer background, role summary). Or we could split: maybe "About the role" includes role summary and customer context. We'll include. - Responsibilities: list of key responsibilities (bulleted). Use

• . - Requirements / Qualifications: The posting has "Required Qualifications And Experience". That's a list of qualifications. Use
  • . - Benefits: The posting mentions "We offer a competitive salary range..." then "Contractor benefits are available through our 3rd Party Employer of Record..." then list: Medical, Dental, Vision, 401k. Also mention salary range but not specific numbers; we should not create Pay section unless posting actually states them. It says "competitive salary range" but no numbers, so we should not create Pay section because it's not specific. Similarly Schedule: mentions hybrid - 3 days/week required on-site in New York City (Midtown). That's schedule info. So we can include a Schedule section with that detail. - Skills: Not explicitly listed; maybe we could infer but we should not create unless posting states. So skip. - Pay: skip. We need to preserve all substantive information; do not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none present). Remove boilerplate: EEO statement, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes an EEO statement at end; we should remove that. Also "An Equal Opportunity Employer..." etc. Remove. Also remove "Contractor benefits are available through our 3rd Party Employer of Record (Available upon completion of waiting period for eligible engagements)" - that's part of benefits; we keep benefits list but maybe we can keep that sentence as part of benefits description? The instruction: Use

    for prose. So we can have a

    describing benefits eligibility then a

    for list. We need to preserve all substantive information: The benefits include Medical, Dental, Vision, 401k. Also mention that contractor benefits are available via 3rd Party Employer of Record upon completion of waiting period. Keep that. Also mention "We offer a competitive salary range for this position. Most candidates who join our team are hired at the median of this range, ensuring fair and equitable compensation based on experience and qualifications." This is about pay but not specific numbers; we should not create Pay section because no specific numbers. However we could include this info in a

    under About the role or maybe under a generic "Compensation" but we shouldn't create Pay heading. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says we can create Benefits section because posting states benefits. For Pay, we should not create a Pay section because no specific numbers. However we could still include the salary range statement in a

    somewhere else (maybe in About the role). But we must not create a Pay heading. So we can embed that sentence in a paragraph within About the role or maybe a separate section like "Compensation" but that would be a heading not allowed? The instruction only mentions Pay, Schedule, Benefits sections. It doesn't forbid other headings like "Compensation". But the list of allowed headings includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't forbid other headings, but to be safe we stick to those. So we can put the salary statement in About the role paragraph. Schedule: we have hybrid - 3 days/week required on-site in New York City (Midtown). That's specific, so we create a Schedule section with that detail. Now we need to output only HTML fragment, no /, no markdown fences. Structure:

    About the role

    With roots dating back to the 1800s, our Customer is a global professional services firm HQ’d in New York City with businesses in insurance brokerage, risk management, reinsurance services, talent management, investment advisory, and management consulting. Today, they are a unique group of businesses with many enduring competitive advantages. Among them are the quality of their colleagues, deep client relationships, vast global footprint, depth of intellectual capital, and cohesive and collaborative culture. We are seeking an AI Project Manager on a contract basis to support our Customer’s business needs. This role is hybrid - 3 days/week required on-site in New York City (Midtown). Role Summary We are seeking an experienced AI Project Manager to lead the planning, coordination, and delivery of a portfolio of AI- enabled initiatives across Marketing Communications. This role will translate business priorities into executable delivery plans, align marketing owners with AI Development teams primarily based in Ireland, and ensure that initiatives move from idea and scoping through build, pilot, adoption, and measurable business value.

    But note we already mentioned schedule in About the role; maybe better to separate schedule into its own section. The schedule sentence appears twice: we have "This role is hybrid - 3 days/week required on-site in New York City (Midtown)." We could keep that in About the role or move to Schedule section. To avoid duplication, we could keep schedule detail only in Schedule section and not repeat in About the role. However we need to preserve all substantive information; we can keep it in Schedule section and remove from About the role. But the About the role paragraph currently includes that sentence; we could rephrase to omit schedule detail. Let's craft About the role without schedule. Thus:

    About the role

    With roots dating back to the 1800s, our Customer is a global professional services firm HQ’d in New York City with businesses in insurance brokerage, risk management, reinsurance services, talent management, investment advisory, and management consulting. Today, they are a unique group of businesses with many enduring competitive advantages. Among them are the quality of their colleagues, deep client relationships, vast global footprint, depth of intellectual capital, and cohesive and collaborative culture. We are seeking an AI Project Manager on a contract basis to support our Customer’s business needs. Role Summary We are seeking an experienced AI Project Manager to lead the planning, coordination, and delivery of a portfolio of AI- enabled initiatives across Marketing Communications. This role will translate business priorities into executable delivery plans, align marketing owners with AI Development teams primarily based in Ireland, and ensure that initiatives move from idea and scoping through build, pilot, adoption, and measurable business value.

    Then schedule section:

    Schedule

    Hybrid - 3 days/week required on-site in New York City (Midtown).

    Now Responsibilities:

    Responsibilities

    • Develop, communicate, and maintain integrated project and portfolio plans, including scope, milestones, dependencies, resourcing, decision points, and delivery risks.
    • Coordinate cross-functional teams across business, architecture, engineering, data, testing, security, vendors, and offshore / distributed delivery resources throughout the project lifecycle.
    • Establish clear accountability for each initiative, confirm responsibilities, track commitments, and hold team members and partners accountable for agreed deliverables.
    • Partner with Marketing Owners to clarify the business problem, define requirements, establish acceptance criteria, secure sign-off, and maintain alignment to expected outcomes and KPIs.
    • Manage critical dependencies, especially data quality and readiness, platform integration, workflow simplification, architecture, and availability of subject-matter experts.
    • Drive responsible AI delivery by ensuring human-in-the-loop checkpoints and incorporating brand, legal, compliance, privacy, security, and governance requirements into workflows before deployment.
    • Oversee pilots, proofs of concept, testing, release readiness, implementation, and transition to sustainable operating support; ensure build and system documentation is complete.
    • Lead adoption and change-management activities, including communications, training, champion engagement, feedback loops, and measurement of user adoption and business impact.
    • Monitor progress through regular status meetings and insightful reporting; communicate status, decisions, risks, issues, and required escalations to sponsors and stakeholders.
    • Facilitate gateway reviews for business-critical initiatives and make sure decisions, assumptions, actions, and approvals are documented and traceable.
    Now Qualifications/Requirements: We have "Required Qualifications And Experience". We'll use

    Qualifications

    (or Requirements). The instruction list includes Requirements and Qualifications as separate possible headings. We could combine but better to have Qualifications. We'll put all bullet points.

    Qualifications

    • Significant experience leading complex, cross-functional technology, data, digital, automation, or AI-enabled initiatives from definition through implementation.
    • Demonstrated ability to manage multiple concurrent workstreams with competing priorities, changing requirements, and distributed teams.
    • Strong project planning, dependency management, risk and issue management, status reporting, meeting facilitation, and executive communication skills.
    • Experience working with business owners, technical delivery teams, architecture, data teams, vendors, and subject-matter experts.
    • Practical understanding of AI delivery concepts, including data quality, integrations, experimentation, model or solution validation, privacy, security, and responsible AI governance.
    • Experience defining KPIs, acceptance criteria, benefits measures, and adoption plans for new products, platforms, or operating processes.
    • Ability to work independently with limited supervision, exercise sound judgment, and create structure in ambiguous environments.
    • Comfort working across Ireland and U.S. time zones, with the flexibility to maintain regular collaboration windows with both teams.
    • (Preferred) PMP, PRINCE2, Agile, Scrum, SAFe, or comparable project / product delivery certification.
    Now Benefits: We have benefits list plus note about contractor benefits via 3rd Party Employer of Record. We'll do:

    Benefits

    Contractor benefits are available through our 3rd Party Employer of Record (available upon completion of waiting period for eligible engagements).

    • Medical
    • Dental
    • Vision
    • 401k
    We should also include the competitive salary range statement somewhere. Since we cannot create Pay heading, we could put it in About the role paragraph after role summary. Let's add a sentence: "We offer a competitive salary range for this position; most candidates are hired at the median of this range, ensuring fair and equitable compensation based on experience and qualifications." Add to About the role paragraph. Thus final About the role paragraph:

    With roots dating back to the 1800s, our Customer is a global professional services firm HQ’d in New York City with businesses in insurance brokerage, risk management, reinsurance services, talent management, investment advisory, and management consulting. Today, they are a unique group of businesses with many enduring competitive advantages. Among them are the quality of their colleagues, deep client relationships, vast global footprint, depth of intellectual capital, and cohesive and collaborative culture. We are seeking an AI Project Manager on a contract basis to support our Customer’s business needs. Role Summary We are seeking an experienced AI Project Manager to