Data Analyst · Git · GitHub
How Git and GitHub Help You Land a Data Analyst Job
Where Git and GitHub actually show up
| Situation | How much Git matters |
|---|---|
| Applying for a first analyst job | GitHub is useful as a public portfolio; deep Git knowledge is rarely tested |
| Excel and BI reporting teams | Often not used at all; files live on SharePoint or shared drives |
| Teams that write SQL or Python in code repositories | Expected: branches, pull requests and reviews are part of daily work |
| Analytics engineering (dbt, data pipelines) | Essential; every change goes through Git |
Read the job description. If it mentions dbt, Airflow, "version control" or "code review", Git is part of the job. If it lists Excel, Power BI and MIS reporting only, it is a bonus.
What to learn first
- SQL, because almost every analyst interview tests it.
- Excel, including pivot tables and lookups.
- One BI tool: Power BI or Tableau.
- Python with pandas, for roles that ask for it.
- Git and GitHub, once you have two or three projects worth showing. A weekend is enough for the basics.
The data analyst syllabus guide lays out the full skill list.
How GitHub helps a job application
- Proof of work. A recruiter or hiring manager can open your SQL queries, notebook and dashboard screenshots in a minute.
- Readable notebooks. GitHub renders Jupyter notebooks in the browser, so reviewers see your analysis and charts without installing anything.
- Visible thinking. A good README explains the business question, data source, method and findings, which is what interviewers ask about.
- One link. You can put a single profile link on your resume and LinkedIn.
A GitHub profile does not replace a good resume. It supports it. Optimising your resume for ATS covers the resume side.
The commands you need
# one-time setup
git config --global user.name "Your Name"
git config --global user.email "you@example.com"
# start a project and make the first commit
git init
git add README.md analysis.ipynb queries/
git commit -m "Add sales analysis notebook and SQL queries"
# connect to an empty GitHub repo and upload
git remote add origin https://github.com/your-username/sales-analysis.git
git branch -M main
git push -u origin main
# everyday loop
git status
git add queries/monthly_revenue.sql
git commit -m "Add monthly revenue query"
git pushThat set (init, add, commit, push, status, plus git log to see history) covers most portfolio use. Branches and pull requests matter when you join a team that uses them.
What a good analyst repository looks like
sales-analysis/
├── README.md question, data source, method, key findings
├── data/
│ └── README.md where to download the raw data (not the data itself)
├── queries/
│ └── monthly_revenue.sql
├── notebooks/
│ └── analysis.ipynb
├── dashboard/
│ └── screenshots/ PNGs of the Power BI or Tableau report
└── .gitignoreA README outline that works:
# Monthly sales analysis
**Question:** Which product categories drove the revenue drop in Q3?
**Data:** Public retail dataset (link), 2 years of orders.
**Tools:** SQL (PostgreSQL), Python (pandas), Power BI.
## Findings
1. ...
2. ...
## How to reproduce
1. Download the data from the link above into data/
2. Run queries/monthly_revenue.sql
3. Open notebooks/analysis.ipynbFor project ideas that suit this structure, see building a job-ready analytics portfolio and the end-to-end analytics portfolio project.
Pitfalls specific to data work
- Never upload confidential or personal data. Use public datasets, or remove anything that identifies people. Keep data files out with
.gitignore. - Large files. GitHub warns about files over 50 MB and blocks files over 100 MB. Link to the data source instead of committing big CSVs.
- Secrets. Do not commit database passwords or API keys in notebooks or config files. If you do, rotate them; deleting the file later does not remove it from history.
- Power BI files. A
.pbixfile is binary, so Git cannot show what changed. Power BI's project format (.pbip) saves the report and model as text files that work with version control. - Empty profiles. Ten forked repositories with no changes look worse than two original, well-documented ones.
Interview questions you may get
If the role uses Git, expect basic questions such as the difference between Git and GitHub (Git is the version control tool; GitHub is a hosting service for Git repositories), what a commit is, and how a pull request works. For the technical core of analyst interviews, practise with common SQL interview queries.