Hello, I'm Justin Stewart
I've worked for fifteen-plus years in tech across companies small and large, with most of that time building services on AWS.
My background leans heavily towards distributed workloads using both containerized and serverless compute: CI/CD pipelines, REST/GraphQL APIs, event-driven architectures, data pipelines, and more. I've typically worn a lot of hats for startups, but platform and infrastructure work has always been where I've excelled and what I've enjoyed.
My current professional interests outside of my core competencies revolve around cloud-based agentic systems.
Many engineering teams need more bandwidth to think about developer experience, CI/CD, operational foundations, and everything else around their product's underlying platform — but not enough to justify a full-time hire.
We also live in a time of rapid change in the tech industry. Working independently and focusing on a small number of core customers gives me the opportunity to get exposed to new technology, new people, and to learn at a faster pace.
I work best with teams that have made a clear strategic choice to build on AWS, embrace a remote work culture, and have a technical leader I can report to directly — someone who can greenlight decisions without a long approval chain.
As a baseline, I'm on your comms, stay current with your system month to month, and flex with development when something is needed. I try to spend 80% of my time on the current focus week and 20% on support and adhoc development work.
Focus weeks are dedicated efforts — only one is active at a time across all of my clients. We schedule a sequence of focus weeks based on planned milestones, and I'm fully locked in during that window for you and your team.
Because I'm one person, not an agency, I keep my active client list intentionally small. That's a feature, not a bug. It's also a reason I always work on automating myself out as I go: your team deserves the ability to work independently.
Based in Tahlequah, Oklahoma. Remote by default.
Tell me what you're working on.
A few lines on what you're building and where the infrastructure is stuck is enough to start. If it looks like a fit, I'll follow up with a few questions before we schedule a call.