Open to new opportunities
Hey, I'mMarcus Reed
I build full stack web apps
Full stack developer in Austin with seven years of shipping web apps for clinics, retailers and logistics teams. I like owning a feature from the database schema to the last loading state, and I like it even more when it stays quiet in production.
View projectsMarcus Reed
Full stack developer, Austin
Available from January 2027
- TypeScript
- React
- Node
- Postgres
- AWS
// seven years in, still curiousconst marcus = { role: "Full stack developer", city: "Austin, Texas", years: 7, stack: ["TypeScript", "React", "Node"], onCall: true,};export default marcus;Selected work
Four projects from the last three years, each one owned end to end.
Replaced a phone only booking process with self serve scheduling for six clinics.
Front desk staff spent most mornings on the phone moving appointments around. I built a Next.js booking flow on top of their practice software's export, with a Postgres mirror that syncs every two minutes and holds a slot for ten minutes while a patient finishes the form. Text reminders go out through a queue so a slow provider never blocks a booking.
62% of appointments now booked online; missed visits down 18%.
- Next.js
- TypeScript
- Postgres
- BullMQ
Click and collect for a regional grocery chain with patchy in store wifi.
Pickers were working from printed lists because the store wifi dropped in the back aisles. I built an offline first picking app in React that caches each order in IndexedDB, queues substitutions locally and syncs when the device finds a signal again. The customer side reuses the same API so stock levels stay honest.
Average pick time per order cut from 14 to 9 minutes.
- React
- Node
- IndexedDB
- Postgres
A public tracking API that had to survive every carrier webhook arriving at once.
Carrier status updates arrived in bursts of thousands, and the old endpoint fell over at the end of each shift. I moved ingestion to Lambda behind a queue and deduplicated events in Redis by carrier and sequence number. Current state is written to Postgres in small batches so reads never wait on writes.
Held 1,200 events per second with p95 reads under 80 ms.
- Node
- Redis
- Postgres
- AWS Lambda
One set of accessible components for three product teams that had drifted apart.
Three teams had built three versions of every button, modal and date picker. I paired with the lead designer to agree on 40 components, built them in React with Storybook as the single reference and added Playwright visual tests so a change in one place could not quietly break another product.
Front end bug reports down 30% in the two quarters after rollout.
- React
- TypeScript
- Storybook
- Playwright
About
I started in support fixing other people's code and never stopped.
My first tech job was on the support desk at a small software company in Austin. Reading stack traces for customers turned into fixing the bugs myself, and by 2019 I had moved onto the product team full time. That habit stuck: I still start every piece of work by asking who will be paged when it breaks.
Since then I have worked at Mesa Learning on their course platform and, since 2024, as an independent developer for clinics, retailers and logistics companies around Texas. Most of my work is the unglamorous middle of a product: schemas, background jobs, permissions and the forms people use every day. I write the front end too, and I care about it looking right on a cheap phone in bad light.
Outside work I volunteer with a weekend coding club at the public library, ride the Southern Walnut Creek trail before it gets hot and keep a sourdough starter alive with mixed success.
- Based in
- Austin, Texas
- Working since
- 2019
- Prefers
- Small teams, long lived code
- Currently
- Reading about Postgres internals
Stack
The tools I reach for first. I am happy to work in yours, and I will say so early if I think a different tool fits the problem better.
Front end
- TypeScript
- React
- Next.js
- CSS modules
- Playwright
Back end
- Node
- Fastify
- Postgres
- Redis
- Prisma
Infrastructure
- AWS
- Docker
- Terraform
- GitHub Actions
- Grafana
How I work
- Tests before the fix
- Small pull requests
- Written decisions
- Pairing on the hard parts
Have a product that needs a steady pair of hands?
I take on one or two projects at a time, usually for three to six months. Send a few lines about what you are building and where it hurts, and I will reply within two working days.
Send an email- Emailmarcus@example.com
- Code@marcusreed
- WritingNotes on backend work
- ResumeOne page, PDF