Power Platform & Copilot Studio Developer — Manufacturing AI

TalentXM builds benches of Power Platform developers for manufacturers automating shop-floor and back-office work. You'd be placed into client engagements building production-support and maintenance-knowledge agents in Copilot Studio, shop-floor apps in Power Apps, and the workflows connecting them to whatever the client already runs — usually D365 F&O or Supply Chain, sometimes SAP, often an MES nobody has documented.

Your users are operators, quality techs and maintenance planners. Mobile and tablet first, often gloved, sometimes offline, rarely patient with a bad form.

What you'll own

Copilot Studio agents in production, not demos — topics, generative orchestration, knowledge grounding, and a credit-cost model that survives finance review

Canvas and model-driven apps for shop-floor use: production tracking, quality inspection, maintenance requests, digital work instructions

Power Automate flows for approvals, escalations and document processing, integrated to the client's system of record via custom connectors

Dataverse design — tables, relationships, security roles, and a model that holds up when a second plant is added

The judgement call on what shouldn't be built in Power Platform at all

What we need to see

Power Platform solutions you shipped to real users. We'll ask what broke and what you'd redo

Copilot Studio or Power Virtual Agents in production — one agent, end to end, with governance

Custom connectors and REST/OAuth integration to a system of record

Dataverse modelling beyond a single table

Comfort with users who aren't at desks. Shop-floor UX is its own discipline

Nice to have

D365 F&O or Supply Chain Management · MES or historian integration · AI Builder document processing · Azure OpenAI and grounded RAG · PL-400 · manufacturing, energy, aerospace or other regulated-operations background