Architect the browser experienceevery Fabric workloadlives inside.
Microsoft's Fabric Platform Shell team — expanding to Vancouver — is building the best SaaS data-development environment on the web: a unified, extensible studio where developers create items, schedule and monitor production jobs, and stay in flow without leaving the browser. This is senior web-architecture work in React and TypeScript, with DRI-grade reliability, telemetry and UX partnership in one mandate — the frontend-architecture seat I have run with high agency as a founder-operator for a decade. Vancouver's three-day hybrid is a deliberate Canada move.
Browser architecture. Gated delivery. Live-site ownership.
Ship the browser experience that scales under real load
I design and deliver React/TypeScript applications and data-heavy UIs for the web — from a real-time Angular + Web Audio collaboration studio () to HIPAA clinical dashboards () — with testing, CI/CD and telemetry as defaults, not afterthoughts.
A gallery, not a wireframe — my own shipped browser surfaces on the facet grammar. Never a Fabric screenshot.
Architecture that survives workloads and scale
Senior work means setting direction for component systems, APIs and integrations while debugging cross-cutting production issues. At I owned that loop end to end — feasibility with product, phased delivery, measurable milestones across nine geographies — and consolidated web, shared libraries and admin tooling on an NX monorepo so many engineers could ship without fragmenting the codebase.
Live-site ownership is a founder reflex, not a rotation
When you co-found the company, you are always the DRI. I integrate logging and telemetry, own incidents through to resolution, keep rollback plans ready, and keep the troubleshooting docs honest — the same reliability instinct behind the JD's live-site mandate.
Together we build the web studio developers stay in — a unified, reliable browser experience where every Fabric workload feels like it belongs.
I build the web experiences customers actually work inside — then I hold the standards, telemetry and incident discipline that let a team keep shipping to them safely.
Fauzul — on why Microsoft Fabric
Every verdict above maps to shipped work. Pick one and challenge it.
Questions a sharp hiring loop would raise.
The objections a sharp senior front-end loop would raise — answered straight.
The JD lists C, C++ and C# among the languages — those aren't in your stack.
Correct — my languages are TypeScript, Python and Go. The minimum requirement is an OR list ('C, C++, C#, Java, JavaScript, or Python'), and I satisfy it directly through JavaScript and Python. More to the point, this is a web front-end seat — React, TypeScript, HTML, CSS — which is exactly my daily surface. If backend collaboration ever needs C#, it's a short on-the-job ramp, and I've named it honestly rather than padding a language list.
Fabric is a data-analytics platform — have you actually built for analytics systems?
I build data-heavy web UIs, not data-analytics tooling as a titled specialism — and I'm candid about the difference. 's clinical dashboards, 's match analytics, and 's telemetry surfaces are the closest analogues: dense data rendered legible and fast in the browser. I'd own the Platform Shell's web-experience layer from day one and ramp on Fabric's analytics-workload domain with the team, rather than overclaim it.
Any concern passing the Microsoft Cloud Background Check?
None — happy to complete it on hire and every two years. My delivery record is compliance-heavy by choice: HIPAA clinical systems, GDPR/VAT commerce, WCAG accessibility across five client organisations. Passing a cloud background check is a straightforward step, not a hurdle.
Are you actually relocating to Vancouver?
Yes — and it isn't a cold bet. I've delivered directly for Canadian clients for about four years (, SkyTracks & SoftCollab, working alongside the client's technical CTO), plus fractional CTO work in Quebec and FDE engagements in Toronto — and a family stay gave me six months in Toronto firsthand, so the country isn't unfamiliar. Vancouver's three-day hybrid is the kind of senior web-architecture work I'm moving for, and it happens to be one of Microsoft's largest engineering campuses outside Redmond.
Do you have a CS degree?
Field of Study: Computer Science & Engineering at North South University (2012–2015). I don't claim a completed degree. The JD allows equivalent experience — a decade of shipped senior-level web systems, exceeding the 8-year preferred band, is the operative credential.
This is framed as a Software Architect on the Platform Shell — where's the senior architecture level?
I've held that shape for years — co-founder → Engineering Manager → CIO at , still hands-on daily, setting architecture for browser applications while owning delivery, standards and the live site. Senior for me is measured, not asserted: 4× faster time-to-market via CI/CD, and engineers I mentored now leading in Norway (2) and at two top local firms, with others coached into graduate study in Canada and a UX design career in Germany.
Why Claude-led if Microsoft's own AI stack is Copilot/Azure OpenAI?
This role isn't an AI role — it's senior web architecture, and my frontend fundamentals stand on their own. Where AI accelerates my delivery, I pick the harness and model per task rather than by vendor loyalty — Claude leads shipped client production work today, Gemini runs this site, Kimi via OpenRouter powers . That said, I ship against Azure today ( voices via Azure) and hold Microsoft's AI Show Azure ML AutoML training — I adopt the team's tools without pretending a history I don't have.
Claude-led, model picked per task, not by vendor loyalty.
The stack and receipts behind the claims — React and TypeScript daily, Azure-ecosystem grounded, Claude-led for client delivery with the model picked per task, not by vendor loyalty.
together we build_the web studio Fabric runs on.
Canada is not a fresh bet: roughly four years delivering for AudioBin, SkyTracks & SoftCollab (Angular/WebSocket collaboration alongside the client's technical CTO), fractional CTO work in Quebec, FDE engagements in Toronto, and six months already lived in Toronto during a family stay. Vancouver's three-day hybrid is deliberate relocation intent on top of real Canadian client history — and Vancouver is where Microsoft already runs one of its largest engineering campuses outside Redmond. See Vancouver 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.