Dynamics 365 Developer, Power Pages lead

What this person does

Builds the public-facing customer portal: account creation and sign-in, online applications, renewals, document upload, status tracking and payment handoff. Works weeks 10 to 22 alongside the integration developer, then supports testing and cutover.

Must have

•      Three or more years of Dynamics 365 and Power Platform development, including at least one production Power Pages or Dynamics Portals customer-facing site the candidate personally built

•      Power Pages specifics: liquid and web templates, page templates, web roles, table permissions, entity forms and lists, basic and advanced forms

•      External authentication setup, for example Entra External ID, Azure AD B2C, or local authentication with invitation flows

•      Model-driven app customisation, C# plug-ins, custom APIs and JavaScript form scripting

•      Power Automate flows supporting portal submissions and notifications

•      Accessibility work on a public-facing portal to WCAG 2.1 AA, including how they tested it

•      Deployment through managed solutions and a repeatable release process

Nice to have

•      Payment redirect or hosted payment page integration from a portal, ideally a government payment provider

•      Portal used by external businesses or licensees rather than internal staff

•      Portal performance tuning and caching

•      Experience supporting a portal through a renewal surge

Certifications to look for

•      PL-400 Power Platform Developer, strongly preferred. Ask for the certification ID

•      PL-200 Power Platform Functional Consultant

•      MB-280 Dynamics 365 Customer Experience Analyst

•      PL-900 on its own is not sufficient for this role