- Where
- London, England, United Kingdom
- Level
- Senior
STRICTLY NO AGENCIES. We are only accepting direct applications for this role. Any unsolicited CVs sent will be treated as a gift and will not be subject to any terms or fees. RECRUITERS: please do not call or email us regarding this role.
HYBRID: THREE DAYS A WEEK IN OUR FARRINGDON, LONDON OFFICE
Stack: Next.js, React and TypeScript on the front end. Laravel and PHP on the back end. A legacy PHP and CodeIgniter platform being modernised alongside it. AWS underneath. Claude Code used throughout engineering.
About Eventogy
Eventogy Ltd is a UK event management SaaS company based in Farringdon, London. Twenty years old, profitable, privately held. Our clients are large international enterprises in regulated sectors: Deutsche Bank, Santander, BNPP, Ford, Kia, Toyota, Linklaters, Clifford Chance and Freshfields among them. The bar for what we ship is set by those customers, not by us.
The role
You will own the engineering team's delivery, every day. What was promised lands, at the standard our clients expect, and problems surface at the start of the week, not the day before a deadline. The work is predominantly on our new platform, built on Next.js and Laravel. Our original PHP and CodeIgniter platform runs alongside it while clients move across.
Engineering is organised into two pods. Each pod is given its own features, epics and technical challenges, and each is led by a hands-on Principal Engineer who reports to you. You drive both pods, and the Principal Engineers are how you do it: each leads their pod technically and is accountable to you for its output. Together you form a small leadership trident, which you head, that owns the technical side of the platform and its delivery: architecture, platform, engineering standards and technical decisions. The Principal Engineers lead technical direction for the areas their pods own and keep both pods building the same way. You set the direction for both pods and the order of ownership and accountability, hold each pod to its output, and make the call when the Principal Engineers cannot agree.
The lines are clear. The CTO sets technology strategy and security, and is ultimately accountable for the platform. The Product Owner owns what gets built. The Delivery Manager owns the plan and its timelines, manages stakeholders, and is the team's voice to the rest of the business. You own the technical delivery behind all of it, and the technical operation of the platform in production. You are the critical path: every date the Delivery Manager communicates is one you are accountable for engineering to hit. You report to the CTO and work directly with the CEO on delivery.
That makes your partnership with the Delivery Manager the centre of the job. You size work with the Product Owner and Delivery Manager before it is committed, so the dates that go out are ones the team can hit. You give the Delivery Manager an honest, early read on progress and risk, so the business hears about a problem while there is still time to act on it. Then you make the dates happen. You will be measured on delivery outcomes.
We work on a simple principle: build it, run it, own it. The engineers who write a feature are the ones who deploy it, support it in production and answer for how it performs. You will embed that across the team, and it starts with you: this role owns the whole of the technical delivery, not just the plan.
This is a hands-on role. Expect to spend 20 to 30 percent of your time writing code: enough to stay credible with the team and close to the codebase, not so much that you disappear into it.
It is not a role for someone who wants to keep a calendar and report status upwards. It is for someone who takes delivery personally: who steps in, unblocks, re-plans and keeps pushing until the work is live.
What you will do
Drive both pods day to day, through the two Principal Engineers. Know where every piece of work stands, and challenge it when a task has taken far longer than it should
Head the…