Power Platform Technical Lead

A significant share of the work in this role 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. This role therefore calls for both strong Power Platform delivery expertise and a reverse-engineering mindset.

Responsibilities

• Design and build Dataverse schemas, 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 by reading their exported source directly, not just working from requirements documents.
• Go beyond no-code and low-code tooling when needed by authoring raw Dataverse Web API and metadata calls, debugging flows through run history and API tooling, and diagnosing undocumented platform behavior through direct testing.
• Own the technical integrity of cross-environment integrations, JIT identity provisioning, service-account patterns, and the security model, including roles and privilege scoping.
• Identify and clearly document design divergences from source systems, distinguishing verified behavior, new functionality, accepted simplifications, and assumptions.
• Mentor and direct supporting developers, review flow and schema designs for correctness and maintainability, and provide hands-on coding guidance.
• Maintain a living requirements-traceability record mapping what is built against the authoritative requirement source.

Requirements

Required Skills and Experience

Screen for concrete, demonstrable experience in each area below. 5+ years of Power Platform experience alone is not a sufficient filter for this role.

• 5+ years of hands-on Power Platform and Dataverse delivery experience, including at least one engagement involving custom Power Automate flows and Dataverse security configuration beyond default settings.
• Experience as a hands-on technical lead who mentors developers, works alongside the team, and demonstrates implementation approaches in practice.
• Direct experience with Dataverse Web API and metadata operations, including creating or modifying tables, columns, and relationships through Web API calls rather than only through the Maker UI.
• Hands-on experience with Workflow Definition Language expressions, connection references, webhook trigger subscription registration, and debugging flows through run history and API tooling rather than only the visual designer.
• Strong experience configuring Dataverse security architecture, including security roles, table-level privilege scoping, business units, teams, JIT user provisioning, and service-principal or dedicated service-account patterns.
• Experience with cross-environment Dataverse integration using OAuth client credentials and secret management.
• Experience building Power Apps code apps or generative pages with React, TypeScript, and component libraries, with an understanding of platform-specific data-binding conventions.
• Experience with advanced PAC CLI operations beyond basic solution export and import, including metadata operations, environment variables, connection references, and solution component management.
• Experience unpacking and reading exported Power Platform solution contents to determine how an existing system behaves in practice.
• Experience troubleshooting platform behavior through deliberate live-environment testing when documentation alone is insufficient.
• Availability during Hawaii Standard Time business hours.

Preferred Qualifications

• Experience with public-sector or government modernization.
• Experience designing audit- and compliance-grade data trails.
• Familiarity with Dataverse auditing settings and edge cases.
• PL-600 or PL-400 certification.

Originally posted on Himalayas