Own it end to end
One incident, one owner, from first symptom to final note. You will never repeat your story to a new agent or wonder who is holding the ball.
Seven years, three hosting platforms, thousands of escalations, and the support philosophy I built from all of it. Open to WordPress Support, Technical Support, and Customer Success Engineering roles.
Most developers meet WordPress by building a site. I met it through a ticket queue: a white screen here, a hacked shop there, a migration that somebody started on Friday and abandoned by dinner.
That vantage point changed how I think. I do not patch symptoms and move on. I read the whole stack, because a "WordPress problem" is usually a PHP problem wearing a DNS costume, or a database problem hiding behind a caching plugin.
Every role added a layer: code first, then servers, then the customer in the middle of both.
Keeping sub-second load times honest on Cloudflare Enterprise + LiteSpeed Enterprise stacks, for publishers and stores that notice every millisecond.
Front-line technical support at serious volume: 30 to 50 WordPress humans every single day.
Domain and DNS support at registrar scale, plus custom WordPress and Laravel builds; the years when "have you checked the nameservers?" became a reflex.
Support is a craft. These are the standards I hold it to.
One incident, one owner, from first symptom to final note. You will never repeat your story to a new agent or wonder who is holding the ball.
You get the diagnosis in plain language, with screenshots, timelines, and next steps, whether you are a CTO or a first-time site owner.
Monitoring, sane caching policy, credential audits: the boring prevention work that keeps the incident from becoming a subscription.
Application code in one hand, server room keys in the other.
I am open to WordPress Support Engineer and Technical Support Engineer roles, or agency partnerships if that is your world.