This is solid advice. In large, technical companies you'd be surprised at the number of technical writers that aren't actually technical. Having someone that acts as a source writer, rather than as an editor for developers that are quickly rushing past the documentation requirements is a game-changer. The best technical writers I've worked with were always folks who understood programming and could write the docs from experience.

I also find most technical documentation teams to be a lot more chill and flexible. Most of them have excellent team-minded work styles.

How to get started in this field? You can't throw a stone without hitting an OSS project that wouldn't want help with its docs. It's a great way to build up a network and some Github activity.