Project Manager

Key responsibilities

Own the delivery plan

One delivery plan per product, internal or customised, covering content, design and

engineering, that PM, engineering and leadership all read from.

Sequence hand-offs between streams so they are planned, not discovered.

Track client-committed dates (CRs, pilots, renewals) and coordinate release calendars so

QA, DevOps and client commitments do not collide.

Make status honest and early

Weekly delivery report and RAID log, published on time, with accurate sprint status in

Jira for both clusters.

Estimate-vs-actual and on-time percentage tracked per cluster; slippage flagged the week

it becomes likely. A surprise in the metrics review is a PM miss.

Prepare and run the weekly P0 review: every item owned and dated, blockers chased

between reviews.

Be the single point of contact

Product, CS, BD and leadership route delivery queries and escalations to the PM, not the

EMs.

Triage each escalation: confirm impact, route to the right team, set a response date, close

the loop, and log it so recurring issues surface.

Escalate to the CTO when a commitment cannot be met and a trade-off is needed.

Enable teams on what ships

Run onboarding for internal teams when a new platform feature lands; keep release notes

usable without an engineer present.

Track adoption and feed gaps back to PM and engineering.

Keep the process light and consistent

Same definition of done, sprint rituals and ticket hygiene across both clusters.

Templatise recurring artefacts (report, RAID log, release checklist) so they run

themselves; supply cycle-time and on-time data to the quality diagnostic.

Skills and experience

Required

3 to 6 years in software delivery, of which at least 2 years coordinating multiple

engineering teams (PM, scrum master, delivery lead or technical programme roles).

Working fluency in Jira: boards, sprints, dashboards, JQL, and enough structure to keep

two clusters consistent.

Comfortable reading engineering conversations: understands what a merge request, a

migration, a flaky test or a rollback means for a date.

Writes clearly and briefly. A weekly report that nobody reads is a failure, so the bar is

plain language and one screen.

Holds people to commitments without escalating everything; knows when to chase and

when to bring the CTO in.

Comfortable with data: builds and maintains simple tracking sheets, reads trends, and

does not report a number without checking it.

Preferred

Experience in a SaaS or product company shipping to enterprise clients with contractual

dates.

Exposure to DORA-style metrics (lead time, deployment frequency, change failure rate)

and how to collect them.

Familiarity with GitLab CI or similar pipelines, enough to read a release status.

Prior experience running a RAID log or risk register in a live programme.

Any client-facing or account-coordination experience: the role increasingly fronts CR and

pilot timelines to clients.

Not required

A PMP or Scrum certification. Useful, not decisive.

Ability to write code. The role needs technical literacy, not technical output.