In February 2025, Tobi Lutke drove a prototype sports car around Daytona International Speedway for 24 hours straight. His co-driver was David Heinemeier Hansson - the man who invented Ruby on Rails, the programming framework Lutke had used to build Shopify from scratch 20 years earlier. They finished 12th in LMP2 class. If there's a more perfect metaphor for how Tobi Lutke operates - full circle, deeply technical, wildly impractical by normal CEO standards, and somehow still moving fast - nobody's found it yet.
Lutke runs a commerce platform that processes more American online retail than any company except Amazon. He employs thousands of people across dozens of countries. He sits on the board of Coinbase. His net worth fluctuates by hundreds of millions with every Shopify earnings call. He was born in Koblenz, Germany in 1980. He left school at 16. He has never attended university. He got a computer at age six and never really came up for air.
The origin story is the kind that gets compressed into mythology: built an online snowboard shop in 2004, hated every available e-commerce platform, coded his own in two months using a then-obscure Ruby framework he was already contributing to, realized the platform was the product. The snowboard shop was called Snowdevil. Shopify launched in 2006. The rest is a $1.6 trillion cumulative GMV and a 14% slice of US e-commerce.
What gets lost in that compression is how specific the technical choices were. Lutke wasn't just "a programmer" who happened to build a store. He was a core contributor to Ruby on Rails. He created Liquid - the template language that powers every Shopify theme, still in use 20 years later. He built Active Merchant, the payment abstraction library that became an industry standard. He wasn't picking a tool off a shelf. He was one of the people who built the shelf.
This matters because it shapes everything about how Lutke runs Shopify. He doesn't manage from abstraction. He has opinions about systems architecture the way some CEOs have opinions about org charts. When he says in a company memo that "AI is not a feature, it's a transformation," he's not speaking in buzzwords - he's someone who has written production code at every level of the stack and is tracking exactly what large language models can and can't do in that context.
In April 2025, Lutke sent an internal memo to Shopify employees that leaked publicly within days. The core thesis: AI proficiency is now a baseline expectation for every employee. Before any team can request additional headcount or resources, they must first demonstrate that AI cannot do the job. The memo was not a vague "we're leaning into AI" announcement. It was an operational mandate. Teams that didn't treat AI as a fundamental tool were described, implicitly, as opting out of the company's future.
The memo went viral for obvious reasons. It was read as either a blueprint for the future of work or a prelude to mass layoffs, depending on where you stood. What it actually was: consistent with everything Lutke has said and done since 2013. His blog posts - on decision-making, compass metrics, apprenticeship - have always reflected a systems thinker who prefers operational clarity over comforting ambiguity. The AI memo was not a pivot. It was Lutke being Lutke, at higher stakes.
Experiencing and learning things quickly is the ultimate life skill.
- Tobi Lutke, "The Apprentice Programmer" (2013)
The German apprenticeship system he went through at Carl-Benz-School in Koblenz - a Siemens subsidiary vocational program - was formative in ways a traditional university education probably wouldn't have been. His mentor Jürgen handed him real production problems on day one. Lutke has written about this: the difference between learning to solve test cases and learning to solve actual systems. The apprenticeship model assumes competence can be built faster through supervised real-world work than through curated academic progression. Lutke's career is an extended argument for that hypothesis.
His intellectual heroes are revealing. He has cited id Software co-founder John Carmack's technical writings - game post-mortems, programming essays, Quake devlogs - as among the most formative texts he encountered as a teenager. Carmack's style was to think in public, document his reasoning in extreme detail, and treat systems design as a subject worthy of rigorous prose. Lutke absorbed this. His own blog posts operate the same way: specific, reasoned, willing to commit to a position and defend it.
He has also been publicly wrong. In July 2022, Shopify laid off roughly 10% of its workforce - around 1,000 people. Lutke sent an internal letter that was extraordinarily candid by the standards of corporate communications: he had predicted the pandemic-era e-commerce acceleration would permanently compress a decade of growth into two years, over-hired accordingly, and the prediction was wrong. "I got this wrong," he wrote. Not "market conditions changed" or "we're rightsizing for the current environment." Just: I bet wrong. The honesty was notable and, for a lot of the people who lost their jobs, not entirely consoling.
The same letter included a passage that became one of the most-quoted management statements of 2022: Shopify is "a team, not a family." It was a deliberate rejection of a Silicon Valley cliche - the idea that a company is a warm, unconditional community where everyone belongs regardless of performance. Lutke's framing was blunter: this is a high-performance sports team. You are here to compete at the highest level. The mission matters. Sentiment doesn't protect employment. A lot of people found this refreshing. A lot of people found it cold. Both readings are correct.
