Senior Project Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes a "General Summary Of Position" which could be About the role. Then "Duties And Responsibilities" -> Responsibilities. Then "Required Qualifications" -> Requirements/Qualifications? The spec says we can have sections like Requirements, Qualifications, Skills. We need to decide mapping. The posting includes "Required Qualifications" and "Preferred Qualifications". Those could go under Qualifications (maybe separate Required and Preferred). Also there are many skill-like items (MS Office, etc.) could go under Skills. But we must not create thin sections. We need to preserve all substantive info. We can combine. We should not repeat job title. No Job ID. Remove boilerplate. We need to output only HTML fragment. Let's extract content: General Summary Of Position: paragraphs describing role. We'll put that under

About the role

with

containing the summary. Duties And Responsibilities: list of duties. We'll put under

Responsibilities

with

• each duty. Required Qualifications: list of qualifications. Could be under

  Required Qualifications

  but spec says we can use Requirements or Qualifications. Since we have both Required and Preferred, maybe we combine into Qualifications section with subheadings? But we cannot add extra headings beyond

  . Could have

  Qualifications

  and then separate

  for Required and Preferred? But spec says use

  for section headings only. We could have two sections:

  Required Qualifications

  and

  Preferred Qualifications

  . Those are allowed as they match the pattern? The list includes Qualifications as a possible heading. It didn't forbid using "Required Qualifications" as heading; but they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That list is examples, not exhaustive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those exact headings. Safer to stick to those. So we need to map content to those headings. We have: About the role (summary). Responsibilities (duties). Requirements (maybe required qualifications). Qualifications (maybe preferred qualifications). Skills (technical skills). Benefits, Pay, Schedule only if present. The posting does not mention Benefits, Pay, Schedule explicitly. It mentions "M-F 8-5 availability, but on call responsibilities will be needed as well" which is schedule info. That could go under Schedule. Also "Able and willing to travel up to 5%" maybe under Benefits? Not exactly. There's no explicit benefits like health insurance. So we may include Schedule section with that info. Benefits and Pay not present, so omit. Now we need to extract details for each. Let's parse the text. General Summary Of Position: "Achieve effective and efficient project management across multiple industries. Perform day-to- day project management work activities using PMI standards, processes, methodologies and Granite systems. Utilize structured and disciplined practices to ensure project management activities are consistent with company initiatives and expectations and achieve high quality, professional service delivery. Achieve financial targets inclusive of project budget, gross profit, and related financial metrics within area of responsibility. Ensure project management activities meet corporate customer satisfaction objectives as well as internal and external SLAs. Work collaboratively across all levels and departments of the organization and ensure a seamless transition of work activities to execute operations functions." We'll keep as paragraph. Duties And Responsibilities: a long list. We'll break into bullet points. Let's list them: - Execute projects per PMO standards, processes, and methodologies in a consistent manner for project planning and execution activities including the following: - Project planning fundamentals: initiating, planning, estimating, resourcing, scheduling and budgeting - Project control fundamentals: monitoring, anticipating potential problems, identifying project conflicts, taking corrective action, resolving issues, managing scope, schedule, cost, profit and budget, project reporting, quality review and assurance. - Relationship management fundamentals: client relationship management; project team management; and overall change management - Prepare Project Roadmap with concurrence of all participating organizations and negotiate agreement with the customer, including identification of work and organizational breakdown structures, requirements creation and management, cost and material estimates, milestone payment schedule, risk and communication management plans. - Establish milestones and monitor adherence to master plans and schedules, identify program problems and obtain solutions, such as allocation of resources or changing contractual specifications - Direct the work of employees assigned to the project from technical, professional, or administrative areas. - Manage the delivery and execution of projects deploying on a National to International scale through a balance of best-in-class and pragmatic project methodologies and practices that achieve KPIs and meet or exceed business results, client satisfaction and SLAs. - Act as primary customer contact for project activities, leading project review sessions with clients working within multiple time zones - to discuss cost, schedule, and technical performance. Conduct recurring customer reviews addressing costs, schedules, risks and customer considerations. - Develop new business or expand the product line with the client as applicable. Manage customer enhancement programs including all bid and schedule estimates and management approval activities. - Issue and communicate program status to leadership, steering committee and other stakeholders as appropriate. - Manage project issues/risks in a timely manner, escalating when necessary. - Foster collaborative working relationships within operations and across all levels and departments of the organization to execute project management activities and company priorities. - Promote continuous growth of project management practices within the PMO and organization to achieve client and organizational objectives. - Achieve performance targets established by leadership for applicable Key Performance Indicators. - Perform other duties as assigned by management. We need to preserve all substantive info; we can keep bullet points as

  . For nested bullet points we could just flatten? But we can keep sub-bullets as separate

  with indentation? HTML doesn't support nested

  inside
  • but we can. It's allowed. We'll keep structure. Required Qualifications: "5-10 years’ experience managing telecommunications and infrastructure projects Relevant industry certifications preferred, but job experience will be considered Understanding of structured cabling systems consisting of cat 5e, cat 6, and fiber optic cable. Understanding of Telephony Projects including POTS, VOIP, and SDWAN Ability to manage multiple (15 or more) projects simultaneously within the estimated budget. Ability to manage projects in locations across USA and Canada. Fluent in MS Office (Word, Excel, PowerPoint, Outlook) , SharePoint, MS Project, PPM tools, ERP, S AD, VISIO, Adobe Acrobat Proficient M-F 8-5 availability, but on call responsibilities will be needed as well Experience working with client and internal teams on a national scale Experience deploying projects across a multisite footprint Excellent service philosophy and understanding the challenges in providing superior customer experience at a national level while controlling costs. Superior collaboration and communication skills: team building, conflict resolution, stakeholder management, risk management, product management, negotiation & decision making. Ability to work effectively across many internal functional groups to optimize product offerings, create a seamless internal and external customer experience and resolve issues. Proven ability to continuously expand and leverage knowledge of market and industry trends and translating to recommending and implementing process and efficiency improvements. End-to-end process thinker, with proven experience in leading change within an organization and understands how change affects employees and utilizes strategies to reduce risk to the organization. Strong experience handling employee issues and making sound judgment decisions in this area. Proficient in MS Office (Word, Excel, PowerPoint), Outlook, SharePoint, MS Project, PPM tools, ERP, Salesforce.com, workforce management and cloud based technology systems. Able and willing to travel up to 5%." Note there is duplication of MS Office etc. We'll keep as is. Preferred Qualifications: "4 year college degree and/or Military experience 5-10 years plus of technology services industry experience. PMP, Six Sigma, Agile preferred, but previous job experience will be taken into account Telephony experience VOIP experience SDWAN experience POTS experience PBX experience WIFI experience Network Infrastructure experience" Now we need to map to sections. We could have:

    About the role

    ...

    Responsibilities

    ...

    Requirements

    ...
    (for Required Qualifications)

    Qualifications

    ...
    (for Preferred Qualifications)

    Skills

    maybe we could extract technical skills from Required Qualifications (MS Office, etc.) but that would duplicate. Better to put those under Skills. But then we would split Required Qualifications into two sections: Requirements (experience, certifications) and Skills (technical). However the spec says prefer few substantive sections over many thin ones. Could combine all Required Qualifications into Requirements section, and Preferred Qualifications into Qualifications section. Skills maybe not needed separately. But we have many skill items; they'd be inside Requirements anyway. That's okay. Schedule: we have "M-F 8-5 availability, but on call responsibilities will be needed as well" and "Able and willing to travel up to 5%". Travel could be under Benefits? Not exactly. Schedule section could include availability and travel. We'll create

    Schedule

    with

    containing that info. Benefits and Pay not present, omit. Now we need to ensure we don't include boilerplate like "Perform other duties as assigned by management." That's substantive, keep. Now produce HTML. We must not include markdown fences. Just raw HTML. Let's craft. We'll need to escape any special characters like & etc. Not many. We'll produce:

    About the role

    Achieve effective and efficient project management across multiple industries. Perform day-to-day project management work activities using PMI standards, processes, methodologies and Granite systems. Utilize structured and disciplined practices to ensure project management activities are consistent with company initiatives and expectations and achieve high quality, professional service delivery. Achieve financial targets inclusive of project budget, gross profit, and related financial metrics within area of responsibility. Ensure project management activities meet corporate customer satisfaction objectives as well as internal and external SLAs. Work collaboratively across all levels and departments of the organization and ensure a seamless transition of work activities to execute operations functions.

    Responsibilities

    • Execute projects per PMO standards, processes, and methodologies in a consistent manner for project planning and execution activities including the following:
      • Project planning fundamentals: initiating, planning, estimating, resourcing, scheduling and budgeting
      • Project control fundamentals: monitoring, anticipating potential problems, identifying project conflicts, taking corrective action, resolving issues, managing scope, schedule, cost, profit and budget, project reporting, quality review and assurance.
      • Relationship management fundamentals: client relationship management; project team management; and overall change management
    • Prepare Project Roadmap with concurrence of all participating organizations and negotiate agreement with the customer, including identification of work and organizational breakdown structures, requirements creation and management, cost and material estimates, milestone payment schedule, risk and communication management plans.
    • Establish milestones and monitor adherence to master plans and schedules, identify program problems and obtain solutions, such as allocation of resources or changing contractual specifications
    • Direct the work of employees assigned to the project from technical, professional, or administrative areas.
    • Manage the delivery and execution of projects deploying on a National to International scale through a balance of best-in-class and pragmatic project methodologies and practices that achieve KPI