About the role
Operational requirements arrive in the language of the mission. Designs get built in the language of interfaces, budgets, and specifications. This role does that translation and then holds the design accountable to it all the way through delivery.
Working within the architecture set by the chief engineer and system architect, you will decompose operational requirements into buildable specifications, define and maintain the interfaces between subsystems, and keep traceability intact from the customer document to the verification evidence. As the design evolves, you are the one tracking whether it still satisfies what was asked for, and raising it early when a decision several levels down has inadvertently broken a top-level requirement.
This is a rigor role rather than an authority role. Architecture decisions belong to the chief engineer; you make sure those decisions are specified precisely enough to build against, and that what gets built matches what was specified.
What you will do
Requirements engineering
- Decompose customer and operational requirements into system, subsystem, and component-level specifications
- Establish and maintain requirements traceability from customer documents through verification evidence
- Identify requirement conflicts, gaps, and untestable language before they become problems
- Manage requirement changes and assess their downstream impact across the design
Interfaces and system budgets
- Author and maintain interface control documents for internal subsystems and external platform interfaces
- Maintain and track RF chain, timing, data rate, processing, and SWaP budgets developed with subsystem leads; flag when allocations are being consumed faster than planned
- Maintain system block diagrams, functional decompositions, and specification documentation
- Coordinate interface agreements across engineering disciplines and with integration partners
Design accountability through delivery
- Assess design artifacts and implementation decisions against allocated requirements as the baseline matures
- Develop verification cross-reference matrices and coordinate verification approach with the test team
- Review test results against requirements and confirm closure of verification objectives
- Support configuration management and baseline control across program milestones
Reviews and documentation
- Prepare artifacts for SRR, PDR, CDR, and TRR events and support their execution
- Track and close review action items across the engineering team
- Produce the specification and analysis documentation that goes to the customer
Customer and partner support
- Support technical interchange meetings and customer working groups
- Translate between operational language and engineering language in both directions
- Contribute to technical volumes for proposals and white papers