Skip to content
View anix-lynch's full-sized avatar

Block or report anix-lynch

Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
anix-lynch/README.md

✨ Anix Lynch — AI/Data Engineer · Los Angeles

I build the trust-to-action stack: trusted data → features → evaluated signals → agent actions → accountable human decisions. Live, evaluated systems on Cloud Run + Vertex AI — not demos. Ex-VC / family-office operator, so I also own the layer most engineers skip: getting executives to actually adopt the AI.

📍 Los Angeles, CA · GCP · AWS · Azure · dbt · Vertex AI · RAG · Python

🌐 gozeroshot.dev · 💼 linkedin.com/in/anixlynch · 🦋 anixlynch.bsky.social


The architecture I build across (L1 → L3)

Layer Question Live project Proof
L1 Truth Can we trust the data? healthcare-ai-data-engineer dbt medallion on BigQuery · 55 tests green · quality gate · PII masking
L1.25 Context How should AI agents see it? ↳ same repo (Feast feature store) point-in-time-correct patient features
L1.5 Signals What might happen? healthcare-signal-platform 5 evaluated signals → agent · anomaly F1 0.85 · cluster silhouette 0.41 (535/40K) · classify ±1-tier 100%
L2 Action What should the agent do? healthcare-genai-engineer RAG · BM25+dense+RRF · PII guardrails · CI eval gate
L3 Influence Will humans adopt it? healthcare-forward-deployed-engineer VPC deploy · runbook · postmortems · human Approve/Override

★ The flagship proves it: the live Signal Console runs an ablation — the same Gemini agent decides with the signals vs without. On the ops-capacity case the call visibly flips WATCH → ACT NOW. Signals change the decision; they don't just decorate it. Evals tracked in Weights & Biases, agent calls traced in Langfuse.


Why the whole chain (not one layer)

Most engineers stop at L2. Most executives start at L3. Few people understand the entire chain — Truth → Context → Signals → Actions → Human adoption. That's the rare part, and it's where 10 years of VC / family-office / CEO-office translation (tech ↔ business ↔ stakeholder) becomes a moat.


Stack

AI/Platform: Vertex AI · Gemini · Signal Intelligence · Decision Intelligence · Feature Stores (Feast) · anomaly/cluster/classify/rank GenAI: RAG · hybrid retrieval (BM25/dense/RRF) · agents · tool calling · guardrails · LLM eval · vector search (Chroma/Pinecone/Qdrant) Data: dbt · BigQuery · analytics engineering · medallion · data contracts · governance · Snowflake · DuckDB · Microsoft Fabric · Power BI Cloud/Infra: GCP · Cloud Run · AWS Bedrock · Azure · Docker · FastAPI · GitHub Actions Eval/Obs: Weights & Biases · Langfuse · Ragas-style eval · CI regression gates Languages: Python · SQL

MBA, University of Chicago Booth · JLPT N1 · Authorized to work in the US (Green Card)

Pinned Loading

  1. www.gozeroshot.dev www.gozeroshot.dev Public

    Clean Astro portfolio - 2025 version

    Astro

  2. healthcare-ai-data-engineer healthcare-ai-data-engineer Public

    Healthcare data engineering on dbt + BigQuery — medallion warehouse, Feast L1.25 feature store, FastAPI grounded-agent API, quality-gate CI. Synthetic data; every claim maps to a file.

    Python

  3. healthcare-genai-engineer healthcare-genai-engineer Public

    Focused presentation cut of healthcare-genai-fullstack — GenAI Engineer lens (RAG · evals · guardrails · API). Source of truth lives in the monorepo.

    Python

  4. healthcare-forward-deployed-engineer healthcare-forward-deployed-engineer Public

    Customer-deployable ER triage assistant for VPC/on-prem hospital deployment — discovery brief, solution design, runbook, integrations, acceptance-gated CI, postmortem. The full loop of making AI wo…

    Python 1

  5. Certification Certification Public

    Professional certifications and credentials - diploma, language, Coursera certs

    Jupyter Notebook 4

  6. healthcare-signal-platform healthcare-signal-platform Public

    L1.25 + L1.5 healthcare AI platform: feature marts and evaluated signal services that feed GenAI agents as structured evidence.

    Python