You are a knowledge engineer

The urgency has never been greater to brand yourself from technical writer -> knowledge engineer | content engineer | information developer. Engineering information is what you've always done: research, write, edit, test, organize, maintain.

This is not a survival tactic or sleight of hand. These skills are more important than ever with exponentially more agents consuming and contextualizing the knowledge we produce and maintain. We believe deeply in the importance of these skills, as do increasingly more of our engineering colleagues. But we need critical mass before it's too late. We need to put our thumbs on the scale to educate the industry on the value we bring.

If you allow yourself to be seen as "just" a writer, you are underselling yourself in an industry that is pressured to optimize headcount at every turn—by public markets, by boards, by peers.

I started my career during the Great Recession, and have been through multiple boom and bust cycles. Tech writers are the last role to fill when things are great, and the first one to cut when things are bad. I had to execute layoffs just a couple years into my career as a young manager. I knew shrinking my team was bad for the business, but all my senior champions had left or been laid off.

I didn't make the mistake of single-threading at Stripe.

Embed into the company DNA. In week one I met all the content managers from across marketing, product, and comms. We aligned on language for our job descriptions and job ladders. Then we worked with engineering leaders to embed documentation duties into engineering job ladders.

Continuously show your work. We published user research reports, we analyzed data, we showed ROI. Being likable in a high-performing organization doesn't save you from layoffs. You must hold a place of high ROI in leadership's mental model. And that takes continuous quantitative and qualitative work.

That set a foundation for hiring people in content roles that garner great respect to this day at Stripe. Because everyone, from IC to C-suite, knows how important the content roles are to Stripe's business.

Every single time it's a strong leadership champion, sometimes even the CEO, that advocates for hiring tech writers. And they put up a fight to keep them. But when there isn't company-wide understanding of what tech writers do, you're leaving your destiny in the hands of a single champion.

Start with a subtle rebellion. When you introduce yourself to new teammates, describe yourself as a content engineer and describe your duties. Update your resumes and LinkedIn descriptions. Then advocate for a title change. It's hard to advocate for yourself, but this is existential.

If you're a technical writing manager, make the bold change now and brand your team accordingly.