Systems Engineer Level 3-FFLL

REQUIRED

• TO BE CONSIDERED FOR THIS POSITION YOU MUST HAVE AN ACTIVE TS/SCI W/ FULL SCOPE POLYGRAPH SECURITY CLEARANCE (U.S. CITIZENSHIP REQUIRED)

• Experience gathering, analyzing, and documenting user and system requirements.
• Experience developing systems engineering artifacts such as requirements specifications, interface control documents, systems engineering plans, and related technical documentation.
• Experience working directly with customers, users, and stakeholders to understand operational workflows and mission needs.
• Ability to translate complex operational challenges into clear, structured requirements for technical teams.
• Experience supporting workflow analysis, process improvement, or capability planning efforts.
• Strong technical writing, communication, and documentation skills.
• Ability to coordinate across multidisciplinary teams and maintain alignment between users, engineers, and leadership.
• Strong organizational and problem‑solving skills with the ability to manage multiple priorities.

• Experience with Agency dataflow, compliance, policy, and data‑governance, as it pertains to Corporate Tools and Analyst workflow.
• Experience managing teams and threads with complex multi‑regional systems with large datasets.
• Experience supporting analyst workflows, mission visibility, or contextual data tracking capabilities.
• Familiarity with content triage, transcription workflows, language analysis, or sourcing‑related mission areas.
• Experience with requirements management, traceability, interface definition, and lifecycle planning.
• Experience developing concepts of operation, workflow documentation, and customer‑facing systems engineering products.
• Strong understanding of systems engineering processes and mission‑focused capability development.
• Ability to communicate effectively with both technical teams and operational users.
• Experience coordinating and integrating AI Technologies within the development workflow.

• Experience as Agency Analyst
• Experience with Enterprise Data Labels and Data Formats

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

• 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) Service‑oriented Architecture (SOA), etc.
• 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.
• Derive from the system requirements a 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…