Embedded FDE & Production Lead Azure Deployments

• The Role

• You are an embedded builder who bridges frontier AI products and production-grade reality inside our clients' operations. After our Fusion Discovery practice ships the prioritized roadmap, you are the named technical principal who turns that roadmap into running software — code, deploy, integrate, ship — inside the client's Azure subscription, against their data, under their compliance constraints, on the calendar they signed up for.

• You are the FDE in the literal sense the term means in 2026: an embedded operator with a founder's mindset who owns outcomes end to end. Discovery hands you a scoped milestone roadmap and a Statement of Work. You take it from there. You can expect to travel up to 30% of the time with this position.

• What This Role Is — And What It Is Not The FDE market is hot in 2026 and the role definition varies wildly across companies. PTM's flavor is specific, and we are explicit about it.

• You will: write production code that ships into the client's runtime. Build agentic systems with PydanticAI. Stand up event-driven ETL on Azure Container App Jobs. Scaffold lovable.dev → Static Web App frontends backed by FastAPI or ASP.NET Core BFFs (Backends-for-Frontends). Provision the whole stack with Bicep + azd. Wire structured logging, LLM cost telemetry, and the auth gateway from commit #1.

Own the engagement's technical outcome.

• You will not: run discovery interviews, facilitate executive prioritization workshops, or produce the Solution Architecture Document. Our Fusion Discovery practice does that upstream and hands you their output. You may sit in on the final readout to take ownership of the implementation phase. The customer-facing volume sits with Discovery. You carry the technical volume.

• If you came into the FDE category because you want to be the engineer who actually ships the system the slideware promised — at a firm where validators are written before production code, every interface gets a documented contract, and the first commit boots a working full local stack — this is the role.

• The Outcome We Hire You For

• In your first twelve months, you will serve as the technical lead on three to five Fusion Development engagements. Each one ships:
• - A working production deployment in the client's Azure subscription, deployed via azd up and reproducible on demand.
• - Vertical slices of demonstrable client value delivered against the milestone roadmap from Discovery.
• - At least one KPI moved, with structured telemetry to prove it.
• - A clean handoff document for ongoing operations: runbooks, infrastructure contracts, and the digital twin of the decisions made along the way.

• What You Will Actually Do

• Approximate time split: ~45% writing code, ~30% integration, infrastructure, and observability plumbing, ~15% client technical touchpoints (architecture standups, demo days, escalations), ~10% specifications, interface contracts, and engagement reflections. The customer-facing volume is lower than Big Lab FDE pool roles because PTM's Discovery practice carries the customer-facing volume upstream.
• - Convert the Discovery roadmap into an executable engineering plan with swimlanes, interface contracts, and validator-first todos.
• - Scaffold the first commit as a working local full stack — frontend, backend, database, auth gateway, observability, IaC (Infrastructure as Code) — bootable with one command on a fresh clone. We do not believe in scaffold-then-wire-later.
• - Implement Python services (FastAPI BFFs, event-driven ETL on Azure Container App Jobs, PydanticAI agentic systems) under our RPIR validator-first loop:
Research, Plan, Implement validators RED, implement production code GREEN, Review.
• - Build ASP.NET Core BFFs when the client's existing investment or team strength calls for it. Use .NET Aspire App Host for local orchestration when there are three or more services or any polyglot mix.
• - Wire frontends scaffolded via lovable.dev into your BFF, hosted on Azure Static Web Apps.
• - Stand up the Azure footprint with Bicep + azd: subscription-level deployments, module contracts, mandatory tagging, Key Vault-backed configuration, and what-if gates on…