A multi-queue help desk with role-based access, PII redaction before storage, SLA clocks and a tamper-evident audit ledger.
Next.js · TypeScript · Prisma · Postgres · Auth.js · Vitest
Case study
Live demo soon
Internal software for wealth management operations.
I’m Jeremy Hamann. I design and build the systems an advisory firm’s operations team runs on every day, from client service and account transfers to trading workflows and statement processing. Full stack in TypeScript, Python and Postgres, with compliance designed in from the first commit.
Full-stack applications
Next.js, React, Express and FastAPI, typed end to end.
Data and reporting
Postgres schema design, warehouse SQL and reconciliation.
Automation and AI
Workflow automation and document extraction with rule checks.
Compliance by design
Audit trails, role-based access and PII handling.
Selected projects
Four production systems, rebuilt as public demos. Each has a case study and, as it ships, a live demo.
An advisor-to-trader workflow with an asset-location engine, drift monitoring and a compliance record for every request.
React · Vite · Express · Postgres · TypeScript · Zod
Tracks incoming account transfers from paperwork to settlement across custodians, including exceptions, assets and fees.
Next.js · React · Prisma · Postgres · pdf-lib · Zod
Case study
Live demo soon
Model-based extraction plus a tested 15-layer rule chain. Cut statement review from 30–45 minutes to under a minute.
Python · FastAPI · Gemini · Postgres · React · fpdf2
Case study
Live demo soon
Experience
CurrentRegistered investment adviser
Operations & Automation Lead
Wealth management · Operations engineering
- Designed, built and run the firm’s internal operations software, including the four systems on this page.
- Built a client operations platform that brings CRM, custodian and warehouse data together for advisors and operations staff.
- Automated recurring operational work with workflow automation, warehouse reporting and AI-assisted document processing.
- Set the engineering guardrails: separate environments, an approval gate on every deploy, audit logging and security scanning in CI.
How I work
Audit trail by default
Every write is attributable and reviewable. When a regulator asks what happened, the answer is a query.
Models assist, rules decide
AI handles reading and drafting. Anything that moves money or changes a record goes through deterministic, tested logic.
Small, reversible releases
Feature flags, separate environments and an explicit approval before anything reaches production.
About
I work where operations and engineering meet. Most of what I build replaces spreadsheets, shared inboxes and manual checks with software that an operations team uses every day.
I pay attention to the parts of a system that rarely make it into a demo: who is allowed to see what, how a record proves it was never changed, what happens when an upstream feed is late, and how a mistake is caught before a client notices it.
- Languages
- TypeScript, Python, SQL
- Frameworks
- Next.js, React, Express, FastAPI
- Data
- Postgres, Prisma, Redshift
- Infrastructure
- Cloudflare, Google Cloud, Docker, GitHub Actions
- Automation & AI
- n8n, LLM extraction and evaluation, MCP servers
Let’s talk
I’m always glad to compare notes on operations engineering, internal tools and fintech platforms.
jeremy@jeremyhamann.dev