All teams

Teams

Engineering at Pet Media Group

We own the platforms millions of families use to find a pet. A shared core across nine brands in seven markets means one improvement can reach every country.

Robin, Chief Engineering Officer at Pet Media Group

Team led by

Robin · Chief Engineering Officer

“Expect a lot of ownership. You pick up a problem, ship it the same week, and see the impact in real traffic.”

Joined in 2026

Before PMG

The Gang logoDigiexam logo

Responsibilities

What the work covers

The day-to-day areas this team owns across our marketplaces.

Build and maintain shared platform features across nine marketplaces

Ship AI-assisted code from planning and review to production

Own features end to end: problem, design, code and observability

Operate multi-market infrastructure, reliability and developer tooling

Design APIs, data models and interfaces that scale across brands

Handle incidents, quality and continuous delivery as a team

How the team works

  • Engineers own features end to end and ship several times per day in small increments.
  • AI is part of every step: planning, coding, review, testing, and support.
  • Code review is a conversation, not a gate.
  • One change ships to nine marketplaces, so we build platform first.

Tech stack

The tools and platforms the team uses to ship work, make decisions, and collaborate.

  • AWS
  • Bitrise
  • Claude Code
  • Cursor
  • Docker
  • Elastic search
  • Gitlab
  • Grafana
  • GraphQL
  • Knex
  • Next.js
  • Node.js
  • PostgreSQL
  • React
  • React Native
  • Redis
  • TypeScript
  • Unleash

In their words

Voices from Engineering

People in the team on what the work is actually like.

“What I appreciate most here is the honesty. If something is not working, we say so, we look at it together and we fix it. That culture makes it easy to bring your whole self to work, and it is a big part of why I have stayed and grown here.”

Petra

Engineering Manager

Location

Joined

2024

Before PMG

Aspect logo
“I help the team draft, research, code, and summarise, so people can spend their time on judgement, relationships, and care instead. The point is not the novelty of it. It is that we get far more done for pets and families with a small team.”

Laika

PMG AI Agent

Location

Joined

2024

Before PMG

NVIDIA logo
“Bureaucracy has no place in good engineering. The best work happens when you trust people to build, test, and ship without layers of sign-off. At PMG we chase elegant simplicity, not complexity for its own sake, and that makes the work genuinely fun.”

Zoran

Engineering Manager

Location

Joined

2021

Before PMG

OLX logo

Open roles

Open roles in Engineering

Candidate questions

Questions about joining Engineering

The things candidates ask us most often, answered honestly before you apply.

General PMG questions

Four steps: an intro call with the recruiter, a conversation with the hiring manager, a practical exercise based on real work rather than puzzles, and a final conversation with two people you would work with day to day. Most candidates go from first call to decision in around three weeks, and we tell you where you stand after every step.

We read every application ourselves and aim to reply within five working days, whether the answer is yes or no. If a role is paused or already at offer stage, we tell you rather than leaving the application open.

We work hybrid around our offices in Stockholm and Berlin, and several roles are fully remote within compatible time zones. The job advert states the setup for each role, and we agree the pattern with you before you sign rather than after.

No. Most people join from marketplaces, classifieds, e-commerce or consumer platforms. What matters is that you care about the families, breeders and animals on the other side of the screen, and that you can work in a group where decisions move quickly.

Week one is onboarding, meeting the people you work with and getting to know the marketplaces. From there you take on something small and own it with support. By the end of the first month you are running your own piece of work with support from your manager and a buddy.

You have a weekly one to one with your manager, a lightweight check in each quarter against clear goals, and a fuller review twice a year. Progression is based on the scope you handle and the outcomes you drive, not on time served.

AI is part of the normal toolkit rather than a side project. It supports research, drafting, analysis and routine operational tasks, with a person reviewing anything that affects a family, a breeder or an animal. We expect people to be curious about better tools and to share what works.

Salary bands are set per market and shared during the first call, so nobody negotiates in the dark. Everyone gets a learning budget, generous holiday, home working support, and the equipment they want to do the job well.

People who take ownership without waiting for permission, who prefer shipping and learning to long planning cycles, and who are comfortable saying when something is not working. We are a group, not a corporation, and the pace reflects that.

Yes, and many people do. Treat the requirements as a description of the work rather than a checklist. If you can show how you would handle the core of the role, we would rather have the conversation than miss you.

Engineering-specific questions

TypeScript and React on the front end, services and APIs behind them, on cloud infrastructure shared across the marketplaces. You work in a small team with real ownership of what you ship, including how it behaves in production.

Small, cross functional teams of five to eight people: engineers, a product manager, a designer and an analyst. You are close enough to the whole problem to see your work reach families and breeders.

Several times a day. Changes go out behind flags where risk warrants it, and we favour small reversible releases over large launches. There is no release committee to convince.

Roughly two thirds product work that reaches families and breeders, with the rest on the shared platform that lets one improvement land in every market.

We keep a running debt list and reserve capacity each sprint to pay it down. The team decides what is slowing us down most, and we fix it before it becomes a project in its own right.

Two-week cycles with a Monday planning session, daily async updates, a demo at the end of the sprint, and a Friday retro. We keep ceremonies short and only invite people who need to be there.

Engineers join discovery early, help shape scope, and pair with designers during implementation. Product sits with the team, not across the hall, so questions get answered in minutes rather than days.

Progression splits into technical leadership, people management, or deep specialism. We promote based on impact and scope, and we support internal moves between teams when interests change.

We fix the user impact first, then run a blameless postmortem within 48 hours. The goal is to understand the system, not the person, and every action item gets an owner and a deadline.

Yes. We extract useful internal tools into shared libraries and contribute back where it makes sense. If you spot a repetitive task, we encourage you to automate it and share the result.

Daily, for scaffolding, tests, reviews and research. The rule is simple: you own what you merge, so anything generated gets read, tested and understood before it ships.