Daniel Corbett

Security PM @Fastly. Building WAF, bot detection & DevSecOps tools. Podcast guest. Tech evangelist. Buffalo wings＞ all wings. Ex-@HAProxy 🛡️🍗

[Daniel Corbett @DanielCorbett_]

If you’re in a technical role and you’re starting to feel like "the glue" - the one people come to for answers, priorities, or direction - you might be on the path to product too.

Already made the switch? Thinking about it? I’d love to hear your story. 👇

[Daniel Corbett @DanielCorbett_]

I didn’t set out to become a Product Manager.

In fact, I like to joke that I slipped and fell and woke up as one.

But here’s how I ended up as a (technical) Principal PM - and why I stayed. 🧵👇

[Daniel Corbett @DanielCorbett_]

Now I lead multiple security-focused products.

I write PRDs, build PoCs, handle escalations, demo new features, contribute code, and sometimes jump into devtools to mock up UX.

Every day looks a little different - and that’s what I love about it.

[Daniel Corbett @DanielCorbett_]

Being a TPM is more than just a job title - it's a mindset.

What other myths have you heard about technical PMs? Drop yours below. 👇

[Daniel Corbett @DanielCorbett_]

I've heard some wild takes on what a Technical Product Manager is.

So today, let's bust a few myths about being a TPM.

🧵👇

[Daniel Corbett @DanielCorbett_]

"If you're a great engineer, you'd be a great TPM."
Being a great engineer helps. But TPMs also need to be great communicators, translators, and facilitators. Influence > authority.

[Daniel Corbett @DanielCorbett_]

If you've ever felt like a translator between teams, you might already be doing TPM work.

Are you a TPM (or work with one)? What’s your definition? 👇

[Daniel Corbett @DanielCorbett_]

What is a (technical) Product Manager, really?
A TPM isn't just a PM who "knows a little code." We sit at the intersection of product, engineering, and business - but we aren't just project managers either.

So what makes a Technical PM unique? Let's break it down. 🧵👇

[Daniel Corbett @DanielCorbett_]

A great TPM balances deep technical knowledge with strategic thinking.

Too tech-heavy? You lose sight of the product.
Too high-level? Engineers won't take you seriously.