Echoes directory - Page 2

I worked with Rahul briefly on overlapping engagements. He's the type of consultant clients actually like — substantive, direct, not allergic to a hard conversation. In a field that produces a lot of polished but hollow practitioners, Rahul stands out as someone who actually cares about doing good work.

We worked together at Meridian. Technically solid. Where I had issues was with how he managed his internal profile — very focused on being seen by the right people, which I found a bit much. The work was fine. The way he operated felt like he was always playing a longer game that didn't always align with just getting the deal done right.

Rahul has an ability to hold a complex engagement in his head — the workstreams, the politics, the key decisions — and keep everyone moving in the right direction. The supply chain redesign he led was well-executed under genuinely difficult client conditions. My only observation is that he can lean on process frameworks a bit heavily when a situation calls for improvisation.

The research is legitimately impressive. What I've heard from people who've worked cross-functionally with her is a different story — territorial, dismissive of non-technical inputs, and slow to accept that business constraints are real. I tried to get her involved in a technical advisory conversation once and it went nowhere. She engages only on her own terms.

Sophia is genuinely talented — probably the best CV researcher on the team. But getting input on work that touched her domain sometimes felt like negotiating a border crossing. She has strong ownership over her work, which is usually a good thing, but it crosses into protectiveness in a way that slows down cross-team dependencies. I learned to come with a clear agenda. Once you have that it works.

Sophia's ViT-Lite work is the kind of thing that gets written up at conferences. What impresses me more is that she's doing it in an applied industrial context with real latency and memory constraints, which is much harder than lab-clean benchmarks. She approaches hard problems like puzzles she's personally excited about, which makes her excellent to work alongside.

David is enthusiastic to a fault. I've seen him commit across four workstreams simultaneously and then disappear when the actual deliverable was due. The intentions are genuine — he clearly wants to be involved in everything — but the result is a lot of dropped threads and colleagues left waiting. I've stopped depending on him for anything time-sensitive. If the timeline is flexible, he's fine. If it isn't, look elsewhere.

When David moved from engineering to PM I was his skip-level. He had strong product instincts but was still running on engineer mode — he wanted to be in the weeds on the how before the what was fully agreed. We had several conversations about that. Credit to him for being coachable, which is not a given for engineers making that transition.

David and I joined Velostack around the same time. On product thinking he's ahead of most people I've worked with — he understands what customers actually need versus what they ask for, which is a rare skill. Where I've coached him is managing up: he undersells his work in ways that leave leadership underinformed. Getting him to be more deliberate about visibility has been a worthwhile investment.

My interactions with Elena have been limited to industry events, but the impression she leaves is of someone with very little patience for anything she considers imprecise. I made a comment about a macro trend — admittedly not my deepest thinking — and the correction was swift and thorough. In a work context that precision is probably invaluable. As a colleague or manager, it would wear thin quickly.