> Markdown version of [/jobs/ext/4588389-power-platform-lead-15-year-exp-is-mandatory](https://www.wearedevelopers.com/jobs/ext/4588389-power-platform-lead-15-year-exp-is-mandatory). 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). --- # Power Platform Lead (15+ year Exp is Mandatory) - **Company:** Agile Global Solutions, Inc. - **Location:** Folsom, United States (Remote available) - **Experience:** Expert - **Contract:** Contract - **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), Software Debugging, Event Logging, Extensible Application Markup Language, JSON, Key Management, OAuth, Reverse Engineering, TypeScript, User Provisioning Software, Extensible Markup Language (XML), Postman, Microsoft Power Automate, Power Platform Integration, ReactJS, Generative AI, Build Management, Material UI, Low-code, Decoding, Powerapps, Web Api - **Published:** November 5, 2026 - **Apply:** https://www.dice.com/job-detail/4b0e7ae1-f436-4545-804a-26332be15c6b ## About the Role Screen for concrete, demonstrable experience in each area below - 5+ years Power Platform alone is not a sufficient filter for this role., * Prior public-sector or government systems modernization experience, especially legacy mainframe to cloud re-platforming. * Experience designing audit/compliance-grade data trails (point-in-time snapshots, immutable event logs) - distinguishing a durable audit design from a convenience log. * Familiarity with Dataverse's auditing subsystem specifically (isauditenabled, isuseraccessauditenabled, useraccessauditinginterval) - these settings have undocumented edge-case behavior that has caused real delivery delays on this program. * Microsoft certifications: PL-600 (Solution Architect) or PL-400 (Developer) are a reasonable signal but not a substitute for the hands-on experience above. * Comfortable working from a real, exported legacy or Power Platform solution as the source of truth, in addition to or instead of written requirements documents. ## Description Moving Legacy Java/mainframe system (child care / caregiver benefits) onto Power Platform. A significant share of the work is matching the exact behavior of real, already-deployed legacy and Power Platform systems from their own source exports, not just building new features from a blank slate - so this role needs both standard Power Platform delivery skill and a reverse-engineering mindset. Key Responsibilities * Design and build Dataverse schema, Power Automate flows, security roles, and generative (code) pages for Power Platform modernization workstreams. * Decode and faithfully replicate the behavior of existing, already-deployed systems (legacy mainframe or existing Power Platform solutions) by reading their exported source directly - not just working from requirements documents. * Go beyond no-code/low-code tooling when needed: author raw Dataverse Web API / metadata calls, debug flows via run-history and API tooling rather than only the Maker UI, and diagnose undocumented platform behavior through direct testing. * Own the technical integrity of cross-environment integrations, JIT identity provisioning, and the security model (roles, privilege scoping, service accounts). * Identify and disclose design divergences from source systems clearly - distinguishing matches the real system from new functionality from accepted simplification - so stakeholders always know what's been verified versus assumed. * Mentor and direct supporting developers; review their flow and schema designs for correctness and maintainability. * Maintain a living requirements-traceability record mapping what's built against the authoritative requirement source (e.g. a Master Register or equivalent)., Has created or modified tables, columns, and relationships via direct Web API calls (not only the Maker UI) - e.g. EntityDefinitions, RelationshipDefinitions, PublishXml, solution component registration. Knows a lookup column can't be created through a plain attribute POST and must go through the relationship endpoint. Power Automate internals Has authored flows using Workflow Definition Language (WDL) expressions directly, not only the visual designer. Understands webhook trigger subscription registration and connection references, and has debugged a flow using run-history/API tooling rather than only the Maker Test button. Dataverse security model Hands-on with security roles and table-level privilege scoping (Create/Read/Write/Append/Delete), business units, teams, and just-in-time (JIT) user provisioning via identity impersonation. Has designed or evaluated a dedicated service-account/service-principal pattern, as distinct from running automation under a personal interactive connection. Cross-environment integration Has built a flow or service that calls one Dataverse environment's Web API from automation running in another - including OAuth client-credentials auth and secret management (e.g. Azure Key Vault). Power Apps code apps / generative pages React + TypeScript experience, comfortable with a component library (Fluent UI or equivalent), and understands that a platform's custom data-binding layer may have its own conventions that differ from the raw Web API - getting this wrong can silently orphan records with no error. PAC CLI Fluent beyond basic solution export/import - entity/attribute metadata operations, environment variables, connection references, solution component management. Reading exported solutions Can unpack a solution export (managed or unmanaged) and read its raw contents - classic workflow XAML, Power Automate JSON definitions, sitemap/role XML - to determine what an existing system actually does, as opposed to what its documentation claims. Empirical troubleshooting Comfortable concluding the documentation doesn't define this and resolving it by direct, deliberate testing against a live environment, rather than guessing or stopping at the docs. 5+ years hands-on Power Platform / Dataverse delivery experience, with at least one engagement involving custom Power Automate flows and Dataverse security configuration beyond default settings. Looking for a hands-on technical lead who can roll up their sleeves, work alongside developers, and provide practical coding guidance by demonstrating how things should be implemented-not just someone focused on project management., Core skill bar Mid-level Power Platform / Dataverse Developer Can build Power Automate flows and Dataverse schema changes from a spec under the Technical Lead's direction; does not need raw-API or reverse-engineering depth. Business / Functional Analyst Traces delivered functionality against an authoritative requirements source, maintains a coverage/traceability tracker, writes use cases and functional design documentation. QA / Test Engineer Comfortable testing via raw API calls (e.g. Postman) and reading flow run-history, not only UI click-testing - this project's defects were consistently found by testing against live data, not by UI inspection alone. Security / Compliance Reviewer (periodic, not full-time) Reviews audit-trail and approval-workflow design choices against compliance requirements; engaged at milestones rather than continuously.