Zach Wilson Portfolio
GitHub profile of data engineer Zach Wilson (DataExpert.io), home base for the Data Engineering Handbook (44.2k stars and 132 contributors on the DataExpert-io repo) plus the free beginner and intermediate bootcamp material published inside it.
Location
San Francisco, CA
Companies
Skills
Notable
- Data Engineering Handbook: 44.2k GitHub stars, 9.3k forks, 132 contributors
- cumulative-table-design teaching repo: 777 GitHub stars
- little-book-of-pipelines (Scala): 331 GitHub stars
What makes it work
A breakdown of the choices that make this portfolio stand out.
A curriculum published as an open, versioned repository
Publishing the bootcamp curriculum as a GitHub repo rather than a gated course page means anyone can read, fork, and contribute to it directly, which is part of why the handbook sits at 44.2k stars and 9.3k forks.
Small, focused practice repos alongside the flagship handbook
Repos like the SQL training set and deduplication tutorial give learners a narrow, self-contained exercise to work through, rather than requiring the entire handbook to get value from the profile.
Community contribution baked into the project structure
The handbook lives under the DataExpert-io organization rather than a personal account and merges outside pull requests (132 contributors), with resources split into topic files (books.md, communities.md, interviews.md, projects.md), so it grows through community additions rather than remaining a single-author repo.
What Data Engineers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
Publish a curriculum or learning path as an open repository instead of a closed course platform — it invites contributions and gets discovered through GitHub search and stars.
Break large teaching material into small, standalone practice repos so a learner can get value from just one piece.
If a project draws outside contributors, give them a structured place to contribute (topic files like books.md, communities.md and projects.md) rather than letting every pull request fight over one giant README.
Projects
Zach Wilson publishes the syllabus where the code lives: a 44k-star handbook with the bootcamp folders inside it, plus small repos that each teach a single pattern. The fork counts suggest people are doing the homework.
A curated repo of everything needed to learn data engineering: a breaking-into-data-engineering roadmap, 25+ books, 10+ communities, newsletters, interview advice, projects, and a company map by category (orchestration, lakehouse, warehouse, data quality, BI). It also hosts the free 4-week beginner and 6-week intermediate bootcamp folders, plus a Databricks AI bootcamp.
Running a resource this large means reviewing and merging a steady stream of community PRs, which is maintainer work, not just curation.
Bootcamp curricula shipped as folders in the repo rather than behind a paywall
Resources split into topic files so contributions don't collide
A teaching repo for one pattern. A daily metrics table is FULL OUTER JOINed with yesterday's cumulative table to build per-user metric arrays, so history is carried forward without rescanning it. Questions over long windows (up to thousands of days) then become ARRAY_SUM-style queries.
Cumulative tables are a standard big-tech answer to long-window user-activity metrics; being able to explain the join and the performance win is a strong interview signal.
Includes a pipeline diagram and a worked user-activity example
Written in Presto/Trino syntax with notes on porting
An example of a pattern for pipelines with many upstream sources. Sources are grouped under a shared, ds-and-group-partitioned schema. A Scala enum records each group's items and data-quality constants, with one group entry per Spark job. The enum is then materialized as a "little book" Hive table that data-quality checks and dashboards can use.
It tackles real pain points at scale — painful backfills, 10+ sources, unclear ownership — with self-documenting data-quality code.
Enum doubles as documentation and data-quality configuration
Trades a little storage for easier backfills
More Data Engineer portfolios
Ready to build your portfolio?
Follow the Data Engineer roadmap — skills, projects, and timeline to get hired.