> Markdown version of [/jobs/ext/3147810-senior-software-engineer-full-stack](https://www.wearedevelopers.com/jobs/ext/3147810-senior-software-engineer-full-stack). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Senior Software Engineer (Full Stack)

- **Company:** Kitt
- **Location:** London, UK (Remote available)
- **Experience:** Expert
- **Salary:** £74,000.0 - £98,000.0
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), Code Review, Database Schema, PostgreSQL, TypeScript, Web Applications, ReactJS, Graphql, React Native
- **Published:** September 2, 2026
- **Apply:** https://www.adzuna.co.uk/jobs/details/5868923014

## About the Role

* Deep TypeScript: Several years writing production TypeScript across both back end and front end, in codebases you then had to live with. This is the core of the role.

## Description

* Own a product end to end: Take technical ownership of one of our two products, from the database schema up to the interface. You make the architectural calls. The Head of Engineering is a sounding board, not an approver.
 * Build across the whole stack: Ship features that start in Postgres and finish in a React component. A typical piece of work touches the schema, the GraphQL API, the web app, and often the React Native app used by engineers on site.
 * Turn problems into shipped software: Take a problem straight from a customer conversation to production. Shape the scope, decide what to leave out, and cut it into slices that ship in days rather than months.
 * Forward deployment: Spend time on site with customers, suppliers and our own operations teams. Watch the software being used, find the gap between what we built and what they actually need, and close it.
 * Set the standard: Review code properly, mentor the mid-level engineers, and establish the practices that still hold when the team is twice the size.
 * Own it in production: Observability, alerting, and the unglamorous fixes for the code you shipped. We deploy continuously and everyone carries their own work.
 * Bring the two products closer together: There is real work in how the two systems fit. You will help shape that and then do it.