The first engagement was specific and hands-on: prototyping with the advanced AI coding agents, and scaling their database across many nodes. Then the CTO pulled me into something harder: An engineer wasn't delivering, there was no manager in between, and each side felt unheard. I told them plainly whether I thought it was a skills gap or a communication gap, then helped them hire the manager the team had been missing. It was easy for them to trust my judgment on it after I'd earned credibility in the codebase and worked with their team.

Later, someone I had worked with there came back with a scoped question. They were moving their Python and TypeScript SDKs onto a shared Rust core, and wanted a judgment on where the boundary between the two should sit. They engaged me to advise them on making a decision. We set up a working session with their engineers, then I did the analysis. I provided them with a written recommendation that carries the reasoning under each decision, so anyone revisiting one six months later can see what it was weighed against, and a plan that keeps both SDKs shipping while the migration happens.