Systems Engineering Mgr - L5
Lockheed Martin · Lexington, KY · 1 mo ago
OTHR$116k–$216k/yrFull-time
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.
Content:
- Intro paragraph: "Standard Job Description Lockheed Martin Missiles & Fire Control is seeking a Systems Engineering Manager to lead the Aviation mission area which is part of the SOF GLSS (Global Logistic Support Service) Program based in Lexington, KY. This program, critical to the success of US service men and women deployed throughout the world has a Mission to rapidly and properly equip the SOF community and its war fighters with the best possible mission systems and equipment. The role will lead the Aviation Project Execution Engineering team and partner with the platform Chief Engineers with the technical execution on all Air Force and Army aircraft and Unmanned Aircraft Systems task orders in the modification of existing equipment, integrating modified components into various platforms, sustainment of existing systems, and developing new devices/software based on customer specifications. The position will require a highly motivated individual with demonstrated exemplary communication and technical skills to lead a diverse team of engineers and/or suppliers. The candidate should possess extensive knowledge of systems engineering principles/processes/lifecycle and the ability to adapt the same rigor for rapid development of design required by SOF GLSS. The role is expected to lead a team in the performance of the following duties for the SOF GLSS contract:"
Then list of duties (Responsibilities) after colon:
"Responsible for systems engineering requirements and interface development, flow down of requirements, coordination and planning of tests, troubleshooting system issues, and execution of tests.
Analyze customer requirements to determine total scope, basis of estimate, plan Systems Engineering tasks within an Integrated Master Schedule (IMS), plan resource requirements, and formulate the overall systems engineering plan.
Manage and ensure tasks are prioritized and on schedule
Work with other Functional Managers to address all staffing needs (direct and contractor) associated with technical execution
Provide oversight of the team and subcontractors to ensure technical review completion/closeout actions and on-time work product deliveries."
Then "Basic Qualifications" list:
"Proven leadership and management skills
Bachelors degree in mechanical, electrical, systems, aerospace engineering, or equivalent related experience
Strong verbal, written, and presentation skills
Strong collaboration with cross-functional teams"
Then "Desired Skills":
"Proficient in systems engineering methodologies
Experience with Model Based Systems Engineering (MBSE)
Experience with Aviation System Architecture"
Then "Pay Information Full-Time Salary Range: $116100.00 - $215700.00"
Then benefits paragraph: "At Lockheed Martin, we know mission success starts with taking care of our people. Our Total Rewards program is designed to attract top talent, support your well-being, and help you grow—both professionally and personally. The salary range for this position is as listed on the requisition. Please note that the salary information listed is a general guideline only. Lockheed Martin considers factors such as (but not limited to) scope and responsibilities of the position, candidate's work experience, education/ training, key skills as well as market(work location) and business considerations when extending an offer. Benefits offered: Medical, Dental, Vision, Flexible work arrangements and schedules (e.g., 4x10), 401(k) match, Paid time off, Holidays, Parental Leave, EAP, Flexible Spending Accounts, Education Assistance, Life Insurance, Short-Term Disability, and Long-Term Disability. Annual short-term and/or long-term incentive compensation programs may be offered depending on the position. Payments under these annual programs are not guaranteed and can vary from year to year and are tied to a range of performance metrics.For (Washington state applicants only) Non-represented full-time employees: accrue at least 10 hours per month of Paid Time Off (PTO) to be used for incidental absences and other reasons; receive at least 90 hours for holidays. Represented full time employees accrue 6.67 hours of Vacation per month; accrue up to 52 hours of sick leave annually; receive at least 96 hours for holidays. PTO, Vacation, sick leave, and holiday hours are prorated based on start date during the calendar year."
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The above doesn't have those except maybe the "At Lockheed Martin..." includes some generic statements but it's about benefits and salary. We need to keep substantive info.
We need sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe Basic Qualifications?), Qualifications (maybe Desired Skills?), Skills (maybe combine?), Benefits, Pay, Schedule.
But we must not repeat job title as heading. Use for each section heading.
We need to decide which sections to include based on content.
- About the role: The introductory paragraph describing role, mission, location, etc. That's substantive.
- Responsibilities: The list of duties after colon.
- Requirements: Could be Basic Qualifications (these are required). Use heading "Requirements" or "Qualifications"? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to differentiate Requirements vs Qualifications vs Skills. Typically Requirements = basic qualifications, Qualifications = desired/preferred, Skills = specific skills. We'll map:
Requirements: Basic Qualifications list.
Qualifications: Desired Skills list (maybe also include "Proven leadership and management skills"? but that's already in Requirements). We'll put Desired Skills under Qualifications.
Skills: Could be specific skills like "Proficient in systems engineering methodologies", "Experience with Model Based Systems Engineering (MBSE)", "Experience with Aviation System Architecture". Those are also desired skills. But we already used Desired Skills for Qualifications. Maybe we split: Requirements = Basic Qualifications, Qualifications = Desired Skills (maybe includes leadership etc?), Skills = specific technical skills (MBSE, Aviation System Architecture). However the Desired Skills list already includes those three items. So we could put Qualifications as Desired Skills (the three items) and Skills maybe left empty? But we must not create a section with filler. So we need to decide: maybe we combine Qualifications and Skills into one? But instruction says we can have only sections with real content. So we could have Requirements (Basic Qualifications), Qualifications (Desired Skills), and maybe Skills not needed if no distinct content beyond those. However we have "Proficient in systems engineering methodologies", "Experience with Model Based Systems Engineering (MBSE)", "Experience with Aviation System Architecture". Those are skills. Could treat them as Skills section. Then Qualifications could be something else like "Bachelors degree..." but that's already in Requirements. Hmm.
Better: Use Requirements for Basic Qualifications (leadership, degree, communication, collaboration). Use Qualifications for Desired Skills (systems engineering methodologies, MBSE, Aviation System Architecture). Use Skills maybe for something like "Strong verbal, written, and presentation skills" but that's already in Requirements. There's no extra distinct skills beyond those. So we could omit Skills section if no distinct content. But we need to check if any other skill specifics: "Strong collaboration with cross-functional teams" is also a skill but could be in Requirements. So we can skip Skills.
Pay: we have salary range.
Benefits: we have benefits list.
Schedule: Not explicitly mentioned except "Flexible work arrangements and schedules (e.g., 4x10)" mentioned under benefits. That's schedule info. Could create Schedule section referencing flexible work arrangements. The posting mentions "Flexible work arrangements and schedules (e.g., 4x10)" as part of benefits. So we could include Schedule section with that detail. However we must not create a section if content is only generic like "not specified". Here we have specific mention of flexible work arrangements and schedules (e.g., 4x10). So we can include Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to output HTML fragment with
for each section heading.
We need to decide which sections to include based on content.
- About the role: The introductory paragraph describing role, mission, location, etc. That's substantive.
- Responsibilities: The list of duties after colon.
- Requirements: Could be Basic Qualifications (these are required). Use heading "Requirements" or "Qualifications"? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to differentiate Requirements vs Qualifications vs Skills. Typically Requirements = basic qualifications, Qualifications = desired/preferred, Skills = specific skills. We'll map:
Requirements: Basic Qualifications list.
Qualifications: Desired Skills list (maybe also include "Proven leadership and management skills"? but that's already in Requirements). We'll put Desired Skills under Qualifications.
Skills: Could be specific skills like "Proficient in systems engineering methodologies", "Experience with Model Based Systems Engineering (MBSE)", "Experience with Aviation System Architecture". Those are also desired skills. But we already used Desired Skills for Qualifications. Maybe we split: Requirements = Basic Qualifications, Qualifications = Desired Skills (maybe includes leadership etc?), Skills = specific technical skills (MBSE, Aviation System Architecture). However the Desired Skills list already includes those three items. So we could put Qualifications as Desired Skills (the three items) and Skills maybe left empty? But we must not create a section with filler. So we need to decide: maybe we combine Qualifications and Skills into one? But instruction says we can have only sections with real content. So we could have Requirements (Basic Qualifications), Qualifications (Desired Skills), and maybe Skills not needed if no distinct content beyond those. However we have "Proficient in systems engineering methodologies", "Experience with Model Based Systems Engineering (MBSE)", "Experience with Aviation System Architecture". Those are skills. Could treat them as Skills section. Then Qualifications could be something else like "Bachelors degree..." but that's already in Requirements. Hmm.
Better: Use Requirements for Basic Qualifications (leadership, degree, communication, collaboration). Use Qualifications for Desired Skills (systems engineering methodologies, MBSE, Aviation System Architecture). Use Skills maybe for something like "Strong verbal, written, and presentation skills" but that's already in Requirements. There's no extra distinct skills beyond those. So we could omit Skills section if no distinct content. But we need to check if any other skill specifics: "Strong collaboration with cross-functional teams" is also a skill but could be in Requirements. So we can skip Skills.
Pay: we have salary range.
Benefits: we have benefits list.
Schedule: Not explicitly mentioned except "Flexible work arrangements and schedules (e.g., 4x10)" mentioned under benefits. That's schedule info. Could create Schedule section referencing flexible work arrangements. The posting mentions "Flexible work arrangements and schedules (e.g., 4x10)" as part of benefits. So we could include Schedule section with that detail. However we must not create a section if content is only generic like "not specified". Here we have specific mention of flexible work arrangements and schedules (e.g., 4x10). So we can include Schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to output HTML fragment with headings and appropriate
or
- .
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must preserve all substantive information.
We need to ensure we don't include boilerplate like "At Lockheed Martin, we know mission success starts with taking care of our people." That's somewhat generic but it's part of benefits description; we can keep it as part of Benefits paragraph.
We need to remove duplicated lines: there may be duplicate of salary range mentioned twice (once in Pay Information and again later). We should include only once.
Let's extract content precisely.
About the role paragraph: from start until colon before duties.
Let's copy:
"Standard Job Description Lockheed Martin Missiles & Fire Control is seeking a Systems Engineering Manager to lead the Aviation mission area which is part of the SOF GLSS (Global Logistic Support Service) Program based in Lexington, KY. This program, critical to the success of US service men and women deployed throughout the world has a Mission to rapidly and properly equip the SOF community and its war fighters with the best possible mission systems and equipment. The role will lead the Aviation Project Execution Engineering team and partner with the platform Chief Engineers with the technical execution on all Air Force and Army aircraft and Unmanned Aircraft Systems task orders in the modification of existing equipment, integrating modified components into various platforms, sustainment of existing systems, and developing new devices/software based on customer specifications. The position will require a highly motivated individual with demonstrated exemplary communication and technical skills to lead a diverse team of engineers and/or suppliers. The candidate should possess extensive knowledge of systems engineering principles/processes/lifecycle and the ability to adapt the same rigor for rapid development of design required by SOF GLSS. The role is expected to lead a team in the performance of the following duties for the SOF GLSS contract:"
We can keep that as a
. Responsibilities: list items: - Responsible for systems engineering requirements and interface development, flow down of requirements, coordination and planning of tests, troubleshooting system issues, and execution of tests. - Analyze customer requirements to determine total scope, basis of estimate, plan Systems Engineering tasks within an Integrated Master Schedule (IMS), plan resource requirements, and formulate the overall systems engineering plan. - Manage and ensure tasks are prioritized and on schedule - Work with other Functional Managers to address all staffing needs (direct and contractor) associated with technical execution - Provide oversight of the team and subcontractors to ensure technical review completion/closeout actions and on-time work product deliveries. We'll put each as
- . Requirements (Basic Qualifications): - Proven leadership and management skills - Bachelors degree in mechanical, electrical, systems, aerospace engineering, or equivalent related experience - Strong verbal, written, and presentation skills - Strong collaboration with cross-functional teams Qualifications (Desired Skills): - Proficient in systems engineering methodologies - Experience with Model Based Systems Engineering (MBSE) - Experience with Aviation System Architecture Benefits: we need to capture the benefits offered list and maybe the introductory sentences. We have: "At Lockheed Martin, we know mission success starts with taking care of our people. Our Total Rewards program is designed to attract top talent, support your well-being, and help you grow—both professionally and personally. The salary range for this position is as listed on the requisition. Please note that the salary information listed is a general guideline only. Lockheed Martin considers factors such as (but not limited to) scope and responsibilities of the position, candidate's work experience, education/ training, key skills as well as market(work location) and business considerations when extending an offer. Benefits offered: Medical, Dental, Vision, Flexible work arrangements and schedules (e.g., 4x10), 401(k) match, Paid time off, Holidays, Parental Leave, EAP, Flexible Spending Accounts, Education Assistance, Life Insurance, Short-Term Disability, and Long-Term Disability. Annual short-term and/or long-term incentive compensation programs may be offered depending on the