Andrew Dao
All work
01

Alternative data pipeline

[One sentence: what the pipeline ingests, who the analysis was for, and the decision it was meant to inform.]

Role[Solo · end to end]
Timeline[3 months, 2025]
Data volume[N rows / N sources]
Stack[Python · pandas · Postgres]

The problem

[Two paragraphs on the question you were trying to answer, and why the obvious data source could not answer it. Alternative data only earns its cost when the standard feed has a blind spot — name that blind spot precisely.]

[What made it hard: rate limits, schema drift, licensing, sparse coverage, survivorship bias in the panel. This paragraph is what separates a portfolio from a résumé bullet.]

What I built

Sources[Web scrapes]
[Vendor feed]
[Filings]
Ingest[Python collectors]
[Retry & backoff]
[Schema checks]
Store[Raw, immutable]
[Normalised tables]
Analysis[Feature construction]
[Signal testing]
[Coverage & bias checks]
[Reporting]

[Walk through the decision that mattered. Why you stored raw and immutable before normalising. How you handled a source changing its schema without warning. What you deliberately left out of v1, and why that was the right call.]

This section is plain markdown, so lists, links and code blocks all work:

# A short, real snippet beats a paragraph describing one.

Results

[N][sources ingested on a daily schedule]
[N][rows, or the coverage figure you hit]
[N][the finding — the thing the data actually told you]

What I'd do differently

[One honest paragraph. Interviewers ask this exact question, and having the answer already written is a real advantage. It also signals seniority better than any metric on this page.]

Next projectEsports match prediction