Moonpig Technology Podcast · Moonpig Tech Podcast

Episode 31 - Platform Power: How Automation is Shaping Moonpig’s Engineering Culture

·38 min·1 clip

Sam opens the episode with Leon and introduces the guests, Dan and Jake. They frame the topic as process automation and Moonpig's journey with it. Dan starts with his background, from sysadmin work on the company's e-commerce estate to his current site reliability and platform responsibilities. He talks through the mix that comes with the role, including Terraform, code, cost, security monitoring, and on-call support. Jake then introduces himself and explains that he moved from Dan's platform team to the Web Platform team. The discussion shifts to why automation mattered in the first place. Engineers on the platform side were being asked to make small production changes for others, and that created a bottleneck because the knowledge sat with the people doing the work while the permissions sat with the platform team. Instead of keeping that manual, the team looked for a safer way to let engineers act for themselves. The conversation keeps coming back to brief, specific elevation instead of broad standing access. The idea was to let someone do the job they needed to do, then drop back down again. Dan and Jake treat that as a way to shrink blast radius as much as to move faster. They describe it as part of platform maturity, where more engineers work directly in production and the support model has to change with them. Moonpig also gave the team room to experiment, including time to read up on a topic and test small proof of concepts. That space mattered when they tried the escalation bot idea before rolling it out more widely. They talk about that kind of experimentation as normal engineering work, not a luxury. It is close to the familiar idea of protected time for trying new tools and learning what actually works. The episode comes back to the bot's core principle. If engineers need a narrow permission for a narrow task, the platform should make that request easy and make it easy to remove afterward. That keeps control in the right place without slowing everyone down. The conversation also shows how the platform team learns from the way the bot is used. A structured way to escalate and de-escalate access gives the team feedback on how the platform really behaves. The closing exchange lands on one plain idea: platform custodians should not all be standing administrators by default. They should have elevated access when the work calls for it, and only then. The episode ends by tying that back to engineering culture, where better tooling changes how teams work together and how responsibility gets shared.

As heard by us

A practical look at process automation and safer self-service at Moonpig.

Moonpig's engineering culture is framed as practical, with the focus on process automation and the move from sysadmin bottlenecks toward safer self-service.

Read the full review in PlayNext →

Why you'd press play

Want a practical look at process automation, escalation bots, and tighter permission control at Moonpig?

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from Moonpig Technology Podcast