Post History

Source: https://writers.stackexchange.com/a/44700
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/

This is a challenging specialization to capture in a job title, which is why my LinkedIn tagline says "speaker to programmers". But that doesn't work as a job title at any but the edgiest startups.

As suggested in [this answer](https://writing.stackexchange.com/a/44698/1993), some use Programming Writer. At a previous company I was documenting but also improving (and writing examples against) our SDK, and where we wanted to make it more clear to upper management and our new corporate overloads that I'm an _engineering-grade_ technical writer, they gave me the title (Senior) SDK Developer. Depending on how involved you are in _defining_ your SDK, that could work for you too.

At my current company I'm an Information Developer because that's the title they use; internally people know that I have programming cred, and if I need to communicate it externally, I'll probably have more than a title available to do it with. On a resume, for example, there are a couple ways to convey important information not covered in a job title. On LinkedIn (and in a cover letter) you can write a summary that people will see before they get to the job history. If I'm handing somebody a business card (I guess that could happen), we'll have the context of whatever conversation led to me doing so.

In my career I've found that the _adjective_ (senior, principal, lead...) carries more weight than the specific tech-writer-ish title. If you get to principal/lead level, people who know anything at all about the field are going to expect you to have some real technical depth.

Original score: 7