The purpose of this thread is to make a community effort to track the postings of employment offers at GOG, so we as a community can rate their metrics against the allegedly hired and/or missing staffing.


As of Q3, 2023:
Open:

Game Releases (1)
Junior Product Specialist
Brand, PR & Communication (1)
‌
NEW
(Senior) Community Management Specialist

If it weren't such a horrible site, I'd be curious to see what (ex) GOG employees say about the company on assdoor.

NEW LISTING NOTICED ON 2023-08-24

GOG is hiring a Head of IT.

Oh dear.

LISTING REMOVED FOR:

(Senior) Community Management Specialist as of 2023-09-05, or sooner.

Hooray?

NEW LISTING NOTICED: 2023-09-08

https://www.gog.com/en/work/brand-pr-communication-pr-communications-lead

Head of PR and Communications.

This one is a regular leave/join position, make of that as you might.

2023-09-17:

New/Changed:
https://www.gog.com/en/work/it-security-head-of-core-platform-devops-sre (This is a useless job phrasing, and seems to have just piled more duties on to the previous "head of IT" listing.

Anyone who had "core platform" on their buzzword bingo may mark it off.

https://www.gog.com/en/work/sales-marketing-liveops-specialist (So is this.)

Remains listed:

https://www.gog.com/en/work/game-releases-junior-product-specialist


https://www.gog.com/en/work/brand-pr-communication-pr-communications-lead

2023-09-21
New/Changed:

https://www.gog.com/en/work/game-releases-technical-producer-reverse-engineer

No longer content with a junior product specialist, the previous listing has probably been upgraded to sound more fanciful.

All other titles/openings appear unchanged.

2023-09-28:

New Listing:

https://www.gog.com/en/work/engineering-devops-engineer

It almost seems as if GOG is recycling their entire tech team. Ah, to be a fly on the wall.

Depends what you are migrating. Stateless applications that rely on remote components for their state make sense, but unless someone else operating your kubernetes for you, you need to be mindful of stateful workloads.

Everyone loves to be a consumer of kubernetes, but the reverse of that medal is that someone needs to operate it. Underneath the hood, kubernetes is an extremely complex very fast-moving platform that is not trivial at all to operate, especially for upgrades.

It is a lot easier if you can just throwaway an old cluster and reprovision a new one which is very hard to do if you have stateful hard to move components living in it.

Here, we run the bulk of our applications (that interact with a remote store) in kubernetes, but we certainly don't run our databases or finicky services that don't behave in a cloudish way at all in kubernetes.

Also, btw, your kubernetes is very likely to be running in VMs so technically you are not getting rid of VMs most of the time, you are just abstracting them away from something you have to manage directly when tackling your application workloads ;). It doesn't have to be, but for practical reasons (because it is just a lot easier to manage with a more modern operational workflow this way and also to segregate for security and stability reasons while not incurring the cost of dedicated hardware), your containerization and container orchestration layer sits on top of a virtualisation layer most of the time.

Well, they said major changes were coming, but as is typical of these promises, they tend to get outshown by small indie devteams of around 1.

Just that one image alone has told me more about what's coming up for Stardew Valley than I've ever been able to ascertain for GOG.

Yeah -- what I'm getting at is that GOG's legacy software probably isn't the nice kind of stateless applications that make this easy. Juuuust a hunch, you know.

For sure.

I have some experience being a solo dev, a small company dev, and a corporate dev...

I not exactly sold on the idea of fabled "10X developers" but I sure as hell do believe in 0.1x work environments, they are everywhere. Corporate bullshit, micromanagement, lack of ownership and such are an incredibly easy way to make progress grind to a halt. Add a critically important pile of legacy software to the soup and you can have tons of people working hard achieving practically nothing at all.

A solo dev, by contrast, can be the master of their universe. They know exactly what they are up against, where they want to be, and how to get there. And when it turns out they don't, they can change their approach and means and goals on a whim, because they are only accountable to themselves. If they feel there's a better way: just go that way, no need to ask anyone, no need to bring it up with TPOs, managers, whatever.. no arguing, no explaining the situation, no communication overhead, no waiting for a green light and context switching to other tasks/projects... Just go the way you want to and do what you feel is best.

This is why indie devs can kick ass while AAAs are churning out more of the same that is easy to parallelize.. huge open worlds with new assets in ever higher resolution, disconnected errand boy side quests, etc.

2023-10-05: New/Updated:

https://www.gog.com/en/work/engineering-senior-cloud-infrastructure-engineer

Well, it's obviously in line with all the others

Removed: Technical Producer/Reverse Engineer.

Filled? Doubtful. The page is still there, the apply button still works. The form still works.

11-10-2023:

Delisted: LiveOps Specialist. Even the posting has been removed.