naomi.cloudqueen.dev
Proxy status: Proxied
$ dig naomi.cloudqueen.dev +short
Naomi Klamen
Customer Engineer candidate
;; status: NOERROR, answered from the edge

HTTP 200.
Ready to help build a better Internet.

Cloud engineer turned customer engineer. I translate L3 to L7 into business outcomes, and I build on Cloudflare myself.

Trace the request Get in touch
Naomi Klamen
Proxied
cf-cache-status: HIT
served from 1 IP, everywhere
x-cloud-certs11
x-years-google-cloud7.5
x-sellers-trained-on-cloudflare400
x-deal-arr$44M
cf-ray: naomi-EWR

Follow the request

Every request to this page takes the same path as a request through Cloudflare. Each hop tells you something about me.

  1. 01 / DNS

    Who I am

    Customer engineer with 7.5 years at Google Cloud and time at Oracle. 11 cloud certifications, all used in front of customers.

  2. 02 / Anycast edge

    Why Cloudflare

    I sold Cloudflare at Oracle and trained 400 sellers on it. Now I want to be on the side of the network that builds it.

  3. 03 / WAF

    Filters noise

    Discovery before demos. I learned that the hard way, and now I ask before I show.

  4. 04 / Cache HIT

    Proven results

    Helped a hosting provider land a $44M ARR deal, with BYOIP and a DDoS architecture decision at the center.

  5. 05 / Workers

    I build

    A RAG pipeline on Cloudflare, and this domain, registered and proxied through Cloudflare with Full (strict) TLS.

Response headers

How I work

x-principled: true

Do the right thing, even when it costs the deal

I tell customers when a product is not the right fit, and I own my mistakes instead of passing them on.

x-curious: always

Ask first, then architect

I read the threat reports, build on the platform, and start every customer meeting with their problem, not my slides.

x-transparent: true

Say the hard thing early

When I disagree, I say so with data, and once we decide, I commit.

Currently reading

More swarms, fewer giants

The Q3 DDoS report shows attacks getting shorter and smaller but far more frequent. Most end before a human could react, which is the strongest case I know for always-on protection.

8,226 attacks per hour
96% over in under 10 minutes
98% under 1 Gbps
my takeaway: always-on > on-demand