Can a Bank Employee Become a Data Engineer Without a Degree?

What you already do            →  What it maps to in data engineering
--------------------------------  ------------------------------------------
Reconciling ledgers               →  Data validation and quality checks
Preparing regulatory reports      →  Building ETL / ELT pipelines
Working with core banking systems →  Understanding source systems
Handling customer data            →  Data privacy and governance
Explaining issues to managers     →  Stakeholder communication

Your unfair advantage:
You understand the business meaning of the data.

Most bootcamp graduates can write Python.
Far fewer understand why a transaction record
has three different timestamps and which one
the risk team actually cares about.

You do.

Minimum viable skill set for a data engineer role:
☐ SQL — joins, aggregations, window functions
☐ Python — pandas, basic scripting, error handling
☐ Data modeling — fact/dimension tables, normalization
☐ ETL / ELT — at least one end-to-end pipeline
☐ One cloud platform — S3 + BigQuery or Snowflake
☐ Git — clone, commit, push, pull request
☐ Basic orchestration — cron or Airflow DAG

You do not need:
✗ Advanced algorithms and data structures
✗ Compiler design or operating systems theory
✗ A CS degree
✗ Every cloud certification
✗ Deep ML knowledge (that's a different role)

You need depth in the core stack, not breadth across everything.

Weekday schedule (2 hours):
7:00–7:30 PM   SQL practice
7:30–9:00 PM   Python or project work

Weekend schedule (4 hours each):
Saturday       Deep project work
Sunday         Review, documentation, next week planning

Total: ~18 hours a week

Weekly review questions:
☐ Did I complete at least 5 SQL exercises?
☐ Did I write any Python code this week?
☐ Is my project progressing, or stuck?
☐ What did I learn that I couldn't explain last week?
☐ Am I on track for this month's checkpoint?

Project 1 — Transaction ETL:
- Source: synthetic bank transaction CSV
- Python script cleans and loads into a database
- SQL queries answer three business questions
- README explains the pipeline, not just the code

Project 2 — Loan Default Analysis:
- Model a star schema (fact_loans, dim_customer, dim_date)
- Build a small ELT pipeline
- Write SQL that answers a risk question

Project 3 (optional) — Fraud Flag Pipeline:
- Rule-based transformation
- Scheduled with cron or Airflow
- Shows orchestration, not just scripting

Every project README should answer:
☐ What problem does this solve?
☐ What is the source data?
☐ How does the pipeline work?
☐ What did you personally build?
☐ How would you scale this in production?
☐ What would you do differently next time?

Job search order:
1. Internal transfer — talk to your bank's data team
2. Adjacent roles — data analyst, BI developer, ETL developer
3. Fintech companies — your domain is a selling point
4. Banking tech vendors — they need people who know banking

Application rules:
☐ Customize every application
☐ Link your portfolio in the resume
☐ Mention your banking domain explicitly
☐ Apply to roles that say "or equivalent experience"

Resume framing:
Instead of: "Bank operations executive, 5 years"
Write: "Banking operations professional with 5 years
of experience in transaction reconciliation,
regulatory reporting, and SQL-based reporting —
now building ETL pipelines in Python and SQL."

The switch is part of the story, not a secret.