Systems Engineer Level 2 -FFLL-8958

About the role

The team is looking for a hands-on DevOps professional with strong troubleshooting skills.

Requirements

• Active TS/SCI with full scope polygraph security clearance (U.S. citizenship required)
• Fourteen (14) years of experience as a Systems Engineer in programs and contracts of similar scope, type, and complexity
• Bachelor’s degree in System Engineering, Computer Science, Information Systems, Engineering Science, Engineering Management, or a related discipline from an accredited college or university; five (5) years of additional SE experience may be substituted for the degree

Skills

• NetApp Storage Administration
• Rancher
• VMware vSphere
• Linux System Administration
• Kubernetes (familiarity helpful)
• Kubernetes NetApp plugin
• Ability to obtain SYS1 access

Responsibilities

• Contribute to the development of sections of systems engineering documentation such as System Engineering Plans, Initial Capabilities Documents, Requirements specifications, and Interface Control Documents
• Manage system requirements and derived requirements to ensure the delivery of production systems that are compatible with the defined system architecture(s)
• Assist with the development of system requirements, functional requirements, and allocation of the same to individual hardware, software, facility, and personnel components
• Coordinate the resolution of action items from Configuration Control Board (CCB) meetings, design reviews, program reviews, and test reviews that require cross‑discipline coordination
• Participate in an Integrated Product Team to design new capabilities based upon evaluation of all necessary development and operational considerations
• Participate in the development of system engineering documentation, such as System Engineering Plans, Initial Capabilities Documents, Requirements Specifications, and Interface Control Documents
• Participate in interface definition, design, and changes to the configuration between affected groups and individuals throughout the life cycle
• Allocate real‑time process budgets and error budgets to systems and subsystem components