Example only: fictional experience
The following resume is an educational example, not a real candidate, testimonial, or verified career history. Employers and institutions are placeholders. Replace every detail with your own; omit anything you cannot support.
Example Candidate
Data Analyst | City | Professional email | Relevant portfolio
Summary
Data analyst using SQL, spreadsheets, and Power BI to investigate operational questions. Checks data quality, documents metric definitions, and explains findings to non-technical stakeholders.
Experience or relevant work
Data Analyst | Example Operations Team
Dates: use your actual start and end dates
- Created a weekly fulfillment dashboard with agreed definitions for delayed orders and the reporting cutoff.
- Reconciled duplicate customer records before joining order and support data, and documented the exclusions.
- Presented a breakdown of delivery delays by processing stage so operations could choose which workflow to investigate.
Selected project
Public Transport Delay Analysis
- Cleaned a public demonstration dataset, recorded missing-value decisions, and compared delay distributions by route.
- Published SQL queries and a dashboard with a limitations note explaining why correlation does not establish causation.
Skills
SQL / Excel / Power BI / Data cleaning / Descriptive statistics / Data visualization / Metric definitions
Education
B.Sc in Statistics | Example College
Why these bullets work
The examples name a specific artifact, explain a method, and show what was checked or changed. This makes the contribution easier to discuss in an interview without relying on invented impact numbers. Keep supporting notes or links where you are permitted to share them.
Rewrite pattern: Replace "responsible for projects" with "implemented [specific change] using [method] and verified [observable result]." Fill each bracket with a fact from your own work.
Writing tips for this role
- Name the decision your analysis supported rather than only the number of dashboards built.
- Show how you checked joins, missing data, and the denominator of a metric.
- For portfolio datasets, record the actual source and license rather than claiming private company results.
Common mistakes to avoid
- Treating a chart as an analysis without a business question.
- Claiming causal impact from an observational comparison.
- Listing machine learning expertise when the evidence is a basic spreadsheet exercise.