Own the programs that movevision to measurable impactin the Frontier era.
Microsoft's Industry Solutions Delivery org is hiring a Principal Project Manager — the single-threaded Program Director for complex, multi-workstream AI and digital transformation programs. I bring a decade of high-agency, single-threaded founder/CIO delivery ownership, AI-first execution already in production, and my strongest Canadian tie in Toronto — mapped to the posting requirement by requirement, every verdict with a receipt.
Vision to value. AI-first delivery. Adoption that sticks.
Single-threaded delivery from vision to outcome
As co-founder → Engineering Manager → CIO I am the one accountable across design, engineering, QA, product and business — a 22-person cross-functional core delivering vision-to-adoption across nine geographies. That single-threaded ownership is the seat this role names, not a motion I would be learning.
Ministry-level clinical rollout — 64 doctors, 13,340 schedules, 7 centers on the patient-data pipeline and EHR interoperability I architected under HIPAA.
Six-plus years Zürich engagement → 2026 acquisition — GDPR and EU VAT compliance built directly into payment flows.
26-year export house turned AI-native — the client team self-serves through a Claude-powered CMS behind CI/CD gates; zero developer dependency.
Norway fintech pod — Vipps-integrated product built to PMF, then a clean handover to the client's in-house team.
AI-accelerated delivery, already in production
Claude-led delivery with governance-gated agent work ('s CMS), agent skills, hooks and evals that cut cost and time — the JD's AI-first delivery mandate is how I already run programs, not a capability I am proposing. Anthropic Claude Code 101 and Introduction to Agent Skills certifications are dated proof.
Outcomes measured by what customers actually use
Value realization is where I keep receipts — 's Ministry-level clinical rollout (64 doctors · 3,242 patients · 13,340 schedules · 7 centers), Frontgo's PMF handover, a legacy export team that self-serves its own content now. Adoption and organizational readiness, not just a shipped plan.
Together we move customers from vision to measurable impact — owning the program end to end, with AI-first delivery that makes the adopted outcome, not just the plan, the deliverable.
I own the program from the customer's business objective to the moment their team actually adopts the outcome — and I use AI to make that path more predictable, not less governed.
Fauzul — on why Microsoft ISD
Every verdict above maps to shipped work. Pick one and challenge it.
Questions a sharp hiring loop would raise.
The objections a sharp Program Director hiring loop would raise — including the ones the gaps invite — answered straight.
Have you led a multi-million-dollar enterprise transformation program at Fortune-500 scale?
Not at that scale, and I won't pretend otherwise. My single-threaded ownership is real and decade-deep — vision through adoption across nine client geographies, a 22-person cross-functional core, 's clinical platform to Ministry-level rollout — but it has been founder/startup- and mid-market-scale, not Fortune-500 multi-million-dollar, multi-workstream consulting programs. The ownership motion transfers directly; the program size is the ramp, and I'd scale into it with ISD's PMO and account teams rather than claim it's already my day scale.
You're a founder/CIO, not a titled Project Manager with 7+ years and a PMP — does that qualify?
The JD's operative clause is '7+ years of project management OR equivalent experience.' I bring the equivalent: 9+ years of accountable, single-threaded delivery ownership plus CSPO for product and backlog governance. My education line is Computer Science & Engineering at North South University (2012–2015) — I don't claim a completed degree or a titled-PM tenure. Equivalent experience is the honest and qualifying frame.
How would you manage program financials, contractual commitments and forecasting?
This is my most honest gap. I bring founder commercial ownership — pricing and scoping engagements, P&L, disciplined cloud-cost economics — but I have not run formal delivery financials, contractual commitments and forecasting for a multi-million-dollar consulting program. The JD pairs that responsibility with account-team partnership, and that's exactly how I'd close it: lean on commercial instinct immediately, build program-financial governance rigor with Microsoft's account and commercial leads, named as a ramp, not a claim.
Your AI is Claude-led — this role delivers Copilot and Azure AI. Isn't that a mismatch?
AI-first delivery discipline is model- and platform-agnostic — the value is knowing how to prioritize high-yield AI use cases, accelerate delivery with agents, and keep it governed, and that's exactly what I do. My production stack has been Claude-led for client delivery — model and harness picked per task, not vendor loyalty (Gemini second, Kimi via OpenRouter on ) — and I have genuine Azure touchpoints — a Microsoft-curriculum Azure ML certification and production Gemini TTS via Azure. I'd learn and deliver Microsoft's Copilot/Fabric/Azure AI stack for customers on top of that discipline, and I'd never claim depth I don't have.
Can you operate inside a large matrixed delivery org after running your own?
I've led a 22-person cross-functional core and client pods across nine geographies, with alumni now leading engineering in Norway (2), Canada and Germany — and influence-without-formal-authority is founder-native. The honest adjacency is that I've led my own organization, not been a node inside a Fortune-500-scale matrix. Moving through Microsoft's internal matrix — Customer Success, Industry Advisors, Forward Deployed Engineering, account teams — is first-quarter orientation, not a leadership gap.
Yes, and it's my strongest Canadian tie — not a cold bet. I've delivered for Canadian clients for four years (, SkyTracks & SoftCollab, working with the client's technical CTO), plus fractional CTO work in Quebec and FDE engagements in Toronto, and a family visit meant I already lived in Toronto for six months. 's international build even centres its growth corridor on Canada. This ISD seat is deliberate relocation to a city I already know firsthand, set up for the 2-days-a-week hybrid from day one.
Claude-led, model picked per task, not by vendor loyalty.
The delivery and AI-first stack behind the claims — Claude-led for production delivery, model picked per task not vendor loyalty, with honest Azure touchpoints.
from vision_to measurable impact.
Toronto is my strongest Canadian tie, not a fresh bet: six months already lived in the city during a family stay, four years of delivery for Canadian clients, fractional CTO work in Quebec, and FDE engagements in Toronto itself. Canada is where my work has kept returning for a decade — this ISD seat makes it official. Set up for the 2-days-a-week hybrid from day one; see Toronto for the full picture.
Four other Microsoft seats, each in its own register.
A personal application fit page, not affiliated with or endorsed by Microsoft. Copilot / Azure / Fabric / ISD references are illustrative of the role's own team and domain — no confidential or internal Microsoft information is shown.