Hey, I'm Alex Smith. I'm a senior full-stack engineer, 10 years in, and I like building things that are fast, resilient, and pleasant to work in. I get hired for four things over and over: AI that has to survive production, systems that have to hold under load, code I didn't write and can't afford to break, and the room where the architecture actually gets decided. I've been building on LLMs since early 2023, long enough to watch most of the tooling get invented and then replaced twice.
I started out on Wall Street, before I wrote code for a living, and that's where the taste for precision came from. Since then it's been startups and growth-stage companies: full-time when a team needs an owner, embedded when it needs a specialist. Either way I show up as an internal engineer rather than a contractor passing through.
Away from the keyboard I'm a hands-on problem solver, which usually means a car in pieces in my garage or an afternoon spent chasing par. I'm happiest where curiosity meets execution, and I'm always poking at something new. If you want to work together, or just talk shop, say hello.
on this wave since early 2023
At ezCater I stood up a self-hosted LiteLLM proxy that became how every squad reached a model, roughly 30 engineers, with provider keys, rate limits and permissions solved once instead of everywhere. The eval harness and LLM-as-judge behind it scored meal recommendations and caught a prompt change that had quietly stopped respecting dietary restrictions. Handing menu verification to a model gave customer support back 20 hours a week. At QuotaPath I cut token spend 30% and runtime 24% on the same kind of workflow without moving the output. The model is the easy part. Making it observable, testable and cheap enough that other teams will build on it is the work.
At Calendly I designed a fault-tolerant ingestion and indexing service on GCP and Pub/Sub, each stage scaling independently across a billion records and millions of messages a day. The interesting part is rarely the throughput number. It's choosing the boundaries, isolating failure, and keeping the p99 boring a year after launch.
I'm usually hired into a system I didn't write. At GiveCampus that meant leading foundational legacy code into a service-oriented architecture, lifting coverage 40% and reliability 70%. The harder half was never the code. It was getting senior engineers across several teams to agree where the boundaries went before anything moved.
strong opinions, loosely held
At ezCater I owned extracting the core menu system from the monolith into its own service, from domain design through delivery, working alongside the Head of ML, an EM and a staff engineer. Then I presented the design and its tradeoffs to senior leadership. Architecture is half the job. Getting a room to agree on it, and stay agreed, is the other half.
Full-time and embedded, across 9 product teams. Most of them were more than one job.
Commission tracking and sales compensation for revenue teams.
Engagement and personalization platform for SaaS and media companies.
Nationwide corporate catering marketplace and ordering platform.
Scheduling automation for individuals and enterprises.
Consumer fintech for splitting a payment across several cards.
Fundraising and alumni engagement for schools and universities.
The open-source platform behind a global developer community.
Real-time and historical market data, delivered over APIs.
Mobile ticketing for event sales, transfers and validation.
the honest version
Sorted by how well I actually know them, rather than by how long the list looks.
Ruby on Rails · Python · Django · FastAPI · JavaScript · TypeScript · React · Stimulus & Hotwire · Tailwind CSS · PostgreSQL · Redis · Sidekiq · Celery · Docker · AWS · NumPy & pandas · RSpec
Elixir & Phoenix · Node.js · Vue · Redux · GraphQL · Kafka · Google Pub/Sub · Kubernetes · Terraform · Elasticsearch · MySQL · GCP · Datadog · GitHub Actions · CircleCI · Argo CD · OpenAPI · WebSockets
Java · C# · NGINX & OpenResty · Cassandra · Ansible · Ember · Angular · Pinia · Sinatra & Padrino · Socket.IO
LLM integration · Agentic workflows · Retrieval-augmented generation · Embeddings & vector search · Prompt engineering · Evals & guardrails · MCP · AI-assisted development
Domain-Driven Design · CQRS · Event sourcing · Service extraction · Server-side rendering (SSR) · Edge caching · Contract testing · Auth & access control · Read/write splitting · Blue-green deploys · SLOs and on-call · Flame-graph profiling
Side projects, homelab infrastructure, and open-source work. Some of it is deployed, some of it only runs on my own hardware, and some I can only describe.
Gives a self-hosted AI assistant a memory, so it remembers what I told it last week instead of starting over every conversation. It sits between the chat window and the model, adding what is relevant on the way in and learning from the conversation on the way out.
There is nothing to click, it runs on hardware in my house and is not reachable from the internet, but I am happy to walk through it. The interesting problem is deciding what is worth remembering and what to surface. It searches both for exact wording and for meaning, then ranks what it finds on how closely it matches, how important it looked at the time, and how recently it came up. Different kinds of memory fade at different speeds, so a one-off event is forgotten long before a habit is.
A server in my house that replaced most of my monthly subscriptions with things I own outright, and is still running today. Photo backup, media streaming, home automation, private code hosting, push notifications, and a graphics card running AI models locally, all reachable only over a private network with nothing exposed to the internet.
Running the AI side at home is the part I would not give back, because the conversations, documents and photos never leave the house. The rest is run the way I would run it at work rather than as a pile of hobby projects. Updates arrive as proposed changes I review, and approving one deploys it on its own. Backups run nightly and are kept for months, alerts reach my phone when something breaks, and I keep a written audit of the risks I have chosen to live with instead of pretending they are fixed.
A browser adaptation of the party game Hues and Cues, where one player gives a one-word cue and everyone else races to guess which color they meant. Real-time multiplayer, played on a 480-color board generated so that neighboring shades sit evenly apart to the eye.
The hard part is that everyone plays at once. Every screen updates live as guesses come in, and a round only moves on when the last person has acted, so nobody gets skipped and a double-tapped button cannot score twice. Answers stay hidden from the other players until the reveal, which has to be enforced on the server rather than just hidden on screen. People can join with nothing but a name, and if they create an account afterwards their past games come with them.
An open-source library for finding patterns and trends in stock price data, the sort of calculations that sit behind charts and trading tools.
Built and open-sourced while I was at Intrinio, so it lives under their account rather than mine. I wrote the calculations themselves, plus the caching that kept them fast enough to run across the company's own systems and for the outside developers building on their data.
While I struggle to play well, I must be a glutton for punishment because I play often. My favorite outings are the ones where I shoot lower than the temperature it is outside...and I live in Florida.
The latest international sports craze, I love watching Formula 1. And if you're wondering, yes, I was a fan 'before it became cool with Drive to Survive'.
Tinkering on cars (or anything with an engine) is my favorite way to decompress. My current project is a 1999 (E36) BMW M3 coupe, 5-speed manual (ofc, IYKYK).
We have 2 dogs who are both named Jax. My boy is a 6 year old Catahoula mix who loves to play and give human-like hugs. He is also really good at playing hide and seek.
As painful as it is to admit, I'm a cold brew addict. I make my own for funsies!
Alex is an articulate communicator and excellent at developing solutions for complex problems. He delivers top quality code. Always. The degree of emotional intelligence possessed by Alex makes him such a well rounded individual and an absolute pleasure to work alongside.
Senior Software Engineer @ Boundless Immigration
Alex, without question, is what you would call a 10x engineer. His ability to crank out quality code and present technical accomplishments to the business is next to none. However, all of that pales in comparison to his dedication to creating a safe and inclusive workspace for all.
Senior Software Engineer @ GiveCampus
Alex has an innate ability to see beyond the code. He's able to have high level conversations typically reserved for product managers unlike any other engineer I've ever seen. He understands how to translate things into layman's terms that is also tailored to a specific audience.
Senior Business Operations & Strategy Manager @ Pinterest
Alex helped me automate painstakingly manual and repetitive tasks that I had no idea could even be automated. He saves me several hours a week now. Throughout the process he was communicative, prompt, and professional. I'd absolutely work with him again.
CEO @ A Creative Co.
As an engineer, Alex is thoughtful, efficient, and has a keen eye for pitfalls and problem areas. As a teammate, he's considerate, conscientious, and deeply engaged. I'm lucky to have had the opportunity to work with and learn from him - couldn't have asked for a better coworker.
Senior Software Engineer @ Calendly
Alex is an engineer who brings a really strong product mindset to his work. He’s particularly good at taking ambiguous problems, figuring out what actually needs to be decided, and turning them into clear, tangible outcomes. He’s also very collaborative when faced with uncertainty, always engaging others in conversation to make sure he understands the “why,” not just the “what.” He combines that thoughtful approach with an impressive speed and quality of execution, and consistently finds a way to turn messy problems into something real.
Senior Product Manager @ QuotaPath
© Alex Smith 2026. All rights reserved.