Skip to main content

Professional profile

I never set out to become "multifaceted." Looking back, though, I realize that's what working as a freelancer and then in startups did to me. There were no clean boundaries between roles. If something needed to be defined, I defined it. If something needed to be built, I built it. If something needed to be explained, documented, promoted, or measured, I usually ended up doing that too.

For a while I read this as a lack of specialization. Over time I came to see it differently: I was learning how to take a project end-to-end, and how to talk with very different kinds of people without losing them along the way.

Comfortable at intersections​

The "full-stack" label usually applies to technical layers. In my case it fits better across:

  • Engineering
  • Product
  • Developer experience
  • Community
  • Communication
  • Business reality

I'm not the deepest expert in any of these. But I speak their languages well enough to translate between them, which often turns out to be more useful than going deeper into just one.

That's how I tend to operate:

  • I can empathize with engineers because I've shipped production code.
  • I can talk product because I've had to make trade-offs and own decisions.
  • I can work with marketing because I've had to promote what I built.
  • I can connect with developers because I've been (and still am) one.
  • I can defend metrics because I've had to justify impact.

Build something tangible​

When a problem is unclear and conversations start going in circles, my instinct is to build something β€” not as a final answer, but as a way to make the discussion concrete. A prototype, a draft, a small initiative. Something we can look at and react to.

That's also how I take initiatives forward: I don't usually rely on formal authority. I rely on having something visible enough that people can engage with it.

Why this matters now​

I've been working with AI tools daily since 2021. They've made me much faster at prototyping, drafting, and iterating. But the bottleneck has shifted. It's no longer mostly about producing output β€” it's about knowing what's worth producing, how it connects to what already exists, and how it should evolve over time.

In that environment, being comfortable across disciplines is less of a workaround for not specializing, and more of an actual leverage point.

A note, not a label​

I still don't think of myself as "the expert" in a single discipline. What I've built over the years is the ability to move an initiative from idea to something real, across the parts of an organization where things tend to get stuck.

That's probably the part that defines me most β€” and the part I enjoy most: turning ideas into something tangible, and making sure they don't stop halfway.

Related: Personal traits Β· My facets Β· Public speaking Β· Projects Β· LinkedIn

I'd love to hear from you​

If you know me β€” is there a facet I might have overlooked? Where do you think my strengths are most visible? Anything here you see differently?

If you don't know me, feel free to reach out. I enjoy thoughtful conversations.