Low-code developer with 4 years building business apps and automations on Microsoft Power Platform. Built a field inspection app that replaced paper forms for 250 inspectors and cut report turnaround from 5 days to same day. Pairs quick delivery with sound data models, governance and documentation.
Experience
Power Platform Developer, Summitline Property Services (Salt Lake City, UT)
Apr 2023 – Present
Built a Power Apps field inspection app with offline mode and photo capture for 250 inspectors, cutting report turnaround from 5 days to same day
Automated 22 approval and notification workflows in Power Automate, saving about 60 staff hours a week
Designed Dataverse tables and security roles and set up DLP policies with IT
Built Power BI reports on inspection data used in weekly regional reviews
Business Systems Analyst, Wasatch Regional Credit Union (Ogden, UT)
Jun 2022 – Mar 2023
Replaced 8 shared spreadsheets with SharePoint lists and Power Apps forms for loan operations
Gathered requirements and wrote user guides for 3 internal tools
Education
B.S. Management Information Systems, Utah State University (Aug 2018 – May 2022)
Skills
Power Platform: Power Apps, Power Automate, Dataverse, Power BI, Power Fx
Integration: SharePoint, Microsoft 365, REST connectors, SQL Server
Practices: requirements gathering, ALM with solutions, DLP governance
Certifications: Microsoft PL-400
How to write a Low-Code Developer resume
A strong Low-Code Developer resume shows the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Put your most relevant recent role first and make every bullet show a result, not a duty.
Sections, in order
Summary
Experience
Projects
Skills
Education
Length: One page for most candidates; move to two only if every line is relevant.
Summary: Write two or three lines: your role, your strongest skills, and one result that proves them.
Skills to feature
Programming languages
System design
Cloud platforms (AWS, GCP, Azure)
CI/CD
Testing and code review
Databases and SQL
Observability
Security fundamentals
APIs and integrations
Technical documentation
Example bullet points
Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users
Introduced contract tests and staged rollouts, reducing production incidents by 45% in two quarters
Migrated 30 services to Kubernetes with Terraform, lowering cloud spend by $250k a year
Tips from recruiters
Group skills by category (for example "Languages: Go, TypeScript") so recruiters and ATS parsers find them quickly.
Link to a repository, demo or write-up for at least one project you can talk about in depth.
Name the stack inside each bullet; keyword matching happens at the bullet level, not only in the skills list.
Recommended templates
Classic (ATS-friendly): Jake's-style LaTeX classic: small caps and hairline rules
Tech (ATS-friendly): Developer style: mono headings and tags, sans body
Modern (ATS-friendly): Clean single column with accent headings and rules
Low-Code Developer resume FAQ
What should a Low-Code Developer resume include?
A Low-Code Developer resume should show the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Use these sections in this order: Summary, Experience, Projects, Skills and Education. Put your most relevant recent role first and make every bullet show a result, not a duty.
What is the best resume template for a Low-Code Developer?
Classic, Tech and Modern work well for Low-Code Developer roles. They are single-column with standard headings, so applicant tracking systems (ATS) parse them reliably.
How long should a Low-Code Developer resume be?
One page for most candidates; move to two only if every line is relevant.
Which skills should a Low-Code Developer put on a resume?
Prioritize the skills named in the job posting. Common ones for Low-Code Developer roles are Programming languages, System design, Cloud platforms (AWS, GCP, Azure), CI/CD, Testing and code review and Databases and SQL.
How do I write strong Low-Code Developer resume bullet points?
Start with an action verb, say what you did, and end with a measurable result such as latency, uptime and deploy frequency. For example: "Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users."