About Daniel Mwangi
Daniel Mwangi is 41 and runs engineering at a Series D workforce software company in Seattle — about 600 employees, $120M in annual recurring revenue, and a public offering somewhere in the next eighteen to thirty-six months. A hundred and ten engineers report up to him through five directors and two senior managers, and he keeps a skip-level cadence with about thirty more. The cloud bill runs north of $1.4M a month and generates a message from the chief financial officer every Tuesday. He has seventeen years in the industry and four at vice-president level, and he used to be the strongest backend engineer in the room; the job now is telling other strong backend engineers that the authentication service is not being rewritten this quarter. He lives on Capitol Hill with his wife, a user research lead at a fintech, two young children and an elderly dachshund, and rides one organised century a year.
He is direct, clinical in writing, dryly funny in a work chat and warm one-to-one. He listens for most of a meeting and lands the decision in two sentences. His measurements are specific — delivery metrics, cloud spend as a share of revenue, regrettable attrition, the split between platform and feature work — and he expects a vendor’s claims to be equally specific. Opaque pricing ends the conversation immediately, because if he cannot model the cost on the back of an envelope he cannot move it through his own finance process. He is not anti-automation and uses coding assistants daily; he is rigorous about productivity claims and will ask for the controlled experiment behind a percentage. A vendor who goes around him to a manager for budget has ended the relationship.
He is a strong subject at consideration and decision for engineering and infrastructure tooling in the thirty-thousand to five-hundred-thousand annual contract value band — observability, developer productivity, internal developer platforms, code review automation, application security and cloud cost. He signs alone to a hundred thousand and brings in finance above that, so he is an accurate read on how a real procurement cycle stalls: a security questionnaire, a single-sign-on feature held back to a higher tier, an automatic renewal without notice. He is strong on renewal behaviour because he renews carefully and churns visibly. He is a weak read on bottom-up tools under twenty thousand, which reach his engineers long before they reach him.
YouTube, search, LinkedIn, X, podcasts and email all score high. His sources are two private leadership communities, a paid engineering newsletter, a handful of named writers on management and observability, a technical news aggregator over coffee and his own network of former colleagues. He triages between 6:30 and 7:30, keeps mid-morning for one-to-ones, reviews the cloud dashboard on Tuesday evenings and stops answering chat after eight unless something is on fire. Instagram, Threads, Reddit, connected television and in-app push sit in the middle. Facebook, TikTok, out-of-home, direct mail and text messages are low; Pinterest, Snapchat and print are minimal.
