Power Apps Technical Lead — Power Pages & Dataverse

Role Summary

Avanade India’s Business Applications practice is looking for a Power Apps Technical Lead to own the technical design and build of applications on the Microsoft Power Platform — with Power Pages and Dataverse at the centre of the role. This is a hands-on lead position: you will set the technical direction, make the design calls, write the harder parts of the code yourself, and lead a team of developers through delivery.

The role is deliberately weighted towards Power Pages and front-end engineering. We are looking for someone who is as comfortable with HTML, CSS, JavaScript and Liquid as they are with a Dataverse security model — because externally facing portals are where those two worlds meet, and where most Power Platform projects run into trouble.

Key Responsibilities

• Own the end-to-end technical design of Power Platform applications — solution architecture, Dataverse data model, security model, integration approach and front-end design — and document the decisions behind them.

• Lead the design and development of Power Pages sites: site structure and templates, web pages and web templates, Liquid, forms and lists, page and table permissions, authentication providers and external user access.

• Build rich, responsive front-end experiences on Power Pages using HTML, CSS, JavaScript and Bootstrap — custom components, client-side validation, dynamic behaviour and integration with the Dataverse Web API.

• Design and build applications in Power Apps — model-driven and canvas apps — including forms, views, business rules, client scripting and app-level performance considerations.

• Design and implement Dataverse solutions: tables, columns and relationships, keys, calculated and rollup fields, business rules, and a security model built on roles, teams, business units and row/column-level security.

• Develop server-side extensions where required — plug-ins and custom APIs in C#/.NET — and integrate with external systems through REST APIs and the Dataverse Web API.

• Build custom controls with the Power Apps Component Framework (PCF) using TypeScript and React where out-of-the-box components fall short.

• Lead the development team day to day — task breakdown, technical guidance, code reviews, unblocking developers and holding the quality bar on what ships.

• Own ALM and release practice: solution layering and management, environment strategy, source control, deployment pipelines and configuration/data migration between environments.

• Set and enforce engineering standards — coding conventions, naming, reusable components, performance patterns, accessibility and security practices for public-facing sites.

• Translate functional requirements into technical designs with the functional and business analyst teams, and challenge requirements where a simpler or more sustainable approach exists.

• Own non-functional quality: performance and page-load optimisation for portals, caching, scalability, accessibility (WCAG) compliance and security hardening of externally exposed sites.

• Support estimation, sprint planning and technical risk identification, and give realistic delivery input to project and client leadership.

• Engage client technical stakeholders directly — design walkthroughs, technical discussions and issue resolution — and represent the technical position credibly.

• Mentor developers on the team, and contribute reusable components, templates and accelerators back to the practice.

.

• 8–10 years of overall application development experience, with substantial recent delivery on the Microsoft Power Platform.

• Strong hands-on experience building applications with Power Apps — model-driven and/or canvas — taken through to production.

• Deep, demonstrable Power Pages (or Power Apps Portals) experience: web templates, Liquid, forms and lists, table and page permissions, web roles, authentication and external-facing site delivery.

• Strong front-end web development skills — HTML5, CSS3, JavaScript (ES6+), responsive design and Bootstrap — with the ability to build custom UI rather than only configure out-of-the-box components.

• Deep Dataverse expertise: data modelling, relationships, business rules, and a genuine command of the security model — roles, teams, business units, and row- and column-level security.

• Experience with the Dataverse Web API and REST integration patterns, including authentication and error handling.

• Server-side development capability in C#/.NET — plug-ins, custom APIs and custom workflow activities.

• Experience with Power Apps Component Framework (PCF) and TypeScript for custom control development.

• Solid ALM discipline: solution management, environment strategy, source control (Git) and automated or repeatable deployments.

• Proven experience as a technical lead — owning design decisions, running code reviews, guiding developers and being accountable for technical quality on an engagement.

• Ability to work directly with clients and functional teams, explain technical trade-offs clearly, and push back constructively where needed.

• Strong debugging and troubleshooting skills across the full stack — browser, portal runtime, Dataverse and integrations.

Preferred / Good to Have

• Microsoft certifications: PL-400 (Power Platform Developer), PL-600 (Solution Architect) or PL-200.

• Experience with modern JavaScript frameworks (React, Angular or Vue) and build tooling.

• Experience delivering high-traffic or public-facing portals, including SEO, CDN and caching considerations.

• Familiarity with Azure services that commonly support Power Platform solutions — Azure Functions, API Management, Key Vault, Service Bus or Azure AD B2C for portal authentication.

• Experience with Dynamics 365 first-party apps built on Dataverse.

• Accessibility experience — WCAG 2.1/2.2 conformance and assistive-technology testing.

• Experience with automated testing for Power Platform solutions (unit tests for plug-ins, UI test automation).

• Experience in a global delivery / SI environment working with distributed teams.

• Prior contribution to reusable components, frameworks or practice accelerators.

.