Vetted SpecialistsExample profileGreg H.Spacecraft Systems EngineerSystem-level lead for a 400 kg Earth-observation bus: owned 1,900 requirements in Jama with full bidirectional traceability and closed the verification matrix at pre-ship review with zero open liensBuilt the SysML architecture model in Cameo and used it to auto-generate 11 subsystem ICDs, cutting interface discrepancies found at integration from 38 on the prior vehicle to 4Ran the propulsion trade (electric vs. green monoprop) with a weighted decision matrix that survived customer review and saved 22 kg of dry massMBSE / SysMLRequirementsICDs
Vetted SpecialistsExample profileRicardo P.Weapon System Lead Systems EngineerLead systems engineer for a loitering munition under an Army OTA: authored the SEP, chaired the interface control working group, and took the system through SRR, PDR and CDR with no major action items open past 30 daysOwned the technical risk register (62 risks, 41 retired before qualification) and presented monthly to the government program officeWrote the V&V plan mapping 340 requirements to DT/OT events and MIL-STD-810 qualification tests; verification closed six weeks ahead of the milestoneDoD acquisitionRisk managementV&V planning
Vetted SpecialistsExample profileTamara J.Launch Vehicle Systems EngineerVehicle-level systems engineer for a small-lift launcher: owned the mass, power and link budgets across four subsystem teams and held margins through two design cyclesAuthored the range safety and payload-to-vehicle ICDs and coordinated the payload interface with three external customers on the same manifestStood up the DOORS-to-Cameo requirements pipeline and the configuration control board process for a 60-person engineering teamBudgets & marginsPayload interfaceConfiguration control