The person behind the queue

Most engineers build websites. I keep them alive.

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.

Showrav Hasan working on WordPress infrastructure
Chapter one

I learned WordPress from the side that breaks

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.

3,500+Incidents closed for founders, publishers, and SaaS teams
Rocket.net · Hostinger · NameSiloPlaybooks and migrations delivered at platform scale
< 2 hrsMy standing response time when something is actually on fire
Career

A career measured in uptime

Every role added a layer: code first, then servers, then the customer in the middle of both.

  • WordPress Engineer

    Rocket.net · 2021–Present

    Keeping sub-second load times honest on Cloudflare Enterprise + LiteSpeed Enterprise stacks, for publishers and stores that notice every millisecond.

    • Moved hundreds of mission-critical sites between servers without a single second of downtime.
    • Chased down PHP worker saturation, database lockups, and plugin conflicts that had survived multiple engineers.
    • Wrote the incident playbooks the global support team now follows when things go sideways.
  • Senior Customer Success

    Hostinger · 2019–2021

    Front-line technical support at serious volume: 30 to 50 WordPress humans every single day.

    • Became the escalation point for the tickets nobody else could close, and trained the juniors who came after me.
    • Resurrected dead cron jobs and rebuilt corrupted databases for enterprise customers.
    • Kept a 98% satisfaction score across thousands of conversations.
  • Web Developer & Support

    NameSilo + freelance · 2016–2019

    Domain and DNS support at registrar scale, plus custom WordPress and Laravel builds; the years when "have you checked the nameservers?" became a reflex.

How I work

Three rules I never break

Support is a craft. These are the standards I hold it to.

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.

Translate, don't jargon

You get the diagnosis in plain language, with screenshots, timelines, and next steps, whether you are a CTO or a first-time site owner.

Fix it so it stays fixed

Monitoring, sane caching policy, credential audits: the boring prevention work that keeps the incident from becoming a subscription.

Capabilities

The toolbox, itemized

Application code in one hand, server room keys in the other.

WordPress engineering

  • White screens & 500s, diagnosed to the root
  • Query tuning & object caching
  • Staging & migrations without downtime
  • Malware forensics, cleanup, hardening
  • WooCommerce checkouts that stay up on sale day

Server room

  • cPanel, WHM, Cloud Panel administration
  • LiteSpeed & NGINX configuration
  • Cloudflare Enterprise edge rules
  • SSL automation & strict firewalls
  • Backups that restore & alerts that fire

DNS & email

  • A, MX, TXT, CNAME, set with intent
  • SPF, DKIM, DMARC enforced properly
  • Propagation mysteries, solved
  • Domain consolidations & clean cutovers

Looking for someone exactly like this?

I am open to WordPress Support Engineer and Technical Support Engineer roles, or agency partnerships if that is your world.

Ping me on WhatsApp