← projects

[Fixed Seed]

End-to-End Synthetic Data Pipeline

A take-home challenge: synthetic data → pure-SQL DuckDB pipeline → Streamlit dashboard → the project's knowledge graph served over MCP.

● ShippedData EngineeringPersonalDuckDBSQLPythonStreamlitMCPDocker
01 /context

A technical challenge for a data engineering role: build an analytics stack from scratch with free choice of tools, and document how AI was used.

02 /my role

Solo, with a coding agent; every architecture decision recorded and approved before implementation.

03 /problem

Show a complete, reproducible architecture without real data — and be honest about what the AI did and didn't do.

04 /how it works
  1. 01 · Deterministic data

    Python + Faker with fixed seeds: every run produces the same dataset.

  2. 02 · Pure-SQL pipeline

    DuckDB, raw → validate → clean → gold. No AI calls at runtime.

  3. 03 · Decoupled dashboard

    Streamlit with the data layer separated from UI code and tested with pytest.

  4. 04 · Project as a graph

    A knowledge graph of the repository served by two read-only MCP servers.

  5. 05 · AI usage log

    A living record of tools, prompts, what was accelerated, what a human reviewed and known limitations.

05 /architecture
01
Generator (fixed seed)
02
Raw
03
Validate
04
Clean
05
Gold
06
Streamlit
07
MCP servers
06 /results
About 70 automated tests.
Published dashboard and a Docker deployment.
Known limitations declared (like right-censoring in recent sales) instead of hidden.
07 /what broke and what I changed
  • ! brokeSome bugs only appeared in the deployed environment, never locally.

    → changedA human checkpoint after each phase: run the real app and read the deploy logs before moving on.

08 /related