Senior Technical Product Manager TS/SCI CLEARED

Most software fails before a line of code is written.

Over ten years leading cross-functional product teams from ambiguity to shipped software — for the U.S. Space Force, the Navy, and venture-backed startups. My method: strip a product down to the mandatory end-to-end capability first, then deliver engineering a specification precise enough that “done” was never in question — fast, and without the rework that comes from starting before the scope was ever clear.

Washington, DC
0→1

Code to shipped product, U.S. Space Force

Clearance: Top Secret / SCI
8 mo

Kickoff to Increment Demonstration

10+ years in product
10

Engineers led on that build

 
50%

Faster reference lookups, U.S. Navy submarines

Scroll to travel 2015 → present
How I work · Road rules
01

Clarity before execution

Before anything gets built, I find the big picture the product is actually solving, then strip away everything that isn’t mandatory. What remains is the minimum end-to-end capability the system needs to stand on — the foundation, laid properly, so nothing has to be re-poured later.

02

Design from the user’s view

Before engineering starts, I design and prototype the solution from the user’s perspective — so the team can iterate rapidly through mockups and flows instead of through code. It’s far cheaper to change a prototype than a codebase, and it keeps future technical debt out of the system entirely.

03

Specify the work

I define the specific scope of work before a line of production code exists — walking the full end-to-end flow, validating that what’s planned is actually what the system needs to do, and writing it up as a specification engineering can build against without guessing.

04

Then engineers build it

Once the flow is validated, engineers build against a scope that’s already correct. Technical debt gets mitigated at the source: it’s cheaper to think clearly once than to refactor an unclear system twice.

“Understand the big picture first, then strip out everything that isn’t mandatory. What’s left is the foundation — get that right, and the engineering takes care of itself.”
— Yonathan Micael, on scoping before building
Selected work · The route

Products shipped under pressure, for organizations that can’t ship twice.

MILE
2015
Mar ’15 — Sep ’16
NASA Center for Climate Simulation / NIST NCCoE

Web Developer II

Advised NASA’s Climate Simulation Department and NIST on prototyping future concepts, and managed a no-downtime migration to a new web platform and CMS.

MILE
2016
Feb ’16 — Jun ’23
DayShyft

Senior Technical Product Manager

Built the MVP roadmap, hired designers, and led a Ruby on Rails / AngularJS product from ideation to launch, architecting the AWS build and deployment environments myself.

MILE
2016
Mar ’16 — Jul ’21
Dynamic Solutions, LLC

Technical Product Manager, U.S. Navy consulting

Cut sailors’ reference-material lookup time by 50%, converting ~10,000 parts of Excel data into a relational database and pitching the solution to win two RFPs worth $2.5M.

Cutting sailors’ reference-lookup time in half for the U.S. Navy

As Technical Product Manager at Dynamic Solutions, LLC, I advised the U.S. Navy on a reference-materials system for sailors aboard submarines — scoping the end-to-end flow from raw Excel data to a queryable database before choosing a single line of the stack, then pitching the solution to win two RFPs.

  • Wireframed and delivered reference software against government requirement guidelines
  • Built ETL tooling to convert Excel spreadsheets into a relational SQLite database
  • Designed the relational structure to hold ~10,000 parts per naval ship delivered
  • Chose the language, framework, and database, then hired contractors to build the frontend
  • Delivered a Python and Spring Boot interface, cutting operation processing time by 50%
  • Pitched the solution to win two RFPs worth $2M and $500K
MILE
2017
Jan ’17 — Sep ’22
UnionBase

Senior Technical Product Lead

Architected the design, build, and deployment of an independently-funded platform in 7 months, managing 3 developers and 2 designers to serve ~3,000 members.

MILE
2023
Jun ’23 — Present
CACI International

Product Owner

Delivered a functioning DSP product to the U.S. Space Force from zero developed code within 8 months, leading a 10-person team using agile delivery on Docker and Kubernetes.

Zero to a fielded product for the U.S. Space Force

As Product Owner at CACI International, I led a 10-person team from zero developed code to a functioning DSP product delivered to the United States Space Force in eight months — defining scope with the mission in view.

  • Built risk-mitigation plans to protect each Increment Feature Demonstration
  • Ran agile delivery on Docker and Kubernetes, iterating and deploying continuously
Skills · Carried on board

Product & leadership

Product managementAgile methodology Cross-functional leadershipStrategic planning Risk assessmentUX design Market research & analysis

Delivery approach

Scope definitionEnd-to-end flow validation Rapid prototypingEngineering specifications Technical-debt mitigation

Technology

Ruby on RailsGroovy on Grails Spring BootJavaJavaScript PythonAngularReact AWSDockerKubernetes
Destination

Building something that needs scoping before it needs code?

B.S. Electrical Engineering Technology, minor in Computer Science — Old Dominion University.

Top Secret/SCI cleared, based in Washington, DC.