System Engineer Security Clearance

Systems Engineer (Software Obsolescence)

Twenty (20) years of experience as a Systems Engineer in programs and contracts of similar scope, type and complexity is required. Demonstrated experience in planning and leading Systems Engineering efforts is required. A bachelor’s degree in Systems Engineering, Computer Science, Information Systems, Engineering Science, Engineering Management, or a related discipline from an accredited college or university is required. Five (5) years of additional Systems Engineering experience may be substituted for a bachelor’s degree.

• Assist with the development of system requirements and functional requirements and allocate 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.
• Allocate real‑time process budgets and error budgets to systems and subsystem components.
• Generate alternative system concepts, physical architectures, and design solutions.
• Define the methods, processes, and evaluation criteria by which the systems, subsystems and work products are verified against their requirements in a written plan.
• Develop system design solutions that satisfy the system requirements and fulfill the functional analysis.
• Review and provide input to program and contract work breakdown structure (WBS), work packages and the Integrated Master Plan (IMP).
• Participate in the development of system engineering documentation, such as System Engineering Plans, Initial Capability 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.
• Derive from the system requirements an understanding of stakeholder needs functions that may be logically inferred and implied as essential to system effectiveness.
• Derive lower‑level requirements from higher‑level allocated requirements that describe in detail the functions that a system component must fulfill, and ensure these requirements are complete, correct, unique, unambiguous, realizable and verifiable.
• Participate in establishing and gaining approval of the definition of a system or component under development (requirements, designs, interfaces, test procedures, etc.) that provides a common reference point for hardware and software developers.
• Develop derived requirements for Information Assurance Services (Confidentiality, Integrity, Non‑repudiation, and Availability);
  Basic Information Assurance Mechanisms (e.g., Identification, Authentication, Access Control, Accountability); and Security Mechanism Technology (Passwords, cryptography, discretionary access control, mandatory access control, hashing, key management, etc.).
• Implement comprehensive Service‑Oriented Architecture (SOA) solutions.
• Implement operational and technical standards views, and system and service views for architectures using applicable DoDAF standards.
• Review and/or approve system engineering documentation to ensure that processes and specifications meet system needs and are accurate, comprehensive, and complete.
• Capture all interface designs in a common interface control format and store interface data in a commonly accessible repository.
• Assess each risk to the program and determine the probability of occurrence and quantified consequence of failure in accordance with an approved risk management plan.
• In conjunction with system stakeholders, plan the verification efforts of new and unproven designs early in the development life cycle to ensure compliance with established requirements.
• Prepare time‑line analysis diagrams illustrating the flow of time‑dependent functions.
• Establish a process to formally and proactively control and manage changes to requirements, consider impacts prior to commitment to change, gain stakeholder buy‑in, eliminate…