Own the flagship engagements Take personal, end-to-end technical ownership of the engagements with the highest stakes: partners building on and alongside Windows, silicon partners whose platforms define the AI developer experience, and enterprise engineering organizations whose choices move the market.
Discover:
get inside a customer's actual engineering reality — their architecture, their roadmap, their constraints, and the honest reason Windows is or is not their default. Establish the problem statement, the baseline, the agreed success measures and the plan.
Build:
work in their codebase and in ours. Design and ship the integrations, prototypes, reference implementations, tooling and platform changes that make adoption real. Apply engineering standards — security, privacy, maintainability, supportability — to work that will run in production long after the engagement ends.
Validate:
prove the outcome with measurement the customer agrees with, not with a demo.
Stay hands-on:
Write the prototypes, read the traces, work in the customer's repository. Your credibility with partner engineering leadership rests on doing the work, not describing it. Deliver unwelcome answers well. Deliver measurable adoption outcomes Bachelor's Degree in Computer Science or related technical field AND 6+ years technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript, or Python. OR equivalent experience. A sustained record of owning the technical relationship with strategic partners or major enterprise engineering organizations, accountable for the outcome rather than for advice — as a forward deployed engineer, partner engineer, principal solutions architect, principal consultant, or technical founder. Experience standing up a new team, practice or engagement model from nothing. Deep technical credibility across the modern developer and AI stack: LLM application and agent architectures, evaluation, local and hybrid inference, developer environments and toolchains, WSL and containers, performance and reliability analysis of systems you did not write, and the enterprise security and identity controls that constrain all of it. Solid programming ability in Python and at least one of TypeScript, C#, Rust, Go, C or C++, with a record of shipping production software recently enough to still be dangerous. Demonstrated influence on a platform roadmap driven by customer evidence — you have changed what a product team built and can point to it. Experience converting bespoke customer work into durable, reusable assets — reference architectures, tooling, guidance — that scaled well beyond the original engagement. Ability to operate with authority in front of executive technical audiences while keeping the respect of the engineers in the room. Practices good judgement in ambiguous and commercially sensitive situations, including knowing what to concede, what to escalate, and what to fix quietly. Experience mentoring senior engineers and raising the technical bar of a team. Deep Windows platform expertise or demonstrated ability to reach that depth quickly from adjacent platform expertise. Familiarity with the Windows app platform — Win
UI, WPF, .NET
desktop — and with application modernization. Not required for this role, but valuable when a customer's adoption conversation turns to their existing app estate.
