Product Manager – IT & Internal Platforms (100% Remote)

What this role is
This is a role for someone who thinks like an engineer but operates like a product owner. You'll report directly to the CTO and be responsible for the internal systems and tools the rest of the business depends on — owning what gets built, why, and making sure it actually works for the people using it.

You won't be handed specs. You'll talk to the teams that rely on these systems, understand their problems better than they can articulate them, and direct the engineering work that solves those problems. The trust you earn won't come from writing every line of code — it'll come from consistently asking the right questions, understanding the landscape deeply enough to make good calls, and following through until things actually work.

You'll also be the connective tissue between a capable, independent engineering team and the rest of the business. The team doesn't need someone looking over their shoulder. They need someone who handles the noise, clears the path, and brings enough technical understanding to have real conversations about architecture, tradeoffs, and direction.

What you'll actually do

• Own internal products end-to-end (~30%) You'll take ownership of internal IT products and systems — from identifying the real problem, through to directing the solution, shipping it, and iterating. You make the calls on what to build and how to approach it. You work with the engineering team to shape architecture and implementation, bringing product clarity so they can focus on execution.
  
• Solve problems and build things (~25%) You have the technical foundation to dig into issues, understand systems, and figure out what's going wrong. When something breaks or underperforms, you can get to the root of it — whether that means jumping into the problem yourself or knowing exactly what to ask. You'll also have the freedom to build smaller internal tools on your own — if you see something that would make people's lives easier or a process that could be smarter, you can go ahead and make it. That kind of initiative is welcomed here, not gatekept.
  
• Keep delivery moving (~15%) We use an internal AI assistant for project logging and prioritisation, so you're not buried in admin. Your job is to make sure things actually get done — following through on commitments, resolving priority conflicts between departments, and keeping momentum without creating overhead.
  
• Run IT operations (~15%) You're the escalation point when things go wrong across the company. Domain renewals, certificates, broken integrations, system incidents — the unglamorous but critical work that keeps everything running. You balance putting out fires with making sure they don't start again.
  
• Be the bridge (~15%) You sit between a strong engineering team and every other department in the business. IT touches everything, which means people will come to you with problems framed in business language, and you'll need to translate that into something the team can act on — and vice versa. You're the person department heads call when they need something from IT, and the person the engineering team trusts to protect their focus.

Who this is for

• You've spent time building software — enough to understand systems, ask sharp technical questions, and hold your own in a conversation about architecture or tradeoffs. But what excites you most isn't writing code all day. It's figuring out what should exist, why it matters, and making sure it gets built well.
  
• You're looking for a role where you can take ownership of products at a level of complexity and impact you haven't had before — and grow into it.
  
• You might not have managed a team formally, but you're someone people naturally turn to. You know how to give others space to do their best work while making sure the right things are getting built.
  

On learning and tooling

The way software gets built is changing fast. We've been leaning into that — for example, we built an end-to-end AI customer support agent before most companies were even considering it. Not because we had a specialist team for it, but because someone was curious enough to explore what was possible and capable enough to make it real.

We don't expect you to walk in as an expert in every tool or method we use. One of our strongest engineers joined without fully realising what modern tooling could do — and became one of our most valuable people once he saw the possibilities and ran with them. What matters is that you're the kind of person who gets genuinely excited when you discover a better way to do something, and you go and try it.

If that sounds like you, you'll find plenty of room here to explore, learn, and apply what you discover.

What we'd like you to bring

• 5+ years in a technical role where you were close to how software gets built — whether as a developer, technical lead, or a product manager with real engineering fluency
  
• Experience owning outcomes, not just tasks — you've been responsible for things that people depended on
  
• Comfort with ambiguity and the ability to figure things out without waiting for perfect information
  
• Strong communication — you can work with department leaders, translate between technical and non-technical worlds, and earn trust across both
  
• Enough technical depth to have meaningful conversations about systems, architecture, and tradeoffs — even if you're not the one implementing every solution
  

Technical foundation
We care about whether you understand how software and systems work — not whether you've used our specific stack. If you've written code in any language, built or maintained something real, or been close enough to the process to understand how things fit together, that's the foundation that matters. The specific language or framework is less important than it's ever been. With the tools and resources available today, anyone with strong fundamentals can pick up a new stack quickly — and we've seen that play out on our team firsthand.

For context, our environment includes PHP (Laravel), Vue.js, Node.js, and Bun on the application side, with AWS infrastructure across services like EC2, Elastic Beanstalk, and Kinesis. Some projects touch data visualisation tools like Tableau and DOMO. But we mention these so you know what you'd be walking into, not because we expect you to know them already.

What we really value is someone who understands the fundamentals — how systems talk to each other, why something might be slow or breaking, what questions to ask when evaluating an approach. That kind of thinking transfers across any language or platform.