Cyber Security Project Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Skills maybe, Benefits, Pay, Schedule. Must include only sections with real content. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions, duplicate lines, etc. Keep all substantive info. We need to parse the posting. Key parts: - Opening paragraph: "We are seeking an experienced Cybersecurity Project Manager to support the planning, coordination, and execution of enterprise cybersecurity initiatives. This individual will partner closely with cybersecurity, technology, infrastructure, and business teams to drive complex programs from initiation through completion. The ideal candidate is highly organized, thrives in fast-paced environments, and has experience managing multiple concurrent projects involving diverse stakeholder groups and competing priorities." That's about the role. - Key Responsibilities: list bullet points. - Required Qualifications: list bullet points. - Preferred Qualifications: list bullet points. - Nice to Have Skills: list bullet points. - Why Join?: paragraph. - Job Type & Location: "This is a Contract position based out of Austin, TX." - Pay And Benefits: includes pay range and benefits list. - Workplace Type: "This is a hybrid position in Austin,TX." - Application Deadline: "This position is anticipated to close on Oct 2, 2026." Might be considered metadata; we can include maybe in a short paragraph but not as heading. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Application deadline is minor metadata; we could include in a short p under maybe About the role or separate? Probably we can include as a short p after role description. - About TEKsystems: company description; might be considered boilerplate? It's not exactly boilerplate but it's about the company. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About TEKsystems" sections are not boilerplate but could be considered company overview; maybe we keep as part of About the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company description if it's substantive. However, the sections like "About TEKsystems" and "About TEKsystems And TEKsystems Global Services" are duplicated. We need to deduplicate. Also there is repeated EEO statements etc. We'll remove those. We need to decide sections: About the role (maybe include opening paragraph + Why Join? + company description?). Could separate Why Join as its own section? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have headings for those categories if content exists. We can also have other headings like "Why Join?" but not in the list; but we could incorporate into About the role or maybe a separate section like "Why Join?" but not required. The instruction says prefer a few substantive sections over many thin ones. So we could combine Why Join into About the role. We need to include Pay and Benefits sections separately if they have content. Pay: we have pay range $70.00 - $85.00/hr. Benefits: list. Schedule: we have workplace type hybrid position in Austin,TX. That's schedule? Could be considered Schedule section. The instruction: include Schedule section only if posting actually states them. It does state hybrid position. So we can include Schedule. We also have Job Type & Location: Contract position based out of Austin, TX. That could be part of Schedule or maybe a separate "Job Type" but not in list. Could fold into Schedule or About the role. We need to avoid repeating job title as heading. We need to output only HTML fragment, no markdown fences. Let's structure:

About the role

We are seeking an experienced Cybersecurity Project Manager to support the planning, coordination, and execution of enterprise cybersecurity initiatives. This individual will partner closely with cybersecurity, technology, infrastructure, and business teams to drive complex programs from initiation through completion. The ideal candidate is highly organized, thrives in fast-paced environments, and has experience managing multiple concurrent projects involving diverse stakeholder groups and competing priorities.

This is an opportunity to work on highly visible cybersecurity initiatives that help protect enterprise systems, operations, and data. You'll collaborate with technology and security leaders, gain exposure to large-scale enterprise programs, and play a key role in advancing strategic cybersecurity objectives. The position offers strong executive visibility, challenging cross-functional work, and the ability to leverage modern AI-enabled tools to enhance project delivery and operational excellence.

TEKsystems is a partner in transformation, helping clients activate ideas and solutions. With 80,000 employees serving over 6,000 clients including 80% of the Fortune 500 across North America, Europe, and Asia, TEKsystems provides full‑stack technology services, talent services, and real‑world application. TEKsystems and TEKsystems Global Services are Allegis Group companies.

But we need to avoid duplication: The "About TEKsystems" appears twice with similar content; we can combine. We need to ensure we keep all substantive info: The "Why Join?" paragraph content is included. Now Responsibilities:

Responsibilities

• Lead the planning, coordination, execution, and delivery of cybersecurity and technology initiatives from initiation through implementation and closure.
• Develop and maintain comprehensive project plans, schedules, milestones, RAID logs, status reports, meeting documentation, and project artifacts.
• Monitor project progress, dependencies, risks, issues, and action items to ensure successful execution and timely delivery.
• Coordinate efforts across multiple teams and stakeholder groups to align project objectives, deliverables, timelines, and expectations.
• Facilitate project meetings, working sessions, workshops, and stakeholder reviews while documenting decisions and tracking action items to completion.
• Prepare concise executive-level communications, dashboards, status reports, and governance updates.
• Identify, escalate, and help mitigate project risks, issues, resource constraints, and schedule impacts.
• Support portfolio governance activities including steering committees, portfolio reviews, and executive reporting.
• Drive accountability across project teams and assist stakeholders in resolving obstacles that could impact project delivery.
• Leverage AI-enabled productivity tools to improve project planning, reporting, documentation, meeting synthesis, action tracking, and operational efficiency.
• Maintain accurate project documentation and knowledge repositories within enterprise collaboration platforms.
• Promote consistency in project management methodologies, reporting standards, and documentation practices across the cybersecurity portfolio.

Now Requirements (maybe combine Required Qualifications and Preferred Qualifications and Nice to Have Skills into Requirements? But we have headings: Requirements, Qualifications, Skills. The instruction list includes Requirements, Qualifications, Skills as possible headings. We could separate: Required Qualifications under Requirements, Preferred Qualifications under Qualifications, Nice to Have Skills under Skills. Or we could combine. The instruction: prefer a few substantive sections over many thin ones. So maybe combine all into Requirements? But we have distinct headings allowed; we could still have three sections if each has substantive content. They do have content. So we can keep three sections: Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Skills (Nice to Have Skills). That seems fine. Thus:

Requirements

• 5‑7+ years of project management or program management experience supporting cybersecurity, technology, infrastructure, cloud, or enterprise IT initiatives.
• Proven ability to manage multiple concurrent projects and competing priorities in a dynamic environment.
• Experience leading complex, cross‑functional initiatives involving multiple stakeholder groups and interdependent workstreams.
• Strong organizational, planning, problem‑solving, and analytical skills with exceptional attention to detail.
• Experience developing and maintaining project plans, schedules, RAID logs, executive status reporting, and governance documentation.
• Excellent verbal and written communication skills, with the ability to communicate effectively with both technical and non‑technical audiences.
• Proficiency with Microsoft Office Suite, including Excel, PowerPoint, and other project management and collaboration tools.
• Experience utilizing AI‑enabled productivity tools to improve project execution, reporting, documentation, and workflow efficiency.
• Working knowledge of enterprise collaboration platforms, wikis, knowledge management systems, and documentation repositories.
• Demonstrated ability to influence stakeholders, drive execution, and achieve outcomes without direct reporting authority.

Qualifications

• PMP, CAPM, Agile, Certified ScrumMaster (CSM), SAFe, or comparable project management certification.
• Experience supporting cybersecurity, information security, infrastructure, cloud, or risk management programs.
• Experience creating executive dashboards, steering committee materials, and portfolio governance reporting.
• Familiarity with cybersecurity frameworks, risk management practices, and enterprise security operations.

Skills

• Cybersecurity
• Information Security
• Security Program Management
• Stakeholder Management
• Process Improvement
• Portfolio Governance
• Agile Delivery Methodologies
• Risk and Issue Management

Now Benefits and Pay: We have Pay And Benefits section with pay range and benefits list. We need separate Pay and Benefits sections? The instruction list includes Pay, Benefits, Schedule as possible headings. So we can have:

Pay

The pay range for this position is $70.00 - $85.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job‑related factors.

Benefits

• Medical, dental & vision
• Critical Illness, Accident, and Hospital
• 401(k) Retirement Plan
• Pre‑tax and Roth post‑tax contributions available
• Life Insurance (Voluntary Life & AD&D for the employee and dependents)
• Short and long‑term disability
• Health Spending Account (HSA)
• Transportation benefits
• Employee Assistance Program
• Time Off/Leave (PTO, Vacation or Sick Leave)

Note: The original also said "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms." That's somewhat boilerplate but still substantive? It's more generic. Might be considered boilerplate; we could drop it as it's not specific benefit. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This benefits eligibility text is somewhat generic but not exactly legal boilerplate; still could be considered boilerplate. Safer to keep only the list of benefits. Now Schedule: We have Job Type & Location: Contract position based out of Austin, TX. Workplace Type: hybrid position in Austin,TX. Application Deadline: Oct 2, 2026. We could combine into Schedule section: maybe include job type, location, workplace type, and deadline. Thus:

Schedule

This is a Contract position based out of Austin, TX. The role is hybrid (remote/on‑site) in Austin, TX. The position is anticipated to close on Oct 2, 2026.

We need to ensure we didn't repeat any content