Uncodemy Success Story: A Data Analytics Career Change

Data Analytics · Career Change Story

Uncodemy Success Story — A Data Analytics Career Change (Composite)

SECTION 01The starting point: who this composite learner is

Let us call our composite learner the switcher. The switcher is in their late twenties, has a commerce or arts degree, and has spent a few years in a non-tech role such as sales operations, customer support, logistics or accounts. They already use Excel every week, mostly for simple lists and SUM formulas, and they keep noticing that the people who can pull and explain numbers get listened to in meetings. That curiosity is usually how a data analytics career change begins.

We built this story from the questions and steps that career changers commonly share in counselling sessions and classes. It is not a real person, and we make no claims about any specific salary, company or timeline. The aim is to show a realistic route, with the doubts and slow weeks included, so you can plan your own switch honestly.

SKILLS AUDIT (rate 0-3 before you start)

Excel formulas (SUMIFS, XLOOKUP)    : __
Pivot tables and charts             : __
Comfort reading numbers in reports  : __
Writing clear emails and summaries  : __
Explaining a problem to a manager   : __
Any SQL or database exposure        : __
Basic statistics (mean, median, %)  : __

Score 0-1 on a line = plan extra practice there.
Communication scores matter as much as tool scores.

REASONS CHECK (write one line each)

Why do I want analytics?         ______________
Which problems at work made me   ______________
  curious about data?
What hours per week can I give?  ____
What will I do on a bad week?    ______________
Who can review my projects?      ______________

If the first two lines are vague, try two weeks of
free Excel and SQL practice before paying for a course.

SECTION 02Three learning phases: from Excel to a working portfolio

The switcher's learning naturally fell into three phases. In Phase 1, they firmed up Excel and learned SQL from zero — SELECT, WHERE, GROUP BY, JOINs and then window functions. In Phase 2, they learned Power BI and basic statistics and used both on case studies. In Phase 3, the focus moved to job search: resume, portfolio and interviews. The phases overlapped, and the timeline depends on how many hours each week you can give.

The weeks that felt slowest were the SQL weeks. Joins and GROUP BY confuse almost everyone at first. What helped was solving small problems every day on a practice database instead of watching more videos, and asking the trainer to review queries that returned wrong totals.

-- Orders per city with average order value
SELECT
  c.city,
  COUNT(o.order_id)          AS orders,
  ROUND(AVG(o.amount), 2)    AS avg_order_value
FROM orders o
JOIN customers c ON c.customer_id = o.customer_id
WHERE o.order_date >= '2026-01-01'
GROUP BY c.city
HAVING COUNT(o.order_id) >= 50
ORDER BY avg_order_value DESC;

-- Monthly revenue with a running total (window function)
SELECT
  month,
  revenue,
  SUM(revenue) OVER (ORDER BY month) AS running_revenue
FROM (
  SELECT
    DATE_TRUNC('month', order_date) AS month,
    SUM(amount)                     AS revenue
  FROM orders
  GROUP BY DATE_TRUNC('month', order_date)
) m
ORDER BY month;

-- DATE_TRUNC is PostgreSQL syntax; in MySQL use
-- DATE_FORMAT(order_date, '%Y-%m-01') instead.

SECTION 03Using the old job: domain projects that stand out

The biggest turning point for the switcher was realising that their previous job was an asset. Instead of building another generic sales dashboard, they built projects around problems they understood from work — delivery delays, customer complaints, returns, or collections — using public or anonymised data. In interviews, they could explain not just how they built a chart but why the business would care.

Each project followed the same structure: a business question, the data and how it was cleaned, the analysis, a dashboard, and two or three recommendations. Writing the recommendation was harder than building the dashboard, and it was also the part interviewers asked about most.

import pandas as pd

# Load an anonymised delivery dataset
df = pd.read_csv("deliveries.csv", parse_dates=["promised_date", "delivered_date"])

# Basic cleaning
df = df.drop_duplicates(subset="shipment_id")
df["route"] = df["route"].str.strip().str.title()

# Delay in days and late flag
df["delay_days"] = (df["delivered_date"] - df["promised_date"]).dt.days
df["is_late"] = df["delay_days"] > 0

# Late share by route, worst first
summary = (df.groupby("route")["is_late"]
             .mean()
             .sort_values(ascending=False)
             .round(3))
print(summary.head(10))

-- Late delivery rate by weekday
SELECT
  EXTRACT(DOW FROM promised_date) AS weekday,  -- 0 = Sunday
  COUNT(*) AS shipments,
  ROUND(100.0 * SUM(CASE WHEN delivered_date > promised_date
                         THEN 1 ELSE 0 END) / COUNT(*), 1) AS late_pct
FROM deliveries
GROUP BY EXTRACT(DOW FROM promised_date)
ORDER BY late_pct DESC;

SECTION 04Templates for your own career change

Use these to plan your weeks, document projects and rewrite your resume the way the composite switcher did.

WEEKLY PLAN FOR A WORKING CAREER CHANGER

Class days       : Sat / Sun (weekend batch)
Weekday evenings : 45 min x 4 — practice, not videos
  Mon  SQL: 5 small queries
  Tue  Excel or Power BI: rebuild one visual
  Wed  Statistics: one concept + example
  Thu  Project work: one small step
Friday           : rest or catch-up
Sunday night     : commit work to GitHub, note doubts

Bad week rule    : do 15 minutes, not zero.

PROJECT WRITE-UP

Title        : Why deliveries run late on certain routes
Context      : My earlier role involved shipment tracking
Question     : Which routes and weekdays drive delays?
Data         : public/anonymised, ~__ rows, 2 tables
Cleaning     : duplicates removed, route names standardised
Analysis     : late % by route and weekday, delay distribution
Finding      : ______________________________
Recommend    : 1. ________  2. ________
Limitations  : sample data, no weather information
Links        : dashboard [ ]  code [ ]

RESUME BULLETS — reframing a non-tech role

Before: Handled daily shipment tracking.
After : Tracked daily shipments in Excel and flagged
        delayed routes to the operations manager.

Before: Prepared monthly reports.
After : Built monthly performance reports with pivot
        tables; automated lookups with XLOOKUP.

Projects section:
- Delivery delay analysis (SQL, Power BI) — [link]
- Complaint trend dashboard (Excel, Power BI) — [link]

SECTION 05Lessons from the composite career change

These lessons came up again and again in the path we described:

• Practise more than you watch — typing queries yourself builds skill far faster than replaying lectures.
• Lead with your domain — your previous industry is what makes your projects different from everyone else's.
• Finish fewer, better projects — three complete case studies with recommendations beat ten half-built dashboards.
• Get feedback early — show your first dashboard to a trainer before polishing it.
• Expect a slow middle — the joins-and-data-model stage feels hard for almost everyone; it passes with practice.

SECTION 06Interview Q&A — career changers into data analytics

SECTION 07Test yourself — planning a data analytics switch

SECTION 08Frequently asked questions

SECTION 09Related reads