Technical Project Manager (Part Time)

We need to output HTML fragment with sections only where there is real specific content. Must use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Key sections: - About The Opportunity (intro) -> could be "About the role" heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have

About the role

and then prose. - Responsibilities: The "What You'll Do" sections (Before Engagement Is Secured, Once Engagement Is Secured, Once Solution Is Live). That's responsibilities. - Requirements/Qualifications: "What You Need" and "Who You Are" maybe combine as Requirements/Qualifications. Could have Requirements heading. - Skills: maybe not separate; but we can include Skills if there is specific content. The posting mentions skills like project management, documentation, etc. Could put under Skills. - Benefits: The "What's In It For You" includes benefits list: 12 paid holidays, 401k, medical etc, pet insurance, flexible vacation, sick leave, parental leave. Also compensation: $50 - $70 an hour. That's Pay. - Schedule: The posting mentions part-time hours: 5-10 hrs/week before engagement, 20-25 hrs/week after, then full-time. That's schedule info. So we can have Schedule section. We must not create sections with filler like "commensurate with experience". We have actual specifics. We must not include boilerplate like EEO etc. Remove. We must preserve all substantive information. Must not invent or summarize away detail. Must keep details. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

... intro paragraph ...

Responsibilities

• ... each bullet ...

We need to break responsibilities into bullet points. The posting has many responsibilities grouped under phases. We could list them as bullet points. We must not lose any detail. So we need to capture all responsibilities statements. Let's extract responsibilities: Before Engagement Is Secured (5-10 hours per week): - Partner with Orb leadership, Sales and Client Solutions to help move the opportunity toward a signed engagement. - Build and maintain the overall project plan across commercial, technical and delivery workstreams. - Coordinate client and internal meetings and ensure discussions result in clear decisions and action items. - Track open questions, requirements, dependencies and commitments. - Help keep the evolving solution, commercial structure and delivery approach aligned. - Work across legal, commercial, technical and delivery teams to ensure nothing falls through the cracks. - Identify risks and gaps early and drive them toward resolution. - Help create the structure needed to move efficiently from opportunity into project kickoff. Once the Engagement Is Secured (20-25 hours per week): - Continue ownership of the overall project plan, timeline, milestones and dependencies. - Coordinate the various workstreams through solution design, development, testing, implementation, training and launch. - Partner closely with the internal implementation lead, who will own the detailed implementation work. - Maintain visibility across technical investigation and solution development without needing to be the technical owner. - Support implementation teams in ensuring translation of customer needs and asks is properly vetted and successfully completed between sales, implementation, and engineering team members. - Keep Orb and client stakeholders aligned on progress, risks, decisions and next steps. - Drive accountability for action items and commitments. - Build and maintain clear documentation throughout the engagement, including project plans, procedures, workflows, templates, standards, technical/solution documentation, proposals, decisions and other reusable materials that help formalize what we build and make future implementations easier to execute and scale. - Ensure the client is prepared for onboarding, training, launch and transition into ongoing operations. - Lead the overall transition from project mode into a sustainable operating relationship. Once the Solution Is Live (full time): - The role will transition into Account Management and success, with continued ownership of the client relationship. - Become a primary day-to-day point of contact for the client. - Coordinate internal teams around ongoing client needs and priorities. - Maintain regular client communication and business reviews. - Develop a strong understanding of the client's workflows, challenges and future needs. - Help drive continuous improvement and successful adoption of the solution. - Identify opportunities for additional services, new workflows and future expansion. - Continue to serve as the connective tissue between the client, Orb's technical teams and operations. We could combine these into a single responsibilities list, but maybe better to keep phases as subheadings? However only allowed headings are the specified list; we could still use

for sections like Responsibilities and then within that we could have

paragraphs describing phases. But we need to preserve detail; we can put paragraphs. Simplify: Under Responsibilities heading, we can have

paragraphs describing each phase. Similarly Requirements/Qualifications: "What You Need" and "Who You Are". We'll combine. What You Need bullet points: - 5+ years of experience in complex project management, client solutions, professional services, implementation, account management or a similar role. - Experience working on complex technology or service engagements where the solution was developed in partnership with the client. - Strong project management skills and exceptional follow-through. - Exceptional documentation and standardization skills. - A high degree of personal ownership and accountability. - Comfortable coordinating multiple teams without direct authority over them. - Comfortable operating in ambiguity when requirements, scope and solutions are still evolving. - Strong commercial awareness and an understanding of how contracts, SOWs, scope and delivery connect. - Technically curious and comfortable working with technical architects, developers and implementation teams. - Strong client-facing communication skills and executive presence, with proven experience in navigating client relationships. - Able to identify problems early, push for decisions and keep momentum when things get complicated. - Experience in media, broadcast, streaming, content workflows, cloud technology or other complex technology environments is a plus. Who You Are: descriptive paragraphs about mindset. We could incorporate as part of Requirements or maybe as a separate "Qualifications" section. But we have only headings list; we could use Qualifications for "Who You Are". However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements and Qualifications separate. Thus:

Requirements

5+ years of experience in complex project management, client solutions, professional services, implementation, account management or a similar role. Experience working on complex technology or service engagements where the solution was developed in partnership with the client. Strong project management skills and exceptional follow-through. Exceptional documentation and standardization skills. A high degree of personal ownership and accountability. Comfortable coordinating multiple teams without direct authority over them. Comfortable operating in ambiguity when requirements, scope and solutions are still evolving. Strong commercial awareness and an understanding of how contracts, SOWs, scope and delivery connect. Technically curious and comfortable working with technical architects, developers and implementation teams. Strong client-facing communication skills and executive presence, with proven experience in navigating client relationships. Able to identify problems early, push for decisions and keep momentum when things get complicated. Experience in media, broadcast, streaming, content workflows, cloud technology or other complex technology environments is a plus.

Qualifications

You are not someone who waits for a project plan to be handed to you. You see a complicated situation, figure out what needs to happen, create the structure around it and start moving people forward. You are comfortable joining a project before all the answers are known. You can sit with a client to understand what they need, work with a technical team to understand what is possible, work with commercial and legal teams to understand what needs to be contracted, and bring all of that back together into a clear path forward. If something is stuck, you find out why. If two teams aren't aligned, you connect them. If an action item is overdue, you follow up. If the client needs an answer, you make sure someone gets them one. And once we get the deal across the line, you don't hand the project off and walk away. You stay with it, lead it through implementation, and ultimately become the person who owns the client relationship.

Skills: maybe we can extract skills like project management, documentation, coordination, commercial awareness, technical curiosity, client-facing communication, etc. But we already covered many in Requirements. Could still have Skills section summarizing: Strong project management, documentation, coordination, commercial awareness, technical curiosity, client communication, problem solving, etc. But we risk duplication. However instruction: Prefer a few substantive sections over many thin ones. Could combine Skills into Requirements or Qualifications. But we have to use headings only when posting has real specific content for it. The posting does mention skills explicitly: "Strong project management skills and exceptional follow-through." etc. Those are skills. Could create Skills section listing them. But we already have them in Requirements. Might be okay to have Skills section with bullet list of skills. But we must not repeat content unnecessarily? Not prohibited, but we should preserve all substantive information; repeating is okay but maybe better to avoid duplication. However we could keep Requirements as experience and qualifications, and Skills as specific skill sets. Let's do:

Skills

• Project management
• Documentation and standardization
• Coordination of multiple teams without direct authority
• Operating in ambiguity
• Commercial awareness (contracts, SOWs, scope, delivery)
• Technical curiosity and ability to work with architects/developers
• Client-facing communication and executive presence
• Problem identification and decision driving
• Experience in media, broadcast, streaming, content workflows, cloud technology (plus)

But we need to ensure we don't lose any detail like "exceptional follow-through", "high degree of personal ownership and accountability", "able to identify problems early, push for decisions and keep momentum". Those are skills too. We'll include them. Now Benefits: list as

• ...

. Benefits from posting: - 12 paid holidays per year - 401k Retirement Plan (employer contributions vested immediately) - Medical, Dental, Vision, and Life Insurance - Pet Insurance - Flexible Vacation (Exempt Positions) or **revise if for hourly - Up to 14 days of paid sick leave - Up to 16 weeks paid parental leave We need to keep the note about Flexible Vacation (Exempt Positions) or **revise if for hourly. That's part of the posting; we should keep it as is. Pay: Compensation: $50 - $70 an hour. Schedule: part-time 5-10 hrs/week before engagement, 20-25 hrs/week after engagement secured, then full-time. We'll put schedule details. Now About the role: we need to summarize the intro paragraph(s) about opportunity. Let's capture: "About The Opportunity Orb Group is looking for a highly technical Client Solutions Project Manager / Account Manager to help us bring a major new client engagement across the finish line and, if the engagement moves forward, take ownership of the initiative through implementation and into an ongoing client relationship. We are currently working with a major global media company to design and build a highly customized technology and workflow solution from the ground up. The solution is still being defined in partnership with the client, with multiple parallel workstreams spanning commercial agreements, solution architecture, technical investigation, workflow design, development, implementation, training and operational readiness. We are looking for someone who can step in now on a part time basis, while the opportunity is still being discussed and finalized, and bring structure, momentum and accountability to the overall effort. The