Jun 2021 – Present · 4 yrs 11 mos

• I lead reserach for EngThrive, Microsoft’s company-wide initiative for measuring and improving the developer experience across our global engineering workforce.
• My work spans large-scale telemetry analysis, field experiments, survey research, and qualitative studies. I partner closely with engineering executives to translate these findings into organizational decisions that reduce developer toil, strengthen focus, and improve the daily experience of more than 50,000 engineers.
• Selected impact:
• Designed and implemented 75% of Microsoft’s top-level developer experience metrics, used biannually in Senior Leadership Team reviews to guide engineering investments and policy decisions.
• Increased active coding time by 8–11% by identifying optimal patterns for focus time and piloting schedule improvements across orgs.
• Improved first-year developer throughput by 23% through targeted onboarding experiments.
• Reduced pull-request dwell time by 14% by analyzing developer work rhythms and optimizing review windows.
• Delivered research that directly shaped multiple company-wide policies and accelerated engineering modernization efforts.
• I also publish peer-reviewed research on developer productivity, including co-authoring the SPACE framework — now one of the most widely adopted models in the industry — and contributing more than 15 papers with over one million cumulative downloads.
• My mission is to humanize the engineering workplace by grounding decisions in evidence and designing environments where developers can do the meaningful and fulfilling work.

Oct 2017 – Jun 2021 · 3 yrs 8 mos

• I led the Windows Developer Productivity team, building a cross-Microsoft coalition of experts to advance how we measure, analyze, and improve developer productivity within the Windows engineering ecosystem.
• Key impact:
• Increased developer productivity by nearly 8%, measured through active coding time, by designing and deploying a modernized, integrated inner-loop experience for Windows engineers.
• Built and operated a quarterly developer satisfaction survey with response rates consistently above 80%, dramatically reducing non-response bias and enabling reliable, long-term tracking of sentiment and pain points.
• Partnered across Windows and Microsoft engineering teams to develop data-driven insights, identify workflow bottlenecks, and guide tooling investments that improved the daily experience of thousands of engineers.
• Helped establish a cohesive, human-centered approach to developer productivity measurement that later informed company-wide efforts such as EngThrive.

Oct 2015 – Sep 2017 · 1 yr 11 mos

• I led the Release team within the Windows Engineering Systems group.
• The Release team was responsible for releasing Windows Client, Server, and IoT to our external customers and partners. We designed, implemented, and deployed a set of Azure cloud services to process and deploy builds of Windows to a variety of endpoints that different external audiences could download from. By automating what was historically a set of manual processes, we reduced the time it takes to process builds by more than 99%. The scalable power of the Cloud allowed us to increase our throughput by over 2500%, all while significantly decreasing our operating costs.

Apr 2014 – Oct 2015 · 1 yr 6 mos

• I led the Windows Device Group - Customer Engagement team, a multidisciplinary team (PM, Test, and Dev) that built structured programs to engage with customers across multiple segments (Enterprise, Education, and Consumer). The goal of these engagements was to provide a channel to receive early responses on feature planning and strategic direction, gather actionable feedback on existing products, and to get validation on in-development products. My teams' responsibilities included working with our legal department to generate the right framework agreements, partnering with marketing to recruit participants into our programs, developing tools for gathering feedback and telemetry, as well as designing and deploying reports that make any received data actionable within the Engineering System.

Mar 2012 – Apr 2014 · 2 yrs 1 mo

• World-Readiness is the idea that all Windows experiences should feel tailored for our users, regardless of where our users live; and which languages they speak. International users should have UI displayed in a format they prefer; with relevant, local, content. They should be able to input in a way that feels natural, and seamless. They shouldn’t have to sacrifice usability, and features to use Windows in their preferred languages. The World-Readiness Test Team partners with feature teams across Windows to make sure those ideals get implemented. Windows release in 108 languages, spanning 269 markets. 95% of the Earth’s population lives outside the United States. Our ability to satisfy the demands of our international customers is critical to the continued success of Microsoft.
• My teams' role is to develop guidelines, requirements, training, tools and sample test collateral to enable feature teams to deliver exception international experiences. We have a particular focus on validating complete end-to-end experiences, and ensuring that integration problems don't break scenarios.

Nov 2009 – Mar 2012 · 2 yrs 4 mos

• The Windows International Test (WIT) team is in charge of ensuring that the user-experience for non-English (US) customers feels natural, fluid, and enjoyable. The WIT team works to ensure the user-experience works correctly for all 108 Windows languages.
• I worked primarily on the tools / infrastructure team; which was tasked with trying to automatically identify and analyze localized screenshots of Windows UI. I developed an image analysis algorithm to detect text on a screen, and to identify which Font was used to render it. This could then be used to determine if localized text was truncated, or displayed incorrectly. The code was written primarily in C++ for performance reasons, with API's exposed in C# for test code to call into.

Aug 2006 – Nov 2009 · 3 yrs 3 mos

• Windows CardSpace was a client application that allowed users to provide a digital identity to a relying party. Identifies could be self-issued, or issued via an identify provider. CardSpace was built on top of the Web Services Protocol Stack, using WS-Security, WS-Trust, WS-MetadataExchange, and WS-SecurityPolicy. Identities were transmitted in digitally signed XML tokens.
• My role in the team was to develop the test case manager (TCM) used to setup, run, monitor, and report the results from all the automated tests used by the CardSpace team. The TCM could coordinate a test run over N machines using .NET 3.0 (Indigo) web-services.
• I also was responsible for designing, developing, and maintaining CardSpace V2 scenario tests for UX, public API’s, installation, ActiveX controls, and interoperability