Senior Digital Product Configuration Management Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have content: "At RTX, the world's largest aerospace and defense company..." that's about company/role. Could be "About the role". We'll put that in
. Responsibilities: list of duties under "What You Will Do". That's a list. Requirements: includes security clearance, US citizenship, etc. Also "Qualifications You Must Have". Might combine Requirements and Qualifications? The instruction says separate sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. We have "Qualifications You Must Have": BS/BA STEM, 5 years experience, version control, DPCM/DevSecOps tech, automation shell scripting, Active and Current Secret security clearance required Day 1, US citizenship required. We have "Qualifications We Prefer": list of preferred qualifications. We have "What We Offer": values, relocation eligibility, benefits list. We have Pay: salary range. We have Schedule: not explicitly given; only mention onsite. No schedule details like full-time, etc. So we should not create Schedule section. We have Benefits: list of benefits. We have Skills: maybe we could extract from qualifications? But we already have Qualifications sections; maybe we can put technical skills under Skills. However instruction: prefer few substantive sections over many thin ones. Could combine Qualifications and Skills? But they ask to use headings for those categories if content exists. We have content for Qualifications (both must have and preferred). We have content for Benefits. We have content for Pay. We have content for Responsibilities. We have content for About the role (company description). We have maybe Requirements (security clearance, citizenship). But those are also in Qualifications Must Have. Could treat Requirements as security clearance and citizenship. But we already have them in Qualifications Must Have. To avoid duplication, we could put security clearance and citizenship under Requirements, and the rest under Qualifications. Let's see. The posting: "Position Role Type: Onsite U.S. Citizen, U.S. Person, or Immigration Status Requirements: Active and transferable U.S. government issued security clearance is required prior to start date. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance Security Clearance Type: DoD Clearance: Secret Security Clearance Status: Active and existing security clearance required on day 1". So that's requirements. Then later "Qualifications You Must Have Typically requires BS/BA Degree in Science, Technology Engineering or Mathematics (STEM) a minimum 5 years of prior engineering experienceExperience with version control and change management/agile planning toolsDPCM/DevSecOps technology, Information Technology (IT), and/or development/scripting experienceExperience with Automation shell scripting in Linux, Unix, and WindowsActive and Current Secret security clearance is required Day 1. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance". So there is duplication. We need to preserve ALL substantive information; do not invent or summarize away detail. We must not duplicate lines? It says remove duplicated lines. So we should not repeat same info. We need to consolidate. Thus we can have Requirements section: Active and transferable U.S. government issued security clearance required prior to start date; U.S. citizenship required (only US citizens eligible for clearance); DoD Secret clearance; Active and existing security clearance required day 1. Qualifications Must Have: BS/BA STEM; minimum 5 years prior engineering experience; experience with version control and change management/agile planning tools; DPCM/DevSecOps technology, IT, and/or development/scripting experience; experience with automation shell scripting in Linux, Unix, and Windows. Qualifications We Prefer: list. Skills: maybe we could put technical skills like version control tools, scripting languages, DevSecOps tools, etc. But we already have them in qualifications. To avoid thin sections, maybe we combine Qualifications and Skills into one "Qualifications" section that includes both must have and preferred, and maybe also skills. But instruction says we can use Skills heading if we have specific content. We have content for skills (list of tools, scripting languages, etc). Could create Skills section. But we need to avoid many thin sections. Let's think: we have About the role (company description), Responsibilities, Requirements, Qualifications (must have), Preferred Qualifications, Skills, Benefits, Pay. That's many sections. Could combine Qualifications and Preferred Qualifications into one Qualifications section with subheadings? But we cannot add extra headings beyond h3. Could use
to separate. Could have Qualifications section containing both must have and preferred as paragraphs. Skills could be merged into Qualifications as well. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we should aim for maybe 4-5 sections: About the role, Responsibilities, Requirements, Qualifications (including must have, preferred, skills), Benefits, Pay. That's 6 sections. Could combine Benefits and Pay into one "Compensation and Benefits"? But headings list includes Benefits and Pay separate. Might be okay to keep both. Let's decide sections: - About the role (company overview, mission, values, role description) - Responsibilities (What You Will Do) - Requirements (security clearance, citizenship) - Qualifications (education, experience, technical skills, preferred qualifications) - Benefits (What We Offer) - Pay (salary range) We'll omit Schedule. Now we need to extract content precisely, preserving all substantive info, not inventing. Let's gather each. About the role: The posting includes several paragraphs about RTX, mission, values, team, DPCM department description, note about onsite. We need to include all that but not repeat job title. We'll combine into a few paragraphs. We must not include boilerplate like EEO, legal, application instructions, privacy policy, etc. Also remove duplicated lines. Let's parse the posting: - Date Posted, Country, Location, Position Role Type: Onsite U.S. Citizen, U.S. Person, or Immigration Status Requirements: ... (we will extract requirements later) - At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Raytheon brings the strength of more than 100 years of experience and renowned engineering expertise to meet the needs of today’s mission and stay ahead of tomorrow’s threat. We deliver solutions that help our nation and allies defend freedom and deter aggression, creating a safer, more secure world. Join us and help shape the future of aerospace and defense. At Raytheon, the foundation of everything we do is rooted in our values and a higher calling – to help our nation and allies defend freedoms and deter aggression. We bring the strength of more than 100 years of experience and renowned engineering expertise to meet the needs of today’s mission and stay ahead of tomorrow’s threat. Our team solves tough, meaningful problems that create a safer, more secure world. The Digital Products Configuration Management (DPCM), formerly known as Software Configuration Management (SWCM), department, is hiring a Senior Digital Product Configuration Management Engineer. The DPCM department provides innovative solutions through automation, continuous improvement, and a skilled workforce providing support for all digital products. The term 'Digital Product' (DP) refers to, but is not limited to, the following software types and their associated data and documentation: embedded (tactical) software, applications, Built-in Test (BIT) software, reprogramming tools, simulation software, test equipment, configurable logic, Application-Specific Integrated Circuit (ASIC) design, analytical tools used to formally qualify deliverable artifacts, Model Based Systems Engineering (MBSE) system models or related artifacts, Free Open Source Software (FOSS), and Commercial Off-The-Shelf (COTS) software. Note This position will be filled onsite at the RTX Facility El Segundo, CA. That's a lot. We'll keep it. Responsibilities: Under "What You Will Do". List items: - Perform builds and releases of digital products manually and/or certified pipelines - Facilitate the Digital Change Review Boards (DCRBs) - Maintain, control, and administer of the Digital Products Development Library (DDL) (formerly known as Software Digital Library (SDL) tools - Maintain control, traceability, consistency, and security of all configuration items across the digital development lifecycle - Perform and maintain configuration planning & identification, change management & version control, status accounting, and configuration audits - Manage digital product development/media libraries - Document and maintain guidelines and standards for dependency management, build and versioning - Provide DPCM Tool administration / management control/access to CM relevant tools/applications (i.e. Microsoft Azure DevOps Server (ADS), Git, Gitlab, Github, Jira, BitBucket, Confluence, ClearQuest, Subversion) - Administer/manage/use DevSecOps tools like Coverity, Artifactory, Jenkins, Nexus, GitLab CI/CD, Bamboo - Coordination of data transfers, courier support among various environments - Lead coordination of various digital product releases and interface with functional and program leadership ensuring on-time delivery and configuration management execution in digital development environment/areas We need to ensure each is a