Technical Product Manager

Must Haves:

• Apache Airflow 3.x
• Hybrid Azure/AKS + on-prem infrastructure literacy
• Postgres
• Redis

• Demonstrated experience authoring
  ** specifications consumed by an isolated implementation team** — clean-room reverse engineering, regulated/defense work, or formal spec-to-vendor handoffs.
• Understands that
  ** the spec is the only communication channel.
  ** Writes requirements that are
  * complete on first contact* — every file path, import, config value, error string, and acceptance criterion is present, because the "single turn, no follow-up questions" standard is the acceptance bar for their own output.
• Comfortable with the wall cutting
  ** both ways**: they cannot see the clean-room code, and they cannot talk to the developers. They validate through
  ** observable test outcomes only**, never by reading the implementation.

• Technical product / technical program management on platform or data-infrastructure products (not consumer apps).
• Track record writing
  ** acceptance-criteria-driven specs validated by automated test suites**, not demos.

• ** Pathological precision and completeness** — "good enough, we'll clarify later" is not the right approach. Ambiguity is a defect.
• ** Empathy for an audience they will never speak to** — must anticipate every clean-room question and pre-answer it in the spec.