A Power Platform CV should make your level of responsibility easy to understand. Product names alone do not show whether you followed a tutorial, built a prototype or supported a live business solution.
The safest structure is role first, evidence second and keywords third.
1. Choose the role before writing the CV
Microsoft's current Power Platform guidance covers several kinds of work, including makers, administrators, business analysts, DevOps engineers and solution architects. A Power Platform developer credential, by contrast, expects experience with extension points, integrations, security, application lifecycle management and conventional code.
Read the vacancy and decide what it is really asking for. Then give the employer a CV for that role.
Your opening summary can be three lines:
- your current level and target role
- the strongest relevant capabilities you can demonstrate
- the kind of evidence included below
Do not call yourself a solution architect because you designed one small app. Do not call yourself a developer if you would be unable to discuss testing, security, integration or deployment.
2. Use a compact skills section
Group skills by capability instead of presenting a wall of product names:
- Apps: canvas apps, model-driven apps, Power Fx
- Automation: cloud flows, approvals, expressions, error handling
- Data: Dataverse, SharePoint lists, relationships, security roles
- Delivery: solutions, environment variables, pipelines, source control
- Integration: connectors, APIs, custom connectors
- Governance: environments, data policies, monitoring, support
Include only the things you could explain in an interview.
3. Describe projects as evidence
Use this pattern for employment and portfolio projects:
Problem: Who needed what?
Contribution: What did you personally analyse, configure, build or test?
Technical choices: What data source, app type, automation and security model did you choose?
Verification: How did you check the result?
Boundary: Was this a personal build, a team prototype or a production service?
For example:
Built a development-only equipment request app using a canvas app, Dataverse and a cloud flow. Defined the table relationships, added role-based access, tested approval and rejection paths, and documented known limitations. The project was created in a Power Apps Developer Plan environment and was not deployed to production.
That statement is modest, specific and interviewable.
4. Quantify only what you can defend
Numbers can help, but invented precision damages trust.
Use a number when you have a record for it, such as:
- number of users supported
- number of environments or solutions maintained
- reduction in manual steps measured before and after
- incident volume or deployment frequency from an actual system
If you do not have measured business outcomes, describe the verified output instead: an approved design, a working test, a documented handover or a resolved defect.
5. Treat credentials accurately
List the exact credential name, issuer, issue date and credential link.
Microsoft Fundamentals credentials do not expire. Microsoft's associate, expert and specialty certifications normally require annual renewal. The catalogue also changes: PL-200 is scheduled to retire on 31 August 2026, and Microsoft now lists the Intelligent Applications Builder Associate credential for AI-enabled Power Platform work.
Check the live Microsoft page before applying. A CV copied from an older article can age badly.
What to do when you lack commercial experience
Do not disguise a practice build as client work. Build a small portfolio and label it properly.
A useful project demonstrates more than the happy path:
- a written requirement
- a simple data model
- permissions or security roles
- a failure path
- a test record
- deployment or export notes
- a short retrospective
The Power Apps Developer Plan provides a development and test environment for eligible work or school accounts. Microsoft is explicit that it is not a production entitlement. That boundary belongs in your project notes.
Transferable experience also matters. Requirements gathering, process mapping, stakeholder support, data quality and operational ownership can all be relevant when backed by a real example.
Final checks
- Keep the layout plain enough to scan.
- Use the spelling and terminology from the vacancy.
- Remove claims you cannot explain.
- Link to a sanitised portfolio, not confidential files.
- Ask somebody unfamiliar with your work what role they think the CV targets.
- Export to PDF and check that links, headings and page breaks still work.
No CV can guarantee an interview. A good one simply reduces ambiguity about what you know, what you have done and what you are ready to discuss.
Sources
- Microsoft: Define Power Platform roles and responsibilities
- Microsoft Certified: Power Platform Developer Associate
- Microsoft credential retirement information
- Microsoft Power Apps Developer Plan
If you want a technical review of the project behind a CV bullet, join the Power Apps Builders Space. Remove personal data, tenant details and employer material before sharing anything.