How much knowledge should a go programmer have in order to be able to find a job?

Question

go

In general, the question is about the technology stack, what is needed, what is not needed, what is urgently needed in the market, what technologies?

Answer 1

After reviewing a bunch of videos from conferences, I noticed one thing ...
Whoever the speaker is (from Yandex, Mail, Badu, etc.), everyone has about the same story:
- We needed to write a (micro) service, we chose GO. Over the weekend, we mastered it and washed down everything we needed, and it has been working in production for a month / half a year / a year.
That is, in fact, not knowledge of GO is needed, but general knowledge of programming.
GO is too young, and so far there is no "stack" that you need to know. Everyone saws as they can and what they can.

Answer 2

You take language too seriously. A programming language is not a human language. He learns quickly. For a programmer, knowing another programming language is nonsense. This is the same elementary base as mastering a blind ten-finger typing method or the ability to do git add, git commit, git push, git pull.
For Go:
Google AppEngine technologies are well described, there are examples (endpoint, queues)
git (basic things)
at least in general terms to know what vendoring is, but it is better to be able to glide/godeps/gb
Gorilla Toolkit (mux, websocket, schema)
RESTful/ RPC
gometalinter, golint
Ability to use a specialized editor or IDE configured for Go. And the ability to customize it.
familiarity with Martini, Revel, etc. getting to know gizmo , go
-micro