Technical Project Manager

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must not include Job ID etc. Remove boilerplate. Keep all substantive info. We need to parse the posting. First paragraph: description about Harbor IT, mission, etc. That's about the role? Actually it's company overview. Could be "About the role" or maybe "About Harbor IT". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have sections: About the role (maybe overview of role). Then Responsibilities (list). Then Qualifications & Skills (maybe combine). But they want separate Qualifications and Skills headings if content exists. The posting has "Qualifications & Skills" heading with bullet list. Also "Education & Experience" under that. Could split: Qualifications (education/experience) and Skills (technical). But we can follow the posting: we have "Qualifications & Skills" as a combined section; we could output under

Qualifications & Skills

but they said use headings exactly those list; they didn't include "Qualifications & Skills". They listed Qualifications and Skills separately. So we need to decide: If we have content for both, we can split. The posting includes both qualifications (education, experience) and skills (technical). So we can create two sections:

Qualifications

and

Skills

. We'll allocate content accordingly. Also there is "Work Environment" section (reports to, hybrid, travel, after-hours). That could be part of About the role or maybe we could treat as "About the role". There's no specific heading for work environment, but we can include under About the role. Benefits: they list benefits. Pay: they give pay range. Schedule: not explicitly given; they mention after-hours and occasional weekend work required for cutover events and project deadlines. That's schedule info. So we can create Schedule section with that detail. We must not create sections with filler like "commensurate with experience" for Pay? Actually they gave pay range: 80,000 - 95,000 USD per year. That's specific, so we can include Pay section. Benefits: they list competitive salary commensurate with experience (but that's redundant with pay), comprehensive benefits package including health, dental, vision, 401(k) with match, unlimited PTO, professional development. That's substantive. Schedule: after-hours and occasional weekend work required for cutover events and project deadlines. Also hybrid role based out of Framingham, MA with remote flexibility, some local/regional client travel less than 10%. That's schedule/work arrangement. We'll put under Schedule. Now we need to preserve all substantive info, not invent or summarize away detail. Must not repeat job title as heading. Must not include cookie/navigation/legal/EEO etc. There's none. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must output only HTML fragment, no /, no markdown fences. Let's structure:

  About the role

  Harbor IT is a leading Managed Service Provider (MSP) specializing in delivering cutting edge Cybersecurity, IT, and Cloud Services to a diverse portfolio of clients. We pride ourselves on our commitment to excellence, innovation, and customer satisfaction. Harbor IT is backed by investment firm Worklyn Partners since 2022 and has built a national platform through acquisition and rapid organic growth. Our mission is to manage our clients’ technology and mitigate their cyber risks, so that they don’t have to. The Technical Project Manager, UCaaS owns the delivery of Harbor IT's unified communications and voice implementations from executed agreement through client handoff to support. This is a senior, client-facing role inside the UCaaS onboarding team. The person in this seat runs the full project lifecycle for cloud voice, contact center, and carrier migration work: kickoff and initiation, discovery and data collection, project planning, cutover execution, monitoring, training, and closeout. Unlike a general infrastructure PM, this role carries a real technical component. The Technical Project Manager must understand dial plans, number porting, call flow and routing design, session border controllers, network readiness and QoS, E911 compliance, and the dependencies between the voice platform and the underlying LAN, WAN, and firewall. They translate that technical detail into plans, risk registers, and change orders a client executive can act on. They direct project engineers, field technicians, trainers, carriers, and subcontractors without direct reporting authority. While the UCaaS practice is the primary focus, this role will also require exposure to or management of IT, data network, and/or cybersecurity projects as the delivery pipeline requires. Ultimately this person is accountable for the success or failure of assigned projects, for on-time and on-budget delivery, and for client satisfaction at handoff. Reports to the Manager of UCaaS Onboarding within Harbor IT's professional services organization, operating under an EOS framework with shared accountability across delivery teams. Hybrid role based out of the Framingham, MA headquarters with remote flexibility. Some local and regional client travel may be required (less than 10%). Direct and frequent client exposure across mid-market and enterprise accounts. After-hours and occasional weekend work is required for cutover events and project deadlines.

  But note we duplicated some content about after-hours etc. We'll keep in About the role maybe, but also we have Schedule section. To avoid duplication, we could keep after-hours etc in Schedule, and keep work environment details in About the role. However the instruction says preserve ALL substantive information; we can duplicate? Better not duplicate but we can split: About the role includes company overview, role description, reporting, hybrid, travel, client exposure. Schedule includes after-hours and occasional weekend work. That seems fine. Now Responsibilities: list of key responsibilities. We'll output

  Responsibilities

  • ...
  . Need to capture each bullet from "Key Responsibilities" list. Let's extract: - Own UCaaS, cloud voice, contact center, and carrier migration projects end to end, from executed agreement through closeout and transition to the Support Center. - Serve as the client's primary point of contact across all project phases: kickoff and initiation, planning, execution, monitoring, and closeout. - Build and maintain project plans that identify scope, resources, tasks, dependencies, milestones, and timelines, and hold the plan current as conditions change. - Lead technical discovery and data collection for voice cutovers, including dial plan design, number inventory and porting, call flow and routing requirements, user and device provisioning, E911 and regulatory compliance, and network readiness assessment covering QoS, bandwidth, PoE, and firewall/SBC configuration. - Coordinate carrier and vendor activity including LOA submission, port scheduling, circuit delivery, and escalation, and hold carriers accountable to committed dates. - Plan and run cutover events including cutover runbooks, rollback criteria, after-hours execution windows, day-one support coverage, and post-cutover stabilization. - Document, quantify, and communicate project risk. Mitigate where possible or proceed under documented and accepted risk with client sign-off. - Schedule and direct project resources including project engineers, field technicians, trainers, associate PMs, carriers, and subcontractors, and delegate effectively without direct reporting authority. - Author and deliver project documentation including project plans, discovery questionnaires, cutover runbooks, training materials, change orders, as-built documentation, and signoff packages. - Manage project budget and margin, issue change orders for out-of-scope work, and prevent eroding project profitability from scope creep. - Log hours and project detail in ConnectWise Manage accurately and on time, and keep client configuration records current in the customer database. - Escalate project and client issues to Client Success and Operations Management on a timely basis, and drive resolution rather than handing off the problem. - Support pre-sales when required by scoping project involvement, drafting statements of work, and budgeting project labor. - Contribute to the maturity of the project management practice through templates, methodology, scope-of-work improvements, and internal training on project workflow and internal process. - Maintain PMP or similar project management certification and current working knowledge of the UCaaS platforms Harbor IT delivers. Now Qualifications: Education & Experience bullet list. Extract: - Bachelor's degree in a technical or business discipline, or equivalent relevant experience. - 5 or more years managing technology implementation projects, with at least 3 years focused on voice, unified communications, or UCaaS delivery. - Direct delivery experience with one or more major UCaaS or cloud voice platforms, for example Intermedia Unite/Elevate, ZoomPhone, Cisco/Webex Calling, Microsoft Teams Phone, RingCentral, or 8x8. - Experience delivering projects in a managed services provider, VAR, telecom integrator, or carrier professional services environment. - PMP certification preferred. - Platform and vendor certifications relevant to the UCaaS stack are a plus. - Experience with ConnectWise Manage PSA and preferred. Now Skills: technical skills list. Extract from Qualifications & Skills section: - Demonstrated command of the full project management lifecycle including scope definition, planning, risk management, budget and change control, and formal closeout. - Hands-on working knowledge of UCaaS and cloud voice delivery: dial plan design, number porting and LNP, call routing and auto-attendant/IVR flow, SIP trunking, session border controllers, E911, and MACD processes. - Working knowledge of the network layer voice depends on, including QoS, VLAN segmentation, PoE, bandwidth planning, firewall and NAT traversal, and SD-WAN. - Proven ability to plan and execute cutover events with defined rollback criteria, including after-hours and weekend windows. - Excellent written and oral communication, including the ability to brief technologists, operations managers, and C-suite executives on the same project with the right level of detail for each. - Ability to hold carriers, vendors, and subcontractors accountable to committed dates and quality standards. - Comfort managing multiple concurrent projects across clients without dropping detail or missing commitments. - Proficiency with project management tooling such as Smartsheet, MS Project, and Microsoft Teams, and with PSA systems, ideally ConnectWise Manage. - Comfort operating in an EOS-managed, growth-stage MSP/MSSP environment with shared accountability across teams. Now Benefits: list. - Competitive salary commensurate with experience - Comprehensive benefits package including health, dental, and vision insurance. - 401(k) retirement plan with company match - Unlimited PTO and standard holidays - Professional development opportunities Pay: The Pay Range For This Role Is 80,000 - 95,000 USD per year (Harbor Networks). We'll output as

  Pay range: $80,000 - $95,000 USD per year.

  Schedule: after-hours and occasional weekend work required for cutover events and project deadlines. Also maybe mention hybrid role? Already in About the role. We'll put schedule:

  After-hours and occasional weekend work required for cutover events and project deadlines.

  We must not include filler like "commensurate with experience" in Benefits? It's okay as it's part of benefits description. But we already have Pay section with range; Benefits includes competitive salary commensurate with experience (some overlap). It's okay. Now ensure we don't include any boilerplate like EEO etc. Not present. Now produce HTML. We must not use markdown fences. Just raw HTML. Let's craft. Check for any repeated content: In About the role we included after-hours etc? We removed that; we placed after-hours in Schedule. Ensure we didn't accidentally include after-hours in About the role. We'll keep