Product Engineer, Eventogy

• Front end is your home:
• Strong Next.js, React and TypeScript, including routing, rendering and data-fetching patterns
• Good component design and state management, and you care about accessibility
• You build interfaces enterprise users trust: predictable, clear and calm
• Back end does not put you off:
• Confident in an existing Laravel codebase: Eloquent, migrations, repositories, API resources, and feature tests with PHPUnit or Pest
• You understand data modelling well enough to spot when a change will break existing records
• You do not need to be a Laravel expert, but you do need to understand what you have shipped
• You are genuinely good with AI tooling:
• You use Claude Code, or something similar, daily, and you know how to brief it well
• You know where it goes wrong, such as shared state, validation, security boundaries and confident-but-wrong fixes, and you check those areas yourself
• You think like a product person:
• You ask "what happens when...?" before writing code
• You would rather own a whole feature than one slice of it
• You write clearly in pull requests, tickets and questions to product

Desirable

• 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
• 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
• 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
• Stack: Next.js, React and TypeScript on the front end. Laravel and PHP on the back end. Claude Code throughout

• Send a CV plus short answers to two questions:
• Describe something you shipped that you owned end to end. What was hard about it, what did you get wrong, and what would you do differently?
• Where has AI-assisted development made you faster, and where have you seen it make a codebase worse?
• Applications without answers to both will not be reviewed. This is deliberate