Alphonso Woodbury

Software engineer. I build data platforms, cloud infrastructure, and tools that help teams and individuals get more from technology.


How I got here

2011
Built inventory system
2015
Saved $1.5M/year
2019
Automated 25% of team time
2020
Joined JPMC
2021
Founded Data Discovery
2023
Founded Data Acquisition

From zero to production

Data Infrastructure

Data Acquisition Platform

Serverless event-driven system at JPMC that coordinates multi-stage ingestion pipelines across the enterprise. I chose configuration-driven ETL over per-vendor custom code because every new integration was taking weeks of engineering time. Factory patterns now handle JSON, CSV, Parquet, XML, and XBRL from dozens of external vendors without code changes.

70%cost reduction
40%faster onboarding
384GBmax file size
45+engineers mentored
PythonStep FunctionsEventBridgeLambdaEKSTerraform
Search & Discovery

Data Discovery Platform

JPMC's internal platform for teams to search, evaluate, and access datasets across the enterprise. I managed the Kubernetes cluster running 8 containerized services and tuned Solr to handle the query volume when adoption grew faster than anyone expected.

150K+datasets
2M+daily queries
<2sresponse time
EKSSolrBlazeMeterPython
ML Infrastructure

RxVision

End-to-end data pipeline for pharmaceutical image classification. Automated ingestion from NIH datasets with format conversion, validation, and metadata generation.

131Kimages
4,864+classes
PythonTensorFlowDocker

Learning, building, and AI

How I Learn

I can learn any tool. The value is what I enable with it.

Learned Terraform→ deployed multi-region EKS clusters70% infrastructure cost reduction
Learned Step Functions→ built event-driven orchestration40% faster vendor onboarding
Learned Solr→ tuned search at scalesub-2-second response at 2M+ queries/day

How I Build

Configuration over code.

If onboarding a new source requires a code change, the platform failed. I build systems that treat definitions as data.

Cost is a design constraint.

Not something to optimize later. I reduced infrastructure costs by 70% by treating cost as a first-class requirement from day one.

Build for the person on-call at 3am.

Observability, runbooks, and clear failure modes are not optional. If the system can't explain what went wrong, it's not production-ready.

Ship the smallest useful thing.

Then iterate. Dashboards delivered 6 months ahead of schedule because the first version was scoped to what actually mattered.

How I Use AI

Research.

I pair with AI to survey a domain before making architecture decisions. Deep research in hours, not weeks. The judgment on what to act on is mine.

Prototyping.

This site was designed and built in conversation with Claude Code. The interactions, layout, and content were iterated in real-time through rapid feedback loops.

The human layer.

AI generates. I decide. Every architecture choice, every design judgment, every “no, that's not right” is mine. The tool accelerates execution. The taste and judgment are not delegable.