Configuration Analyst Senior

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Include a section only when posting has real specific content. Remove boilerplate etc. We need to parse the job description. Key sections: - About the role? The description starts with "Job Description The Engineering, Science and Analysis (ESA) Strategic Capabilities Unit comprises..." That's about the unit. Could be "About the role" or maybe "About the team". We'll treat as "About the role". Provide prose. - Responsibilities: many bullet-like sentences: "Provide configuration and data management (C&DM) support for multiple programs..." etc. We'll list as

  • . - Requirements: Required Education, Experience, & Skills: includes Bachelor's degree plus 4+ years experience, etc. Also includes abilities: coordinate, knowledge, organizational skills, PLM tools, problem solving, MS Office, security clearance eligibility. We'll list as
    • . - Preferred Education, Experience, & Skills: includes current active Secret clearance desired, CM certifications, MBSE knowledge, PLM tools experience, familiarity with regulations. Also maybe "Preferred" separate section? Could be under "Qualifications" or "Preferred Qualifications". We'll create a section "Preferred Qualifications" maybe. But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use those headings for section headings. It doesn't forbid other headings? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. We can map content accordingly. We have "Required Education, Experience, & Skills" -> could go under Requirements. "Preferred Education, Experience, & Skills" -> could go under Qualifications or Skills. Since we have both Qualifications and Skills headings allowed. We could put required under Requirements, preferred under Qualifications, and maybe specific skills under Skills. But we have overlapping. Simplify: Use Requirements for required education/experience/skills. Use Qualifications for preferred qualifications. Use Skills for maybe specific technical skills? But we already have skills in required and preferred. Could combine. Better: Use Requirements for required education/experience. Use Skills for technical skills (CM principles, PLM tools, MBSE, etc). Use Qualifications for preferred qualifications (clearance, certifications). But we need to avoid duplication. Let's extract: Required: - Bachelor’s degree in a related field plus 4 or more years related experience. - Each higher-level degree (Master’s or Ph.D.) may substitute for two years of experience. - Related technical experience may be considered in lieu of education. - Degree must be from an accredited institution. - Demonstrated ability to coordinate effectively with cross-functional teams, customers, subcontractors. - Possess extensive knowledge and understanding of CM principles and other engineering disciplines. - Excellent organizational skills and proven ability to organize and prioritize tasks effectively. - Experience utilizing PLM tools and ability to understand technical and engineering data and provide technical feedback. - Ability to independently identify solutions to complex problems by applying ingenuity and innovation, aligning with department objectives. - Proficiency with Microsoft Office products, and comfortable learning new tool technologies when needed. - Willing and eligible for security clearance submission after offer; must be able to maintain applicable clearance/access. Preferred: - A current, active Secret security clearance is desired but not needed to start employment. - Configuration Management certifications (e.g., CMII, NDIA, CMPIC). - Knowledge of Model Based Systems Engineering (MBSE). - Experience with PLM tools (e.g., ARAS Innovator, Windchill, Oracle Agile). - Familiarity with industry-specific regulations and standards (e.g., EIA-649). Also we have Pay Information: Full-Time Salary Range: $97008 - $164914. Also note about market pay structures etc. We need to include Pay section only if posting states them. It does, so include Pay. Benefits: described: health, dental, vision insurance; HSAs; 401(k); disability coverage; life and accident insurance; employee assistance program; legal plan; perks; leave programs; recognition program; other incentives. Include Benefits. Schedule: On-Site Work Environment: requires regular in-person engagement by working on-site three or more days each normally scheduled week. Travel and local commute may be required. Also "Maintain a regular and predictable work schedule." So we have schedule info. So include Schedule. Also we have Working Conditions: office environment, lab, cleanroom, production floor. Could be part of Schedule or maybe not needed. Not a heading. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The text includes "This position will be posted for at least 5 calendar days..." etc. That's boilerplate; remove. Also "About BAE Systems Space & Mission Systems" paragraph is maybe about company; could be considered "About the role"? Might be considered boilerplate but it's descriptive of company; maybe we keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About BAE Systems..." is not exactly those; it's company description. Could keep as part of About the role? But we already have About the role from the unit description. Might be redundant. We could include a short paragraph about company under About the role or maybe omit as it's not strictly required. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive? It's about the employer, not the role. Might be considered boilerplate but not listed. Safer to keep it as part of About the role? However, the instruction says "Prefer a few substantive sections over many thin ones." So we could combine unit description and company description into About the role. Let's craft About the role paragraph: combine the first paragraph about ESA Strategic Capabilities Unit and the later "About BAE Systems Space & Mission Systems" paragraph. Now Responsibilities: list each duty as

      . We need to ensure we don't include filler like "Perform other duties as necessary." That's substantive? It's generic but still a duty. Keep. Now Requirements: list required education/experience/skills as

      . Skills: maybe list technical skills: CM principles, PLM tools, MBSE, etc. But we already have many in required. Could separate: Skills: CM principles, PLM tools, MBSE, MS Office, etc. But we might duplicate. Better to put technical skills under Skills, and keep Requirements for education/experience. Let's decide: - Requirements: education/experience requirements (degree, years, accreditation, etc.) - Skills: technical and soft skills (coordination, CM principles, organizational, PLM tools, problem solving, MS Office, security clearance eligibility) - Qualifications: preferred qualifications (clearance, certifications, MBSE knowledge, PLM tools experience, regulations familiarity) But there is overlap: PLM tools appears both required and preferred. Required says "Experience utilizing PLM tools". Preferred says "Experience with PLM tools (e.g., ARAS Innovator, Windchill, Oracle Agile)". So we can keep required under Skills (experience using PLM tools) and preferred under Qualifications (specific tools). That's okay. Let's extract: Required education/experience: - Bachelor’s degree in a related field plus 4+ years related experience. - Each higher-level degree (Master’s or Ph.D.) may substitute for two years of experience. - Related technical experience may be considered in lieu of education. - Degree must be from an accredited institution recognized by US Secretary of Education. Required skills/abilities: - Demonstrated ability to coordinate effectively with cross-functional teams, customers, and subcontractors, ensuring process integrity and successful execution across all phases of the programs. - Possess extensive knowledge and understanding of CM principles and other engineering disciplines. - Excellent organizational skills and proven ability to organize and prioritize tasks effectively. - Experience utilizing PLM tools and the ability to understand technical and engineering data and provide technical feedback to engineering when needed. - Ability to independently identify solutions to complex problems by regularly applying ingenuity and innovation, while ensuring that these solutions align with department objectives. - Proficiency with Microsoft Office products, and comfortable learning new tool technologies when needed. - Willing and eligible for submission for security clearance (or access with Polygraph) after offer, and able to maintain applicable clearance/access. Preferred qualifications: - A current, active Secret security clearance is desired but not needed to start employment. - Configuration Management certifications (e.g., CMII, NDIA, CMPIC). - Knowledge of Model Based Systems Engineering (MBSE). - Experience with PLM tools (e.g., ARAS Innovator, Windchill, Oracle Agile). - Familiarity with industry-specific regulations and standards (e.g., EIA-649). Now Benefits: list items. Benefits list: - health, dental, and vision insurance - health savings accounts - a 401(k) savings plan - disability coverage - life and accident insurance - employee assistance program - a legal plan - other perks including discounts on things like home, auto, and pet insurance - leave programs: paid time off, paid holidays, paid parental, military, bereavement, and any applicable federal and state sick leave - company recognition program to receive monetary or non-monetary recognition awards - other incentives may be available based on position level and/or job specifics Schedule: - On-site work environment: regular in-person engagement by working on-site three or more days each normally scheduled week. - Travel and local commute between company campuses and other possible non-company locations may be required. - Maintain a regular and predictable work schedule. Pay: - Full-Time Salary Range: $97,008 - $164,914 (note formatting: original $97008 - $164914; we can keep as is or add commas for readability but must preserve info; adding commas is okay as not altering meaning? Might be considered summarizing? Safer to keep exactly as given: $97008 - $164914.) - Note: This range is based on market pay structures; individual salaries determined by various factors (business considerations, local market conditions, internal equity, candidate qualifications). We can include that as prose under Pay. Now About the role: combine unit description and company description. Unit description: "The Engineering, Science and Analysis (ESA) Strategic Capabilities Unit comprises the technical talent and organizational leadership that enables the successful delivery of high-impact discriminating technologies for our customers’ missions. Our collaborative, cross-functional teams are committed to innovation, integrity, continual learning and strong execution." Company description: "BAE Systems, Inc. is a defense, aerospace, and security company headquartered in Falls Church, Virginia, with more than 40,000 employees worldwide. We serve, supply, and protect those who protect us. As one of the most geographically diverse international defense companies, we deliver a full range of products and services spanning air, land, maritime, space, and cyber, including advanced electronics, intelligence solutions, and dedicated customer support. Our culture is performance-driven and values-led, built on curiosity, creativity, and collaboration. Purpose isn't a tagline here. It's what drives us. We're developing breakthrough technologies that defend national security and make a lasting impact on our communities and our planet. When you join BAE Systems, you're not just building a career. You're contributing to a mission that truly matters." We'll combine into a paragraph. Now ensure we don't include any boilerplate like "This position will be posted for at least 5 calendar days..." etc. Now