Engineer · Enterprise capability

A paying customer has already moved whole platform operations teams into one system: dozens of accounts, several business lines, one shared way of working. This role owns the layer that holds that up — accounts and permissions, org structure, org-level sharing and audit.

The requirements come from real customers rather than from us guessing. The role splits into a front-end track and a back-end track; tell us which side you lean towards when you apply.

What you will do

Front-end track:

• The enterprise-side interface: account and permission management, org-level sharing, team dashboards
• Turn a complicated permission model into something an administrator can read and get right — with permissions, an interface done badly is the same as no interface

Back-end track:

• Account provisioning and management, modelling the organisation hierarchy
• Org-level sharing of knowledge and skill libraries: how one person's accumulated work safely becomes the whole team's
• Data isolation and access control

Both tracks:

• Take part in the requirements directly. This line follows what real customers work out, and you will be in the room

What we look for

• Solid engineering fundamentals; code someone else can maintain
• Fluency with tools like Claude Code. A requirement, not a bonus point
• You learn fast. This line keeps moving; the problem a year from now is not today's problem
• Willingness to sit across from the customer. Enterprise capability gets built right only when the requirement is asked for in person
• Front-end: judgement about interaction and information hierarchy, not only implementing someone else's mockup
• Back-end: understanding of where the boundaries of a permission model and data isolation lie, and where shortcuts are not available