Sam Rivera / Full-stack engineer
I build the systems behind the product.
Full-stack engineer. I care about deploys, logs, and a screen that tells the truth when something fails.

Featured work
Selected work, with the stack and a case study for each one.
Stack
Languages and tools I use on most projects.
Go
Services and the job runner.
TypeScript
The product surface and internal tools.
PostgreSQL
The system of record.
Redis
Sessions and short-lived state.
Observability
Logs, latency, and deploys.
Linux
The machine the service runs on.
Find me
GitHub, LinkedIn, and anywhere else the work lives. Replace these addresses with your own.
Experience
Roles, teams, and the work I owned.
2022 to present
Founding engineer, Harbor
The deploy path, the activity log, and the permission checks around them.
2018 to 2022
Platform engineer, Northline
Queues, retries, and a page that shows when a release failed.
2015 to 2018
Backend engineer, Keel
Sessions and the services that had to agree on who the user was.
Available for a staff or founding role.
One product at a time. I reply to notes about the problem, the team, and the timing.
Open to the next role.
A product team, a founding role, or a focused contract. Tell me the problem and the timing.
Writing
Notes and articles from the work. These samples stay drafts until you publish them.
Notes
The long way around a short idea
A first draft is allowed to wander. The published one should know exactly where it is going, and why.

Product
What we shipped this spring
Three changes customers asked for, the one we decided not to build, and what we learned from both.

Training
A quieter kind of strength
The session that looks easy from the doorway is usually the one that was earned over months.

