Head of Business Operations

Take over founder-led operations and build the systems that help us grow.You might be a consultant who moved into a startup, a founder’s associate already running important parts of a business, or an operator who has started building software and automations yourself. You enjoy understanding how a business works, finding what slows it down, and making it work better. You can turn an unclear problem into a practical plan, bring people with you, and build the first solution. We are looking for someone ready to take that ability further: own our operations function, lead a small team, and join the company’s leadership team. About usPlatform Engineering Masters is the company behind platformengineering.org and PlatformCon. We bring together engineers, technology leaders and vendors through our community, conferences, education and Weave Intelligence. As the business grows, the systems behind it need to grow too: how we deliver for customers, run events, produce content, understand performance and share information across teams. Our co-founder, Christoph currently leads operations. You will work closely with him during the handover, then take responsibility for running and developing the function independently. You will report to Luca, our Managing Director. The challengeWe have a working business, an existing operations team and plenty already being built. We also have manual handovers, disconnected information and processes that depend too much on particular people. Your job is to decide what needs attention, understand the business problem behind each request, and lead the work through to a solution people actually use. Some of the questions you will tackle: How do we turn a customer commitment into a reliable delivery process across sales, content and events? How do we give teams trustworthy information about what is working and where to focus? How do we make recurring work, such as publishing a webinar or delivering a sponsored asset, easy to run consistently? Which problems need custom software, which need better use of existing tools, and which simply need a clearer process? How do we keep improving our systems without making the business dependent on their original builders? What you will ownThe operations roadmap. Work directly with Sales, Growth, Content and Events to understand their needs. Prioritize by business impact, challenge requests where necessary, and make trade-offs explicit, including when requests come from founders. A small, growing team. You will manage our existing revenue operations and systems engineering specialists from the start, and help recruit and develop additional content/design and growth operations capacity. Hands-on delivery. Prototype, write code, connect systems and build automations yourself when that is the fastest way to make progress. Give your team clear direction and space to own delivery. Systems that last. Make sure critical workflows have clear ownership, useful documentation and sensible standards for reliability, access and maintenance. Adoption and results. Work with business teams until the solution is part of their everyday work. Judge success by better delivery, useful information and time saved. Your remit is the operational systems supporting the business. Functional leaders own their commercial, editorial and event outcomes; you work with them to make those outcomes easier to achieve. What you will bringStructured problem-solving and strong communication. You can understand an internal customer’s needs, question assumptions and explain a recommendation clearly. Consulting or similar client-facing experience would be useful. Evidence that you build. You have used code, APIs, automation or AI tools to solve real problems. You can walk us through what you built, why you chose that approach and what happened when people used it. Commercial judgment. You connect operational improvements to revenue, delivery quality, cost or capacity. Ownership in an ambigu