Principal Systems Engineer
Sierra Nevada Corporation · Dayton, OH · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: About the role? The posting includes description paragraphs before responsibilities. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We have:
- Intro paragraph about IAS, SAOC mission, etc. Could be "About the role" or maybe "About the role" is appropriate.
- Responsibilities: bullet list.
- Qualifications: includes "You Must Have" and "We Prefer". Could be combined as "Qualifications". Also there is "Essential Functions" maybe could be part of Qualifications or separate? But we only have headings list; we could include "Qualifications" covering both must have and preferred, and maybe "Skills" for essential functions? However essential functions are more about physical abilities; could be placed under "Qualifications" or maybe "Skills". The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Qualifications, Benefits. Pay and Schedule only if present. Pay: "SNC offers annual incentive pay based upon performance that is commensurate with the level of the position." That's vague, "commensurate with experience" - we should NOT include Pay section if it's just vague/commensurate. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The pay statement is vague but does state something: annual incentive pay based upon performance that is commensurate with the level of the position. That's still vague but it's not exactly "commensurate with experience"? It says commensurate with the level of the position. That's still vague but maybe acceptable? The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The example includes "commensurate with experience". Our phrase is "commensurate with the level of the position". That's similar filler. Safer to omit Pay section.
Schedule: none.
Benefits: they list specific benefits: medical, dental, vision, 401(k) with 150% match up to 6%, life insurance, 3 weeks paid time off, tuition reimbursement, and more. That's substantive. So include Benefits.
We also have "Essential Functions" which could be under Qualifications or maybe Skills. Since we have Skills heading available, we could put essential functions under Skills. But essential functions are more about physical ability; still could be Skills. We'll include a Skills section for essential functions.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, legal, etc. Also remove "Learn more about NC3 and SAOC here." etc. Also remove "Learn more about the background check process for Security Clearances." etc. Also remove "SNC is an Equal Opportunity Employer..." etc. Also remove "Important Notice" about security clearance? That is substantive: requires Secret clearance, US citizenship. That's important. Should we include that? It's not in the heading list but could be part of Qualifications or maybe a separate section like "Requirements". There's a heading "Requirements" in allowed list. We could put security clearance and citizenship under Requirements. Also "Essential Functions" maybe under Requirements as well. But we already have Qualifications for education/experience. We could split: Requirements (clearance, citizenship, essential functions) and Qualifications (education, experience, skills). However we must not create thin sections. Let's see content:
- Security clearance: "This position requires current/active Secret U.S. Security Clearance. U.S. Citizenship status is required as this position needs an active U.S. Security Clearance for employment. Non-U.S. Citizens may not be eligible to obtain a security clearance." That's substantive.
- Essential Functions: list of physical/computer abilities.
We could combine those into a "Requirements" section.
Qualifications: education, experience, technical skills, preferred qualifications.
Skills: maybe not needed if we put essential functions under Requirements.
But we have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can use About the role (intro), Responsibilities, Requirements (clearance, citizenship, essential functions), Qualifications (education/experience/technical), Benefits.
We must not include Skills if not needed.
Now craft HTML:
.
Qualifications:
"You Must Have" bullet list:
- Bachelor's degree in Systems Engineering, Electrical Engineering, Mechanical Engineering, or related field; Master's degree preferred.
- 14+ years of experience in systems engineering or related field.
- Higher level relevant degree may substitute for experience.
- Expert proficiency with Systems modeling and simulation tools.
- Extensive leadership experience in systems engineering.
- Demonstrated knowledge of multiple Engineering principles and practices.
- Progressive experience working in multi-disciplinary design and development teams.
- Advanced understanding of requirements management, functional requirements parsing, derivation, and allocation; systems design, systems integration, technical risk identification and management strategies, and V&V principles.
- Experience in systems modeling with Cameo and SysML.
"Qualifications We Prefer" list:
- Expertise in advanced systems technologies (e.g., AI, machine learning, cloud computing).
- Familiar with real-time operating systems and embedded systems.
- Experience with requirements management and system modelling tools, such as DOORS, Cameo, MATLAB.
- Advanced Knowledge of industry-standard mechanical design principles, to include, but not limited to requirements management, MBSE.
- Experience or certification in International Council on Systems Engineering (INCOSE) standards [Certified Systems Engineering Professional (CSEP)].
- Background in the Aerospace and Defense Industry.
- Progressive experience leading baseline definition and maturation in a complex development setting, including the use of high impact trade studies.
- Ability to establish and track key Technical Performance Measurements (TPM).
- Strong problem-solving skills and the ability to work effectively in a team environment.
- Agile methodologies and Scrum Master certification.
- experience in cockpit avionics equipment and interfaces for part 23, part 25, and military aircraft.
- Experience in evaluating vendor equipment.
- Experience in air to air/ground/satcom communications.
- Experience in aircraft systems.
- Familiarity with FAA and military airworthiness process.
- Experience in operating test equipment in aircraft environments.
We need to preserve all.
Essential Functions (under Requirements):
- Ability to work on a computer for extended periods.
- Hand/finger dexterity for system modeling and documentation.
- Ability to work in a hybrid environment with occasional travel.
Also the posting mentions: "This posting will be open for application for a minimum of 5 days and may be extended based on business needs." That's application instruction; remove.
Now Benefits:
"SNC offers annual incentive pay based upon performance that is commensurate with the level of the position." That's pay but vague; we decided to omit Pay section. However we might still include Benefits section with the list: medical, dental, vision, 401(k) with 150% match up to 6%, life insurance, 3 weeks paid time off, tuition reimbursement, and more.
Also note: "SNC offers a generous benefit package, including medical, dental, and vision plans, 401(k) with 150% match up to 6%, life insurance, 3 weeks paid time off, tuition reimbursement, and more." That's benefits.
Now Security clearance and citizenship: we need to include under Requirements.
Thus Requirements section will have:
- Must possess current/active Secret U.S. Security Clearance.
- U.S. Citizenship status is required.
- Ability to work on a computer for extended periods.
- Hand/finger dexterity for system modeling and documentation.
- Ability to work in a hybrid environment with occasional travel.
We could also include note about Non-U.S. Citizens may not be eligible to obtain a security clearance. That's part of citizenship requirement.
Now we need to ensure we don't repeat any info.
Now craft HTML.
We'll output:
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We have:
- Intro paragraph about IAS, SAOC mission, etc. Could be "About the role" or maybe "About the role" is appropriate.
- Responsibilities: bullet list.
- Qualifications: includes "You Must Have" and "We Prefer". Could be combined as "Qualifications". Also there is "Essential Functions" maybe could be part of Qualifications or separate? But we only have headings list; we could include "Qualifications" covering both must have and preferred, and maybe "Skills" for essential functions? However essential functions are more about physical abilities; could be placed under "Qualifications" or maybe "Skills". The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Qualifications, Benefits. Pay and Schedule only if present. Pay: "SNC offers annual incentive pay based upon performance that is commensurate with the level of the position." That's vague, "commensurate with experience" - we should NOT include Pay section if it's just vague/commensurate. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The pay statement is vague but does state something: annual incentive pay based upon performance that is commensurate with the level of the position. That's still vague but it's not exactly "commensurate with experience"? It says commensurate with the level of the position. That's still vague but maybe acceptable? The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The example includes "commensurate with experience". Our phrase is "commensurate with the level of the position". That's similar filler. Safer to omit Pay section.
Schedule: none.
Benefits: they list specific benefits: medical, dental, vision, 401(k) with 150% match up to 6%, life insurance, 3 weeks paid time off, tuition reimbursement, and more. That's substantive. So include Benefits.
We also have "Essential Functions" which could be under Qualifications or maybe Skills. Since we have Skills heading available, we could put essential functions under Skills. But essential functions are more about physical ability; still could be Skills. We'll include a Skills section for essential functions.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, legal, etc. Also remove "Learn more about NC3 and SAOC here." etc. Also remove "Learn more about the background check process for Security Clearances." etc. Also remove "SNC is an Equal Opportunity Employer..." etc. Also remove "Important Notice" about security clearance? That is substantive: requires Secret clearance, US citizenship. That's important. Should we include that? It's not in the heading list but could be part of Qualifications or maybe a separate section like "Requirements". There's a heading "Requirements" in allowed list. We could put security clearance and citizenship under Requirements. Also "Essential Functions" maybe under Requirements as well. But we already have Qualifications for education/experience. We could split: Requirements (clearance, citizenship, essential functions) and Qualifications (education, experience, skills). However we must not create thin sections. Let's see content:
- Security clearance: "This position requires current/active Secret U.S. Security Clearance. U.S. Citizenship status is required as this position needs an active U.S. Security Clearance for employment. Non-U.S. Citizens may not be eligible to obtain a security clearance." That's substantive.
- Essential Functions: list of physical/computer abilities.
We could combine those into a "Requirements" section.
Qualifications: education, experience, technical skills, preferred qualifications.
Skills: maybe not needed if we put essential functions under Requirements.
But we have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can use About the role (intro), Responsibilities, Requirements (clearance, citizenship, essential functions), Qualifications (education/experience/technical), Benefits.
We must not include Skills if not needed.
Now craft HTML:
About the role
... intro paragraph(s) ...
Responsibilities
- ... each bullet ...
Requirements
- ... security clearance, US citizenship
- ... essential functions items
Qualifications
... maybe split into Must Have and Preferred? Could keep as paragraphs.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, except boilerplate. Let's extract content. Intro paragraphs: "The ISR (Intelligence, Surveillance & Reconnaissance), Aviation, and Security (IAS) business area is a leader in ISR and aviation, it is a leading prime manned and unmanned aircraft systems integrator for innovative, high-performance ISR and aviation systems. Its end-to-end Command, Control, Computers, Communications and Intelligence, Surveillance & Reconnaissance (C4ISR) capabilities encompass design, integration, test, certification, ground/flight training and complete logistics support. IAS tailors solutions to customer cost, performance, and schedule requirements and designs to consistently exceed expectations – with an unrivaled record of on time and on (or under) budget deliveries. SNC has led thoughtful and disruptive change in the aerospace and defense industry for the past 60 years and now, we’re applying this tenacity and expertise to the U.S. Air Force’s (USAF) Survivable Airborne Operations Center (SAOC) mission. Join the SNC-led SAOC team and be a part of exciting and meaningful work to modernize and deliver the next-generation SAOC aircraft trusted by the President, Secretary of Defense and Chairs of the Joint Chiefs of Staff to ensure continued critical command, control and communication during national emergencies. If you’re passionate about building the airborne command post of the future, consider SNC for your next mission. Learn more about NC3 and SAOC here. Are you a bold thinker? We dream big at SNC—advocating the exploration of space, keeping service members safe and creating the systems that keep our world united and sustain our way of living. Join our team!" We should remove "Learn more about NC3 and SAOC here." as it's a link/instruction. Also maybe remove "Join our team!" at end? That's a call to action but could be considered boilerplate? It's not exactly legal/EEO but it's a generic invitation. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Join our team!" is not exactly those but could be considered a call to action; but it's not substantive detail about the role. Might be considered boilerplate. Safer to remove it. Thus intro paragraph(s) will be the above without the "Learn more..." and "Join our team!" and maybe also remove "Are you a bold thinker? We dream big at SNC—advocating the exploration of space, keeping service members safe and creating the systems that keep our world united and sustain our way of living." That is actually substantive about company values; could keep. It's not boilerplate. Keep. Now Responsibilities: list: - Demonstrate mastery in requirements engineering, systems integration, V&V, and MBSE. - Guide strategic system and decision analysis, technical planning, and risk management initiatives. - Manage critical project components and influence project direction. - Apply extensive expertise in architecture/design development, technical monitoring, and lifecycle management. - Exhibit exceptional leadership, communication, and collaboration skills. - Mentor senior engineers and drive innovation. We need to keep each asAbout the role
... (intro without boilerplate) ...
Responsibilities
- ...