- Location
- London, England, United Kingdom · published
- Type
- Full-time
- Department
- Engineering
- Source
- Workable
Description
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.
THIS IS A HYBRID ROLE WITH THREE DAYS IN OUR FARRINGDON, LONDON OFFICE.
Stack: Next.js, React and TypeScript on the front end. Laravel and PHP on the back end. Claude Code throughout.
About Eventogy
Eventogy is the event management platform used by investment banks, corporate banks and law firms to run their events, from partner dinners to 3,000-person conferences. Our clients care about the details: who is invited, who approved it, what they have registered for, and what happens to their data afterwards. Governance is what sets us apart.
We are a small team rebuilding our platform, and we have changed how we build. Features start as working prototypes, become clear specs, and are increasingly built with AI coding agents. We are looking for someone who can do this well.
The role
This is not a front-end role or a back-end role. You will be a product builder: someone who takes a feature from spec to production and owns all of it.
You will usually start from a ticket with a working prototype, acceptance criteria and a suggested approach. A feature often has both a hub ticket and an API ticket, and you will take both. You will question the spec, fill in the gaps, brief and direct Claude Code, review its output critically, test it and ship it.
Your strength will be on the front end, but you will be comfortable in our Laravel API whenever a feature needs it.
What you will do:
- Build features end to end across our Next.js admin hub and attendee websites and our Laravel API
- Turn prototypes and specs into production-quality code, raising gaps and edge cases before you build
- Use AI coding agents as a core part of your workflow, including running work in parallel where it makes sense
- Review agent-written code sceptically, especially around permissions, shared state and data that crosses client boundaries
- Write and maintain tests, and use our automated test suite and seeded test events to check your work
- Ship safely to a live product: non-destructive migrations, feature branches, no surprises for existing clients
- Work closely with product on the why, not just the what