Power Platform Interview Questions Worth Asking

The standard Power Platform interview list asks for definitions: what is a canvas app, what is Dataverse, name three connectors. Those answers are memorisable and predict nothing.

The questions below have follow-ups. Each one distinguishes someone who has shipped and maintained something from someone who has completed a tutorial, and each includes what a strong answer contains — which makes them useful for preparing as well as for asking.

Power Apps

What is a delegation warning, and why does it matter?

This is the single best Power Apps question, because the wrong answer is extremely common and sounds reasonable.

Weak answer: it means the app might be slow with large data.

Strong answer: it means results will be wrong. A non-delegable operation is evaluated only over the records already retrieved under the row limit, so a filter or a search silently omits records that exist, and totals are incorrect. Nobody reports it as a bug because nothing appears broken.

Follow-up: which functions delegate? A real answer notes that it depends on the connector — SharePoint delegates less than Dataverse, and the same formula can be delegable against one source and not another.

How do you make a canvas app genuinely responsive?

Strong answer: turn off the fixed aspect ratio and scale-to-fit, then lay out with containers rather than absolute positions, using relative width formulas. Mentions that the app's size properties are the anchor everything else is expressed against, and that a screen designed by dragging controls will not survive a change in window size.

How do you improve a slow canvas app?

Strong answer: measure first with the monitor tool rather than guessing. Then: reduce what OnStart does, avoid loading whole collections when a filtered query would do, push filtering to the source, cut the number of controls on a screen, and use concurrent where independent calls can overlap. Points at the network as the usual culprit rather than formula complexity.

Dataverse and security

Explain the Dataverse security model to a non-technical stakeholder.

Strong answer: a security role grants a privilege on a table — create, read, write, delete and so on — and each privilege has a scope saying how far it reaches: only your own records, your business unit, that unit and those beneath it, or the whole organisation. Records have owners, teams can own records, and sharing grants access to one specific record. Field-level security narrows it to individual columns.

What it reveals: whether they understand that access is a property of the data rather than of the app. Anyone who answers by describing app-level visibility has missed the model.

When would you not use Dataverse?

Strong answer: when the data belongs in a system that already owns it and is not moving, when licensing cannot be justified for the audience, or when the requirement is genuinely a list rather than a relational model. Willingness to say "not Dataverse" is a good signal.

Power Automate

A flow works for its author and fails for everyone else. Where do you look?

Strong answer: connections. A flow runs with the connections it was built with; if those authenticate as the author, they carry the author's permissions. Then: trigger conditions, the sharing configuration of the flow, and whether the run history shows an authorisation failure or no run at all — which distinguishes a permission problem from a trigger problem.

How do you handle failure in a production flow?

Strong answer: scopes with a configure-run-after path for failure, retry policies set per action rather than left at default, idempotency for anything that writes, a dead-letter destination for what cannot be processed, and alerting that is not "someone notices the run history is red". Mentions that retrying a non-idempotent write can duplicate the effect.

What happens when the flow owner leaves?

Strong answer: a personal flow with personal connections stops. The fix is structural — a solution, connection references bound to a service principal or service account, and co-owners. A candidate who raises this without prompting has operated a real environment.

ALM and governance

Walk me from a change on your machine to that change in production.

The best question in the whole list, because it cannot be answered from a tutorial.

Strong answer: develop in an unmanaged solution in a development environment; export; unpack into source control; build a managed solution; import into test through a pipeline; validate; import into production. Connection references and environment variables carry the per-environment configuration. Nothing is edited directly in production.

Weak answer: anything that includes exporting from production, or editing there.

What does a DLP policy do?

Strong answer: prevents connectors in different data groups being used together in the same app or flow. Notes that it is a combination control rather than an on/off switch per connector, that it applies at environment scope, and that introducing one breaks existing apps that violate it — so it needs to be announced before it is applied.

Judgement

When would you tell someone not to use the Power Platform?

Strong answer: high-volume transactional systems, anything needing sub-second guaranteed latency, complex algorithmic work, and requirements where the licensing cost at the intended scale exceeds building it properly. Someone who thinks everything is a Power Platform problem will build several things that should not have been.

Tell me about something you built that you would build differently now.

Specific answer, specific reason. The common and welcome one is "I built it outside a solution and paid for it later".

Common mistakes candidates make

• Answering the delegation question as a performance question. It is a correctness question, and getting that wrong is the clearest signal available.
• Describing features instead of a method. When asked how you would diagnose something, give the order you would check things in.
• Having only built in one environment. The walk-me-to-production question exposes this immediately, and it cannot be bluffed.
• Claiming everything is a Power Platform problem. Knowing where the platform stops is part of knowing the platform.
• No opinion on governance. Anyone who has run an estate has views on the default environment and on flow ownership.

Frequently asked questions

How much Power Fx should a candidate know?

Enough to explain delegation, to know why ForAll with a patch inside is usually the wrong shape, and to read someone else's formula. Memorising the function list is not the skill.

Is a developer background necessary?

For maker roles, no. For roles owning ALM, integration or PCF components, yes — those are software engineering with a different toolchain.

What is the most common gap?

Deployment. Many candidates can build well in one environment and have never moved a solution between two. That gap shows up immediately in the walk-me-to-production question.

What should a candidate ask?

How environments are structured, whether solutions and pipelines are in use, who owns governance, and what happens to an app when its maker moves on. The answers describe the job accurately.

Preparing properly

If you are preparing, do one thing: build something small, put it in a solution, and move it to a second environment with connection references and environment variables. Doing that once teaches more than a hundred memorised definitions — and it is exactly what the strongest question in the list is asking about.