Backend Engineer

You will focus on friction points around primarily backend issues for all teams in Engineering (90 Engineers). How should we do inter-service testing? Some teams are using monorepo, others aren’t. How can we bring overall stability up? Generally steering BE in the right direction. In the near future, standardising things across all of Engineering and bringing R&D teams (another 40 Engineers and Researchers) closer. You will have ownership of projects that span quarters, requiring you to have the ability to break a problem down into small steps that can be delivered and validated iteratively. You will evaluate your own work, leveraging our data pipeline and frameworks that we have established to understand the impact your features have on our commercial objectives and pivoting where necessary. You will consider the long-term direction of Engineering, making sure that we are developing the engineering capabilities that will allow us to stay ahead of the challenges we are likely to encounter in 12-18 months' time. You will work end-to-end, from our client application written in React to our monolithic backend written in Python, and lead projects that span across multiple teams.