You’ve probably been there. You pour years of your life into a demanding role, blending your identity with the company’s mission. You build a following. You become the face of the brand. Then, when it’s time to leave, you write a heartfelt farewell, expecting a wave of validation and a dramatic exit that cements your legacy.
Instead, you get silence. Or worse, outright indifference.
Recently, a Developer Relations professional penned a vulnerable, frustrated goodbye to their role. They had poured themselves into an ambiguous, demanding job, hoping for a recognized exit. The internet’s response was brutal. Commenters called it an “uninteresting rant by a nobody.” They asked why they should even care.
It feels cruel, but it reveals a brutal truth about modern work.
The corporate machine doesn’t mourn; it just updates the org chart.
In externally-facing roles like DevRel, marketing, or developer advocacy, the lines between your personal identity and the company brand blur. You tweet from your own face, but you’re talking about someone else’s product. You build a community, and you start to believe the community is yours.
It’s an intoxicating illusion. You think you’re building a personal brand. You think your audience is engaging with your unique insights and sparkling personality.
You thought you were building a legacy. You were just wearing a really well-recognized company polo.
The audience was never clapping for you; they were clapping for the logo on your shirt. They followed you because you had access. You were the conduit to the API, the product roadmap, or the support escalation path. The moment you lose that access, your value proposition evaporates.
We all want our work to mean something. We want our departures to be felt. But tying your self-worth to your employer’s reach is a dangerous game. When you leave, the followers stay. The inbox moves on. The brand finds a new face to fill the polo.
Never confuse the company’s microphone for your own voice.
If you’re in a role where your identity and your employer’s are tangled, it’s time to separate them. Build something that belongs to you. Write code that isn’t proprietary. Build an audience that cares about your thoughts, not just your access. Because when the day comes to say goodbye forever, the only legacy that will actually stick around is the one you built for yourself.
FAQ
Q: Isn't it possible to build a genuine personal brand while employed?
A: Yes, but only if your audience would still follow you if you switched companies tomorrow. If your entire following is predicated on your access to a specific product or team, you don't have a personal brand—you have a corporate megaphone.
Q: What should I do if I'm currently in a DevRel or externally-facing role?
A: Start decoupling your identity from the company immediately. Create content that stands on its own merit, independent of your employer's product. Build a portfolio of work that you own and can take with you when you walk out the door.
Q: Is expecting a meaningful farewell really too much to ask?
A: From a human perspective, no. From a corporate reality perspective, absolutely. Companies optimize for continuity, not sentimentality. Expecting the internet to validate your career choices is a recipe for disappointment.