> Markdown version of [/jobs/ext/4648918-mecm-automation-api-engineer](https://www.wearedevelopers.com/jobs/ext/4648918-mecm-automation-api-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # MECM Automation/API Engineer - **Company:** AgreeYa Solutions, Inc. - **Location:** Phoenix, AZ, United States - **Salary:** $110,000 - $150,000 - **Contract:** Contract - **Skills:** Application Programming Interfaces (APIs), Configuration Management, System Configuration, Microsoft Software, System Center Configuration Manager, Windows PowerShell, Short Message Service, Systems Integration, Windows Management Instrumentation, Restful APIs - **Published:** November 9, 2026 - **Apply:** https://www.careerbuilder.com/job-details/mecm-automation-api-engineer-phoenix-az--c9e41c84-84ab-4edd-bf3d-6009e28c78d0 ## About the Role Automation, Application Programming Interface (API), Automation, Configuration Management, Application Programming Interface (API), Microsoft Product Family, REST (Representational State Transfer), WMI API (Windows Management Instrumentation), Short Messaging Service (SMS), Windows PowerShell ## Description We are seeking an experienced MECM Automation/API Engineer to provide engineering ownership of the Microsoft Endpoint Configuration Manager (MECM) platform capabilities required to support enterprise automation and integrations. This resource will be responsible for enabling, configuring, securing, monitoring, and supporting MECM APIs and automation interfaces, including AdminService/REST, SMS Provider/WMI, and PowerShell. Responsibilities include managing authentication and role-based access, validating API functionality and usability, troubleshooting MECM-side integration issues, monitoring service health and performance, developing utilization and availability reporting, and ensuring MECM automation services are resilient, recoverable, documented, and operationally supportable. The scope is specifically focused on the MECM platform and its interfaces; development of downstream applications, workflows, or automation consuming MECM APIs is outside the primary scope.