Say you write Go and you want your next job to be a Go job. The obvious move is to search for "Go" or "Golang" and read what comes back.
Across the tech companies we track, a search that only reads job titles finds about 60 roles. The number of open roles that name Go somewhere in the post is 2,190.
That gap is the whole story of this post, so it is worth being careful about what sits inside it. Some of it is great news for Go developers. Some of it is a menu of five languages where Go happens to be item four.
All figures below were measured on September 17, 2026, across 11,688 open tech roles at 791 companies, counted as distinct roles (one role posted in twelve places counts once).
Go is the second most named language on the board
Here is how often each language shows up in the stack of an open role:
| Language | Open roles naming it | Companies |
|---|---|---|
| Python | 4,798 | 529 |
| Go | 2,190 | 341 |
| TypeScript | 1,798 | 443 |
| Java | 1,514 | 279 |
| JavaScript | 1,143 | 338 |
| C++ | 980 | 167 |
| Rust | 768 | 154 |
Go is named in almost one open tech role in five. That puts it ahead of TypeScript, even though more companies use TypeScript. Go companies simply hire more Go people each: about six roles per company against four for TypeScript.
If you have been told Go is a niche bet, the board disagrees.
Where the rest of them live
Very few companies put Go in the job title (and one of the handful of title matches is a designer role on Pokémon GO, which our search dutifully counted). Go lives in the body of the post, in the stack section, usually next to other languages.
So we counted how many programming languages each Go role names alongside it:
233 roles name Go and no other language.
1,171 roles name Go plus one or two others.
786 roles name four or more languages in total.
That last group is where you find the laundry lists. A services architect post whose stack reads Java, Python, Ruby, Go, Node.js, PHP and .NET is probably not the Go job you had in mind. About 140 of the Go roles are titled as sales, support, solutions or partner roles, which is a very different job from writing Go all day.
For some newer roles we can also separate the core stack of the job from everything else the post mentions. Of the 661 Go roles where that split exists, Go sat in the core in 445 of them. Two in three. That is a small sample and it skews toward recently posted roles, but it is the closest thing we have to "how often is Go the actual job", and the answer is "most of the time, not always".
What Go comes with
Two thirds of Go roles also name Python (1,476 of them). Be careful reading that one: a lot of those are "Go or Python" posts, and a tag list cannot tell an "and" from an "or".
The pairing that means more is infrastructure:
Kubernetes in 1,103 Go roles, half of them
AWS in 899
Terraform in 495
Prometheus and Grafana in about 255 each
Go roles lean hard toward infrastructure, platform and backend work. If you know Go and have never touched Kubernetes, that is the adjacent skill the data points at most.
Who is hiring for it
341 companies name Go in at least one open role. The twelve with the most:
| Company | Go roles |
|---|---|
| Cloudflare | 87 |
| Anduril Industries | 78 |
| Sezzle | 61 |
| Canonical | 52 |
| Nebius | 50 |
| Roblox | 49 |
| Datadog | 44 |
| OpenAI | 43 |
| Snowflake | 43 |
| MongoDB | 40 |
| Grafana Labs | 40 |
| Coinbase | 39 |
Those twelve hold 626 roles, 29% of all Go roles. The other 71% is spread across 329 companies, and about 200 of those have only one to three Go roles open.
The less fun numbers
Seniority first. Of the 2,190 Go roles, 1,444 are senior, 674 are mid-level and 72 are junior. That is 3.3% junior, a little under the 4.3% across all open tech roles. A bit harder than average to enter as a junior, then, but not dramatically.
Remote: 256 Go roles are fully remote. Another 659 are remote but restricted to a country or region, 883 are hybrid and 392 are onsite.
Pay: among Go roles that publish a yearly US dollar band, the median bottom of the band is $170,000 (1,205 roles). Python lands on exactly the same $170,000. Rust ($191,000) and C++ ($190,000) sit higher. So Go is a very good language to be employed in, but the idea that it carries a pay premium over Python does not show up here.
What we would do with this
If Go is your language:
Search by stack, not by title. Every role on remoet.dev/jobs carries its stack, and an agent can filter on it directly (that works without an account now).
Read a post that lists five languages as "one of these", not "all of these". If you have any of them and the rest of the role fits, apply.
Treat the sales, support and solutions roles as their own category. They name Go for a different reason than a platform team does.
If you are choosing what to learn next, look at Kubernetes before a second language.
Where this data is soft
The stack on each role is extracted from the post text by a model, so it inherits two limits. It cannot tell "Go and Python" from "Go or Python", and it sometimes picks up a company's wider stack that the post mentions in passing. We also found a couple of dozen roles with Go in the title and no Go tag, so the extraction misses some too. The counts are a good map, not a census.
The title count is approximate for a sillier reason: "Go-to-market" is a very popular job title, and we had to filter those out.
Salaries only cover roles that publish a band, and we used the bottom of each band, so every figure understates the band itself.
And these are distinct roles on a single day. On the same day we fixed a bug that had been splitting some roles into many, so if you compare this against older posts of ours, some counts moved for that reason and not because the market did.
If you write Go for a living and this does not match what you are seeing out there, we would like to hear it. Come argue with us in Discord.
