Principal Platform Engineer

You will own the architecture of client platforms end to end: the design conversation, the code, the production cutover, and the fortnight afterwards when it is carrying real traffic. What the work looks like Two weeks mapping an existing system with the client's engineers, then a written architecture and risk assessment they keep whether or not they continue with us. After that, a vertical slice in their staging environment by week four — running code with measured latency, not a diagram. What we expect Ten years or more building distributed systems, and at least one of them you were on call for. Deep Kubernetes and infrastructure-as-code. The judgement to know when the answer is "do not build this". Direct, unhedged communication with people who are not engineers. What we do not do There is no bench and no delivery-manager layer. You talk to the client yourself, you write the code yourself, and nobody reassigns your account to somebody junior after the contract is signed. If that sounds like more exposure than you want, this is not the right firm.