The short version

For six years I've built software inside a Fortune 100 financial company — systems used by millions of people, under the kind of compliance and reliability constraints that make you careful. I've also designed, built, and shipped my own products end to end, which teaches a different skill: deciding what not to build.

Freelancing lets me bring both to smaller teams. The engineering discipline of an enterprise, the speed and ownership of a founder, and a bias toward measurable outcomes instead of billable hours.

My background is Computer Science and Business Information Systems. That combination is the whole job: understand how the business actually makes money, then remove the friction between the people doing the work and the systems supporting them.

6+Years shipping software
20+Products and tools built
100%Fixed-scope engagements
∞Still learning
Experience

Where I've worked

Software Engineer

Fidelity Investments

Full-stack engineering on large-scale financial systems serving millions of users. Designing software infrastructure, leading feature delivery end to end, and contributing across the stack at one of the largest asset managers in the world.

Associate Software Engineer

Fidelity Investments

Promoted from intern to full-time engineer within six months. Ramped quickly on production codebases and began contributing to core platform work.

Software Engineer Intern

Fidelity Investments

Six-month internship building internal tooling and gaining hands-on experience with enterprise-scale software development practices.

Lead Quality Manager

CVS Health

Led quality and process operations at a major pharmacy retail location. Saw firsthand how much operational time disappears into manual tracking.

Quality and Process Manager

CVS Health

Managed store quality, compliance, and operational processes. Built systems for tracking and improving team performance — the first automation work.

Capabilities

Tools I reach for

Chosen for the problem, not the résumé. These are the defaults I know deeply — not the only things I can use.

Languages

  • TypeScript
  • JavaScript
  • Go
  • Python
  • SQL

Frontend

  • React
  • Next.js
  • React Native
  • Expo
  • Accessibility

Backend

  • Node.js
  • REST & GraphQL
  • WebSockets
  • Auth
  • Queues

Data & AI

  • PostgreSQL
  • Redis
  • Prisma
  • LLM APIs
  • Vector search

Infrastructure

  • Docker
  • AWS
  • GitHub Actions
  • Vercel
  • Monitoring
How I work

Three rules I don't break

01

ROI before architecture

The first question is never "what stack?" It is "what does this cost today, and what will it save?" If the math does not work, the project does not start.

02

Small scope, shipped

I would rather ship the one workflow that saves ten hours a week than spend six months on a platform nobody uses. Value compounds after launch, not after planning.

03

You own the outcome

Code, infrastructure, documentation, and accounts stay yours. I am a temporary accelerator, not a permanent dependency.

Have a process that eats your week?

Tell me about it. The first conversation is free, and you'll leave with a straight answer.

Get a free automation audit