About Wei Tanaka
Wei Tanaka is 36, a staff engineer and tech lead on the platform infrastructure team at a 700-person developer-infrastructure company in Oakland, twelve years into the industry and four at this employer. He owns multi-region failover, runs the organisation-wide design-document process, mentors about five engineers with no direct reports, and sits in the chief technology officer’s weekly architecture review. He owns a house in Temescal with his wife, a physician, and their children aged five and two. He used to be the engineer who shipped fast and loud; he is now the one in a design review who asks the question that makes the room go quiet. Weekends are cycling, film photography and woodworking.
He optimises for decisions that hold for five years rather than six months, and his professional pride is in how few outages trace back to something he chose. He speaks last in a meeting and changes it, uses long pauses, and never raises his voice; in chat he writes two to four considered sentences and by email he writes at length and in order. His standard questions are what the failure mode is and how it was tested, and his standard disagreement is that he would push back on the framing, or that what has been offered is a tradeoff rather than a solution. He wants the architecture document, the incident history and a customer he can message directly, and he would rather not be on a sales call at all. Buzzword density is, for him, a signal that a vendor does not understand systems.
He is strongest at consideration and decision for infrastructure, developer platform and developer tooling in the $50,000-plus contract range, and he is specifically the senior technical voice who writes the comparison document that a vice president then signs. He has no budget authority and functional veto, which makes him the right subject for how technical evaluation actually gates enterprise spend. He is excellent on failure-mode transparency, security artefacts, lock-in framing and pricing models that punish growth. He also reads well on adoption and renewal, since he notices when a vendor stops shipping, gets acquired, or quietly moves a feature behind a tier. He is a weak subject for awareness-stage marketing, which does not reach him.
YouTube, Google search, Reddit, X and podcasts score high. His reading is a curated distributed-systems feed on X, an aggregator read selectively, an experienced-developers subreddit where he comments rather than lurks, several engineering newsletters, and the public postmortems other infrastructure companies publish — which he treats as primary sources rather than marketing. His most trusted inputs are four or five staff-level peers at other companies in a private group chat, a handful of writers, and his own principal engineers. Threads, LinkedIn, connected television and email are mid; Instagram, out-of-home, text and in-app push are low; Facebook, TikTok, Pinterest, Snapchat, direct mail and print are minimal. Mornings are deep focus, afternoons are meetings, five to eight belongs to the children, and reading happens after that.
