Senior Software Engineer (front-end focused)

# **Department:** Technology **Location:** Home based, UK (with occasional travel to our London office) **Reports to**: Head of Engineering **Hours**: 37.5 per week **Salary**: (Depending on experience) Role Overview This is a significant new role. We are building a product engineering capability that did not previously exist at Cambridge Spark: engineers who own business outcomes, not just feature backlogs, and who work directly with stakeholders to understand problems rather than waiting for specifications to arrive. As a Senior Software Engineer, you will be a founding member of our Learner Experience pod: a small, autonomous team responsible for the quality, usability, and impact ofhttp://edukate.ai for the people learning through it. You will work across the full stack, from understanding what learners and curriculum teams actually need, through to shipping and iterating on the solutions you help shape. You will be a multiplier for the engineers around you: raising the bar on how the team thinks about problems, not just how it solves them. This role reports to the Head of Engineering. You will carry seniority in a team that we’re deliberately rebuilding around product ownership and outcome focus. ## Key Responsibilities - Own end-to-end delivery within the Learner Experience pod: from discovery and problem framing through to production, iteration, and outcome measurement - Work directly with internal stakeholders — curriculum, operations, delivery — to understand problems at their root, not just their surface symptoms - Shape solutions collaboratively: contribute to proposals, decision records, and discovery conversations, not just pull requests - Bring an AI-first approach to your work: use AI tooling actively in prototyping, agentic coding, and accelerating delivery — and help the wider team develop the same habits - Hold a high engineering standard across the pod: TDD, code review discipline, and a genuine commitment to quality are non-negotiable here - Coach and support less experienced engineers in the pod, sharing your experience of what good looks like in a product engineering context - Contribute to the evolution of our engineering practices as the pod model matures ## Candidate Specification ### Technical - Front-end expertise, including UX design: we want to make our product delight customers - Comfort owning the full delivery lifecycle: problem framing, solution design, production, and iteration - Strong engineering fundamentals: test-driven development, code review culture, and a demonstrable commitment to quality - Active engagement with AI-assisted development: prototyping, agentic coding, and using AI tooling as an accelerant rather than a novelty - Experience with edtech, regulated industries, or other complex domains is a plus; the ability to absorb a new domain quickly is essential - Professional experience in our stack (React / Vue) is a bonus, but not essential - Back-end engineering knowledge is a nice-to-have for this role ### Stakeholder and Communication - Demonstrated experience working directly with non-technical stakeholders to shape requirements — through product engineering, professional services, client-facing delivery, or similar - Strong written communication: you can write a clear proposal, a concise technical decision record, or a stakeholder update that lands without needing translation - Comfortable running or contributing to discovery conversations, not just delivering code once the brief is written ### Ways of Working - Outcome ownership over feature delivery. You question whether the proposed solution is the right one, not just whether you can build it. - Comfortable with ambiguity. Small pods mean limited process overhead. You make good decisions with incomplete information and know when to escalate versus when to proceed. - AI-first mindset. You are not just curious about AI; you actively use it, prototype with it, and bring that practice into the team around you. - Collaboration…