Developer platforms
CI/CD, deployment automation, self-service tooling, supply-chain controls, and observability—so engineers ship safely without fighting the platform.
Platform engineering · Infrastructure · Security
I build internal systems that help engineering organizations run better.
I work across developer platforms, cloud foundations, data pipelines, and security programs—the layers teams depend on every day but rarely get to redesign properly.
Most engagements start with a bottleneck: manual runbooks, fragile deploys, access sprawl, or data that can't be trusted downstream. I map the constraints, choose tools that fit the operational reality, and ship systems people can run and maintain for years.
The goal isn't the newest stack. It's the right stack—implemented so it still works after the launch demo is over.
Capabilities
The through-line is operational reliability—platforms, foundations, data, and security designed to run for years, not demos.
Foundations & operations
Cloud infrastructure, networking, Kubernetes, automation, and reliability engineering—the layer everything else depends on.
Data systems
Pipelines that move, validate, and operationalize data at scale—including healthcare interoperability and ETL workflows teams can audit and rerun.
Security & compliance
Zero Trust access, secure PHI environments, vulnerability management, and compliance programs built into the architecture—not bolted on after launch.
Selected work
Architecture diagrams and full write-ups live on dedicated case study pages. Below: what was broken, what we built, and what changed.
Zero Trust network access
Problem: Hundreds of servers and internal environments still depended on exposed services, firewall allow-lists, and VPN-style network trust.
Outcome: Identity-driven access for 200+ systems—policy-managed, remotely operable, without treating the network perimeter as the security boundary.
Internal developer platform
Problem: Teams spent too much time on bespoke deploy paths, weak supply-chain controls, and inconsistent operational tooling.
Outcome: Standardized CI/CD, deployment automation, and guardrails—so engineers ship product work instead of reinventing infrastructure.
VistaDesk
Problem: Service organizations ran operations across disconnected tools—customers, field crews, and workflows didn't share a single system of record.
Outcome: CRM and field-service platform unifying scheduling, workflows, and customer data for teams in the field and the office.
Personal projects
Tools I built for my own use—smaller in scope than client work, but held to the same bar on privacy and reliability. A dedicated projects page can go deeper later.
Expense Tracker
Mobile app that parses SMS on-device to track income and expenses. No cloud sync, no third party holding your financial data.
Privacy-first · on-deviceDockly
One view for shipments across carriers—so you're not opening five tracking pages for five packages.
Logistics · aggregationPrinciples
Understand before you build
Constraints, trade-offs, and how teams actually operate matter more than framework trends. The tool choice comes after the problem is clear.
Design for the on-call shift
Success means someone can run it at 2 a.m.—monitor it, patch it, and explain it to a new hire—not that it worked once in a slide deck.
Security ships with the system
Especially where sensitive data is involved. Access, auditability, and blast-radius control are architectural decisions, not backlog items.
Automate the repeat work
Durable organizations scale on documented processes and reliable automation—not on one person who "just knows how it works."
Background
I go where the bottleneck is. I started in systems administration and infrastructure; the work grew into platform engineering, security, healthcare data systems, compliance programs, developer tooling, and product delivery.
The technologies change. The aim doesn't: systems that let engineering organizations operate with less friction and more confidence.
I'm most useful when the problem is underspecified, the constraints are real, and the answer has to balance engineering, operations, security, and business pressure—not just ship a feature.
Recent work spans Zero Trust access, internal developer platforms, healthcare data processing, PHI validation environments, and operational software like VistaDesk. Outside client work, I still build small tools for problems I hit in everyday life.
Let's talk
Scaling an engineering org, untangling platform debt, hardening access, or standing up systems that need to last? I'd be glad to hear what you're working on.