Operations Project Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us", "Summary", "Essential Duties & Responsibilities", "Education & Experience", "What We Offer", "Diversity Commitment". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to map content to appropriate headings. The posting does not have explicit "About the role" but we have "About Us" and "Summary". Could combine as "About the role" maybe using Summary. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create headings that match those generic names only if we have content. We must include a section ONLY when posting has real, specific content for it. So we need to decide which sections we have content for. We have: - About the role: could be Summary (description of role). So we can put Summary under

About the role

. - Responsibilities: Essential Duties & Responsibilities. - Requirements: Education & Experience (maybe also qualifications). Could be Requirements. - Qualifications: maybe also Education & Experience; but we can combine. - Skills: maybe from Education & Experience includes skills; but we could separate. - Benefits: What We Offer. - Pay: not provided, so omit. - Schedule: The posting mentions hybrid schedule: "It Is Eligible To Work a Hybrid Schedule, Generally Requiring Work In-office And/or Show-site 2-3 Days Per Week." Also location preferences. So we have schedule info. So we can create

Schedule

with that content. We must not include headings with filler like "commensurate with experience". We have actual schedule info. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from each section. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes a Diversity Commitment paragraph (EEO). That is boilerplate; we should remove it. Also "#TFCFreeman" maybe a tag; remove. We need to keep the rest. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

... summary text ...

Responsibilities

• ... each duty ...

Requirements

... education & experience ...

Maybe also

Skills

if we want to separate skills from requirements. But we can keep all under Requirements. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So we could combine Education & Experience and Skills into one Requirements section. But we also have Benefits separate. Schedule separate. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. We must not include Pay. Now we need to extract content. Let's copy the relevant parts. About Us and Summary: "About Us Freeman is a global leader in events, on a mission to redefine live for a new era. With a data-driven approach and the industry’ largest network of experts, Freeman’s insights shape exhibitions, exhibits, and events that drive audiences to action. The integrated full-service solutions leverage a 99-year legacy in event management as well as new technologies to deliver moments that matter. Summary The Operations Project Manager is a critical execution role within Operations Enablement, responsible for independently driving day-to-day delivery across a fast‑paced, high‑stakes operational transformation program. This role applies advanced project management and execution knowledge to keep complex initiatives moving forward, ensuring alignment across teams, clarity on ownership, and disciplined follow‑through on commitments. This position is ideal for an experienced project manager who thrives in ambiguity, brings structure to complexity, and exercises sound judgment to balance speed, risk, and quality. The Operations Project Manager operates with minimal day‑to‑day guidance, leads assigned projects or workstreams end‑to‑end, and serves as a trusted execution resource for cross‑functional teams and less‑experienced colleagues. This Position Will Support Our Operations Enablement Team. It Is Eligible To Work a Hybrid Schedule, Generally Requiring Work In-office And/or Show-site 2-3 Days Per Week. The Ideal Candidate Will Be Located In Dallas, TX; However, We Are Also Open To Candidates Based Out Of Atlanta, GALas Vegas, NVNashville, TNNew Orleans, LAOrlando, FLSan Antonio, TX" We need to separate schedule info maybe later. But for About the role we can include the Summary paragraph (maybe also About Us?). The About Us is company description; could be part of About the role? Might be okay. But we should preserve all substantive information. So we could include About Us as part of About the role section. Thus About the role content: combine About Us and Summary (excluding schedule line maybe). But schedule line is part of Summary; we might extract schedule to Schedule section. Thus we need to parse: The sentence "This Position Will Support Our Operations Enablement Team. It Is Eligible To Work a Hybrid Schedule, Generally Requiring Work In-office And/or Show-site 2-3 Days Per Week. The Ideal Candidate Will Be Located In Dallas, TX; However, We Are Also Open To Candidates Based Out Of Atlanta, GALas Vegas, NVNashville, TNNew Orleans, LAOrlando, FLSan Antonio, TX" We'll move schedule info to Schedule section, and location info maybe also schedule? Could be part of Schedule or maybe we keep location in About the role? The location is not schedule but could be part of Requirements? Usually location is separate but we don't have a heading for location. Could include in About the role or Requirements. Since we have no specific heading for location, we could include location info in About the role or Requirements. Probably better to include in About the role as part of role description. Thus we will keep location info in About the role. Now Responsibilities: The bullet list under "Essential Duties & Responsibilities". We need to convert each sentence into

. The paragraph includes multiple sentences each starting with a bolded phrase? Actually the text: "Program Execution & Day‑to‑Day Coordination Leads the end‑to‑end execution of multiple concurrent projects or workstreams within a large‑scale operational transformation effort, maintaining forward momentum across all areas of responsibility.Owns and maintains a comprehensive, integrated master project plan, tracking milestones, task ownership, dependencies, risks, and delivery timelines across workstreams.Operates independently within established governance, guidelines, and priorities, making day‑to‑day execution decisions and escalating issues appropriately when impacts or risks exceed defined thresholds.Runs rigorous action item, issue, and decision logs—capturing commitments, monitoring progress, and holding owners accountable to agreed timelines.Proactively identifies gaps, delivery risks, and misalignment across teams; applies judgment and practical problem‑solving to resolve issues before they escalate.Coordinates across operations, functional teams, and external partners to ensure handoffs are clear, responsibilities are understood, and work does not stall between groups.Maintains delivery pace in a high‑velocity environment by setting clear expectations, reinforcing priorities, and adjusting plans as conditions change." Then "Tracking, Reporting & Transparency Produces clear, accurate, and timely status reporting on a regular cadence, translating complex project activity into decision‑ready insights for working teams and leadership.Analyzes delivery progress, risks, and dependencies using multiple inputs to assess program health and recommend corrective actions when needed.Builds and manages dashboards and tracking tools that provide leadership with visibility into milestones, risks, and execution performance.Prepares structured, concise materials for leadership reviews, steering committee discussions, and stakeholder updates—highlighting impacts, tradeoffs, and required decisions.Maintains complete, up‑to‑date program documentation as a single source of truth, ensuring accessibility, accuracy, and consistency across stakeholders." Then "Stakeholder Engagement & Influence Serves as a primary point of coordination for assigned projects or workstreams, working across functions and levels to maintain alignment on priorities, progress, and next steps.Facilitates working sessions, standups, and cross‑functional meetings with a clear agenda and a bias toward resolution—ensuring discussions lead to decisions, owners, and timelines.Communicates complex or sensitive information clearly and constructively, helping stakeholders understand implications, risks, and recommended paths forward.Works to build alignment and consensus among teams with competing priorities, exercising influence without authority to drive progress.Builds trust through consistent follow‑through, transparent communication, and reliable delivery against commitments." We need to split each of these into separate list items. Could group by the headings (Program Execution..., Tracking..., Stakeholder...). But we can just make each sentence a list item. However some sentences are long and contain multiple clauses separated by periods but not separate sentences? Actually they are separated by periods. We'll split at periods. Let's extract each sentence: Program Execution & Day‑to‑Day Coordination - Leads the end‑to‑end execution of multiple concurrent projects or workstreams within a large‑scale operational transformation effort, maintaining forward momentum across all areas of responsibility. - Owns and maintains a comprehensive, integrated master project plan, tracking milestones, task ownership, dependencies, risks, and delivery timelines across workstreams. - Operates independently within established governance, guidelines, and priorities, making day‑to‑day execution decisions and escalating issues appropriately when impacts or risks exceed defined thresholds. - Runs rigorous action item, issue, and decision logs—capturing commitments, monitoring progress, and holding owners accountable to agreed timelines. - Proactively identifies gaps, delivery risks, and misalignment across teams; applies judgment and practical problem‑solving to resolve issues before they escalate. - Coordinates across operations, functional teams, and external partners to ensure handoffs are clear, responsibilities are understood, and work does not stall between groups. - Maintains delivery pace in a high‑velocity environment by setting clear expectations, reinforcing priorities, and adjusting plans as conditions change. Tracking, Reporting & Transparency - Produces clear, accurate, and timely status reporting on a regular cadence, translating complex project activity into decision‑ready insights for working teams and leadership. - Analyzes delivery progress, risks, and dependencies using multiple inputs to assess program health and recommend corrective actions when needed. - Builds and manages dashboards and tracking tools that provide leadership with visibility into milestones, risks, and execution performance. - Prepares structured, concise materials for leadership reviews, steering committee discussions, and stakeholder updates—highlighting impacts, tradeoffs, and required decisions. - Maintains complete, up‑to‑date program documentation as a single source of truth, ensuring accessibility, accuracy, and consistency across stakeholders. Stakeholder Engagement & Influence - Serves as a primary point of coordination for assigned projects or workstreams, working across functions and levels to maintain alignment on priorities, progress, and next steps. - Facilitates working sessions, standups, and cross‑functional meetings with a clear agenda and a bias toward resolution—ensuring discussions lead to decisions, owners, and timelines. - Communicates complex or sensitive information clearly and constructively, helping stakeholders understand implications, risks, and recommended paths forward. - Works to build alignment and consensus among teams with competing priorities, exercising influence without authority to drive progress. - Builds trust through consistent follow‑through, transparent communication, and reliable delivery against commitments. Now Requirements: Education & Experience section. Text: "Education & Experience 5–8 years of project management experience, with demonstrated success leading complex initiatives or multiple concurrent workstreams in operational, transformation, or high‑stakes environments.Proven track record of maintaining delivery discipline—managing action items, reporting cadences, risks, and cross‑functional accountability.Experience supporting large‑scale operational or technology‑enabled programs; familiarity with enterprise platforms such as SAP, Salesforce, or Microsoft Dynamics preferred.PMP or equivalent project management