Engineer, open-source builder, and the person behind Atlas Crew. Based in Tampa Bay. I've spent my career walking into broken infrastructure and rebuilding it into something that runs without me.
Who I am and how I got here. A decade of walking into broken infrastructure until the same pattern turned into a methodology.
The name is personal. My middle name is Crew. And my great-great uncle was Charles Atlas, the strongman who built an empire on the idea that anyone could become stronger than they thought possible.
Atlas holds up the world. Crew is the team that does the work. Infrastructure engineering is exactly that: carrying the weight so everyone else can move fast without thinking about what's underneath. The family connection wasn't planned, but it fits.
Everything under Atlas Crew ships with the same philosophy: build it to run without you, document it like you're leaving tomorrow, and open-source it so the next person doesn't have to start from zero.
Sit with your engineers. Watch them fight the tooling. Map the pain points, the tribal knowledge, the undocumented dependencies. Understand what's actually broken, not what the ticket says.
I don't ask teams to migrate on their own timeline. I do the work for them. Onboard their services to the golden path, all the way through deployment. Eliminate the bottleneck, don't relocate it.
Everything is built to run without me from day one. Documentation, runbooks, monitoring. At ThreatX, I mentored the SOC team into SRE practitioners who took over the platform entirely.
Everything I build is designed to run without me from day one. Documentation, runbooks, monitoring. If it requires tribal knowledge to operate, it's not done.
Working software in production beats slide decks. I'd rather show you the running system than walk you through the plan for one.
Every major project under Atlas Crew is open source. The best infrastructure work compounds when other people can build on it.
Start from what's broken, not from what's trendy. The right tool is the one that fixes the problem in front of you, not the one with the most stars on GitHub.
Senior Platform Engineer. Inherited a SaaS platform with no IaC. Migrated everything to Terraform-managed EKS with GitOps. Cut AWS spend by ~$60K/mo. Built Synapse from scratch when the legacy codebase couldn't carry the weight.
Senior Platform / Build Engineer. First platform developer in a newly created role across four acquired companies. Built a cross-platform build DSL, automated 600+ pipelines. When ransomware hit, engineering kept shipping because everything was already in AWS.
Systems administration, IT infrastructure, networking. The foundation that makes everything else possible: understanding the full stack from bare metal to application layer.
What I take on when someone hires me, and the stack I've shipped with in production. Reach me at the bottom.
Your CI takes 45 minutes. One person understands the deploy process. Your Terraform is copy-pasted across a dozen repos. I've inherited this exact situation at every company I've worked for and rebuilt it into infrastructure that runs without tribal knowledge. Bare Docker to EKS. Manual deploys to GitOps. Scattered scripts to reusable modules.
Build the internal platform your engineers actually use. Golden path modules built by infrastructure, approved by security, monitored by SRE. Self-service pipelines. Shift-left documentation. The goal is your developers stop thinking about infrastructure entirely.
Embed AI into existing products and workflows. Not chatbots: context orchestration, behavioral analysis, LLM-augmented development pipelines, and automated test generation at production scale. The kind of integration that requires understanding your architecture, not just an API key.
Take an idea from architecture through production deploy. Backend, frontend, infrastructure, design system. Best for seed-stage companies with domain expertise who need the person that makes everything work. I've shipped complete platforms solo that teams of five quoted months for.