Renton, Washington, United States
Leading a team of 8 engineers, ranging from early in career to Principal Software engineer, working on a variety of UI features for SharePoint Lists and Libraries with ownership including: - Various features in the Microsoft Lists app revamp (https://techcommunity.microsoft.com/t5/microsoft-365-blog/microsoft-lists-easier-better-faster-stronger/ba-p/3806075) - List and library templates - Telemetry and monitoring infrastructure for lists and libraries in SharePoint Leading my team by practicing the core pillars of Management Excellence at Microsoft: Model, Coach, Care. As of October 2025, also leading a V-Team of Engineers (including my own) from across multiple EM teams on a project to create AI tools for Lists and Libraries in SharePoint, part of the AI in SharePoint effort. AI tools are code that tool-calling reasoning LLM agents can invoke in order to perform actions, such as adding or editing data in your lists or libraries, as well as performing deep data analysis across your enterprise data. This involves crafting tool descriptions and parameters to ensure correct invocation by the LLM, the actual tool code itself, as well as an evaluation (evals) framework that can run against the whole system end-to-end and an eval suite that targets actual customer scenarios to ensure accuracy, completeness, relevance, and appropriate tone of the AI responses with a goal towards delighting users and helping them utilize their lists and libraries in SharePoint more fully.
Since joining the SharePoint team in March 2017 (was still "Senior" then), I've worked on the following: - Implemented Groupify from start to finish, and continue to maintain it. Groupify is a full-stack feature which allows users to attach a new Office 365 Group to an existing SharePoint site, allowing them to get the benefits of the Group experience while maintaining consistency with their existing data. - Prototyped and implemented the server back-end for Teamify, which allows existing Groups to be connected with a new Microsoft Team. - Maintain Workflow 2010 and 2013, which are complicated IW features used by many enterprises for business-critical processes. This involves implementing new monitoring and logging to understand how the features are being used and what their reliability is, as well as fixing critical bugs. - Worked on an overhaul for the Quick Edit feature, to re-architect it using modern frameworks (Typescript, React) so that it can be more quickly innovated and iterated on by team members. - Shipped features between SharePoint and Teams, which help users more easily find their Team and Channel content when using SharePoint UI.
From November 2015 through January 2017, I worked on the Office Access team, developing Project Osaka, a V1 web app on top of an OData service. - Implemented two new data types in the Web App, from the Data Source connection layer up through the Data Model, View Model and View layers of the Web App. Each was, at the time, the most complicated data type in the application, requiring an overhaul to much of the core logic and functionality for the app. Each data type set a template for similar work on future data types in terms of Data Model logic and UI design. - Investigated a serious performance issue in the app, where displaying certain data sets could take an unbounded amount of time to render (minutes or more). From the results of the investigation, prototyped and then implemented a performance feature which brought the render time down to a bounded (10 seconds or less) period of time. This was a medium-term fix that allowed the app to maintain its visual polish while getting the performance into a place where it could ship a Preview. - Based on the performance investigation, led an effort to overhaul the view and view model code, moving from the original Knockout implementation to a much better performing React implementation based on a Flux data flow, bringing max render time for a large data set down from 8 seconds to 1.5. This was a long-term plan to create a more future-proof base for the product. I am now part of the SharePoint team.