I rarely see Go specific job positions. Its usually companies tacking it on the end of a large list of random unrelated programming languages that qualify them for the job so their company appears relevant.
Go is really bad for research and development tasks. If i want to write a program and test out some API endpoints every single piece of code has to be used in my script. I can’t test things out without getting errors everywhere. I cant run half of my code by commenting stuff out. I have to manually nitpick and send everything to the _ variable. This kind of thing probably works great for Google’s gigantic 20,000 developer communist regime, but for the average developer at X company its just annoying.
The second worst part of Go is the Go community that thinks godoc is enough documentation.
Most repos have a completely empty GitHub wiki page, no getting started code besides maybe a useless hello world message.
Here is an example https://github.com/gdamore/tcell/
To understand how to use a library like this, you need to probably start looking at the main method, which isn’t named main, so you need to find it first. Then trace step by step every function call through every file to determine which structs and functions you need to use to put together a coherent and well thought out application. This will take hours.
I really love go but there are a lot of trade offs that are superficial limitations and they make alternative programming languages more desirable.