Product Leader · Builder · Perpetual Student

Eric Hall

Data · Analytics · Platform · AI

I work with data by day and play with data by night. I lead product org transformations—from reactive shared-service models to outcome-driven product operating models, formally trained in Marty Cagan / SVPG principles.

Every personal project is an extension of what I do on the job: it's how I stay sharp on the skills that make me a better PM. I can sit down with an analyst's dataset or an engineer's codebase and actually work in it—untangle bad code, spot what's fragile, and make grounded calls on where AI and agents genuinely help versus where they get in the way.

Proof: 3 product concepts shipped in 4 months, directing engineering, AI agents, and tooling to build them. What I love most is what comes out the other side—giving people better data to make decisions with, or just more fun ways to engage with something they care about.

Active Projects

FIG. 01
Heddlepin
Heddlepin
Live ↗

Community exploration platform for obsessives—people who care too much about the right things and want to find their people in the real world. Pinned locations unlock full lore and community marks only when you physically show up. Built on Node.js, PostgreSQL + PostGIS, MapLibre, and Cloudflare.

What it taught me: Geographic UX is deceptively hard. The "arrive and unlock" mechanic required rethinking every assumption about how users interact with map interfaces—and forced me to feel every friction point my engineers warned me about.
Node.js PostgreSQL PostGIS MapLibre PWA Cloudflare
FIG. 02
Bracket Battle
Bracket Battle
Live ↗ Repo ↗

Single-elimination bracket tracker for the 2026 NCAA Men's Lacrosse tournament. 16 teams, 15 picks, one champion. Deployed as a static site—zero backend, zero dependencies, zero budget.

Refreshed each year during NCAA Lacrosse championship season (2 weeks). Off-season between refreshes.

What it taught me: Constraints are a gift. Building with no server forced creative thinking about state, persistence, and UX that a "just add a database" approach would have skipped entirely.
Vanilla JS Static Site GitHub Pages
FIG. 03
Melee
Melee
In Development Repo ↗

Sports social product built around watch parties, live event energy, and the communities that form around them. Deep schema design, ontology work, and scenario modeling before a single line of product code.

What it taught me: Writing a full ontology before building anything surfaces assumptions you didn't know you were making. The design thinking docs changed the product more than any user interview did.
Product Design Schema Design PostgreSQL

Reference Projects

Sabo
Early product experiment — archived.
Archived Repo ↗
Dotfiles
Dev environment config, scripts, and tooling.
Repo ↗

Skills Acquired

Geolocation & location-based services
Ontologies & schema design
Platform design & architecture
AI agent building and training
AI tool orchestration
Bootstrapping & solo shipping
Market research & customer discovery
Financial feasibility analysis
Competitor analysis
Mobile app design
Deployment & DevOps
Testing & QA
Product management fundamentals

Background

Craft

  • Product operating model (SVPG)
  • AI / LLM product development
  • Agentic workflow design
  • Data infrastructure & governance
  • BI & analytics platforms

What I build with

  • Node.js, PostgreSQL, PostGIS
  • Claude API, agentic pipelines
  • MapLibre, Cloudflare, Hetzner
  • Vanilla JS, PWA patterns