Key responsibilities
Own the target architecture: Dataverse data model, shared services, security model, ALM approach.
Design the Dataverse data model — tables, relationships, choice columns, calculated and rollup columns — across all ten applications.
Design the record-level security model, translating Notes Reader and Author fields and ACL roles into Dataverse security roles, business units, teams and row ownership. This applies to most of the applications in scope and is the single largest design risk.
Define the shared services layer: approval orchestration, notification, scheduled execution, audit and reference data.
Set the solution layering and ALM strategy: environments, managed solutions, deployment pipelines.
Define how content — documents and attachments — is held in the external content store and referenced from Dataverse.
Review and approve each application design before build starts.
Own Dataverse capacity planning and Power Platform API request budgeting, and design within those limits.
Essential experience
8+ years on Microsoft Power Platform, at least 3 of them as an architect.
Deep Dataverse: data modelling, security roles, business units, teams, row-level ownership, business rules, plug-ins.
Model-driven and canvas app design; Power Automate at scale.
Power Platform ALM: solutions, environments, pipelines, DLP policies.
Understands Power Platform request limits and Dataverse capacity entitlements, and designs to stay inside them.
Desirable
Has migrated a legacy document database — Notes, FileNet, Documentum — onto Dataverse.
Power Pages, for external-facing scenarios.