Golang jobs: where can you search for open positions

Adrian B.G. - Sep 1 '18 - - Dev Community

Hello,

I am currently researching the market and I am gathering a list of bookmarks about Go. I thought it will be nice to share them with the community, and find out about other ones as well.

gopher

Spoiler alert, there are not many openings for Go (I estimate around few hundreds around the globe, but mostly in the US), but the numbers are increasing each month.

The order of resources is random, I included all the websites in which you can find at least 5-10 positions with a clear tag (usually Go doesn't work), and they are not local (only for one country).

Other problem when searching on general websites (like linkedin) is that you will find many positive-negative openings that wrote ".... development experience in one or more languages: Java, Go, ...", but the position is definitely not on Go.

Other issue is that the recruiters do not use proper tags for their openings and the tag #golang is useless.

Bottom line is that is very hard to scoop the Golang specific positions, the language name and the HR is making it more difficult, and dedicated websites are a blessing for the community.

Sidenote, here is the "official" list of the companies that uses Go, usually in a small extent.

Go(lang) dedicated websites

golangprojects.com
welovegolang.com
chat- the channel #jobs on Gophers slack community
golang.cafe
forum.golangbridge.org - jobs
golangjob.xyz

Tip: these websites are not updated so often, check the date and if the position is still available before reading all about it!

Others

stackoverflow jobs
angel list - startups, you have to be logged in
glassdoor
indeed
remoteok.io
goremote.io remote jobs for all languages
golang.works-hub ~AI based
fullstackjob.com/jobs/go--developer-jobs multi-language positions
cybercoders

If you know more resources please put them in comments, I will try to update the article each week or so with your URLs.

Thanks! See you in the #cloud!

Last update: 19 jul 2019

. . . . . . . . . . . . . . .