by Brad Stone
After one year in Seattle, Manber was already tired of his commute, and he was asked to head up the new Palo Alto office. In October 2003, Amazon’s first development center was opened on Waverly and Hamilton Streets in downtown Palo Alto. Staying true to his affinity for mathematical abbreviations, Bezos called it A9—shorthand for algorithms. Despite his move, Manber kept up his weekly meetings with Bezos via conference calls and regular trips to headquarters.
They were still thinking big. A9 not only worked on revamping product search on Amazon.com but also, in a direct attack on Google’s turf, developed a general Web search engine. The company licensed the Google search index but built on top of it—simultaneously partnering with and challenging Google. “Search is not a solved problem,” Manber said in April of 2004 when Amazon unveiled a Web search engine at A9.com. “There are lots more things that can be done. This is just the beginning.”
A9 would give Bezos and Manber a forum to try out some of their more ambitious ideas, most of which had nothing to do with Amazon’s core business. In one brainstorming session, they decided the Web presented a natural opportunity to reinvent the Yellow Pages and ginned up a project called Block View that matched street-level photographs of stores and restaurants with their listings in A9’s search results. This was two years before Google announced a similar (more successful and ultimately controversial) initiative called Street View.
Google would blanket the country with a fleet of company-owned trucks outfitted with expensive, specialized cameras to get its street views, but Amazon approached the problem with its usual emphasis on frugality. Manber’s budget for the project was less than a hundred thousand dollars. A9 flew photographers and portable equipment to twenty major cities and rented vehicles.
By late 2005, with Google gaining in both popularity and market capitalization, the general Web search at A9.com started to look like a noble but failed experiment. Web search, it became apparent, was not something that could be done cheaply or by piggybacking on a rival’s search index. Manber had a dozen engineers working on Web search, while Google had several hundred. Still, the A9 development center was showing promise. It made modest improvements to product search on Amazon.com and started work on an advertising service called Clickriver, which would allow advertisers (a television installer, for example) to purchase links within search results on Amazon.com (a search for HDTVs, for instance). Clickriver contained the seeds of a new advertising business, seeds that would later sprout into a healthy source of revenue for the company. Manber’s time at Amazon was productive in other ways too: after three years, he had more than twenty patent applications, several of which carried Bezos’s name too.
But then a series of conflicts erupted that rocked the S Team, broke up the Bezos-Manber partnership, and sent Bezos all the way back to the drawing board in his ongoing attempts to prove to the world that Amazon was something more than just a boring retailer, or a technology company that had chosen the least inspired business model of a new age.
At ten years old, Amazon could be a deeply unhappy place to work. The stock price was flat, there were strict limits on annual raises, and the pace was unrelenting. Employees felt underpaid and overworked. When the new development centers opened in Palo Alto and elsewhere, the joke inside Amazon was that it was a necessary move because everyone in Seattle was aware of how abjectly miserable employees at the company were.
In the engineering department, employees were constantly trying to fix a technical infrastructure that was now an aging, sprawling mess. The company had outgrown the original framework devised by Shel Kaphan in the 1990s, the monolithic code base dubbed Obidos that for years was held together by what Amazon executive Werner Vogels later called “duct tape and WD40 engineering.”4 And when Amazon cloned its clunky code base to run the websites of Target and Borders, those deals were lucrative but they magnified the company’s infrastructure problems. Instead of fighting flames emanating from a single building, engineers often had to deal with a neighborhoodwide inferno.
Like a lot of other technology companies at the time, Amazon got an education in the wisdom of moving to a simpler and more flexible technology infrastructure, called service-oriented architecture. In this kind of framework, every feature and service is treated as an independent piece and each can easily be updated or replaced without breaking the whole.
Led by Amazon’s chief technology officer at the time, an avid pilot named Al Vermeulen, whom colleagues fondly called Al V., the company rebuilt its technology infrastructure as a series of these independent but interconnected parts. The awkward and extended transition to this new code base, one element of which Amazon called Gurupa (after a section of the Amazon river where the tributaries diverged), took over three years and caused all kinds of excruciating pain among its network engineers, who were forced to carry pagers so they could respond promptly to the numerous problems.
As a result, dozens of these talented technicians left, many of them defecting to Google. Steve Yegge was one such engineer who made the move around this time. He would publish his opinion of his former employer years later by writing a screed on the Google+ social network and accidentally making it public for the entire Internet to read. “My challenge with Amazon is finding a way to describe it without making me puke,” Yegge wrote. “But I’ll figure something out, eventually. In many ways they’re a world-class operation—primarily in ways that matter to their customers; employees, not so much. But I guess in the end it’s the customers that matter.”
In late 2004, another window opened on the mood and inner workings of Amazon. Toys “R” Us sued Amazon in federal court, contending that Amazon had violated the agreement to allow the chain store to be the exclusive seller of the most popular toys on the Amazon website. The issues in the case were numerous and complex and hinged on some of the arcane legal language in the original contract. But they boiled down to a clash of goals and worldviews. Toys “R” Us thought it was paying Amazon hefty annual fees and a percentage of sales for exclusivity as the seller of the most popular toys on Amazon. But Amazon and its CEO could not abide anything that impeded their drive to give customers the ultimate selection, and Amazon constantly angered its partner by conceiving of new ways to allow other sellers to list competing toys on the site.
The trial was held in September of 2005 in a stuffy courtroom in Paterson, New Jersey. Bezos testified over the course of two days, and from court records, it does not appear that he enjoyed himself. Judge Margaret Mary McVeigh questioned Bezos’s inability to recall key decisions and ultimately ruled in favor of Toys “R” Us, allowing the toy seller to break its contract with Amazon and revive its own website. In her ruling, the judge described Amazon employees as contemptuous toward their offline counterpart and worshipful and apprehensive of their own CEO and his demands. “It was certainly my perception that nothing major happened at Amazon without Jeff Bezos’s approval,” she wrote in her judgment, quoting the testimony of a Toys “R” Us executive.
Amazon appealed the settlement but lost and was required to pay $51 million to its former partner. The dispute with Toys “R” Us would become exhibit A in the argument that Amazon was so fixated on catering to its customers and on the mechanics of its own business that the corporation was often hostile to the large companies it partnered with. (At the same time as the Toys “R” Us suit, another partnership, with travel site Expedia, also dissolved in litigation. That matter was settled out of court.)
With the toy business now in transition after the dissolution of the agreement with Toys “R” Us, the hard-lines retail division was cast into further disarray. Part of the problem was that categories like electronics and jewelry were not yet profitable but were growing faster than the older media businesses, which dragged down the company’s finances. Bezos felt he needed to give the issue specific attention, and so in late 2004, he hired Kal Raman, the former Drugstore.com executive who had played a supporting role in the employee poaching that had led to the Walmart lawsuit i
n 1998. Overnight, Bezos cleaved in two the domain of Diego Piacentini, then the senior vice president for worldwide retail, and he handed hard lines over to Raman. Bezos announced the move on a Tuesday in an internal e-mail to the company. Almost everyone from that time says the message was a shock not only to them but also to Piacentini (though Piacentini insists that he knew about the change before the e-mail went out).
Raman was a native of a small village in southern India. His father had died when he was fifteen, plunging his family into poverty. He bootstrapped his way to a degree in electrical engineering, then to a job at Tata Consulting Engineers in Mumbai, and then to a consultant gig at Walmart in Texas, where he climbed the ranks of its IT department and met Rick Dalzell.5 Raman was whip-smart, a tireless worker, and he had a reputation as an exceedingly demanding manager. He also had some memorable habits, including chewing an Indian betel leaf called pan during meetings and spitting into the garbage pails. Diane Lye, who ran Amazon’s data warehouse at the time and reported to Raman, sums it up this way: “Kal was a screamer.”
Applying his experience from Walmart, Raman pushed to build systems that finally realized Bezos’s vision of Amazon as a company with data at its heart. His groups created automated tools that allowed buyers to order merchandise based on dozens of variables such as seasonal trends, past purchasing behaviors, and how many customers were searching for a particular product at certain times. Raman’s teams also improved the software for pricing bots, which were automated programs that crawled the Web, spied on competitors’ prices, and then adjusted Amazon’s prices accordingly, ensuring that Bezos’s adamant demand that the company always match the lowest price anywhere, offline or online, would be met.
Buyers were held strictly accountable for keeping their products in stock and their prices competitive. If they somehow failed to deliver—if their shelves were suddenly empty or if Amazon’s prices were higher than a rival’s—then “Kal was going to personally hunt you down and kill you,” says Diane Lye, who worked for Raman for eighteen months. “There was so much fighting and yelling at each other. The technology was broken all the time and because the technology was broken, the data was often wrong. We would bring it to Jeff Bezos and it was all contradictory and he would be yelling and screaming at us. Oh, it was horrible.”
Raman spoke fast and had a thick accent, and his malapropisms, dubbed Kalisms, were legendary. “You all must be smoking cracks!” he yelled. Or “Can I have some of what you’re drinking so I can feel good about your business too?” He lasted at Amazon less than two years, but people at the company still talk about him.
“Kal was brutal,” says Jason Goldberger, a retail manager who worked for Raman. “He’s like out of a movie. The year after Katrina, I took over the home-improvement business, and he could not understand why generator business had fallen [compared to the increase that had accompanied the storm]. He’s such a driven personality.”
The turbulence caused by all these changes added to the overall dysfunction gripping Amazon at the time. The S Team was beset by a variety of internecine rivalries, perhaps typical for a large company. Raman and Piacentini, uncomfortably splitting ownership of the retail business, did not get along. Raman also battled with Jeff Wilke. At one point, Wilke heard that Raman had spoken negatively about the fulfillment team and he confronted him in a large meeting. “I heard there’s something you want to say to me,” Wilke said. “Do you want to say it in front of all these people?” Onlookers thought they might come to blows. In addition, Kathy Savitt, the vice president of communications, didn’t get along with Piacentini, and Jason Kilar, who had fully imbibed Bezos’s principles and mannerisms, had committed to run the video site Hulu but stuck around while he gave Amazon months to find his replacement.
Bezos handled it all poorly; it was as if the personal dramas were happening on a different dimensional plane that he couldn’t or didn’t want to access. As a result, the S Team, according to several of its members, became a highly combustible forum, a group in which everyone felt the need to be outspoken and curry favor with the boss and where political disputes were allowed to fester.
One of the biggest of those disputes was between Udi Manber and another technical leader of the company, Jeff Holden—Bezos’s former colleague at D. E. Shaw, the onetime teenage hacker who had dubbed himself the Nova.
Holden had been at Amazon longer than anyone else on the management team and had the closest personal relationship with Bezos. If members of the S Team were planets revolving around the sun, then Holden was Mercury, occupying a privileged orbit and drawing a fair amount of criticism, partly based on jealousy. Now in his midthirties, Holden remained a fast talker and a prodigious diet soda and Frappuccino drinker who always paced intensely during product meetings. Like Bezos, he was an aggressive manager who wanted to see results fast.
As senior vice president of worldwide discovery, Holden oversaw more than five hundred employees in Personalization, Automated Merchandising, Associates, E-Mail Marketing—and the department in charge of the search engine. It had been partly his idea to have Manber return to Palo Alto and run A9. But after a while, Holden began to feel that Manber’s group was too absorbed with the abstract challenges of general search and wasn’t focused enough on the practicalities of running the search for the Amazon website and solving nagging problems, such as latency, or the amount of time it took for searches on Amazon.com to generate results. The problem was that Holden retained ownership of the search experience on the website while Manber held responsibility for the search technology; they were basically dependent on each other.
Eventually, after growing increasingly frustrated, Holden concluded the situation was unworkable and, with an engineer named Darren Vengroff, started his own secretive effort in Seattle to rebuild Amazon’s search engine using the open-source tools Lucene and Solr. After a few months, Holden demonstrated the prototype to Bezos, who agreed to let them test it. Holden told Bezos he wanted to develop the Solr-based engine further and, if things went well, move search back to Seattle. Bezos said he’d think about it and later ran the proposal by Manber, who felt it was a sneak attack on his turf.
Now everyone was in a difficult spot. Bezos came back and told Holden and Manber to form a joint team to evaluate the new approach. There are various versions of what happened next, but the bottom line is that Manber and Holden didn’t like each other and couldn’t work well together. After the evaluation period ended, Bezos decided that search should remain the purview of A9. Holden was crestfallen. He argued that his organization had spearheaded the project and was doing the hard work to fix the persistent search problems on the site. Bezos pointed out that those were emotional concerns, not logical ones.
Feeling that Bezos had chosen Manber over him, Holden planned his departure from Amazon. With Vengroff, he would start a mobile search company called Pelago (which Groupon later acquired). Though this was a difficult time in their relationship, Holden and Bezos remained friends, and Bezos invested in Pelago. But when Holden left, Bezos lost one of his oldest friends at the company and one of Amazon’s most versatile innovators. Fortunately, he still had Udi Manber.
And then Manber decided to leave.
Manber said he didn’t like running a remote office and felt isolated from the decision-making in Seattle. Privately, he was annoyed that Bezos had allowed Holden’s rival search effort to take root in Seattle. He told Bezos and Rick Dalzell that he was considering going back to academia to do research in the science of memory. Bezos pleaded with Manber to stay on as what he called an Amazon Fellow. Manber said he would consider it.
Meanwhile, Urs Hölzle, one of Google’s first employees and its vice president of engineering, wanted to relinquish his oversight of search to focus on Google’s infrastructure. Hölzle invited Udi Manber to have dinner with him and surprised the Israeli scientist by asking if he was interested in replacing him as Google’s head of search engineering. Manber demurred at first, saying he was planning on getting out
of the field. Then a few weeks later he changed his mind and decided that he might as well hear Google’s offer. Hölzle arranged a dinner that January with Larry Page in a private room of Il Fornaio, a restaurant in downtown Palo Alto. Page and Manber made sure to enter the restaurant separately. In the middle of dinner, Sergey Brin joined them. Google CEO Eric Schmidt showed up for dessert. It was an impressive full-court press.
By February, Manber had received an extraordinarily lucrative offer to run the search team at Google, and he decided to take it. Money aside, for any search engineer at the time, going to Google meant stepping onto the biggest playing field in the world and joining a championship-caliber team. For its part, Google had snagged one of the brightest minds in search and simultaneously decapitated the efforts of a competitor with one swift stroke.
Now Manber had to inform Bezos, right in the midst of so many other defections to Google. He delivered the news over the phone. Amazon employees would describe what happened next as one of Bezos’s all-time biggest nutters. Manber anticipated that Bezos would be disappointed and perhaps try to persuade him again to stay. “That’s what I had expected Jeff to do, but that’s not what he did,” Manber says. “He was clearly angry and he was dumping on me. I don’t recall now his exact words, but it was something like ‘No! No! No! You can’t do that!’ He was blaming me almost like I was a kid who did something very wrong.”
In that moment, Manber felt like he had lost a friend. He pleaded with Bezos that an engineer with his background and interests could not possibly decline the opportunity to run search at Google. Bezos viewed it as a personal betrayal. This time, he couldn’t brush away an employee’s departure easily. “He was not mincing words, and I felt horrible. He was always very good to me, the closest to a mentor that I ever had, and I was letting him down,” Manber says. “I don’t know if he ever forgave me, probably not, but I didn’t really have a rational choice. I [had] already decided to leave Amazon, so it was between moving to the top of my field or starting from scratch in a new field.”
