Non-IT Graduate Career Change: Is Big Data the Right Move?

Big Data is not one job.
It is a set of roles around large datasets.

Most entry-level "big data" jobs are:
- Data analyst
- BI analyst
- Reporting analyst
- Junior data engineer (less common)
- Data ops / platform support

Very few entry-level jobs are:
- Data scientist on large datasets
- Senior Spark engineer
- ML engineer

Those roles exist, but they usually need
2-4 years of prior data or engineering experience.

Non-IT graduates most often enter through:

1. Data Analyst
   - SQL, Excel, Power BI or Tableau
   - Business questions and reporting
   - Easiest entry from any background

2. BI Analyst
   - Dashboards, KPIs, stakeholder reporting
   - Similar to analyst but more dashboard-heavy

3. Junior Data Engineer
   - ETL, SQL, some Python
   - Usually needs a bit more technical skill

4. Data Ops / Platform Support
   - Monitoring pipelines, fixing failures
   - Needs comfort with tools and systems

The "big data stack" usually comes after
one of these entry roles, not before.

If you come from commerce or finance:
→ BI Analyst or Data Analyst in fintech, banking, retail

If you come from operations or support:
→ Data Ops or BI Analyst

If you come from marketing or sales:
→ Data Analyst with marketing or growth focus

If you come from teaching or research:
→ Data Analyst with strong documentation skills

If you come from a technical trade:
→ Junior Data Engineer or Data Ops

Domain experience is an advantage, not a weakness.

Roles that are hard as a first step:

- Data Scientist on day one
  Needs math, stats, ML, and projects
  Usually needs 2-4 years of related work

- Spark / Hadoop Engineer on day one
  Needs strong systems background
  Usually comes after data engineering experience

- ML Engineer
  Needs software engineering + ML depth

Avoid these as a first job.
They are fine as a second or third job.

Realistic first-job titles for non-IT graduates:

- Junior Data Analyst
- Business Analyst (data-heavy)
- BI Analyst
- Reporting Analyst
- MIS Executive (with SQL)
- Data Quality Analyst
- Junior ETL Developer
- Data Ops Associate

These are entry points.
After 1-2 years, you can move toward
bigger data roles and stack.

SQL checklist for a career change:

□ SELECT, WHERE, ORDER BY
□ JOINs (inner, left, right)
□ GROUP BY and HAVING
□ Subqueries
□ CTEs (WITH clauses)
□ Window functions (ROW_NUMBER, LAG)
□ Basic date and string functions
□ Understanding indexes and slow queries

Practice on:
- Sales data
- Customer data
- Any free public dataset

BI tool checklist:

□ Connect to a database
□ Build a simple table visual
□ Build a bar chart and line chart
□ Add filters and slicers
□ Create a summary page with KPIs
□ Publish or share a dashboard

Pick ONE tool and finish a project:
- Power BI (free desktop version)
- Tableau Public (free)
- Metabase (free, open source)
- Google Looker Studio (free)

Demos beat certificates.

Python checklist:

□ Read a CSV or SQL query into pandas
□ Clean missing values
□ Rename and select columns
□ Group and aggregate data
□ Merge two dataframes
□ Basic plotting
□ Write a small reusable function

You do not need ML for most
data analyst and data engineer entry roles.
Focus on cleaning, analysis, and automation.

Phase 1 — SQL and Excel:

Daily practice:
- 30 minutes theory (joins, groups, subqueries)
- 60 minutes writing queries on a real dataset
- 30 minutes reviewing mistakes

Weekly goal:
- 5 working queries on a real dataset
- 1 short writeup explaining what you found

Do not move on until:
- You can write a JOIN without help
- You can use GROUP BY confidently
- You can explain a query line by line

Phase 2 — BI tool:

Pick one tool: Power BI, Tableau Public, or Metabase.

Week 1-2:
- Connect to a database or CSV
- Build simple tables and charts

Week 3-4:
- Build a summary page with 4-5 KPIs
- Add filters and slicers
- Publish the dashboard

Week 5-6:
- Pick a new dataset
- Build a second dashboard
- Write a README explaining the goal and findings

Do not jump between tools.
Finish one, then continue.

Phase 3 — Python basics:

Week 1-2:
- Read CSV and SQL results into pandas
- Clean missing values, rename columns

Week 3-4:
- Group and aggregate
- Merge two dataframes

Week 5-6:
- Write a small reusable cleaning script
- Plot a few charts

Week 7-8:
- Take a real messy dataset
- Clean it and summarise it
- Write a short report

Do not chase ML.
Cleaning and automation are the goal.

Phase 4 — Portfolio and domain focus:

- Finish two end-to-end projects
- Write clear READMEs for both
- Pick a domain to highlight
  (finance, retail, healthcare, marketing, etc.)
- Include one project in that domain
- Prepare one story about a bug or insight

Phase 5 — Apply and interview:

- Update resume and LinkedIn with projects
- Apply to 5 tailored roles a day
- Practice SQL interview questions
- Practice explaining your projects
- Do mock interviews with a friend or mentor
- Track applications and follow up

Realistic expectations:
- 8-12 weeks of applying is normal
- Rejections are part of the process
- One offer changes everything

Portfolio checklist:

□ Two end-to-end projects
□ One with strong SQL focus
□ One with a BI dashboard
□ Clear READMEs with problem, data, findings
□ Screenshots of dashboards
□ Code you can explain line by line
□ A short writeup for each project
□ All hosted on GitHub

Hiring managers look for:
- Clarity of thinking
- Real data, not toy datasets
- Clean presentation
- Domain relevance

Resume checklist:

□ Clear title: "Data Analyst (Career Switch)"
□ Skills: SQL, Excel, Power BI, Python
□ Projects listed first, not coursework
□ Each project has:
   - One line on the problem
   - One line on the tools used
   - One line on the outcome
□ Soft skills backed by example
□ LinkedIn matches the resume
□ No vague phrases like "hardworking team player"

Interview story checklist:

Prepare these three stories:

1. A project you built
   - What was the goal?
   - What data did you use?
   - What did you find?
   - What would you do next?

2. A bug or issue you fixed
   - What was broken?
   - How did you debug it?
   - What did you learn?

3. A time you explained something clearly
   - Who was the audience?
   - How did you simplify it?
   - What was the outcome?

These stories matter more than grades.