A small number of clients
Retainers are capped deliberately. The arrangement only works if I know your architecture well enough to diagnose it without reading it from scratch.
13+ years of production PHP. Now spent keeping other people's infrastructure boring.
13+ years of production PHP. Now spent keeping other people's infrastructure boring.
I run AWS infrastructure for SaaS teams that have outgrown doing it themselves but are not ready to hire for it. That usually means I am the person who gets paged, the person who notices the bill moving, and the person who can change the application code when the fix belongs there rather than in the infrastructure. I work with a small number of clients at a time, because the value of this arrangement is that I know your system rather than your ticket history.
Both certifications have since lapsed; the work in the case studies is current.
13+ years of production PHP, across ad-tech systems handling high request volumes, enterprise delivery work with the process weight that implies, and agency projects where the same person wrote the code and answered for it at 2am. Most of that time was spent on applications that were already live and already had users, which is a different discipline from building something new.
The AWS work grew out of that. Applications I had written needed somewhere reliable to run, and the gap between "it works on the server" and "it survives a traffic spike, a failed deploy and a lost instance" turned out to be where most of the real engineering was. That is the part I now do for other people.
Retainers are capped deliberately. The arrangement only works if I know your architecture well enough to diagnose it without reading it from scratch.
You talk to the person doing the work. Nothing is relayed, and nothing gets lost being relayed.
Findings, incidents and recommendations arrive in writing. You should be able to forward them without translating them first.
If you replace me, the next person inherits Terraform and runbooks rather than a mystery. That is the standard whether or not you ever use it.
Mukesh is a standout developer who played a critical role in architecting our Laravel and AWS infrastructure. He successfully translated complex, multi-functional operational requirements into a robust and scalable system. His technical expertise and ability to build for high-stability environments are exceptional. Beyond the technical, he brings a down-to-earth approach that I value, a rare quality in these complex architectural cases. I highly recommend him for any large-scale projects.
Mukesh has been excellent to work with. I highly recommend him as an AWS consultant and programmer.
Stop firefighting your AWS.
Book a free AWS audit