Systems Engineering SME

What you will need:

• Minimum of 16 years with BS/BA;
  Minimum of 14 years with MS/MA;
  Minimum of 10 years with Ph.D.

• Critical engineering milestones, and associated documentation such as System Requirements Reviews (SRR), Preliminary/Critical Design Reviews (PDR/CDR), and Engineering Review Boards (ERB).
• Assessment, deployment, and integration of complex technical solutions integrating government and industry technologies with Commercial Off-The-Shelf (COTS) solutions into an operational architecture.
• Technical risk management to include continuous technical risk assessment across project lifecycle, identifying critical path bottlenecks evaluating technical debt, and formulating ongoing risk mitigation strategies and contingency plans to support operational sustainment.
• Operational acceptance and evaluation of integration strategies to ensure that systems align with existing operational baseline metrics and can be fully supported and sustained within the current infrastructure without degrading legacy capabilities.
• Expertise in the technical infrastructure of the Naval Oceanographic Office and the technical interface with external organizations including NRL, ONR, and APL‑UW at a level sufficient to lead cross‑organizational coordination.
• Secret security clearance.

Peraton is hiring a part‑time Systems Engineering SME in a hybrid position at the Stennis Space Center to provide project management for continuous technical oversight across parallel modernization tracks to ensure the project's technological critical path is sound and viable for operational sustainment. Core daily and monthly activities include providing technical expertise for risk assessment, guiding the transition of software into operational environments, and conducting expert review and validation of critical systems engineering documentation and project planning materials.

• Requirements Analysis & Traceability:
  Oversee the requirements traceability matrix (RTM) on an ongoing basis across to verify that all operational deficiencies are addressed by the proposed architecture. Integration & Interface Assessment:
  Regularly review Interface Control Documents (ICDs) to identify potential interoperability issues between disparate systems (e.g., legacy decoders, autonomy engines, and C2 interfaces) prior to operational fielding.
• Operational Acceptance and Readiness Evaluation:
  Evaluate integration strategies to ensure that systems align with existing operational baseline metrics and can be fully supported and sustained within the current infrastructure without degrading legacy capabilities.
• Oversight of Systems Transition & Lifecycle Planning:
  Develop and refine engineering recommendations for the continuous transition of software from development to operational sustainment. Assess deployment configurations, environmental requirements, and long‑term sustainment viability.
• Technical Review Facilitation:
  Plan, facilitate, and provide expertise during ongoing critical engineering milestones, including System Requirements Reviews (SRR), Preliminary/Critical Design Reviews (PDR/CDR), and Engineering Review Boards (ERB).
• Executive Technical Communication:
  Routinely synthesize complex systems engineering data, test results, and integration risks into clear, actionable information. Prepare, review, and deliver high‑level technical briefings and decision memos for senior‑level leadership as required.