Ask HN: What are some non-coding roles that a developer can easily switch to?
1–9 of 9 posts
Re: Ask HN: What are some non-coding roles that a developer can easily switch to?
#2Writing API docs, user guides, blog posts, how-to guides, etc...
Pay is usually less than dev but still high.
Re: Ask HN: What are some non-coding roles that a developer can easily switch to?
#3The career progression isn’t great. Basically it’s just management, EPM, or back to SDE.
Re: Ask HN: What are some non-coding roles that a developer can easily switch to?
#4I rarely see people mention it but documentation writer/tech writer is a full time role at bigger companies, especially SaaS companies with large/complex APIs. Writing API docs, user guides, blog posts, how-to guides, etc... Pay is usually less than dev but still high.
It’s sad to see how many great open-source projects get overlooked on GitHub because they’re poorly documented.
Re: Ask HN: What are some non-coding roles that a developer can easily switch to?
#5Re: Ask HN: What are some non-coding roles that a developer can easily switch to?
#6Re: Ask HN: What are some non-coding roles that a developer can easily switch to?
#7Re: Ask HN: What are some non-coding roles that a developer can easily switch to?
#8Re: Ask HN: What are some non-coding roles that a developer can easily switch to?
#9Process improvement (a ton of overlap between the ideas here and with program from a general systems perspective).
Some management roles (advising at the C-suite level, or running teams but not coding anymore).
Instructor (using expertise to teach within your current org or at schools or professional training companies).
Technical writer (if you have the writing chops or can develop it).