Senior Principal Actuation Systems Leader
or drop it. Probably we can include a short paragraph with location and role type. - Security clearance requirements: ability to obtain and maintain US govt security clearance required; US citizenship required; DoD Clearance: Secret; Active and existing security clearance required after day 1. - About Raytheon: paragraph about foundation, values, etc. That's "About the role"? Actually "About the role" could be the description of the team and mission. We'll put that under About the role. - The Control Systems section ... has an exciting employment opportunity for a Senior Principal Actuation Systems Leader (P5 Electrical Engineer) with control system, power conversion, and strong technical / project / team leadership experience. The ideal candidate possesses ... This is description of role. - The RAP department is responsible for design, product and production support engineering in the following areas: then list of areas (Power System Design, Power Conversion, Power Distribution, Power Sub-System Design, Control Systems). That's a list. - This position is an onsite role. Regular travel to ... may be required depending on the assignment. Travel to supplier or customer sites may also be required (up to 10%). That's schedule/travel info. - What You Will Do: bullet list of duties. - Responsibility will cover ... (more duties). Actually "What You Will Do" includes many duties; we can treat that as Responsibilities. - Qualifications You Must Have: bullet list. - Qualifications We Prefer: bullet list. - What We Offer: values, relocation eligibility, etc. Also benefits list. - Salary range: The salary range for this role is 132,400 USD - 251,600 USD. - Benefits: list of benefits (medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, holidays). Also mention short-term/long-term incentive compensation programs. - Also mention relocation eligibility. - Also mention that specific benefits depend on business unit. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. - About the role: could include the introductory paragraph about Raytheon foundation, mission, and the Control Systems section description. - Responsibilities: the "What You Will Do" and subsequent paragraphs about leading complex tasks, etc. - Requirements: security clearance, US citizenship, ability to obtain clearance, etc. Also maybe degree and experience? Those are qualifications. But we have separate Qualifications section. Requirements could be the mandatory qualifications (must have). However the instruction says use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to separate Requirements (maybe mandatory qualifications) and Qualifications (preferred) and Skills (maybe technical skills). But we can also combine. We need to avoid filler headings. So we must only include sections that have real specific content. We have content for: - About the role: yes. - Responsibilities: yes. - Requirements: we have security clearance, US citizenship, ability to obtain clearance, maybe also the degree/experience minimum? Those are qualifications but could be considered requirements. We'll put them under Requirements. - Qualifications: we have "Qualifications We Prefer" list. - Skills: we could extract technical skills from the preferred qualifications list (e.g., experience with actuation systems, control theory, Matlab/Simulink, dSpace, hardware-in-the-loop, etc). But we might also put those under Qualifications. However we need a Skills section if we have specific skill content. The preferred qualifications list includes many skill-like items. We could treat them as Skills. - Benefits: we have benefits list. - Pay: we have salary range. - Schedule: we have travel requirements (onsite role, travel up to 10%, regular travel to certain locations). That's schedule. Thus we can create sections accordingly. We must not include boilerplate like EEO, privacy policy, etc. Also remove duplicated lines. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details as they appear, but we can format them into lists. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment, no /, no markdown fences. Let's craft. First, maybe a short paragraph for metadata: location and role type. Could be placed under About the role or as a separate
before sections. The instruction: "fold minor metadata into a short
or drop it." So we can include a
with location and role type. Then sections. Let's extract content precisely. About the role: We'll combine: "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 Control Systems section within the Radar Analog and Power Department (RAP) has an exciting employment opportunity for a Senior Principal Actuation Systems Leader (P5 Electrical Engineer) with control system, power conversion, and strong technical / project / team leadership experience. The ideal candidate possesses a combination of project / team leadership, design, product and production support experience, electronics knowledge, & hands-on laboratory skills, and is also a recognized Subject Matter Expert (SME) in areas related to actuation systems, motion control, motor drive systems, motor control, and/or electric machine design. The RAP department is responsible for design, product and production support engineering in the following areas:" Then list the areas. We need to list the areas as
- . The areas are: - Power System Design - Power System Noise, System Simulation and Modeling, Solid State Transmitters, Tube Transmitters, High Voltage Design, Power Sources, Generators - Power Conversion - AC/DC, DC/DC and DC/AC, Linear and Switching Supplies, Power Factor Correction (PFC), Zero Voltage Switching (ZVS), Resonant Circuits, Synchronization, Noise Controls - Power Distribution - Ground, Air, Shipboard, and Space, Power Generation, Line Voltage, High Current, Low Voltage, Micro-Power, DC, AC, Multi-Phase Power Control, Fault Reporting, Isolation, Protection Circuits, Redundant Systems - Power Sub-System Design - Filters, Harmonic Control, EMI, Circuit Simulation, Magnetics, Protective Relay Systems, Short Circuit and Stress Analyses - Control Systems – Servo Control Systems, Motor/Power/Process Control, Digital Feedback Systems, Command Generation, Inertial Stabilization, Navigation Algorithms We need to preserve the detail. Could format each as a
- with the heading and subitems.
Now Responsibilities: from "What You Will Do" paragraph and following.
Let's extract:
"You will be expected to lead complex tasks, work autonomously with limited oversight, have expert-level knowledge of the Controls Engineering domain, manage medium-sized or multiple smaller projects around assigned program work, mentor other professionals, and actively drive to the development of strategic vision for functional and organizational priorities of the Radar Power and Digital organization, beyond assigned Program work. Work may include but is not limited to detailed actuation system design, test design and execution, and collaboration with systems or software engineering functions. In this position, the candidate will be responsible for defining and developing technical solutions for a wide range of high-performance actuation system and motion control challenges (array or launcher deployment, platform/enclosure stabilization, and azimuth rotation of array, platform/enclosures or launcher). Responsibility will cover a major portion of the life cycle of the product, from conceptualizing and design, to prototyping and manufacturing, integration and verification testing, through production support. You will be expected to apply sound systems engineering principles to define and solve sometimes complex actuation system problems while influencing engineering teams to include electrical engineering, mechanical engineering, control systems engineering, software and firmware engineering, manufacturing engineering, supply chain and others. You will also be responsible for supporting and driving the execution of product development projects. You will be working as a Team / Technical Lead and in collaboration with an Integrated Product Team (IPT) Lead. Work is performed in a multidisciplinary team environment focused on execution and engineering excellence, using established business, and engineering tools and processes. You will interact with internal and external customers and leadership team members."
We can break into bullet list for clarity but must preserve all detail. We can keep as paragraphs or list. The instruction: Use
- for any list of duties/requirements/benefits. So we should turn the duties into a list. However we must not lose detail. We can split each sentence into a list item. Let's create list items: - Lead complex tasks, work autonomously with limited oversight. - Have expert-level knowledge of the Controls Engineering domain. - Manage medium-sized or multiple smaller projects around assigned program work. - Mentor other professionals. - Actively drive the development of strategic vision for functional and organizational priorities of the Radar Power and Digital organization, beyond assigned program work. - Perform detailed actuation system design, test design and execution, and collaborate with systems or software engineering functions. - Define and develop technical solutions for a wide range of high-performance actuation system and motion control challenges (array or launcher deployment, platform/enclosure stabilization, and azimuth rotation of array, platform/enclosures or launcher). - Cover a major portion of the product life cycle: conceptualizing and design, prototyping and manufacturing, integration and verification testing, through production support. - Apply sound systems engineering principles to define and solve complex actuation system problems while influencing engineering teams across disciplines (electrical, mechanical, control systems, software/firmware, manufacturing, supply chain, etc.). - Support and drive execution of product development projects. - Function as a Team / Technical Lead in collaboration with an Integrated Product Team (IPT) Lead. - Work in a multidisciplinary team environment focused on execution and engineering excellence, using established business and engineering tools and processes. - Interact with internal and external customers and leadership team members. That seems to capture all. Now Requirements: we have: - Ability to obtain and maintain a U.S. government issued security clearance is required. - U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance. - DoD Clearance: Secret. - Active and existing security clearance required after day 1. - Also maybe the degree/experience minimum? Those are under Qualifications Must Have. But we could put them under Requirements as they are mandatory. However we have a separate Qualifications section for "You Must Have". The instruction says we have sections: Requirements, Qualifications, Skills. So we can treat "You Must Have" as Requirements, and "Qualifications We Prefer" as Qualifications, and maybe extract skills from that as Skills. But we need to avoid duplication. Let's decide: - Requirements: mandatory qualifications (degree, experience, security clearance, citizenship). That seems appropriate. - Qualifications: preferred qualifications list. - Skills: maybe we can extract specific technical skills from the preferred qualifications (like experience with actuation systems, control theory, Matlab/Simulink, dSpace, hardware-in-the-loop, etc.) But we could also just put the preferred qualifications under Qualifications and not have a separate Skills section if we don't have distinct skill content beyond that. However the instruction says we should include a section ONLY when the posting has real, specific content