Coach the engineers whohelp customers innovatewith Cloud and AI.
Microsoft's Azure Solution Engineering team is hiring a people-manager to lead and develop a team of Solution Engineers, own customer and partner relationships, and drive pipeline. This page maps that seat to a decade of running its core motions: coaching a 22-person team into engineers who now lead abroad, customer trust measured in years rather than quarters, and Cloud & AI shipped daily — Azure included, hands-on. Every claim below carries a receipt.
Coaching people. Customer credibility. Cloud & AI, lived.
Grow engineers into their best next role
Weekly 1:1s and design/code review as default; judgment over activity. I led a 22-person cross-functional core (52+ with contractors) from Engineering Manager to CIO, and the engineers I coached now lead in Norway (2) and at two top local firms, with others grown into graduate study in Canada and a UX design career in Germany. Microsoft's Model · Coach · Care is a framework I would adopt over a coaching instinct that is already proven, not invent from scratch.
Customer trust earned on technical depth
Client relationships measured in years, not quarters — six years with to its Loopcloud acquisition, four with , SkyTracks & SoftCollab, two-plus and counting with . I speak to IT leaders, business decision-makers and developers without a translation layer, which is exactly the trusted-advisor motion this role runs on.
Honest about the sales-org ramps
Formal pipeline generation, forecasting accuracy and quota accountability is named as the one real gap, not dressed up as a strength. That candour — pointing at the single honest ramp rather than hiding it — is the same discipline the whole application runs on.
The coaching, the customer credibility, and the Cloud & AI fluency — Azure included — I bring today. The formal pipeline discipline I would earn fast — named honestly, not oversold.
The trusted-advisor job is coaching a team and owning a customer relationship at the same time. I have done exactly that inside a customer's codebase — and handed it over clean.
Fauzul — on why Microsoft, candidly
Every verdict above maps to shipped work. Pick one and challenge it.
Questions a sharp hiring loop would raise.
The objections a sharp hiring loop would raise for a founder-operator applying to a pre-sales sales-org people-manager seat — answered straight.
Because the rest of the seat — coaching a team of Solution Engineers, being the trusted technical advisor to enterprise customers, orchestrating stakeholders, and understanding what Cloud & AI actually does for a business — is proven at real scale, and I'd rather be honest that formal pipeline/forecast/quota ownership is the gap than pretend otherwise. I'd expect to pair closely with a sales-manager or segment peer on the number specifically, while I bring the coaching and technical credibility that make the SE team's solutions land.
This is an Azure seat — how credible are you on Azure specifically?
Credible, and honest about the edges. I'm hands-on with the Azure API, hold a light Azure ML AutoML certificate, and ship Gemini TTS via Azure — on top of cloud-agnostic architecture across Azure, AWS (ECS, Lambda, EventBridge, DynamoDB, CloudFormation, IAM/WAF) and GCP (Cloud Run), so the architecture, migration and cost-discipline muscle is real and multi-cloud. Azure isn't foreign to me. What's lighter is deep enterprise Azure migration delivery at SE-org scale day to day — that specific depth I'd sharpen fast with the team, but I'm not starting from zero on the platform. Worth noting: Microsoft's own posting insights list AWS as the top skill among previous hires into this discipline — multi-cloud arrivals are the norm here, not the exception.
You've managed product and delivery engineers, not pre-sales Solution Engineers in a sales org. Does your coaching transfer?
The coaching instinct transfers directly — weekly 1:1s, design and code review, growing judgment over activity, and a measured record of engineers I coached now leading in Norway, Canada and Germany. What's new is the sales-org context: coaching against pipeline stages and customer-facing SE outcomes rather than delivery milestones. I'd learn that context fast, but I won't pretend I've already managed a pre-sales team inside a vendor.
Do you actually have technical pre-sales or consulting experience?
Not under that title. A decade of client discovery, technical scoping, solution architecture, RFP responses and SOW authoring at is technical consulting by any honest reading — and the posting allows equivalent experience — but it wasn't inside a vendor's pre-sales function. I'm framing it as equivalent experience with a real ramp onto Microsoft's SE motion, not as a like-for-like match.
Why Calgary, and is 25–50% travel realistic for someone relocating?
Canada isn't a cold move: four years delivering for , SkyTracks & SoftCollab with the client's technical CTO, fractional CTO work in Quebec, FDE engagements in Toronto, and six months already lived in Toronto during a family visit. Calgary is a deliberate relocation on real Canadian history, and the travel is the same muscle as nine geographies of client delivery — I'm comfortable being wherever the customer is.
Do you have a completed degree?
Field of Study: Computer Science & Engineering at North South University (2012–2015). I don't claim a completed degree. The role allows equivalent experience — a decade of shipped, customer-facing technical leadership is the operative credential.
Claude-led, model picked per task, not by vendor loyalty.
The stack and receipts behind the claims — Cloud & AI lived daily, Claude-led for production delivery, model and harness picked per task, with Azure familiar (API + light cert) and genuine multi-cloud depth.
help customers innovate_with Cloud and AI.
Canada is a professional tie, not a cold move: four years of delivery for Canadian clients, fractional CTO work in Quebec, FDE engagements in Toronto, and six months already lived in Toronto during a family stay. Relocating to Calgary is deliberate intent built on a decade of work that kept returning to Canada. And the 25–50% travel is welcomed — being wherever the customer is has been the job across nine geographies already.
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.