Power Query skills on a CV: what to list and how to prove it
Career · By Tahir Nas · Examples run in our simulator · Updated
12 min read
List Power Query skills on your CV (résumé) as tasks you can finish, not as a list of ribbon buttons: combining monthly files, reshaping wide reports, merging tables on a clean key, building a refresh that doesn't break. Then prove each claim with one small, runnable piece of work and be ready to repeat it under time pressure, because some analyst interviews include a practical test.
Why "Power Query" on its own says very little
Power Query is the data preparation engine built into Excel, Power BI and several other Microsoft products. Microsoft describes it as an engine with a graphical editor that records your transformations as a repeatable query you can refresh (What is Power Query?, Microsoft Learn). That breadth is the problem for a CV. A person who once clicked Remove Duplicates and a person who maintains twenty refreshing queries can both write "Power Query" in a skills list.
A reviewer can't tell those two people apart from the word alone. What separates them is the kind of mess they can deal with and whether their work survives next month's file. Your CV needs to show which of the two you are.
What to list: five skill groups
A useful way to organise the section is by the job the skill does. These groups follow the order data moves through a query. They also line up closely with the "Prepare the data" area of Microsoft's PL-300 Power BI Data Analyst exam. Its study guide lists connecting to sources, profiling and cleaning, resolving import errors, choosing data types, pivoting and unpivoting, and merging and appending queries (Study guide for Exam PL-300, Microsoft Learn). The same study guide says candidates should be proficient at using Power Query and DAX.
| Skill group | What it covers | Example CV wording |
|---|---|---|
| Getting data | CSV, Excel tables and sheets, folders of files, JSON, databases | "Combined 12 regional CSV exports from a shared folder into one refreshable table" |
| Cleaning | Types, locales, trimming, nulls versus blanks, errors | "Fixed day-first dates and decimal-comma amounts so totals matched the ledger" |
| Reshaping | Unpivot, pivot, fill down, header rows, group by | "Turned a wide budget sheet with one column per month into a tidy table" |
| Combining | Append, merge, join kinds, keys, duplicate checks | "Matched orders to customers on a cleaned composite key and reported unmatched rows" |
| Reliability | Parameters, dynamic steps, validation, folding awareness | "Built checks that stop the refresh when an expected column is missing" |
Those example figures are illustrations; use your own.
You don't need all five. Two groups described well beat five described vaguely. Pick the ones you have done on real data, and if a group is only from practice, the portfolio section below covers how to say so.
Keywords and where the bullets go
Keep the plain terms somewhere on the page as well: a skills line such as "Power Query (M), Excel, Power BI" helps when a recruiter or an applicant tracking system searches for the words in the job advert. Then put the outcome bullets under the role or project where you did the work, so each claim sits next to its context. Mirror the advert's wording where it is true of you, and nowhere else.
Wording that survives a follow-up question
Every line on a CV is an invitation for the interviewer to say "tell me about that". Write each bullet so you can answer three questions about it: what the data looked like, what you did to it, and what stopped it breaking later.
Compare these two versions:
- Weak: "Advanced Power Query: merge, append, pivot, unpivot, custom columns."
- Strong: "Replaced a two-hour monthly copy-paste with a query that combines every supplier file in a folder, unpivots the month columns and flags rows whose amount won't convert."
The strong version names the input, the transformation and the safeguard. If you haven't done that job yet, replacing a monthly copy-paste process walks through it. It also gives the interviewer an easy first question, which is a good thing: you get to talk about work you know well.
If you have numbers you can stand behind (hours saved, files combined, rows checked), use them. If you don't, leave numbers out rather than estimating. A specific description without a number is still far better than a made-up figure.
Where M fits
Every query has an M script behind it, whether the editor wrote it or you did. Microsoft's documentation explains that the Applied Steps pane is a friendly view of that script, and that you can open the full code in the Advanced Editor (Understanding query evaluation and query folding, Microsoft Learn).
Be honest about your level, because it is easy to test. A fair scale:
- Reads M: can open the Advanced Editor, follow the steps and fix a broken step reference.
- Edits M: changes generated code by hand, for example replacing a hard-coded column list with one built from
Table.ColumnNames. - Writes M: writes custom functions, uses
eachand_confidently, handles errors withtry … otherwise.
"Reads and edits M in the Advanced Editor" is a perfectly good line. Claiming to write M and then freezing at a let expression does more damage than the claim was worth. If you are at level 1 and want to move up, the lesson on reading the M behind the Applied Steps is the place to start.
How to prove it: a small portfolio
A CV makes claims; a portfolio lets someone check them. For Power Query, a portfolio doesn't need to be large. Two or three queries, each solving one recognisable problem, are enough to make an interviewer confident you have done the work.
What a good portfolio piece contains
Each piece should be something a reviewer can open in five minutes:
- A short description of the business problem in one or two sentences.
- The raw input, anonymised or invented, small enough to read at a glance.
- The query itself, with step names that say what each step does. A naming convention for queries and steps helps here.
- The output, and one or two checks that show it is right.
Never use an employer's real data. Recreate the shape of the problem with invented rows: the layout, the messy values and the edge cases are what matter, not the real customer names.
Here is the kind of query that works well as a portfolio piece. It takes a small sales export with a repeated order, untidy region names and an amount that isn't a number, and produces a summary by region:
let
Source = #table(
{"Order ID", "Region", "Amount"},
{{"00412", " north ", "120.50"}, {"00413", "South", "n/a"}, {"00414", "NORTH", "80"}, {"00413", "South", "n/a"}}
),
Deduped = Table.Distinct(Source, {"Order ID"}),
Cleaned = Table.TransformColumns(Deduped, {{"Region", each Text.Proper(Text.Trim(_)), type text}}),
Typed = Table.TransformColumns(Cleaned, {{"Amount", each try Number.From(_, "en-GB") otherwise null, type nullable number}}),
ByRegion = Table.Group(Typed, {"Region"}, {{"Orders", each Table.RowCount(_), Int64.Type}, {"Revenue", each List.Sum([Amount]), type nullable number}})
in
ByRegionResult
| Region | Orders | Revenue |
|---|---|---|
| North | 2 | 200.5 |
| South | 1 | null |
Output produced by the Power Query Exercises simulator, an independent implementation of a documented subset of M.
The result has two rows: North with 2 orders and revenue 200.5, and South with 1 order and a null revenue, because its only amount was "n/a". That null is the interesting part to talk about. A reviewer will ask whether South should show null, zero or an error, and your answer shows how you think about data quality. The order ID stays as text so "00412" keeps its leading zeros, a point the lesson on choosing types deliberately explains.
Add a check that fails loudly
A clear sign of experience with Power Query is planning for what happens when the data changes. Adding a validation step to a portfolio piece shows you have thought about next month, not just today:
let
Source = #table({"Order ID", "Amount"}, {{"00412", 120.5}, {"00413", null}, {"00414", 80}}),
Missing = Table.RowCount(Table.SelectRows(Source, each [Amount] = null)),
Checked = if Missing > 0
then error Error.Record("Validation failed", Text.From(Missing) & " order(s) have no amount", null)
else Source
in
CheckedResult: an error
Validation failed: 1 order(s) have no amount
Output produced by the Power Query Exercises simulator, an independent implementation of a documented subset of M.
This query raises the error "Validation failed: 1 order(s) have no amount" instead of quietly loading a total that is too low. Whether stopping the refresh is the right choice depends on who uses the report, and saying that out loud in an interview is a strong answer. The lesson on validating data and failing loudly covers the trade-offs.
Where to put the portfolio
Keep it simple: a public repository or a shared folder with each query's M code in a text file, the sample input as a small CSV, and a short read-me for each piece. Put the link in the CV header next to your email. A reviewer is far more likely to open one link than to request files.
How to prove it in the interview
Some analyst interviews include a practical task: here is a messy file, clean it and answer a question within a set time. You can't bluff through that, but you can prepare for it.
Practise against the clock
Doing an exercise slowly at home is different from doing it with someone watching. Set a timer, take a task you haven't seen, and talk through what you're doing as you go. The guide on preparing for a Power Query practical test lists the task types that come up most and how to pace them.
Timed tasks worth rehearsing include combining files, unpivoting a wide report, merging two tables and explaining the row count, and finding the second-highest value per group. The interview task on second-highest salary per department is a good test of whether you can handle ties under pressure.
Explain your query, not just the result
Interviewers want to know why each step is there. A short, practised explanation of one of your portfolio queries (input, steps, checks, what you would change for a larger source) is often worth more than finishing the task a few minutes early. The lesson on explaining your query in an interview gives a structure for that answer.
Two topics come up often enough to prepare a sentence for each:
- Query folding: when the source is a database, Power Query tries to translate steps into a query the source runs itself; files such as CSV and Excel don't fold (Microsoft's query folding overview). Knowing which of your steps would stop folding shows you have thought about performance.
- Where Power Query stops and DAX begins: shaping rows and columns belongs in Power Query; measures that respond to report filters belong in DAX. The guide on Power Query M versus DAX sets out the line. The post on where each step belongs across SQL, Power Query and DAX adds the database.
Certifications: useful, but not proof on their own
If you work with Power BI, the PL-300 certification is the obvious one, and its study guide gives preparing data a weight of 25–30% of the exam (PL-300 study guide). It is a reasonable line to add, and the study guide's skills-measured list is a handy checklist even if you never sit the exam.
Treat a certificate as a supplement to the portfolio, not a replacement. It shows you studied the material; a runnable query shows you can apply it to a file that doesn't behave.
A checklist before you send the CV
- Each Power Query bullet names an input, a transformation and a safeguard.
- No feature lists without context.
- Your M level is stated honestly.
- Any number on the CV is one you can explain.
- Two or three portfolio pieces, with invented data, linked from the header.
- At least one timed practice run on a task you hadn't seen before.
If you want material for the portfolio and timed practice, the projects and interviews exercises on Power Query Exercises run in the browser and check your result against hidden test cases, so you know a query works before you show it to anyone.
Frequently asked questions
Should I write "Power Query" or "Get & Transform" on my CV?
Write "Power Query". It is the name Microsoft uses for the engine across Excel, Power BI and its other hosts, and it is the term most job adverts use for this skill. Some Excel menus call the feature Get & Transform, so you can mention both, and add "(Excel and Power BI)" to show where you used it.
Is Power Query worth listing if I've only used it in Excel?
Yes. It is the same engine in Excel and Power BI, with differences in where results load, how refresh is scheduled and which connectors are available, so the skills transfer directly. Say which product you used, and if you're applying for Power BI roles, the lesson on Power Query in Excel and Power BI explains what changes. The post on whether Power Query is worth learning covers who it helps most.
How do I show Power Query skills without work experience?
Build the portfolio from practice problems that mirror real work (combining monthly files, cleaning a messy export, reconciling two lists) and describe them as projects, not jobs. Be clear that the data is invented. Reviewers respect that more than vague claims of experience.
Sources
- What is Power Query?, Microsoft Learn (learn.microsoft.com)
- Study guide for Exam PL-300, Microsoft Learn (learn.microsoft.com)
- Understanding query evaluation and query folding, Microsoft Learn (learn.microsoft.com)
About the author
Tahir Nas, software engineer, writes and reviews the lessons, guides and exercises on Power Query Exercises. Tahir has 8 years of experience in tech, working across system administration, cloud architecture, QA, scripting and automation, and software engineering in many languages and mainstream databases. GitHub profile. Every M example shown with a result was run in the site's simulator when the page was built, and the output is that run's result; examples marked for Excel and Power BI only are shown without output. How content is tested.
Keep reading
- How long does it take to learn Power Query? A realistic timelineA stage-by-stage timeline for learning Power Query, from a first useful query to writing M functions, with a self-test for each stage.
- Is Power Query worth learning? Who it helps and who can skip itWho gets real value from learning Power Query, who can safely skip it, how the skill builds in stages, and what to learn first if you decide it pays off.
Practise Power Query in the browser with graded exercises checked against fresh data.
Power Query Exercises is an independent educational platform and is not affiliated with, endorsed by, sponsored by, or approved by Microsoft Corporation. All third-party trademarks belong to their respective owners.