Project Manager II

We need to output HTML fragment with sections: headings using

. Use

• for lists. Use

  for prose. No job title heading. No Job ID etc. Remove boilerplate like EEO etc. Also remove navigation/legal etc. The posting includes sections: "Why Work for Us", "Job Summary", "About our PMO", "Job Duties & Responsibilities", "Qualifications". Also maybe "Competitive compensation and benefits" etc under Why Work for Us. Also "Opportunities for professional development and advancement". Also "Make a real impact...". Also "Competitive compensation and benefits". Also "Opportunities for professional development and advancement". Also "Make a real impact...". Also "Why Work for Us" includes bullet points? It's a list of statements. We'll treat as

  • . We need to include sections only if there is real specific content. Provide headings: About the role? The posting has "Job Summary" and "About our PMO". Could map to "About the role". But we must use headings exactly as given? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not mandatory to use exactly those, but we should use those headings when appropriate. However we have content like "Job Summary", "About our PMO", "Job Duties & Responsibilities", "Qualifications". We could map: Job Summary -> About the role (or maybe Responsibilities?). Actually Job Summary is a brief description; could be About the role. About our PMO could be also About the role or maybe Responsibilities? But we need to avoid duplicate headings. Perhaps we combine Job Summary and About our PMO into About the role section. Then Job Duties & Responsibilities -> Responsibilities. Qualifications -> Requirements (or Qualifications). Also we have "Why Work for Us" which could be Benefits? Actually it's about culture, compensation, benefits, development. Could be Benefits section. Also we have "Competitive compensation and benefits" and "Opportunities for professional development and advancement". So we can create Benefits section. We must not create Pay or Schedule sections unless posting states them. Not present. We must not repeat job title as heading. Not include Job ID. We must preserve all substantive information. So we need to include all bullet points from Why Work for Us, Job Summary, About our PMO, Duties, Qualifications. We need to format lists with

    • . For prose paragraphs use

      . We need to avoid boilerplate: EEO statement, maybe also "Logically provides equal employment opportunities..." Remove that. Also remove duplicated lines? Not seeing duplicates. Let's extract content. First paragraph: "Managing modern technology has become increasingly complex..." That's company description. Might be considered part of About the role? Could be included as prose in About the role. Then "Logically closes that gap..." etc. That's also company description. Then "With shared visibility..." etc. Then "Our approach is cyber-first..." etc. Then "For more than 20 years..." etc. Then "Logically. Cyber-First. Future-Ready." maybe tagline. Then "Why Work for Us" heading. Then bullet list: - A culture built on doing the right thing - Work at the forefront of cybersecurity and emerging technologies - Collaborative, growth-oriented environment - Competitive compensation and benefits - Opportunities for professional development and advancement - Make a real impact by helping organizations reduce risk and build resilience Then "Job Summary:" paragraph. Then "About our PMO:" paragraph. Then "Job Duties & Responsibilities:" heading then list of duties each bolded? Actually each duty is a heading like "Project Ownership & Customer Experience:" then description. We need to treat each as list item? The instruction: Use

      • for any list of duties/requirements/benefits. So we should make each duty a
      • with its description inside maybe as

        or just text. Could embed

        inside

      • . Simpler: each duty as
      • containing the duty title and description. Could use for title but not required. We'll just put the duty title and description as text. Similarly Qualifications: list of qualifications each maybe bullet? Actually it's a paragraph with sentences separated by periods. Could treat as list? Might be better to keep as prose paragraphs. But instruction: Use
        • for any list of duties/requirements/benefits. Qualifications is a list of requirements; we could make each requirement a
        • . However the text is not clearly bulleted; it's a paragraph with many clauses. Could split by sentences? Might be overkill. Safer to keep as prose paragraphs (

          ) for Qualifications. But then we violate instruction? It says "Use

          • for any list of duties/requirements/benefits". If we don't make a list, we might be missing that instruction. However if the content is not presented as a list, we could keep as prose. The instruction says "for any list of duties/requirements/benefits". If the source does not have explicit list formatting, we can decide to keep as prose. I'd keep as prose paragraphs. Similarly for "Why Work for Us" we have a list; we will make
            • . Now we need headings: Use

              . Which sections? Let's decide: - About the role (combining company description, Job Summary, About our PMO) - Responsibilities (Job Duties & Responsibilities) - Requirements (Qualifications) - Benefits (Why Work for Us) We must not create Pay or Schedule. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML fragment. Let's craft content. About the role: include company description paragraphs (maybe two or three). Then Job Summary paragraph. Then About our PMO paragraph. We'll separate with

              tags. Responsibilities:

              • each duty. Duties list from posting: - Project Ownership & Customer Experience: Take ownership of assigned projects from Sales handoff through successful completion and closure, serving as the primary point of contact and ensuring a best-in-class customer delivery experience. - Scope Management: Validate project scope, deliverables, assumptions, dependencies, and customer expectations during the transition from Sales to Delivery. Manage scope throughout the project lifecycle and identify, document, and communicate changes or potential scope conflicts. - Schedule Management: Develop and maintain comprehensive project plans and Work Breakdown Structures (WBS), including milestones, dependencies, critical path, resource assignments, and forecast completion dates. Proactively identify and address issues that may impact the project schedule. - Resource Management: Coordinate internal and external resources required for successful project delivery, proactively addressing resource constraints, conflicts, or dependencies and escalating when necessary. - Risk & Project Health Management: Continuously evaluate project health and proactively identify, document, mitigate, and escalate risks before they materially impact the customer, schedule, scope, budget, or successful delivery. Develop and drive recovery plans for at-risk, stalled, or challenged projects. - Financial Management: Manage project financial performance, including budgets, expenditures, time entries, procurement activity, and invoicing alignment, ensuring projects remain financially aligned with approved scope and expectations. - Stakeholder Communication: Maintain clear, timely, and proactive communication with customers and internal stakeholders regarding project status, accomplishments, upcoming activities, risks, decisions, and changes. Lead difficult conversations and de-escalate issues when necessary. - Project Documentation & Reporting: Maintain accurate and timely project information within Logically’s project management systems, including schedules, forecasts, risks, milestones, financial information, decisions, and communications to support effective project management and leadership reporting. - Project Governance & Escalation: Apply established PMO standards, procedures, and escalation processes while using sound judgment to identify when additional leadership involvement is required to protect the customer experience and successful project delivery. - Mentorship & Team Development: Provide mentorship and guidance to Project Coordinators and Project Manager I’s, helping develop their project management capabilities and promoting consistent application of PMO standards and best practices. - Continuous Improvement: Identify and contribute to opportunities to improve PMO processes, tools, reporting, customer communication, and project delivery practices. We'll put each as
              • . Requirements: Qualifications paragraph. We'll keep as

                maybe multiple paragraphs. Qualifications text: "Associate’s Degree or equivalent combination of education and relevant professional experience required. 5+ years of progressive project management experience, including experience independently managing multiple concurrent customer-facing projects. Experience within technology, cybersecurity, managed services, or professional services is preferred. Certified Associate in Project Management (CAPM) certification required. Candidates holding an active Project Management Professional (PMP) certification are not required to also hold a CAPM. PMP certification is preferred but not required. Strong working knowledge of core project management disciplines, including scope, schedule, Work Breakdown Structures (WBS), dependencies, critical path, resource planning, risk management, financial management, and project forecasting. Demonstrated ability to identify project risks and issues, develop practical solutions, manage competing priorities, and successfully lead challenged or at-risk projects. Strong customer and stakeholder management skills, including the ability to establish trust, manage expectations, facilitate meetings, communicate difficult information, and work effectively with technical resources and senior leadership. Strong business and financial acumen with the ability to understand project budgets, customer objectives, and the potential business impact of project decisions, risks, and delays. Excellent written and verbal communication, organization, problem-solving, and leadership skills with the ability to remain effective in a fast-paced environment managing multiple priorities. Demonstrated ability to work collaboratively, take ownership, exercise sound judgment, and mentor or support the development of less-experienced team members. Experience with ConnectWise or similar Professional Services Automation (PSA) and project management platforms preferred." We'll keep as

                . Benefits: Why Work for Us list. Items: - A culture built on doing the right thing - Work at the forefront of cybersecurity and emerging technologies - Collaborative, growth-oriented environment - Competitive compensation and benefits - Opportunities for professional development and advancement - Make a real impact by helping organizations reduce risk and build resilience We'll put as

                • . Now ensure we removed EEO statement. Now produce HTML. We'll start with

                  About the role

                  then paragraphs. Let's write company description paragraphs: Paragraph1: "Managing modern technology has become increasingly complex. As organizations scale across clouds, endpoints, and hybrid environments, IT operations and cybersecurity often remain fragmented, creating gaps in visibility, slowing response times, and increasing risk. Logically closes that gap. We unify IT operations and cybersecurity into a single, accountable operating model that reduces risk, accelerates response, and strengthens resilience across the systems businesses depend on. With shared visibility, integrated workflows, and clear ownership, organizations gain greater control, fewer blind spots, and more confidence in their technology. Our approach is cyber-first by design, embedding protection into every layer, from end user to edge to cloud. By combining AI-assisted monitoring with human-led expertise, we deliver faster insight, smarter decisions, and more effective outcomes without the complexity of siloed tools." Paragraph2: "For more than 20 years, Logically has partnered with mid-market and enterprise organizations to simplify complexity, reduce risk, and improve resilience, acting as a true extension of their teams with clear accountability and measurable outcomes. Logically. Cyber-First. Future-Ready." Then Job Summary paragraph: "The Project Manager II (PMII) is responsible for the successful delivery of customer-facing technical projects from initiation through closure. The PMII owns project scope, schedule, financials, resources, risks, deliverables, and stakeholder communication while ensuring a high-quality customer experience. The PMII also serves as a mentor to less-experienced Project Managers and contributes to the continued improvement of PMO standards and practices." Then About our PMO paragraph: "At Logically, Project Management is a profession, not simply a job title. Our Project Managers own the full project lifecycle, including scope,