Principal Backend Engineer

The systems thinker

The one who sees failure modes six months before they happen. Who designs for scale before scale is real. Who knows the difference between a decision that is reversible and one that is not, and treats them accordingly. You might be a staff engineer at a growth-stage company. You might be a principal at a larger tech firm who has been quietly building the infrastructure others will depend on for years. There are engineers who built the core banking layer at Monzo, the dispatch system at Deliveroo, the data pipelines that now feel inevitable, who started exactly where you are: Staring at a hard problem with no playbook and real consequences. We do not care about the title. We care about whether you can design a backend system from first principles, defend every trade-off under pressure, and own the outcome when the requirements change at 11pm on a Thursday.