Echoes directory

I didn't work with her much but she seemed a nice gal.

Working with Aisha at Synapse has been intellectually one of the best experiences of my career and interpersonally one of the more challenging. She operates on her own schedule, responds to external timelines as suggestions rather than constraints, and can be opaque about where her thinking is during work-in-progress. The NeurIPS papers are extraordinary. The day-to-day collaboration is a test of patience. The output justifies the difficulty. Just barely.

Aisha's work was genuinely good. The issue was that she treated the desk as a resource to draw from — data access, compute time, context on positions — without contributing much back. Requests for early reads on her research were consistently deferred. When the models finally landed they were excellent. The process of getting there was frustrating for everyone waiting on her outputs.

Aisha came to Arcturus as a quant analyst but clearly had her eye on what was coming in ML. The signals work she did with satellite and alternative data was ahead of what most of us were building. She's since moved that expertise in a direction that makes a lot of sense. My only note is that she was sometimes slower to loop in the broader team than would have been ideal — not secretive, just private about process.

I respect what Thomas built at Velostack. The onboarding systems work. But the culture that came with them is quite rigid — there's a right way and a wrong way and it's usually his way. For engineers outside the implementation track, the processes feel constraining rather than enabling. He's effective within his domain; the question is whether that domain should extend as far as it does.

A lot of people leave consulting and discover the skills don't move as cleanly as they thought. Thomas is an exception. He took what he built at Pinnacle and applied it in ways that were practical for a scale-up. The frameworks he runs are lean and they work. Unpretentious about it too, which I appreciate.

Thomas joined Velostack when we were still figuring out what customer success meant for our platform. By the time I worked closely with him we had a 48-person org with documented playbooks, clear SLAs, and customers who liked implementation. That transformation is largely him. The only friction I've felt is around pace — he builds systems carefully and the company's growth sometimes pushed for faster than his process preferred.

I sat next to Claire at an energy dinner and the first fifteen minutes were some of the most unsolicited technical explanation I've sat through. She's clearly extraordinarily capable. What the evening also made clear is that small talk, light conversation, and anything not directly related to her work do not compute. That's fine for a conference paper. For sustained cross-functional collaboration it would be limiting.

I had to work with Claire on a regulatory interface issue that touched both our organizations. She was exactly the expert you'd want when stakes were high — systematic, prepared, impossible to fluster. Getting her up to speed on context outside her technical lane took real patience. She operates at a level of specificity that most cross-functional discussions don't natively support.

Different industries, but we've crossed paths at energy and infrastructure conferences. Claire talks about reactor safety with the kind of precision that makes you realize most engineering discussions are extremely sloppy by comparison. I came away from one conversation completely rethinking how I document safety cases in my own work. She holds an extraordinarily high bar and does so quietly.