What is a more techy Technical Writer job title that isn't cutesy or confusing? Announcing the...
What is a more techy Technical Writer job title that isn't cutesy or confusing?
As a dual citizen, my US passport will expire one day after traveling to the US. Will this work?
Monty Hall Problem-Probability Paradox
Tips to organize LaTeX presentations for a semester
Show current row "win streak"
Why are vacuum tubes still used in amateur radios?
What does Turing mean by this statement?
Is there public access to the Meteor Crater in Arizona?
Why is std::move not [[nodiscard]] in C++20?
Delete free apps from library
Mounting TV on a weird wall that has some material between the drywall and stud
One-one communication
Why is a lens darker than other ones when applying the same settings?
How does light 'choose' between wave and particle behaviour?
Can an iPhone 7 be made to function as a NFC Tag?
Google .dev domain strangely redirects to https
Trying to understand entropy as a novice in thermodynamics
Sally's older brother
Printing attributes of selection in ArcPy?
Is there hard evidence that the grant peer review system performs significantly better than random?
Would color changing eyes affect vision?
Is CEO the "profession" with the most psychopaths?
What initially awakened the Balrog?
Flight departed from the gate 5 min before scheduled departure time. Refund options
What is a more techy Technical Writer job title that isn't cutesy or confusing?
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Announcing our contest results!
Tags of the week! April 15-21, 2019: Planning & TranslationExplaining that experience is far greater than official job title impliesHow can one make technical issues more accessible to a non-technical audience?What help is there for a technical reseacher/writer that can't edit?What are the key skills for a new technical writer?Does a technical writer need a technical background?What Types of Jobs can a Writer find?Best practices for maintaining documented code examples?How can we make compiling release notes less chaotic?Looking for sites that describe minimalist writing for technical contentTechnical writer degree with an English BA?Technical review process when using FrameMaker
I have been hired as a Technical Writer at a firm who needed multiple types of writers: A few people were hired to write content for the average website reader interested in our product, such as a Product Manager, and user documentation, such as user guides. However, I was hired to dig down into the code and actually write sample code to explain how to use the company's SDK (software development kit). I interface with the development team on a daily basis and actually test their code, analyze it, and give them suggestions for improvement.
I would like to add another descriptive term in my job title on my email signature and resume to show that I have in-depth software engineering knowledge. For anyone who thinks this is to puff myself up or to downplay normal Technical Writers, you are wrong. The primary reason I want to do this is so my resume doesn't look like I switched careers. The secondary reason is so that people who receive my emails and read my resume can tell by my title that I have extensive software engineering experience inside software development.
I read this, but it didn't help. Of course, I searched the internet, too. I found articles about my current role, but nothing about job titles.
I thought perhaps:
- Technical Writer (Sr. Software Engineer)
- Technical Writer as Sr. Software Engineer
- Technical Writer specializing in the full SDLC
technical-writing career
New contributor
add a comment |
I have been hired as a Technical Writer at a firm who needed multiple types of writers: A few people were hired to write content for the average website reader interested in our product, such as a Product Manager, and user documentation, such as user guides. However, I was hired to dig down into the code and actually write sample code to explain how to use the company's SDK (software development kit). I interface with the development team on a daily basis and actually test their code, analyze it, and give them suggestions for improvement.
I would like to add another descriptive term in my job title on my email signature and resume to show that I have in-depth software engineering knowledge. For anyone who thinks this is to puff myself up or to downplay normal Technical Writers, you are wrong. The primary reason I want to do this is so my resume doesn't look like I switched careers. The secondary reason is so that people who receive my emails and read my resume can tell by my title that I have extensive software engineering experience inside software development.
I read this, but it didn't help. Of course, I searched the internet, too. I found articles about my current role, but nothing about job titles.
I thought perhaps:
- Technical Writer (Sr. Software Engineer)
- Technical Writer as Sr. Software Engineer
- Technical Writer specializing in the full SDLC
technical-writing career
New contributor
1
Welcome to Writing.SE. We love questions about technical writing here and we hope you'll stick around (and pick a name of your choice so we can remember who you are). I'm not sure this question is on topic though. The one you link to is 7 years old and a lot of old posts here would be off topic now, as I think that one would be without question. I'm not voting to close because I'd like to hear from others here about whether or not your question is on topic. Either way, please do post other questions as desired and answer what you like.
– Cyn
4 hours ago
add a comment |
I have been hired as a Technical Writer at a firm who needed multiple types of writers: A few people were hired to write content for the average website reader interested in our product, such as a Product Manager, and user documentation, such as user guides. However, I was hired to dig down into the code and actually write sample code to explain how to use the company's SDK (software development kit). I interface with the development team on a daily basis and actually test their code, analyze it, and give them suggestions for improvement.
I would like to add another descriptive term in my job title on my email signature and resume to show that I have in-depth software engineering knowledge. For anyone who thinks this is to puff myself up or to downplay normal Technical Writers, you are wrong. The primary reason I want to do this is so my resume doesn't look like I switched careers. The secondary reason is so that people who receive my emails and read my resume can tell by my title that I have extensive software engineering experience inside software development.
I read this, but it didn't help. Of course, I searched the internet, too. I found articles about my current role, but nothing about job titles.
I thought perhaps:
- Technical Writer (Sr. Software Engineer)
- Technical Writer as Sr. Software Engineer
- Technical Writer specializing in the full SDLC
technical-writing career
New contributor
I have been hired as a Technical Writer at a firm who needed multiple types of writers: A few people were hired to write content for the average website reader interested in our product, such as a Product Manager, and user documentation, such as user guides. However, I was hired to dig down into the code and actually write sample code to explain how to use the company's SDK (software development kit). I interface with the development team on a daily basis and actually test their code, analyze it, and give them suggestions for improvement.
I would like to add another descriptive term in my job title on my email signature and resume to show that I have in-depth software engineering knowledge. For anyone who thinks this is to puff myself up or to downplay normal Technical Writers, you are wrong. The primary reason I want to do this is so my resume doesn't look like I switched careers. The secondary reason is so that people who receive my emails and read my resume can tell by my title that I have extensive software engineering experience inside software development.
I read this, but it didn't help. Of course, I searched the internet, too. I found articles about my current role, but nothing about job titles.
I thought perhaps:
- Technical Writer (Sr. Software Engineer)
- Technical Writer as Sr. Software Engineer
- Technical Writer specializing in the full SDLC
technical-writing career
technical-writing career
New contributor
New contributor
edited 4 hours ago
Cyn
18.2k13985
18.2k13985
New contributor
asked 5 hours ago
user2263986user2263986
61
61
New contributor
New contributor
1
Welcome to Writing.SE. We love questions about technical writing here and we hope you'll stick around (and pick a name of your choice so we can remember who you are). I'm not sure this question is on topic though. The one you link to is 7 years old and a lot of old posts here would be off topic now, as I think that one would be without question. I'm not voting to close because I'd like to hear from others here about whether or not your question is on topic. Either way, please do post other questions as desired and answer what you like.
– Cyn
4 hours ago
add a comment |
1
Welcome to Writing.SE. We love questions about technical writing here and we hope you'll stick around (and pick a name of your choice so we can remember who you are). I'm not sure this question is on topic though. The one you link to is 7 years old and a lot of old posts here would be off topic now, as I think that one would be without question. I'm not voting to close because I'd like to hear from others here about whether or not your question is on topic. Either way, please do post other questions as desired and answer what you like.
– Cyn
4 hours ago
1
1
Welcome to Writing.SE. We love questions about technical writing here and we hope you'll stick around (and pick a name of your choice so we can remember who you are). I'm not sure this question is on topic though. The one you link to is 7 years old and a lot of old posts here would be off topic now, as I think that one would be without question. I'm not voting to close because I'd like to hear from others here about whether or not your question is on topic. Either way, please do post other questions as desired and answer what you like.
– Cyn
4 hours ago
Welcome to Writing.SE. We love questions about technical writing here and we hope you'll stick around (and pick a name of your choice so we can remember who you are). I'm not sure this question is on topic though. The one you link to is 7 years old and a lot of old posts here would be off topic now, as I think that one would be without question. I'm not voting to close because I'd like to hear from others here about whether or not your question is on topic. Either way, please do post other questions as desired and answer what you like.
– Cyn
4 hours ago
add a comment |
1 Answer
1
active
oldest
votes
The conventional term is "programmer writer" or, sometimes, "programming writer". It is generally used to describe someone whose training and focus is programming rather than technical writing, but who is currently performing a technical communication function specifically aimed at documenting things for programmers. I did most of my tech writing for developers as well, but because my career focus was technical writing, I stuck to the term "technical writer". Same job, more or less. The difference in titles is more to cover differences in career track, which seems to be what you are concerned about.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "166"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
user2263986 is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwriting.stackexchange.com%2fquestions%2f44693%2fwhat-is-a-more-techy-technical-writer-job-title-that-isnt-cutesy-or-confusing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The conventional term is "programmer writer" or, sometimes, "programming writer". It is generally used to describe someone whose training and focus is programming rather than technical writing, but who is currently performing a technical communication function specifically aimed at documenting things for programmers. I did most of my tech writing for developers as well, but because my career focus was technical writing, I stuck to the term "technical writer". Same job, more or less. The difference in titles is more to cover differences in career track, which seems to be what you are concerned about.
add a comment |
The conventional term is "programmer writer" or, sometimes, "programming writer". It is generally used to describe someone whose training and focus is programming rather than technical writing, but who is currently performing a technical communication function specifically aimed at documenting things for programmers. I did most of my tech writing for developers as well, but because my career focus was technical writing, I stuck to the term "technical writer". Same job, more or less. The difference in titles is more to cover differences in career track, which seems to be what you are concerned about.
add a comment |
The conventional term is "programmer writer" or, sometimes, "programming writer". It is generally used to describe someone whose training and focus is programming rather than technical writing, but who is currently performing a technical communication function specifically aimed at documenting things for programmers. I did most of my tech writing for developers as well, but because my career focus was technical writing, I stuck to the term "technical writer". Same job, more or less. The difference in titles is more to cover differences in career track, which seems to be what you are concerned about.
The conventional term is "programmer writer" or, sometimes, "programming writer". It is generally used to describe someone whose training and focus is programming rather than technical writing, but who is currently performing a technical communication function specifically aimed at documenting things for programmers. I did most of my tech writing for developers as well, but because my career focus was technical writing, I stuck to the term "technical writer". Same job, more or less. The difference in titles is more to cover differences in career track, which seems to be what you are concerned about.
answered 2 hours ago
Mark BakerMark Baker
56.9k496206
56.9k496206
add a comment |
add a comment |
user2263986 is a new contributor. Be nice, and check out our Code of Conduct.
user2263986 is a new contributor. Be nice, and check out our Code of Conduct.
user2263986 is a new contributor. Be nice, and check out our Code of Conduct.
user2263986 is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Writing Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fwriting.stackexchange.com%2fquestions%2f44693%2fwhat-is-a-more-techy-technical-writer-job-title-that-isnt-cutesy-or-confusing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Welcome to Writing.SE. We love questions about technical writing here and we hope you'll stick around (and pick a name of your choice so we can remember who you are). I'm not sure this question is on topic though. The one you link to is 7 years old and a lot of old posts here would be off topic now, as I think that one would be without question. I'm not voting to close because I'd like to hear from others here about whether or not your question is on topic. Either way, please do post other questions as desired and answer what you like.
– Cyn
4 hours ago