And as patio11 says, combining engineering with good writing skills makes it very easy to be one of the top with your combined skills
I’ve been trying to lean more into that advice the past couple months by publishing on my blog :)
Surprisingly enough, just this morning I woke up to realize someone had shared an article I wrote and it was on the HN front page!
It's been recognized by my peers and managers. Not much has ever really come from it. I've been given opportunities to draft "bad news" copy to be sent to clients, and I'm the point person for editing design documentation. But none of these are really roles of prestige. If anything, I'm really seen as being the person responsible for the grunt work that people don't generally enjoy doing.
It might come easily to you, but me and other people I know often draft emails and such 3-4 times, asking for proofreading from trusted friends.
Yea, the proofreading for docs and writing client copies isn't fun, but the skills to do these well help all of your written communication immensely.
Your org could be very different, but I feel like I am recognized in large part because I care about communicating, and put a lot of effort into clear emails and docs. Part of your recognition could be because you have great writing skills.
The benefits don't accrue as much when you're writing material you've been told to write, especially when it's not something the recipient will be happy to receive. Those can be valuable learning experiences, but it's not harvest season yet.
The value comes when you CHOOSE to compose messages meant to persuade YOUR peers and internal stake holders. Your skill with the pen gives you a voice, like a bard who can urge a crowd to action.
What words do we associate with those kinds of people?
Influence
Leadership
Writing can help get you there
Here's the thing - the typical software engineer interview doesn't assess writing(or many other valuable traits that can become unusually valuable when combined with good coding ability). Almost every one I've done has been a rehash of data structu res and algorithms along with a few other technical topics. Someone who is an excellent writer and merely a good programmer is likely to be screened out. If you combine skills, you're treading a path that people don't really hire for, mainly because they can't conceive of it, and it doesn't fit into the silos.
That's fine. You need to accept that the google-style software engineering path probably isn't for you. But you do need to have more initiative. Companies that post jobs tend not to look for these combinations. However, if you have personal initiative, you can often build this role within a company (or on your own), and the career path it opens up can be very satisfying.
Like, I haven't seen Raymond Chen's resume, but if he calls me up tomorrow looking for a job, I'll find something for him, even if we're not hiring.
Ditto for Steve Klabnik, Carol Nichols, and some other people in the Rust community.
I started brushing up on my writing skills since at the higher levels of engineering (and prob all other fields) communicating your ideas more effectively will open up way more opportunities down the line.
Some of those may have monetary rewards. But the reward can be something else as well
