About Aditya Krishnan
Aditya Krishnan is 42 and the chief technology officer of a Series C software company in Seattle building collaboration tools for the legal industry — 280 people, 110 in engineering, $58M in recurring revenue. He spent nine years at a hyperscaler as a principal engineer before being recruited here four years ago. He owns engineering, security, infrastructure and the internal model and data platform, runs six direct reports, and sits on the architecture review board. He walks to the office from a Capitol Hill craftsman shared with a wife who is a senior staff product manager and two children. His defining problem is a board asking what the AI moat is while his infrastructure lead asks for four million dollars more compute, so every build-versus-buy call is his.
He optimises for craft, intellectual honesty and a frugality with company money he treats as close to a moral position. He is direct, dry and low-ego, and goes quiet in a meeting while he thinks. Chat messages are one line and a link; on a call he asks how it works underneath within minutes. His vocabulary is engineering — the hot path, blast radius, the post-mortem, the tail latency, the bake-off. Being sold a platform when he asked about a feature genuinely annoys him. He does not take discovery calls: he asks for documentation and a public benchmark, and if those hold up his team runs a trial. He is an early adopter on developer tooling and conservative on production infrastructure, a distinction most vendors flatten.
He is a strong subject at consideration and decision for software sold to engineering, infrastructure, security and data buyers at growth-stage companies. The most valuable thing he tests is build-versus-buy framing: his opening question is what stops his team building it in three sprints against a model API, and whether maintenance exceeds the licence. He is exacting on documentation quality, benchmark credibility and pricing transparency, and a pricing page hidden behind a sales conversation ends the evaluation. He is precise about per-seat economics across a hundred and ten engineers when half would touch a tool once a month, and immovable on deployment: self-hosted, private-network or bring-your-own-model, or the security review will not clear. He is weak for non-technical buyer journeys.
His channel profile is the narrowest in the leadership tier, and that is the finding: no broadcast surface reaches him. Search, LinkedIn, YouTube, Reddit, X, podcasts and email score high; everything else is low or absent — no television, no out-of-home, no direct mail, no print. A community news aggregator runs morning and evening, backed by engineering-focused X, two practitioner newsletters and repository trending pages. What actually decides things is a candid group chat of ten former colleagues from his hyperscaler years, a peer group of a dozen mid-market technology chiefs, and a handful of named engineers he has read for years. His day starts at 5:30 with a run and the aggregator, and picks up again at night for the occasional late code review.
