About the role
As a Full Stack Engineer (Frontend Focus), you will own the customer-facing surfaces that sit at the heart of Fable's product. Fable helps companies manage human risk – using signals intelligence from customer integrations to build risk profiles of employees and target behavioural interventions accordingly. This role sits at the delivery end of that pipeline: the interfaces through which those interventions actually reach people, spanning a front end application hosting video briefings and compliance training modules, slideware, and real-time notifications across Slack and Google Chat.
You will spend roughly 70% of your time on the front end and 30% on the backend – but that split reflects emphasis, not a hard boundary. Fable's compliance training product is a good illustration of what this means in practice: content is served from the backend, assembled from JSON modules, and rendered through the Puck editor on the front end. Owning that kind of feature requires you to hold both sides of the stack in your head at once, and to have clear opinions about how the two should interact. You will help evolve the GraphQL schema that sits between the front and back end, keeping it backwards-compatible as the product grows, and there is meaningful work to be done improving data loading efficiency across the stack.
Note: this is not a platform role, a design systems role, or a front end infrastructure role. If you are drawn to abstraction layers, component libraries, and developer tooling over shipping things that land in front of real users, this is probably not the right fit.
With only one product manager across the entire team, engineering and product thinking are deeply intertwined here. You will be expected to understand not just how to build something, but why it is worth building and what problem it solves for the customer. Beyond your own work, you will help raise the front end bar across the team through code reviews, shared standards, and mentorship as Fable scales. The engineers who thrive here are as comfortable asking "should we build this?" as they are asking "how do we build this?"