Shawn Mcdowell Email and Phone Number

• Integrated core workloads into Microsoft Graph Webhooks API. Prototyped integration, identified core design issues and worked with partner team on resolving issues required for integration.• Built and scheduled core SCOPE scripts for data analysis and reporting at monthly service reviews. Established core metric definitions for Graph Webhooks Monthly and Daily Active Users (MAU/DAU) as well as Actual and Ideal Customer Experience (ACE/ICE).• Implemented logging infrastructure integration with Geneva logging system from quick business reporting metrics, to investigative logging, to core analytics storage in COSMOS.

• Implemented strategy, tools, and data analysis for improving support experience for developers through insights from support data, direct connections with support engineering, and drove changes of top issues with product group.• Identified developer journey into end to end experiences and tracking success through key metrics. • Owned features for Getting Started experiences on http://dev.office.com using MVC, HTML5, Bootstrap, JavaScript, and jQuery.• Analyzed telemetry data from COSMOS and Google Analytics.

• Owned the Apps for Office core end-point deliverables, including Office.js API, Desktop and Online (WAC) API integration. • Drove engineering relationship with the Office Store integration with the OMEX team in Ireland with key initiatives around top customer and service health issues. Drove the OMEX/ODP MSR.• Developed and executed plan for improving Customer Partner Experience (CPE) working with Supportability PM to drive resolution of top customer issues, understanding of PSAT/CSAT, and reduced SLA for escalation and QFEs through process improvement. Won award for reducing impact of top SharePoint Workflow issue. • Drove Office-suite wide initiative to reduce COM Add-in crashes due to poorly implemented 3rd party add-ins.• Had impact on quality of 2014 SharePoint Conference as scrum driver for Scenarios Scrum by executing the Office 365 API solutions, • Cross team driver for driver roles in key horizontal areas, such as Security, Performance, World Readiness, Dogfooding, etc.• Main point of contact for recruiting for FTE on the ODP and Vendors in the APPS org. Responsible for resume reviews, setting up tech screens, and interviews.

• Owner for quality of first release of Apps for Office integration and API across Excel, Word, PowerPoint, and Outlook.• Drove strategy for Office Programmability (VBA, VSTO, PIA, Form3 controls) across Office Suite partners. • Spent the first 6+ months on the OSF team helping to ship the first version of Office 365 and SharePoint Online. Owned the quality of the provisioning pipeline from Office 365 signup through SharePoint Online site creation.

• Release lead for Access team. Coordinated test passes and signoff across the test team and communicated status. Key person for ensuring signoff on Access 2007 and 2010.• Drove 64-bit release of Office across Office Suite addressing compatibility issues with 32-bit processes concurrently with providing testing and customer guidance.

• Shipped web package that utilized the Web Part framework for SharePoint Services connected to Great Plains web service data. • Drove team to develop automation framework and tools for testing client and server features. Learned new technologies for SharePoint, SOAP. • Built web-based tool for test case development using the DHTML Edit control and an existing SQL server backend. • Frequent communication with Great Plains team in Fargo, ND and status to team on product health.

• Responsible for individual features across the product. • First product shipped was Access Developer's Toolkit for Access 95. • Shipped Access 97, and Access 2000 before becoming a Test Lead on 9/1999. • Wrote whitepaper for Visual SourceSafe Integration in Access.• Developed core skills in automation using VB, test case writing and review.

Automated mock reports based off of production COBOL reports using DYL-280. Fed mock sample data into the mock report and production report to compare actual and mock output to ensure regressions in behavior did not occur with coding changes.