Systems Engineer Sr Stf - E5
- for any list of duties/requirements/benefits, and
for prose. We need to decide which content goes where. We have: - About the role: could be the introductory paragraph describing the team and need. - Responsibilities: could be bullet list of duties: support integration, design CONOPs, collaborate, identify solutions, identify gaps, ensure compatibility. - Requirements: Basic Qualifications (mandatory). Could be list. - Qualifications: maybe Desired Skills? Or we could treat Desired Skills as Skills section. The headings list includes Qualifications and Skills separate. Could put Desired Skills under Skills, and maybe leave Qualifications empty? But we must not emit a heading with filler. So if we have content for Skills, we can include Skills heading. For Qualifications, we could put Basic Qualifications under Requirements, and maybe not have Qualifications heading. Or we could swap: Requirements = Basic Qualifications, Qualifications = Desired Skills. But the heading list includes both; we can choose to use either if we have content. Better: Use Requirements for Basic Qualifications (mandatory). Use Skills for Desired Skills (preferred). Then we may not need Qualifications heading. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Check if any other sections like "Schedule" not needed. Now we need to preserve all substantive information; do not invent or summarize away detail. We need to include all details from posting. Let's extract details: About the role: "The Mission Engineering and Operations (MEO) team is in need of a senior systems engineer to support the integration of ground mission systems into vehicle payload operations. The MEO team will be designing new CONOPs and payload tasking strategies for multiple programs within the Global Security portfolio." That's about the role. Responsibilities: The successful candidate will be able to collaborate between multiple internal and external teams to identify strong systems-level solutions that satisfy customer requirements and achieve mission milestones. Further, the candidate will embody the true spirit of systems engineering and integration by identifying gaps in the plan and engaging in solutions to ensure system compatibility. We could also include support integration, design CONOPs, payload tasking strategies (these are more about the team's work, but could be responsibilities). However we already used that in About the role. To avoid duplication, maybe keep About the role as description of team's mission, and Responsibilities as candidate duties. Thus Responsibilities bullet list: - Collaborate between multiple internal and external teams to identify strong systems-level solutions that satisfy customer requirements and achieve mission milestones. - Embrace the spirit of systems engineering and integration by identifying gaps in the plan and engaging in solutions to ensure system compatibility. Maybe also include: Support integration of ground mission systems into vehicle payload operations. Design new CONOPs and payload tasking strategies for multiple programs within the Global Security portfolio. But those are more about the team's work; but could be considered responsibilities of the role. However to avoid duplication we could incorporate them in Responsibilities as well. Let's think: The posting says "The MEO team will be designing new CONOPs and payload tasking strategies..." That's a team activity, not necessarily candidate's duty but likely part of role. The candidate will support integration, etc. So we could include those as responsibilities. Better to capture all substantive info: The candidate will support integration of ground mission systems into vehicle payload operations. The MEO team will be designing new CONOPs and payload tasking strategies... The candidate will collaborate..., identify gaps, ensure compatibility. Thus responsibilities could be: - Support integration of ground mission systems into vehicle payload operations. - Contribute to designing new CONOPs and payload tasking strategies for multiple programs within the Global Security portfolio. - Collaborate between multiple internal and external teams to identify strong systems-level solutions that satisfy customer requirements and achieve mission milestones. - Identify gaps in plans and engage in solutions to ensure system compatibility. That covers all. Now Requirements (Basic Qualifications) list: - 10+ years as a systems engineer / integrator - Current active TS clearance with ability to obtain TS/SCI - Expert communication skills in a team setting - Experience on agile, go-fast programs Now Skills (Desired Skills) list: - Experience with Agile and DevOps delivery process, to include Jira/Confluence/Gitlab interfaces - Knowledge of Global Security ground systems and its interfaces with other systems - Experience with system-level modeling in Cameo or other MBSE tools - Python scripting experience Now Benefits: list all benefits mentioned. We need to capture all benefits: 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 preserve all that detail. Should we include the Washington state specifics as part of benefits? Yes. Thus benefits list items: - Medical - Dental - Vision - Flexible work arrangements and schedules (e.g., 4x10) - 401(k) match - Paid time off - Holidays - Parental Leave - EAP (Employee Assistance Program) - Flexible Spending Accounts - Education Assistance - Life Insurance - Short-Term Disability - Long-Term Disability - Annual short-term and/or long-term incentive compensation programs (not guaranteed, vary year to year, tied to performance metrics) - For Washington state applicants only: - Non-represented full-time employees: accrue at least 10 hours per month of Paid Time Off (PTO) 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 format as
- for any list. For the Washington state specifics, we could have nested list or just include as part of li text. Probably simplest: include as li with the details.
Now Pay: we have salary range: Full-Time Salary Range: $145100.00 - $269500.00. Also note: "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."
We need to preserve all substantive information. So we should include that prose about salary being guideline and factors considered. That's part of Pay section.
Thus Pay section:
Full-Time Salary Range: $145100.00 - $269500.00
plusAt Lockheed Martin, we know mission success starts with taking care of our people. Our Total Rewards program is designed to attract top talent
- for any list. For the Washington state specifics, we could have nested list or just include as part of li text. Probably simplest: include as li with the details.
Now Pay: we have salary range: Full-Time Salary Range: $145100.00 - $269500.00. Also note: "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."
We need to preserve all substantive information. So we should include that prose about salary being guideline and factors considered. That's part of Pay section.
Thus Pay section: