Senior Control System Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description. First, job title is Senior Control System Engineer, but we should not repeat as heading. We have Working Pattern: Full-time, Working location: Indianapolis, IN (Hybrid Work Schedule). That's schedule info: hybrid work schedule, up to 20% travel between Rolls-Royce sites and up to 10% other travel. Also mention hybrid work schedule details: remote and in-office days each week, subject to change, need secure high-speed internet, etc. So we can include a Schedule section with that info. Pay: The posting includes Pay Range: $98,566- $160,169-Annually. Also note pay ranges for remote employees based on state may vary. So we have pay info. Benefits: There's a Benefits section describing comprehensive Total Rewards package: base pay, discretionary bonus, health, dental, vision, disability, life, accidental death & dismemberment insurance; flexible spending account; health savings account; 401(k) with company match; Employee Assistance Program; Paid Time Off; certain paid holidays; paid parental and family care leave; tuition reimbursement; long-term incentive plan. Also mention eligibility factors. Thus we have Benefits. About the role: The initial paragraph: "Rolls-Royce is looking for a Senior Control System Engineer to join our growing team. This is an exciting opportunity to work on flagship Rolls-Royce programs and play a vital role in solving some of the most complex and interesting technological challenges in the industry while being part of a global, multi-disciplinary team." Also maybe "As a Senior Control System Engineer, you will be the owner of assigned control system functions and interfaces..." That's more responsibilities. But we can put an About the role section summarizing the role overview. Responsibilities: The bullet list after "What you will be doing With this attractive opportunity you will get a chance to:" includes items: Collaborate with other teams and customers to develop electrical, electronics and mechatronics control system requirements, design and verification work products for mission critical applications as per ARP4754A and appropriate guidance within DO-178C. Work with a cross-functional team to establish the highest standards of technical capability, quality, professionalism, and teamwork. Provide and support engineering process guidance and training. Prepare and review engineering work products for technical documentation, quality and completeness. Resolve complex problems through the application of acquired technical experience and knowledge. Develop and communicate complex technical ideas and information in a concise and logical way. Also earlier responsibilities: "As a Senior Control System Engineer, you will be the owner of assigned control system functions and interfaces. You will be responsible for providing technical guidance, counsel, and direction to a small team of engineers to ensure technical outcomes are delivered to appropriate standards and quality while working with a global engineering community to identify areas for collaboration and knowledge exchange. You will support full life cycle development and mentor junior engineers on processes, tools, and technical solutions." Could be included in responsibilities. Requirements: Basic Requirements: Bachelor's degree in Aerospace, Mechanical, Electrical or Computer Engineering with 2+ years of product development engineering experience, OR Master's degree in in Aerospace, Mechanical, Electrical or Computer Engineering, OR PhD in degree in in Aerospace, Electrical, Mechanical or Computer Engineering. Must be US Citizen or Permanent Resident. Preferred Requirements: 5+ years of product development engineering experience, Experience with FAA or military qualification of airborne systems, Application of agile development methods to deliver engineering work products, Gas turbine engine, propulsion, or electrical control system experience, Demonstrated experience with control system design and analysis tools, Development of model-based systems with digital engineering toolsets (MATLAB, Simulink and/or similar), Knowledge of system engineering, using robust design tools and techniques, Experience with Cameo Systems Modeler (MagicDraw) or similar SysML modelling software. Qualifications: Might overlap with Requirements; but we can treat Requirements as basic qualifications, and maybe Skills as preferred? However we need to decide which sections to include. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. We have content for About the role, Responsibilities, Requirements (basic), Preferred maybe could go under Skills or Qualifications. We have Qualifications maybe same as Requirements; but we can separate: Requirements = basic eligibility (education, citizenship). Qualifications = preferred experience/skills. Skills = specific technical skills (tools, methods). But we can combine. Better: Use Requirements for basic education/citizenship. Use Qualifications for preferred experience (5+ years, etc). Use Skills for specific technical skills (control system design tools, MATLAB/Simulink, Cameo Systems Modeler, agile, etc). That seems reasonable. Pay: we have. Schedule: hybrid work schedule details. Benefits: we have. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce something like:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Skills

• ...
...

Benefits

• ...
...

Pay

$98,566‑$160,169 annually (pay ranges for remote employees may vary based on state of residence).

Schedule

Hybrid work schedule with remote and in‑office days each week; up to 20% travel between Rolls‑Royce sites and up to 10% other travel. Employees must maintain a secure, high‑speed internet connection and appropriate workspace meeting information security requirements.

We need to preserve all substantive information, not invent or summarize away detail. Must not include filler like "commensurate with experience". We must not include boilerplate like EEO, scam warning, navigation, cookie, legal, duplicated lines, application instructions. Also must not include Job ID/requisition numbers. We need to ensure we include all substantive info from the posting. Let's extract details precisely. About the role: The first paragraph after job title: "Rolls-Royce is looking for a Senior Control System Engineer to join our growing team. This is an exciting opportunity to work on flagship Rolls-Royce programs and play a vital role in solving some of the most complex and interesting technological challenges in the industry while being part of a global, multi-disciplinary team." Also maybe include "As a Senior Control System Engineer, you will be the owner of assigned control system functions and interfaces. You will be responsible for providing technical guidance, counsel, and direction to a small team of engineers to ensure technical outcomes are delivered to appropriate standards and quality while working with a global engineering community to identify areas for collaboration and knowledge exchange. You will support full life cycle development and mentor junior engineers on processes, tools, and technical solutions." That seems more responsibilities but could be part of About the role. However we have a separate Responsibilities section; we could keep About the role short as above, and responsibilities include the rest. Let's capture About the role: two sentences. Responsibilities: combine the bullet list from "What you will be doing With this attractive opportunity you will get a chance to:" plus the earlier responsibilities about owner, guidance, mentoring, full life cycle, collaboration. We need to preserve all details, not lose any. Let's list responsibilities bullet points: - Owner of assigned control system functions and interfaces. - Provide technical guidance, counsel, and direction to a small team of engineers to ensure technical outcomes are delivered to appropriate standards and quality. - Work with a global engineering community to identify areas for collaboration and knowledge exchange. - Support full life cycle development. - Mentor junior engineers on processes, tools, and technical solutions. - Collaborate with other teams and customers to develop electrical, electronics and mechatronics control system requirements, design and verification work products for mission critical applications as per ARP4754A and appropriate guidance within DO-178C. - Work with a cross-functional team to establish the highest standards of technical capability, quality, professionalism, and teamwork. - Provide and support engineering process guidance and training. - Prepare and review engineering work products for technical documentation, quality and completeness. - Resolve complex problems through the application of acquired technical experience and knowledge. - Develop and communicate complex technical ideas and information in a concise and logical way. That seems comprehensive. Now Requirements (basic): Bachelor's degree in Aerospace, Mechanical, Electrical or Computer Engineering with 2+ years of product development engineering experience, OR Master's degree in Aerospace, Mechanical, Electrical or Computer Engineering, OR PhD in Aerospace, Electrical, Mechanical or Computer Engineering. Must be U.S. Citizen or Permanent Resident. Note the posting has some typos: "Master's degree in in Aerospace, Mechanical, Electrical or Computer Engineering", "PhD in degree in in Aerospace, Electrical, Mechanical or Computer Engineering". We'll preserve as is but maybe correct minor duplication? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Should we keep the exact wording? It might be okay to keep as is but we could clean obvious duplication? It's ambiguous. Safer to keep the meaning but not invent. The duplication is likely a typo; preserving the typo might be considered preserving substantive info? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we must keep typos exactly; we can correct obvious errors? Usually we keep the meaning. I'd keep the corrected version for readability but not add info. I think it's fine to present as: Bachelor's degree in Aerospace, Mechanical, Electrical or Computer Engineering with 2+ years of product development engineering experience; OR Master's degree in Aerospace, Mechanical, Electrical or Computer Engineering; OR PhD in Aerospace, Electrical, Mechanical or Computer Engineering. Must be a U.S. Citizen or Permanent Resident. Now Qualifications (preferred): 5+ years of product development engineering experience; Experience with FAA or military qualification of airborne systems; Application of agile development methods to deliver engineering work products; Gas turbine engine, propulsion, or electrical control system experience; Demonstrated experience with control system design and analysis tools; Development of model-based systems with digital engineering toolsets (MATLAB, Simulink and/or similar); Knowledge of system engineering, using robust design tools and techniques; Experience with Cameo Systems Modeler (MagicDraw) or similar SysML modelling software. Now Skills: Could be overlapping with Qualifications; but we already used Qualifications for preferred experience. Maybe we can treat Skills as the specific technical skills: control system design and analysis tools, MATLAB/Simulink, Cameo Systems Modeler, agile methods, robust design tools, etc. However we already listed many of those in Qualifications. To avoid duplication, we could shift: Requirements = education/citizenship; Qualifications = experience (2+ years basic, 5+ years preferred); Skills = technical skills/tools. But the posting lumps experience and skills together under Preferred Requirements. We could still separate: Qualifications = preferred experience (5+ years, FAA/military, agile, gas turbine, etc). Skills = specific tools (control system design and analysis tools, MATLAB/Simulink, Cameo Systems Modeler, robust design tools). However the posting also mentions "Development of model-based systems with digital engineering toolsets (MATLAB, Simulink and/or similar)" and "Knowledge of system engineering, using robust design tools and techniques" and "Experience with Cameo Systems Modeler (MagicDraw) or similar SysML modelling software." Those are skills. Thus we can have: Qualifications: Preferred experience items: 5+ years product development engineering experience; Experience with FAA or military qualification of airborne systems; Application of agile development methods to deliver engineering work