Carlos
Sandoval.
Lead Software Engineer
Currently leading platform engineering at a healthtech company (under NDA — happy to walk through it). Previously cloud infrastructure at Amazon Web Services.
Selected work.
A few personal projects spanning IoT, full-stack, and tooling. Production work is under NDA — happy to walk through architecture and decisions in conversation.
How I work.
Four operating principles I bring to every system I lead.
Own the system end-to-end.
Frontend, services, data layer, infra. The seams between layers are where most production failures live — owning all of them is how you make those failures rare.
Decisions over diagrams.
Every non-trivial system change is a written decision: what was chosen, what was rejected, and why. Future-me (and the team) need the trade-off, not the topology.
Boring on purpose.
Lean toward Postgres, plain HTTP, and a small dependency surface. Novelty is reserved for the parts of the product that are actually differentiated.
Mentor by review.
Standards are set in pull requests, not docs. Tight, specific code review is how a single engineer's taste becomes a team's shared vocabulary.
Experience.
- Oct 2023 — Present
Lead Software Engineer
Healthtech (NDA)Solo lead on a multi-year platform rebuild. Own architecture across frontend, services, data, and AWS infrastructure. Set engineering standards through review; mentor contributors and contractors.
- Apr 2023 — Oct 2023
Full Stack Engineer
Healthtech (NDA)Shipped end-to-end product features and contributed to performance, reliability, and infra work that preceded the lead role.
- Jul 2021 — Mar 2022
Cloud Support Engineer
Amazon Web ServicesResolved production incidents on EC2, S3, EMR, and networking for enterprise customers. High-volume exposure to real distributed-systems failure modes.
Let's talk.
Open to senior and lead engineering roles. Easiest path is email — happy to share more about the production work in conversation.