Senior Specialist, Configuration Management

We need to output HTML fragment with sections: About the role? The posting includes description of company and role. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We have: - About the role: The description of the role: "Senior Specialist, Configuration Management TerraPower is seeking a Senior Specialist, Configuration Management to support the implementation and day-to-day execution of configuration management across TerraPower projects and engineering organizations. This role will help ensure that configuration items, configuration information, approved baselines, engineering changes, and associated records remain accurate, complete, traceable, and controlled throughout the product and facility lifecycle. The Senior Specialist, Configuration Management will work under the direction of Configuration Management leadership and collaborate with engineering, project management, Digital Engineering, Information Technology, Quality Assurance, Document Control, suppliers, and partner organizations. The successful candidate will support configuration identification, change control, configuration status accounting, configuration verification, audits, data-quality reviews, and configuration-management system administration." We can put that as

About the role

then

...

. - Responsibilities: list of duties. We have many bullet-like sentences. We'll put

• each. - Requirements: maybe combine Key Qualifications and Skills? The posting has "Key Qualifications and Skills" then list. Could split into Requirements (maybe education/experience) and Qualifications/Skills? But we have sections: Requirements, Qualifications, Skills. We need to decide what content fits each. We have: Key Qualifications and Skills paragraph includes: "Bachelor's degree in engineering, engineering technology, information management, business systems, computer science, or a related discipline and 5 to 7 years of relevant experience; or an equivalent combination of education and directly applicable experience. Experience supporting configuration management, engineering change control, document control, product lifecycle management, data management, records management, or a related controlled process. Working knowledge of configuration identification, change control, configuration status accounting, configuration verification, and configuration audits. Ability to understand relationships among requirements, engineering documents, equipment, software, design changes, and configuration baselines. Experience reviewing detailed technical or administrative information for completeness, accuracy, consistency, and traceability. Strong organizational skills and demonstrated attention to detail. Ability to independently manage assigned work, maintain accurate records, and follow actions through closure. Strong written and verbal communication skills. Ability to communicate configuration-management expectations clearly to personnel from different technical and functional backgrounds. Ability to work on multiple assignments and adjust priorities based on project needs. Experience identifying process weaknesses and supporting practical continuous-improvement solutions. Proficiency with enterprise software, engineering information systems, databases, spreadsheets, or workflow applications. The successful candidate will demonstrate trust and integrity, communicate openly, show respect for others, and actively foster teamwork." Then Preferred Qualifications list. We could treat "Key Qualifications and Skills" as Qualifications (maybe combine with Skills). But we have separate sections: Requirements, Qualifications, Skills. We could put education/experience under Requirements, and the rest under Qualifications and Skills. However we need to avoid duplication. Simplify: Use Requirements for education/experience (Bachelor's degree ... 5-7 years). Use Qualifications for the list of experience/knowledge/abilities (the bullet items). Use Skills for maybe the technical proficiencies and soft skills? But many overlap. Given instruction: Prefer a few substantive sections over many thin ones. Could combine Qualifications and Skills into one section? But we have separate headings allowed. However we should only include sections when there is real specific content. We could include Requirements, Qualifications, Skills each with content. Let's extract: Requirements: Bachelor's degree in engineering, engineering technology, information management, business systems, computer science, or a related discipline and 5 to 7 years of relevant experience; or an equivalent combination of education and directly applicable experience. Qualifications: Experience supporting configuration management, engineering change control, document control, product lifecycle management, data management, records management, or a related controlled process. Working knowledge of configuration identification, change control, configuration status accounting, configuration verification, and configuration audits. Ability to understand relationships among requirements, engineering documents, equipment, software, design changes, and configuration baselines. Experience reviewing detailed technical or administrative information for completeness, accuracy, consistency, and traceability. Strong organizational skills and demonstrated attention to detail. Ability to independently manage assigned work, maintain accurate records, and follow actions through closure. Strong written and verbal communication skills. Ability to communicate configuration-management expectations clearly to personnel from different technical and functional backgrounds. Ability to work on multiple assignments and adjust priorities based on project needs. Experience identifying process weaknesses and supporting practical continuous-improvement solutions. Proficiency with enterprise software, engineering information systems, databases, spreadsheets, or workflow applications. The successful candidate will demonstrate trust and integrity, communicate openly, show respect for others, and actively foster teamwork. Skills: maybe the Preferred Qualifications list? Those are additional preferred qualifications, could be considered Skills. But we could also put them under Qualifications as well. However we need to avoid duplication. Better: Use Requirements for education/experience. Use Qualifications for the key qualifications list (the long list). Use Skills for the preferred qualifications list (maybe). But the preferred qualifications are also qualifications. However we can treat them as Skills. Let's extract Preferred Qualifications: - Experience supporting configuration management in commercial nuclear power, Department of Energy facilities, aerospace, defense, utilities, medical devices, or another highly regulated industry. - Familiarity with ASME NQA-1, 10 CFR Part 50 Appendix B, ANSI/EIA-649, ISO 10007, or equivalent configuration-management and quality standards. - Experience with nuclear design control and the relationship between design requirements, design outputs, verification, configuration changes, and records. - Experience administering or using configuration-management, product-lifecycle-management, requirements-management, enterprise-asset-management, or document-management systems. - Experience supporting configuration control boards, engineering change boards, or release-management processes. - Experience performing data-quality reviews, configuration reconciliations, audits, surveillances, or self-assessments. - Familiarity with engineering document types such as specifications, calculations, analyses, drawings, system design descriptions, design basis documents, interface-control documents, and supplier data. - Experience developing metrics, dashboards, or automated reports. - Configuration-management certification or relevant professional training is desirable. Also note: "This position is subject to qualification requirements in accordance with ANSI/ANS 3.1. Candidates must meet the minimum education and experience criteria applicable to the role, including relevant nuclear industry experience where required. Verification of data will be part of the hiring process." Could be part of Requirements? Might be extra. We'll include that in Requirements maybe. Now Benefits: we have list: Competitive Compensation Salary, eligible to participate in discretionary short-term incentive payments Comprehensive Medical and Wellness Benefits Medical Vision Dental Life and Disability Gender Affirmation Benefits Parental Leave 401k Plan Generous Paid Time Off (PTO) 21 days of annually accrued PTO Generous Holiday Schedule 10 paid holidays Relocation Assistance Professional and Educational Support Opportunities We'll put as
  • . Pay: Salary Range: $131,828 - $171,206 Any salary offered within the posted salary band is based on market data and commensurate with the selected candidate's qualifications and experience. This range is specific to Washington State. We need to include Pay section only if posting states them. Yes, we have salary range. So include

    Pay

    ...

    . Schedule: Job Type: Full-time. Also maybe travel 0-10%? That's schedule? Could include under Schedule? The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So Schedule likely refers to work schedule (full-time, part-time, shift, etc). We have Job Type: Full-time. Also Travel required 0-10% maybe not schedule but could be included. We'll include Schedule with Full-time and maybe note travel. Thus Schedule section:

    Full-time position. Travel required 0-10%.

    Now we need to remove boilerplate: EEO, equal opportunity, scam warning, application instructions, cookie/navigation/legal, duplicated lines. Also remove "Job Functions: Job Functions are physical actions..." etc. That's boilerplate? It's describing physical abilities; might be considered job functions but maybe we should keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Job Functions section seems like part of the posting describing physical demands; not explicitly boilerplate but could be considered part of job description. However it's quite detailed; maybe we should keep as part of Responsibilities? But it's about physical abilities, not duties. Might be considered boilerplate? Not sure. Safer to keep? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Job Functions is not that. It's describing physical abilities; could be relevant. However we already have Responsibilities covering duties. The Job Functions section is separate; we could include it under Responsibilities? But it's not duties; it's physical requirements. Might be considered part of the job description; we could keep as a separate section? But we don't have a heading for Physical Requirements. Not in allowed headings. Could fold into Responsibilities as a note? But it's not a duty. Might be better to omit as it's not clearly a duty/responsibility/qualification etc. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit Job Functions, we lose substantive info about physical abilities. However the allowed headings don't include a section for that. Could we include it under Responsibilities as a bullet? It's not a responsibility but could be considered a job function. Might be okay to include as a bullet under Responsibilities? Might be stretching. Alternatively, we could create a section "Requirements" and include physical abilities there? Not ideal. Given the instruction to use only those headings, we might need to omit Job Functions because there's no appropriate heading. But that would lose info. However maybe the Job Functions section is considered boilerplate? It's describing physical abilities; could be considered standard. Not sure. Given typical job postings, the "Job Functions" section is often included but not required. The instruction says remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. It doesn't say to remove Job Functions. So we should keep it. But we need a heading. Not in list. Could we treat it as part of Responsibilities? Might be acceptable as it's still about job functions. I'll include a bullet list under Responsibilities for physical abilities? But that mixes duties with physical demands. Better: Add a subsection under Responsibilities titled "Physical Requirements"? Not allowed heading. Given constraints, I'll include Job Functions as a

    under Responsibilities? Might be okay. But to be safe, I'll include a separate section "Requirements" for education/experience, and "Qualifications" for skills/knowledge, and "Skills" for preferred qualifications, and keep Job Functions as part of Responsibilities? Hmm. Let's decide: We'll keep Job Functions as a

    after Responsibilities, but without a heading? That would be stray text. Not good. Maybe we can treat Job Functions as part of "Requirements" (since they are requirements for the job). So we can add bullets under Requirements for physical abilities. That seems plausible: Requirements include education/experience and also physical abilities. We'll combine. Thus Requirements section will have two sets: education/experience and physical abilities. We'll list bullets for each. Now we need to ensure we don't repeat content. Let's craft HTML. Structure:

    About the role

    ...

    Responsibilities

    • Managing the day-to-day activities of the Configuration Management process, including establishing priorities and work assignments
    • Tracking compliance to policies and