Technical Architecture & Delivery Lead architecture decisions across the portfolio — schema design, API contracts, integration patterns, workflow orchestration, and when to integrate via direct API versus MCP (Model Context Protocol), weighing latency, control, security, auditability, and reusability tradeoffs Hold delivery accountability — scope, timeline, quality — across all active workstreams, in partnership with the Director who owns product requirements and prioritization Design and own the Postgres data schema underpinning the product (multi-table: pipeline data, access control, cost attribution, audit) — correctness and extensibility here is foundational, not incidental Build and own the Claude/API integration layer: system prompt design and testing, multimodal document ingestion for XLSX, DOCX, PPTX, and PDF via reliable extraction/conversion pipelines, structured output parsing, schema validation, and fallback handling Design practical automation workflows — background jobs, ...