Job 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).
Required Skills and Experience
Screen for concrete, demonstrable experience in each area below — 5+ years Power Platform alone is not a sufficient filter for this role.
Area
- Dataverse Web API / metadata API
- Power Automate internals
- Dataverse security model
- Cross-environment integration
- Power Apps code apps / generative pages
- PAC CLI
- Reading exported solutions
- Empirical troubleshooting
Preferred Qualifications
- 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.
Supporting Roles (same project, reporting to the Technical Lead)
- Mid-level Power Platform / Dataverse Developer
- Business / Functional Analyst
- QA / Test Engineer
- Security / Compliance Reviewer (periodic, not full-time)