Matt Peart

Senior Technical Writer at Microsoft

Goodyear, Arizona, United States
email-iconphone-icongithub-logolinkedin-logotwitter-logostackoverflow-logofacebook-logo
Join Prog.AI to see contacts
email-iconphone-icongithub-logolinkedin-logotwitter-logostackoverflow-logofacebook-logo
Join Prog.AI to see contacts

Summary

👤
Senior
🎓
Top School
Matt Peart is a seasoned Senior Technical Writer at Microsoft with over two decades of experience crafting award-winning documentation and content for enterprise products. He focuses on Dynamics 365 and Power Apps, authoring and publishing content for multiple services while maintaining documentation quality through tooling like Acrolinx. His long Microsoft tenure follows earlier hands-on support engineering for Exchange, giving him deep product and customer-facing technical context. Based in Goodyear, Arizona, he blends marketing and information-systems training from Washington State University with practical content strategy. Colleagues rely on him to translate complex platform features into clear guidance that speeds adoption and reduces support friction. Outside headline writing, he contributes to repo-level configuration and publishing workflows, underscoring a keen interest in the systems that keep docs accurate and ship-ready.
code9 years of coding experience
job12 years of employment as a software developer
bookIssaquah High School
bookBachelor of Arts (B.A.), Marketing and Information Systems, Bachelor of Arts (B.A.), Marketing and Information Systems at Washington State University
github-logo-circle

Github Skills (5)

acr10
documentation10
branches9
manage9
configuration-management8

Programming languages (4)

PowerShellC#MermaidMarkdown

Github contributions (5)

github-logo-circle
MicrosoftDocs/powerapps-docs

Mar 2018 - Jan 2023

Technical Documentation for Microsoft Power Apps
Role in this project:
userTechnical Writer
Contributions:4 reviews, 5018 commits, 201 PRs in 4 years 11 months
Contributions summary:Matt's contributions primarily involve modifying the `.acrolinx-config.edn` file within the repository. These changes focus on adjusting allowed branch name matches and allowed filename matches, likely to configure the Acrolinx integration for documentation quality checks. The consistent edits, often merging changes from the 'main' branch, indicate ongoing maintenance or updates to these configurations related to documentation standards.
technical-documentationopenxmlpower-platformprosemicrosoft-power-apps
bensack/powerapps-docs

Oct 2019 - Jul 2020

Technical Documentation for Microsoft PowerApps
Contributions:8 pushes in 9 months
technical-documentationopenxmlpowershellsolidworksmicrosoft
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.
Request Free Trial
Matt Peart - Senior Technical Writer at Microsoft