Technical Project Manager & Delivery Lead with Security Clearance

The user wants me to reformat a job posting into clean semantic HTML. I need to follow the rules: use

for section headings,

• for lists,

  for prose. Don't repeat job title as heading. Don't include Job ID/requisition numbers. Preserve all substantive info. Remove boilerplate. Only include sections with real content. No filler. Output only HTML fragment. Let me analyze the content: The posting has: - "Requirements" heading (but that's a section heading in the original) - "What You'll Do:" - list of duties - "Required Qualifications:" - list - "Preferred Experience:" - list - "Tech Stack & Tools:" - list - "You'll Thrive Here If You:" - list I need to map these to appropriate section headings. The rules say use

  for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So: - "What You'll Do:" -> Responsibilities - "Required Qualifications:" -> Requirements (or Qualifications) - "Preferred Experience:" -> Qualifications (or Preferred Qualifications) - "Tech Stack & Tools:" -> Skills (or Technical Skills) - "You'll Thrive Here If You:" -> maybe "Culture" or "About You" but not a standard heading. Could be "Qualifications" or "Additional Qualifications". But the rule says only include sections with real content. This is a list of traits. Could be "Qualifications" or "Personal Attributes". I'll use "Qualifications" for required, and maybe "Preferred Qualifications" for preferred, and "Technical Skills" for tech stack. "You'll Thrive Here If You" could be "Culture & Fit" but not a standard heading. Might fold into a paragraph or skip? The rule: include a section ONLY when posting has real, specific content. It does have specific bullet points. I'll create a section "Qualifications" for required, "Preferred Qualifications" for preferred, "Technical Skills" for tech stack, and "Additional Attributes" for thrive? But the allowed headings are limited: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Qualifications" and "Requirements" might be similar. The rule says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I can use those. I'll map: - Responsibilities (for What You'll Do) - Requirements (for Required Qualifications) - Qualifications (for Preferred Experience) - but Qualifications is similar. Maybe "Preferred Qualifications" but not in list. Could use "Qualifications" for both? Better to have separate sections: "Requirements" and "Preferred Qualifications". But the example headings include both Requirements and Qualifications. I'll use "Requirements" for required, "Qualifications" for preferred? Actually "Qualifications" might be for preferred. But the rule says use those headings. I'll use "Requirements" for required qualifications, "Qualifications" for preferred experience. Then "Skills" for tech stack. "You'll Thrive Here If You" could be "Qualifications" again? Might be "Culture" but not allowed. Could be a paragraph under "About the role"? But there's no "About the role" section. The posting starts with a paragraph describing the role. That could be "About the role". Let's see: first paragraph: "We are seeking a highly motivated and experienced Technical Project Manager & Delivery Lead to join our team. This role will lead the planning, coordination, and delivery of complex technical projects, ensuring work is completed on schedule, within scope, and in alignment with program objectives and customer requirements." That's an overview. So I'll create "About the role" with that paragraph. Then "Responsibilities" for What You'll Do list. Then "Requirements" for Required Qualifications list. Then "Qualifications" for Preferred Experience list. Then "Skills" for Tech Stack & Tools list. Then "You'll Thrive Here If You" - maybe "Additional Qualifications" but not in allowed headings. Could be "Qualifications" again? But we already used Qualifications. Could be "Personal Attributes" but not allowed. The rule says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." so maybe we can use other headings? But it says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the typical ones, but we can use others? However, the instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create a heading that matches the content. "You'll Thrive Here If You" is a section in the posting. I'll use "Culture & Fit" or "Additional Attributes". But to stay safe, maybe use "Qualifications" for both required and preferred? But they are distinct. I'll create "Preferred Qualifications" as a heading? Not in list. The rule says "use

  for section headings (e.g. ...)". It doesn't forbid other headings. But the system prompt says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That's a guideline. I think it's okay to use a heading like "Preferred Qualifications" or "Additional Qualifications". However, the user might expect only those headings. But the posting has "Preferred Experience" which is a list. I'll use "Qualifications" for preferred experience, and "Requirements" for required qualifications. That matches the example headings. Now "You'll Thrive Here If You" - this is like cultural fit. Could be "Benefits"? No. Could be "Schedule"? No. Could be "About the role"? Already used. Might be omitted? But it has substantive content: bullet points about wanting to grow career, comfortable in fast-paced, passionate about learning, US citizen and able to obtain clearance. The last bullet repeats citizenship and clearance which is already in required qualifications. The first three are soft skills/culture. I could include as a "Qualifications" section? But we have Qualifications for preferred experience. Could create a "Personal Attributes" section. But the rule says only include sections with real content. It has real content. I'll create a section "Additional Attributes" but not in the example. However, the system prompt says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use others. I'll use "Qualifications" for preferred experience, and for "You'll Thrive Here If You" I'll use "Culture & Fit" or maybe "Additional Qualifications". But to be safe, I'll include it as a subsection under "Qualifications"? But the rule says use

  for section headings. I'll create a separate

  "Additional Qualifications" for the thrive section. But the example doesn't include that. However, the instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So I'll output HTML with appropriate headings. Let's structure:

  About the role

  We are seeking a highly motivated and experienced Technical Project Manager & Delivery Lead to join our team. This role will lead the planning, coordination, and delivery of complex technical projects, ensuring work is completed on schedule, within scope, and in alignment with program objectives and customer requirements.

  Responsibilities

  • Serve as ODME’s primary day-to-day delivery interface with USMC Customer.
  • Manage integrated execution across architecture, software, data, cyber, test, HSI, training, and transition activities.
  • Collaboratively establish project governance, battle rhythm, schedule, risk management, action tracking, and decision processes with USMC Customer and ODME Project Executive.
  • Coordinate dependencies among Government program offices, technical authorities, operators, engineers, labs, and external stakeholders.
  • Manage MVP delivery increments, technical reviews, demonstrations, deliverables, and Government feedback cycles.
  • Maintain the Integrated Master Schedule and track major technical, access, staffing, environment, cybersecurity, and integration dependencies.
  • Identify schedule or technical risks early and drive timely resolution.
  • Facilitate technical decision-making without unnecessarily slowing engineering execution.
  • Manage staffing, onboarding, access, travel, security, equipment, and resource coordination.
  • Support level of effort estimates for evolving requirements.
  • Coordinate preparation and delivery of technical reviews to USMC leadership.
  • Ensure MVP results are translated into actionable transition, sustainment, and scaling plans.
  • Support operator and PMO familiarization events and structured feedback activities.
  • Maintain alignment between technical execution and customer mission priorities.

  Requirements

  • 10+ years of relevant technical-program, engineering-program, or C4ISR project-management experience.
  • Demonstrated experience managing multidisciplinary technical teams.
  • Experience delivering DoD engineering, integration, prototype, software, or C4ISR programs using Agile practices.
  • Strong understanding of military systems engineering, software integration, test, cybersecurity, or tactical-network environments.
  • Experience managing technical schedules, risk registers, dependencies, deliverables, and Government reviews.
  • Strong Government Customer relationship management and communication skills.
  • Ability to operate effectively in ambiguous, rapidly evolving environments.
  • Demonstrated ability to sustain high levels of project team morale while balancing technical rigor, schedule pressure, customer priorities, and resource constraints.
  • U.S. citizenship.
  • Ability to obtain and maintain a Secret clearance; TS eligibility preferred.

  Qualifications

  • Marine Corps or Navy C4ISR programs involving PAE-MC, MCTSSA, MCWIL, NIWC, NAVWAR, or related organizations.
  • OTA, rapid-prototyping, Middle Tier Acquisition, or accelerated-acquisition programs.
  • AI/ML integration.
  • DevSecOps / Agile delivery.
  • Classified systems or facilities.
  • Prototype demonstrations and operational experimentation.
  • ROM development and lifecycle-cost estimating.
  • CMMI / ISO 9001 certified operational environments.

  Skills

  • Microsoft Project or equivalent scheduling tools
  • Jira / Confluence
  • SharePoint / Teams
  • Power BI
  • Risk and action-item tracking systems
  • Agile / Scrum / Kanban tools
  • Configuration-management environments
  • Technical documentation and requirements tools

  Additional Attributes

  • Want to grow your career while working on impactful, defense-related projects
  • Comfortable working in fast-paced, mission-driven environments
  • Passionate about learning new things and solving complex technical problems
  • U.S. Citizen and able to obtain a security clearance
  But note: the last bullet repeats citizenship and clearance. That's okay. Now, check for any boilerplate: The original has "Requirements" at top but that's a heading. We'll ignore that. Also "What You'll Do:" etc. We've captured all. We must