Sr Tech Project Manager

We need to output HTML fragment with sections: About the role? The posting includes Overview, Responsibilities, Qualifications, What Will Make You Stand Out, Physical Requirements, Success Profile, Compensation, Benefits. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. The headings we can use: Overview could map to About the role. Responsibilities is present. Qualifications is present. What Will Make You Stand Out could be Skills? Or maybe we can treat as Skills. Physical Requirements maybe not a standard heading; we could omit or incorporate into Responsibilities? But we must not create sections without content. The allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have: - Overview: description of role. That fits About the role. - Responsibilities: list. - Qualifications: includes Bachelor's degree, experience, etc. That's Requirements/Qualifications. Could combine as Qualifications. - What Will Make You Stand Out: additional preferred qualifications; could be Skills. - Physical Requirements: travel etc. Not a standard heading; maybe we could incorporate into Responsibilities or omit? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't say we must only use those headings; we can use other headings? It says: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should use those headings where appropriate, but we could also use other headings if needed? The examples are given, but not exclusive. Safer to stick to those headings. Physical Requirements could be placed under Responsibilities? Not ideal. Could create a section "Requirements" and include both qualifications and physical requirements? But Requirements heading is for prerequisites. Physical requirements are not qualifications but could be part of Requirements. Might be okay. - Success Profile: maybe not needed. - Compensation: Pay section. - Benefits: Benefits section. - Schedule: Not mentioned; no schedule info. So omit Schedule. Thus we will output sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. Possibly also Requirements? But we have Qualifications covering requirements. Could also have Requirements separate but would duplicate. Better to have Qualifications. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities list, Qualifications list (maybe bullet), Skills list, Benefits list. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings; we can drop them. We must remove boilerplate: location list at top, etc. Also remove "Overview" heading? We'll replace with About the role. We need to keep location info? The location is given in first line: "Location: Providence, RI, US, 02903 FL Statewide, FL, US Statewide, SC, US VA Statewide, VA, US West Greenwich, RI, US, 02817 CT Statewide, CT, US DE Statewide, DE, US MI Statewide, MI, US MA Statewide, MA, US IN Statewide, IN, US OH Statewide, OH, US NY Statewide, NY, US MD Statewide, MD, US PA Statewide, PA, US RI Statewide, RI, US NC Statewide, NC, US GA Statewide, GA, US ME Statewide, ME, US NH Statewide, NH, US DC Statewide, DC, US WV Statewide, WV, US". That's a list of locations where the job is available? It's weird. We need to preserve substantive information; location is substantive. Should we include it? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Location could be considered metadata; we could include a short paragraph at top:

  Location: Providence, RI (hybrid) with availability across multiple states.

  But we need to preserve all substantive information; we could summarize but not invent. However summarizing location list may lose detail. But we could keep the list as a paragraph. It's not a heading, just a paragraph. That's acceptable. We also have Requisition ID: 19703 - we can drop or fold into minor metadata paragraph. We also have "Nearest Major Market: Providence Nearest Secondary Market: Rhode Island" at end; we can include. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's none. Now craft HTML. Structure:

  Location: Providence, RI, US, 02903; FL Statewide, FL, US; Statewide, SC, US; VA Statewide, VA, US; West Greenwich, RI, US, 02817; CT Statewide, CT, US; DE Statewide, DE, US; MI Statewide, MI, US; MA Statewide, MA, US; IN Statewide, IN, US; OH Statewide, OH, US; NY Statewide, NY, US; MD Statewide, MD, US; PA Statewide, PA, US; RI Statewide, RI, US; NC Statewide, NC, US; GA Statewide, GA, US; ME Statewide, ME, US; NH Statewide, NH, US; DC Statewide, DC, US; WV Statewide, WV, US. Requisition ID: 19703.

  Then

  About the role

  with paragraph from Overview. Overview text: "As a Senior Project Manager, SAP S/4HANA Transformation, you will support Brightstar Lottery's global ERP transformation by leading the planning, execution, and delivery of SAP S/4HANA implementation and migration initiatives. You will connect business stakeholders, IT leadership, system integrators, and external partners to deliver strategic outcomes on schedule and within budget. This role will be located hybrid in Providence, Rhode Island." We should keep that. Then

  Responsibilities

  with
  • each responsibility line. Responsibilities lines are separated by periods but we can split at each sentence. List: - Lead end-to-end SAP S/4HANA transformation initiatives across Finance, Procurement, Supply Chain, Manufacturing, and Operations. - Establish comprehensive project plans, schedules, budgets, resource models, success criteria, and governance structures. - Coordinate interconnected workstreams, dependencies, and resources across global business and technical teams. - Oversee process design, system integration, data migration, testing, training, cutover, deployment, and stabilization activities. - Facilitate steering committee meetings, design workshops, status reviews, executive communications, and solution decisions. - Monitor program finances, vendor contracts, milestones, risks, issues, scope, and overall program health. - Drive organizational readiness, stakeholder alignment, business adoption, and transition to ongoing support operations. - Perform other duties as assigned. Make each
  • . Then

    Qualifications

    with bullet list. Qualifications text: "What You'll Bring Bachelor's degree in Business, Information Technology, Engineering, Supply Chain, Finance, or a related field. Minimum of 10 years of project or program management experience, including at least five years managing SAP ERP initiatives. Demonstrated success leading at least one full lifecycle SAP S/4HANA implementation, upgrade, or migration. Expertise in enterprise project management methodologies, ERP business processes, and cross-functional integrations. Fluency in written and spoken Italian, including facilitating meetings, workshops, training, and presentations. Proven leadership of large, geographically dispersed teams, system integrators, consulting partners, and offshore resources. Strong executive communication, negotiation, facilitation, decision-making, risk management, and issue-resolution skills. Ability to read, write, and communicate effectively in English is required" We can bullet each sentence. Then

    Skills

    for "What Will Make You Stand Out" content. List: - Master's degree in a relevant discipline. - Certification in PMP, SAP Activate, Agile, Scrum, or a comparable methodology. - Background leading SAP ECC to SAP S/4HANA transformation programs. - Familiarity with SAP Ariba, SAP Business Technology Platform, SAP Analytics Cloud, and related SAP solutions. - Exposure to multinational manufacturing, distribution, pharmaceutical, life sciences, or consumer products organizations. - Success managing global business transformation and process harmonization initiatives. Make bullet list. Then

    Benefits

    with bullet list from benefits paragraph. Benefits text: "In addition, we offer employees a 401(k) Savings Plan with Company contributions, health, dental, and vision insurance, life, accident, and disability insurance, tuition reimbursement, paid time off, wellness programs, and identity theft insurance. Note: programs are subject to eligibility requirements." Also mention Base pay etc? That's Pay section. Also mention "Sales roles may be eligible for commission payments, while other roles are eligible for discretionary bonuses." That's part of compensation/benefits? Could be under Pay. We'll handle Pay separately. Thus Benefits bullet list: - 401(k) Savings Plan with Company contributions - Health insurance - Dental insurance - Vision insurance - Life insurance - Accident insurance - Disability insurance - Tuition reimbursement - Paid time off - Wellness programs - Identity theft insurance Note about eligibility could be a sentence after list maybe as

    Note: programs are subject to eligibility requirements.

    Then

    Pay

    with paragraph about compensation. Pay text: "At Brightstar, we consider a wide range of factors in determining compensation, including background, skills, experience, and work location. These factors can cause your compensation to vary. The estimated starting compensation range is $74,961 - $164,800. The actual pay offered may end up being higher or lower. The Company will comply with all local pay requirements and collective bargaining agreements, where applicable. Base pay is only one part of our Total Rewards program. Sales roles may be eligible for commission payments, while other roles are eligible for discretionary bonuses." We can keep as paragraph(s). Could also bullet but not needed. We should not include Schedule section as no info. We should not include Requirements separate. We should not include Success Profile. We should not include Physical Requirements; maybe we could incorporate into Responsibilities? But it's separate. Could we add a section "Requirements" and put physical requirements there? But Requirements heading is for prerequisites; physical requirements could be considered a requirement. However we already have Qualifications covering prerequisites; we could add another bullet under Qualifications about travel etc. But the instruction: Use
    • for any list of duties/requirements/benefits. So we could add travel etc under Qualifications as a bullet. That would preserve info. Thus we add a bullet under Qualifications: "Willingness to travel domestically and internationally up to 30–50% based on business needs; participate in global workshops, testing events, deployments, governance meetings, and stakeholder sessions; flexibility to collaborate across multiple time zones and support international project teams." That captures Physical Requirements. Now we need to ensure we didn't miss any substantive info: Overview, Responsibilities, Qualifications, What Will Make You Stand Out, Benefits, Pay, Location, Requisition ID, Nearest Major Market/Secondary Market. We included location paragraph with requisition ID. We could also add Nearest Major Market: Providence; Nearest Secondary Market: Rhode Island as a sentence. Add to location paragraph: "Nearest Major Market: Providence; Nearest Secondary Market: Rhode Island." Now ensure we didn't repeat job title as heading. We didn't. Check for any boilerplate: "