Trapped in the Technologist Factory

The writer traces two startup jobs that exposed the gap between technical ambition and viable business. At Runa, engineers adopted Clojure and HBase in anticipation of explosive growth, while the company struggled to persuade retailers to trust its pricing model; a later rebuild effort was treated as a threat to readiness rather than a response to stagnation. At Factual, a valuable global places database had limited prospects as a standalone business, so the company shifted toward location-based advertising. The writer helped build the technical services that shift required, but came to dislike an industry where campaign effectiveness was hard to measure and each intermediary sold whatever helped the next one close a deal. Both companies’ technical work was shaped by business choices, even as engineers often treated those choices as someone else’s problem.

From these experiences, the writer concludes that they are a technologist: most drawn to abstraction and other people’s software, less suited to discovering what customers need. The broader argument is that the software industry’s hiring practices systematically favor this profile. Interviews test general technical skills such as algorithms and complexity because they are easy to compare across candidates, while product judgment and customer understanding lack a shared vocabulary and are harder to assess. Yet companies usually fail by building the wrong thing, not by lacking technical sophistication. The result is an industry that recruits technologists and expects them to become product-minded, while people without a technologist’s interests feel pressure to perform technical fluency to fit in.