Playson logo

Playson

More roles at Playson

Technical Program Manager

Region Restricted

Remote work allowed only within certain countries or regions.

Europe

Employer listed it 6 months ago · Added 2 months ago

Been open since 6 months ago. Long-running listings are sometimes left up after the role is filled.

Salary

Not stated

Location

Europe

Timezone

CET ±2

Contract

Full-time

Experience

Mid

Category

Software

The employer did not publish a salary, and we have too few comparable roles to estimate one.

What the advert says

Quoted word for word from the employer's advert. Where it says nothing, we say so.

Working hours
Not mentioned in the advert
Where you can work from
Location eligibility not confirmed
Contract
Not mentioned in the advert
Experience asked for
Not mentioned in the advert
Pay
Competitive Salary

Remote flexibility

Region Restricted

Remote work is allowed, but only for candidates based in Europe.

What the employer says

  • Source listing states candidate location: "European Union, Remote"

What Nomaders makes of it

  • Applications outside the listed area are usually rejected
  • Timezone overlap with the listed area is often expected

The quotes above are the employer's own words; the reading is ours. Always check the original listing and employment terms before working from another country.

Before you apply

Questions worth asking: Nomaders interpretation

  • The advert does not say where you can be based. Ask which countries they can legally employ or contract you from.
  • The advert does not say whether this is employment or a contractor arrangement. Ask, as it affects tax and benefits.

Produced automatically from this advert's text; not reviewed by a person. The employer's own page is the final word.

About the role

About the role

We're looking for someone who owns delivery - not tracks it, not reports it, owns it.

You'll be responsible for a specific area: games, features, or platform work. From the first conversation about a requirement through to production - you're on the hook for the whole thing.

This isn’t a coordination-only role. We need someone with previous hands-on software engineering, DevOps, release engineering, or similar technical experience who can actively improve and automate the way software is built, tested, and released.

You set the timeline, track it, and communicate changes before people start asking questions. If there's a blocker, you've already seen it. If a release isn't ready, you say so - clearly and early.

You'll look at how work flows through your area and fix what's broken. Not just follow whatever process exists. You'll design something that actually works, iterate on it, and make it better over time.

A key part of the role will be identifying manual steps, bottlenecks, and failure points in development and release workflows, and then building practical automation to remove them. This may include improving CI/CD pipelines, automating release checks, connecting tools through APIs, and developing scripts or lightweight internal solutions.

Quality is yours too. Not QA's problem alone, not the tech lead's problem. You own release readiness: is it tested, is it documented, does anyone know the operational risk. If the answer is no, it doesn't ship.

You'll work closely with product, engineering, QA, and client-facing teams, keep them aligned, and report directly to the VP of Delivery. What we expect from you

First 30 days

Understand how delivery actually works in your area - not how it should work, how it actually works

Map where work gets stuck, what the recurring blockers are, and who the key people are

Meet everyone who matters: product owners, tech leads, QA, release managers, client teams

Write up what you found and share it with the VP of Delivery

First 60 days

Take ownership of delivery tracking for your area

Pick the biggest workflow problem you found and start fixing it

Show you can catch a blocker before it causes a delay - at least twice

First 90 days

Own and communicate a delivery forecast that stakeholders actually trust

Ship at least one release with no last-minute surprises - quality gates passed, documentation done, everyone aligned

Present your view on how delivery should work in your area going forward

What we're looking for

3+ years in an engineering delivery, software delivery leadership, or similar role where you owned outcomes, not just process

Requirements

The employer hasn't listed requirements separately, they're described in the role summary above and on the original listing.

Benefits

  • ·Competitive Salary
  • ·Quarterly Bonuses
  • ·Unlimited Paid Time Off
  • ·Unlimited Paid Sick Leave
  • ·Remote & Flexible Working

How to apply

  1. 1Check the flexibility label above, region restricted, matches where you plan to live and work.
  2. 2Tailor your CV to the role at Playson, mentioning your remote working experience and working hours (CET ±2).
  3. 3Apply directly on the employer's careers page using the button below. Nomaders never handles your application.

Found 2mo ago. Last checked 17 Nov. Always confirm the details on the original posting, salary and location can change after publication.

Listing sourced from Company boards.

Similar roles

Other open software roles with comparable remote rules.

Browse all open roles

Pay not stated · You'll be taken to the employer's careers page.