Engineering leadership & technical direction
- Own the technical direction of AppFox’s products and the new application (architecture, standards and tooling) and evolve them as the business and the technology landscape move.
- Bring breadth. Challenge how things are done today, introduce modern approaches and managed services where they earn their place, and make sure decisions are made on merit rather than habit.
- Hold the quality bar high. Protect and extend the team’s DORA high-performing practices (CI/CD, frequent small releases, strong review and testing discipline) without rebuilding what already works.
- Own delivery: planning, prioritisation and predictable shipping, in close partnership with Product.
- Be accountable for security, privacy and quality across the engineering org.
- Lead, coach and grow a team of 13 engineers, including two team leads and a layer of lead engineers.
- Develop people deliberately, especially emerging leaders, creating space for them to grow rather than directing every outcome.
- Own the people side fully: performance, development, hiring and the difficult conversations.
- Build a culture of curiosity and outward-looking engineering, including industry awareness, meetups, new ideas brought in from outside.
- Partner closely with the Head of Product. Bring engineering reasoning to the table early and in the open, so decisions are made with shared understanding.
- Shape technical strategy and the resourcing of the initiatives that matter most, and advise on what’s feasible, what it costs, and where technical investment pays back commercially.
- Hold the senior relationships the role needs, across the business, and with Atlassian and monday.com on ecosystem direction.
Where AI changes everything
This is the part we care most about, and it’s why this role looks different from the one we’d have written even a year ago. It comes in two halves, and we need both.AI in how we build. The engineers who thrive over the next few years won’t treat AI as a novelty. They’ll use it as a force multiplier, and bring the rest of the team with them. You’ll set the standard: AI coding assistants and agentic development tooling (Claude Code, Cursor and the like) used daily and used well; AI-assisted review, testing and the automation of routine engineering toil; small agentic workflows that take repetitive work off the team. At a higher level, you will consider how AI can be used in identifying and remediating bottlenecks, and project management. The playbook is still being written, and we want the person driving it, not waiting for it.
AI in what we build. Our products help teams govern, approve, optimise and manage content across Confluence, Jira, Miro and monday.com, and AI changes what those apps can do for customers. You’ll spot where AI adds genuine value across the portfolio - and, just as importantly, where it doesn’t, and lead the team to ship AI- and LLM-powered features that hold up in production: sound on evaluation, cost, latency and safety, not just impressive in a demo. You’ll also consider how external AI agents will affect our products and how the products should interact with them. Having built AI features yourself, or led teams that have, matters here.
We don’t expect you to have every answer. We expect you to set the direction.