Technical screening questions
Ask for one example per question and listen for specifics.
- What is a level of detail (LOD) expression and when do you use one? A good answer: Computing at a different granularity than the view, with a real example.
- How do you speed up a slow dashboard? A good answer: Extracts, fewer marks, simpler filters and data model changes.
- Live connection or extract? A good answer: Freshness against performance and load on the source.
- How do you manage permissions on Tableau Server? A good answer: Projects, groups and row-level security.
- Describe a dashboard that changed a decision. A good answer: The question, design choices and the outcome.
Quick screening questions
Use these when you have only a few minutes.
- Show a dashboard you built and who used it.
- When do you use LOD expressions?
- How do you speed up a slow workbook?
What separates the levels
Match the level to the requirement before you submit.
- Junior: builds views from specs.
- Mid: owns data sources and dashboards.
- Senior: sets governance and design standards.
Red flags
Any of these is a reason to probe further.
- Only built charts, no data prep.
- Cannot explain LOD expressions.
- No server administration exposure for a lead role.
Tools you should hear mentioned
A Tableau developer with real experience usually names several of these without prompting.
- Tableau Desktop
- Tableau Server or Cloud
- Calculated fields and LOD expressions
- SQL
- Prep Builder
- Extracts
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a Tableau developer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.