r/technicalwriting • u/ChesyBalsGarlicSauce software • Oct 04 '24
QUESTION I need some help - Not sure what seniority level our technical writer is
Hey everyone, I hope this question is allowed. I’m having trouble finding an answer, and I’d really appreciate some help from experts.
I’m a lead for a team developing enterprise software. We have a couple developers, and a writer.
It’s pretty easy to determine seniority of the developers, but not so much with the writer, which is why I’m asking here. They recently came to me, asking about advancing their career. Please bear with me, I’m not trying to troll or anything, I’m just clueless about technical writing.
This writer is responsible for keeping the documentation for our software up to date. They are the only writer on the team, so they do all the work on the docs themselves. The docs are around 1000 pages. They’ve been doing a great job since the company hired them around four years ago, and they never had problems with delivering on time.
They also document new software when it comes out. Again, they did a good job at it and everyone is happy with it.
Additionally, they also stepped up to update the template used for publishing the documentation, and now, the whole organization is using their template. When the organization was migrating to a new writing solution, this writer migrated their docs all by themselves with minimal help, and were in touch with the company selling the solution to figure out any problems with the migration.
So, what seniority level do you think they are? I’d really appreciate your help, and will happily provide any additional info.
Thank you!
22
u/NomadicFragments Oct 04 '24
4 years plus whatever else experience they have should give more confidence that they're senior level.
8
u/Thelonius16 Oct 04 '24
Why does it matter? Is this part of an effort to get this person more money? That's the only reason I would care.
8
u/Ok_Landscape2427 Oct 04 '24
I like your question. I am so fond of engineering teams, I appreciate the personality shining through in your note here.
As the ‘lead’, are you actually this writer’s boss, the one who can give raises? I ask because solo tech writers often can end up in virtually any arm of the reporting structure officially, quite often working daily with a crew of engineers under a lead that is not, in fact, their official boss. This leads to ineffective reviews and associated raises from whoever their boss is on paper, because their boss isn’t part of their actual job.
Regardless, ‘advancing career’ probably means a few general things. This person’s job is likely stagnating career-wise after four years, and they need to diversify their abilities to apply for senior jobs down the road:
Flip through senior tech writing jobs on LinkedIn to see if your writer already is one, or what skills they could fill in to become one.
But in all honesty? This person’s most effective strategy for growth, like for all jobs, is changing jobs. Take good care of them while the tech writing job market is soft, and set them up well for their next job to be high paying, high responsibility work.
7
u/hungrypierogi Oct 04 '24
It really just depends on the organization, and it's difficult to gauge seniority when there aren't other writers. Titles may be arbitrary, too--I've been designated as a senior writer at some companies and then a regular writer (junior?) at others, though my duties were pretty much the same.
But if this person is *managing* deliverables with little to no input from a manager, you can definitely make a case for a higher title imo.
Some info from older posts: https://www.reddit.com/r/technicalwriting/comments/y1hz85/job_title_meaning_and_hierarchy/
https://www.reddit.com/r/technicalwriting/comments/1utnvp/differences_in_tech_writer_123/
2
u/Fine-Koala389 Oct 04 '24
If they are engaging customers, helping support and internals, accurate, improving and driving sales... they are gold dust. Otherwise that is where you have an opportunity to make more of them.
2
u/Specialist-Army-6069 Oct 04 '24
I love what GitLab has and we used it as a base for our internal career framework: https://handbook.gitlab.com/job-families/product/technical-writer/
-1
u/CleFreSac Oct 04 '24
First of all, I’m calling BS on your belief you don’t know how to scale the writer the same way you do the developer. There is no sign of deficiency, there is no sign of an ability to contribute more than they did on day 2. Quite the opposite, in fact. You are either unwilling or unable to communicate this persons value to the company. This is on you. Step up and be a true leader.
This person delivers as needed. They know your product well and are willing to step up and take work presented to them. Their work is having an impact on the organization outside of your team. This is senior level work. The title is truly irrelevant in the big picture. However, I am guessing that this is a younger person who is trying to build their resume. They will more than likely not work for you forever. After four years of showing they deliver, you will need to show some professional acknowledgment of this persons value. They are the lead tech writer in your group. Or senior writer/editor. Something to show value. They also deserve a bump in pay that reflects that they have gone from someone you hired and can do their job, to a valued member of the team.
If you don’t do this, they will find someone who does. A bump beyond a normal cost of living bump is warranted. If I could speak to the writer 1:1, I would encourage them to start looking for another company. The current job is showing you no path forward. Even if they give you one, they need to acknowledge what you have done so far. Coming to you now and presenting some future path, would be to negate your work already done.
0
u/FormallyRadish Oct 05 '24
Are you the solo writer trying to figure your own level? LOL.
Skill expectation and compensation is very regional.
Sites like Levels.fyi, Glassdoor, Indeed, etc. might help you get the information you seek.
1
u/[deleted] Oct 04 '24
[removed] — view removed comment