Interview Questions for Hiring a Data Analyst
Use these grouped interview questions to assess a Data Analyst candidate's technical competency, analytical reasoning, and ability to translate data into business decisions. Each question category—technical skills, business impact, and communication—includes clear markers for strong versus weak responses, plus flags for legally sensitive areas under Swiss employment law.
A Data Analyst in a Swiss SME must combine SQL and visualization skills with the ability to support non-technical stakeholders. This guide provides structured questions organised by competency, with guidance on what strong answers demonstrate and where Swiss employment law creates risks.
Before any interview, confirm the role's Pensum percentage and whether the position reports to finance, operations, or IT. That context shapes which technical questions matter most.
Technical & Analytical Skills
Test the candidate's hands-on ability with databases, spreadsheets, and business intelligence tools. Ask them to walk through a real example from their previous role—not a textbook case.
A strong answer includes specific tool names (SQL Server, Tableau, Power BI), describes a concrete project outcome (e.g. 'reduced report generation time from 4 hours to 20 minutes'), and acknowledges limitations they encountered. A weak answer is generic ('I'm good with Excel') or theoretical.
- Describe a time you wrote SQL to extract data for a business question. What was the question, and how did you validate your result?
- Walk me through how you'd approach a dataset you've never seen before. What's your first step?
- Which data visualization tool do you use most, and why? Give an example where the wrong chart type misled stakeholders.
- Tell me about a time a stakeholder asked for a metric that didn't exist. How did you handle it?
- Have you worked with automated data pipelines or ETL processes? Describe what went wrong once.
- What's the difference between a correlation and causation, and when has that distinction mattered in your work?
Business Acumen & Impact
Data Analysts who thrive in SMEs understand the business context, not just the data. Ask about their experience translating numbers into decisions that affected revenue, cost, or risk.
Strong answers show curiosity about *why* a metric matters, evidence of follow-up after delivering a report, and naming a specific business outcome. Weak answers treat analysis as a technical exercise divorced from strategy.
- Describe an analysis you completed that led to a real business decision. What happened after you delivered the result?
- When you present findings to a non-analyst manager, how do you decide what to show and what to leave out?
- Tell me about a time you spotted something unexpected in the data. How did you investigate, and what did you do with it?
- What KPIs or metrics are most critical in your industry, and why?
- Have you worked with a GAV (collective labour agreement) or sector-specific compliance reporting? How did you ensure accuracy?
- Describe a project where the data didn't support what stakeholders hoped to see. How did you communicate that?
Communication & Collaboration
In an SME without a dedicated analytics team, the Data Analyst must work across departments and explain technical concepts to non-technical leaders. Assess how they handle ambiguous requirements and push back constructively.
Strong answers include examples of clarifying a vague request, showing their work to build trust, and admitting when they need help. Weak answers suggest working in isolation or dismissing non-technical input.
- Give me an example of a time you had to explain a statistical concept or data limitation to someone without a technical background.
- How do you handle a request for an analysis when the requirement is unclear? Walk me through a real example.
- Tell me about a disagreement with a colleague—analyst or not—over how to interpret data. How did you resolve it?
- Do you document your analysis process? Show me an example of documentation you're proud of.
- ⚠️ LEGAL FLAG: Do not ask about family, age, or plans to relocate within Switzerland. See FAQ below.
- How do you stay current with tools and techniques? Have you completed any certifications (optional but valued: Coursera, DataCamp)?
Frequently asked questions
- Which questions are illegal or risky under Swiss employment law?
- Avoid questions about age, family status, plans to have children, religion, political views, or health (except job-specific fitness). The Swiss Labour Code and regional cantonal rules protect personal rights. Questions about residential stability or relocation plans within Switzerland are not inherently illegal but risk discrimination claims if they influence hiring decisions based on protected status. When in doubt, consult an employment lawyer in the relevant canton before interview.
- Should I ask about salary expectations or previous salary?
- You may ask about salary expectations for the role. However, asking what they earned previously is legally risky in Switzerland and unnecessary—focus on the market rate for the Pensum and location. Some cantons (e.g. Zurich, Geneva) have stronger equal-pay rules, making salary history questions more problematic. Stick to transparent salary bands for your role.
- How do I evaluate their technical level if I'm not technical?
- Ask candidates to use plain language when explaining concepts, and request concrete examples over theory. Listen for specificity: tool names, project outcomes, and honest acknowledgment of gaps matter more than jargon. If technical validation is critical, consider a short technical screen with a colleague or external advisor before the final interview. Many Data Analysts are comfortable explaining their skills to non-technical hiring managers.
General information for Swiss employers, not legal advice. Have a lawyer confirm anything with legal consequences.