Configuration Management Specialist (Associate, Experienced and Lead)

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions (like "Applications for this position will be accepted until Sept. 29, 2026")? The instruction says remove application instructions. So we should drop that line. Also remove "Export Control Requirements" etc? Those are not part of the defined headings; they might be considered boilerplate? They are substantive? Possibly they are part of job details but not in headings list. The instruction: "Prefer a few substantive sections over many thin ones." We can include sections like About the role (intro paragraph), Responsibilities, Requirements (basic qualifications), Qualifications (preferred), Skills (maybe NDIA certification, Automated Builds & DevSecOps), Benefits, Pay, Schedule. We need to decide what content goes where. We must not repeat job title as heading. The page already shows it, so we don't add a heading for job title. We need to include all substantive info: location (Seal Beach CA or Colorado Springs CO), onsite 100%, active DOD-Secret clearance, responsibilities (list), other duties (contracts, CDRL, SDRL), etc. Also mention "Position Responsibilities: Responsibilities of a Software CM practitioner include but not limited to ..." which duplicates some responsibilities. We need to preserve all substantive info but avoid duplication? The instruction: "Remove duplicated lines". So we should consolidate responsibilities, not repeat same bullet twice. We need to include Pay: they gave summary pay range for levels 2,3,4. Also mention "Pay is based upon candidate experience and qualifications, as well as market and business considerations." That's substantive. Also mention "At Boeing, we strive to deliver a Total Rewards package..." That's benefits. So Benefits section can include that paragraph. Schedule: "This position is expected to be 100% onsite in Seal Beach CA or Colorado Springs CO" and "This position is for 1st shift". So schedule includes onsite and shift. We also have "Relocation: This position does not offer relocation." That's maybe part of Benefits? Could be included in Benefits or maybe separate but we don't have a Relocation heading. Could fold into Benefits or maybe into a short p under Benefits? But we should not create a heading unless we have real specific content for it. We could include relocation info in Benefits section as a note. Also "Drug Free Workplace" etc is boilerplate; remove. Also "Conflict of Interest" maybe not needed? It's substantive but not under defined headings; could be placed under Requirements? Might be considered a requirement. Could include in Requirements as a bullet. Also "Typical Education/Experience" details for Lead levels. That's qualifications. We need to use

• for any list of duties/requirements/benefits. So responsibilities list, requirements list, qualifications list, skills list, benefits list maybe. We need to use

  for prose. We must not include headings with filler like "commensurate with experience". We have actual pay ranges, so Pay section is valid. We must not include Schedule unless posting actually states them. It does: onsite 100% and 1st shift. So Schedule section valid. We must not include Benefits unless posting actually states them. It does: total rewards package, health insurance, etc. So Benefits section valid. We must not include Skills unless posting actually states them. It does: NDIA certification, Experienced in Automated Builds & DevSecOps. So Skills section valid. We must not include Qualifications unless posting actually states them. It does: Preferred Qualifications (Desired Skills/Experience): Level 3, Level 4, Bachelor's Degree or higher, NDIA certification, Experienced in Automated Builds & DevSecOps. Also Basic Qualifications (Required Skills/Experience): Active DOD-Secret clearance, 1-3 years experience in CM. So we can split into Requirements (basic) and Qualifications (preferred). Or we could combine but instruction says use headings for those categories if content exists. We also have "Typical Education/Experience: Lead, Level 2..." etc. That's more detail about qualifications; could go under Qualifications as well. We also have "Conflict of Interest" maybe as a requirement. We also have "Relocation: This position does not offer relocation." Could be under Benefits? Or maybe under a short p under Benefits? But we could also include under Benefits as a note: "Relocation assistance is not offered." We also have "Drug Free Workplace" etc - remove as boilerplate. We also have "Equal Opportunity Employer" - remove. We also have "Export Control Requirements" - maybe not needed; but it's substantive? It says US Person required. Could be considered a requirement (citizenship). Already we have active DOD-Secret clearance requiring US citizenship. So maybe we can omit export control as redundant. We also have "Visa Sponsorship Employer will not sponsor applicants for employment visa status." That's also covered by citizenship requirement. We also have "Shift This position is for 1st shift" - schedule. We also have "Applications for this position will be accepted until Sept. 29, 2026" - remove as application instruction. We also have "Pay & Benefits:" heading in original; we will split. Now craft HTML. Structure:

  At Boeing, we innovate and collaborate to make the world a better place. We’re committed to fostering an environment for every teammate that’s welcoming, respectful and inclusive, with great opportunity for professional growth. Find your future with us. Boeing Space, Intelligence & Weapons Systems (SI&WS) in Seal Beach California or Colorado Springs, Colorado, is seeking an Configuration Management Specialist (Associate, Experienced and Lead) to support the ESS – MPA Phase 3 Program.

  Then

  About the role

  maybe we already have intro; but we could treat that as About the role. Actually the intro is about the role and company. Could put that under About the role. But we already used a paragraph; we could wrap that in

  About the role

  ...

  . However instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should have headings for each section. The intro could be About the role. Thus:

  About the role

  At Boeing, we innovate and collaborate to make the world a better place. We’re committed to fostering an environment for every teammate that’s welcoming, respectful and inclusive, with great opportunity for professional growth. Find your future with us. Boeing Space, Intelligence & Weapons Systems (SI&WS) in Seal Beach California or Colorado Springs, Colorado, is seeking an Configuration Management Specialist (Associate, Experienced and Lead) to support the ESS – MPA Phase 3 Program.

  Then Responsibilities:

  Responsibilities

  • Oversee and review of software and hardware documentation for internal consistency and adherence to Boeing and program standards
  • Oversee configuration control of work products
  • Generate CM records as evidence of adherence to CM plans and Boeing standards
  • Verify accuracy of deliveries, both internal and external
  • Support Change Boards
  • Respond to internal audits and customer queries
  • Evaluate contracts and modifications to establish Contract Data Requests List (CDRL) and Supplier Data Requirements List (SDRL) submittal schedules to meet contract
  • Input schedules and metadata into a data tracking system to allow notifications to responsible parties of submittal schedules
  • Review submittals for compliance to contract and work with Procurement and Subcontractors to ensure timely data submittals
  We should avoid duplication: The "Position Responsibilities: Responsibilities of a Software CM practitioner include but not limited to ..." is essentially same as above; we already captured. Now Requirements (basic qualifications):

  Requirements

  • Active DOD-Secret U.S. Security Clearance (U.S. Citizenship Required). (A U.S. Security Clearance that has been active in the past 24 months is considered active)
  • 1-3 years of experience in Configuration Management
  • Must satisfy the Company's Conflict of Interest (COI) assessment process
  • U.S. Person required for export control compliance (U.S. Citizen, U.S. National, lawful permanent resident, refugee, or asylee)
  We could also include "No relocation assistance" maybe under Benefits? But we can add a note under Benefits. Now Qualifications (preferred):

  Qualifications

  • Level 3: 3-5 years of experience in Configuration Management
  • Level 4: 6-8 years of experience in Configuration Management
  • Bachelor's Degree or higher
  • NDIA certification
  • Experienced in Automated Builds & DevSecOps
  • Typical Education/Experience for Lead levels:
    • Lead, Level 2: Education/experience typically acquired through advanced education (e.g. Associate) and typically 1 or more years' related work experience or an equivalent combination (e.g. Bachelor, 3 years' related work experience)
    • Lead, Level 3: Education/experience typically acquired through advanced education (e.g. Associate) and typically 3 or more years' related work experience or equivalent combination (e.g. Bachelor+1 years' related work experience, 5 years' related work experience)
    • Lead, Level 4: Education/experience typically acquired through advanced education (e.g. Associate) and typically 6 or more years' related work experience or equivalent combination (e.g. Bachelor+4 years' related work experience, 8 years' related work experience)
  But note: we cannot nest
  inside
  • ? Actually we can, but it's okay. However instruction: Use
    • for any list of duties/requirements/benefits. It didn't forbid nested lists. Could be okay. But maybe better to keep as separate

      for the typical education/experience description. However it's a list; we could keep as

      with details. But to avoid complexity, we could just include as

      under Qualifications. Simplify: Qualifications section includes bullet points for Level 3, Level 4, Bachelor's, NDIA, Automated Builds & DevSecOps, and then a paragraph describing typical education/experience for Lead levels. Thus:

      Qualifications

      • Level 3: 3-5 years of experience in Configuration Management
      • Level 4: 6-8 years of experience in Configuration Management
      • Bachelor's Degree or higher
      • NDIA certification
      • Experienced in Automated Builds & DevSecOps

      Typical Education/Experience for Lead levels: Lead, Level 2 typically requires advanced education (e.g., Associate) and 1+ years' related work experience or equivalent; Lead, Level 3 requires 3+ years' related work experience; Lead, Level 4 requires 6+ years' related work experience.

      Now Skills: maybe we already covered NDIA and Automated Builds & DevSecOps under Qualifications; but we could still have Skills section for those. However to avoid duplication,