Most people who put "Excel expert" on a CV are describing advanced skills — pivot tables, Power Query, a tidy protected workbook. Genuine expert level is a different job: connecting several tables into one data model, writing DAX measures that recalculate correctly under any filter, and building tools for people who will never see a formula bar. Here is where the real line sits.
What "Expert" Actually Covers
The centrepiece is the data model: multiple tables — sales, products, regions, dates — connected through relationships in Power Pivot instead of merged into one flat sheet through repeated VLOOKUPs. That single change removes an entire category of maintenance work, because the tables update independently and the relationships between them stay intact.
On top of the model sits DAX (Data Analysis Expressions): measures that calculate totals, ratios and running values across the model and respond correctly to whatever filter is applied — a date range, a single region, a product category — without being rebuilt for each one. A cell formula has to be copied and adjusted for every new view; a DAX measure does not.
Alongside the model: advanced Power Query for merging and reshaping data from multiple sources before it ever reaches a sheet, and VBA or Office Scripts for automating a workflow that spans several files or an entire recurring process, not just one repeated click sequence within a single workbook.
What Genuinely Still Trips Up Experts
- A relationship in the data model set to the wrong direction, so a filter on one table silently fails to affect a related one
- A DAX measure that is correct in total but wrong at a specific filter combination — the hardest class of Excel bug to spot, because most of the report looks right
- A model that scales badly once the source data grows past what it was designed for, turning a fast report into a slow one
- Tooling built by one expert that the next person cannot maintain, because DAX and data-model design are far less commonly known than cell formulas
The last one is the real ceiling of the tier. Expert Excel work is powerful and comparatively rare, which means the maintainability problem that advanced Excel solved with protection and named ranges reappears here in a harder form: the next person who opens the file may not know the tools well enough to fix it at all.
What to Put on a CV at This Level
Name the components: "Power Pivot data models, DAX measures, advanced Power Query, VBA/Office Scripts automation" is specific and checkable. It also tells the reader exactly what to test you on, which is the honest version of an expert claim.
If the work stops at a very well-built single workbook — structured tables, named ranges, protection, one automated macro — that is advanced, not expert, and the distinction is worth keeping straight on a CV. An interviewer who asks a data-modelling question and gets a pivot-table answer will notice the gap immediately.
Where This Actually Stops
Past this point the tool usually stops being Excel. Multi-user real-time collaboration, enterprise-scale data volumes, and shared governed reporting move into Power BI, SQL, or a dedicated BI platform, and the skills transfer heavily — DAX in Excel is the same DAX in Power BI — but the tool changes.
The Excel Skills test is scenario-based across formulas, lookup, data handling and presentation, which places its ceiling around the advanced tier rather than testing full data-model design — a genuinely useful gut check on the fundamentals even for someone operating at expert level day to day. If the role leans on interpreting the numbers a model produces rather than building the model itself, the Numerical Reasoning test is the more relevant companion check.
A Note on Calling Yourself an Expert
Because "Excel expert" is such a common overstatement, some hiring teams have started reading it as a mild negative signal rather than a neutral one — a sign the candidate has not seen genuine expert-level work up close and does not know how far the tier actually goes. Naming the specific components you can do avoids that entirely, and it costs nothing extra on a CV to be precise.
The upside of precision runs the other way too. A candidate who lists "structured tables, protection, Power Query" honestly at the advanced tier reads as more credible than one who claims "expert" and cannot explain what a DAX measure is when asked — and in a screening conversation, that difference decides which candidate the interviewer trusts on everything else they said.