Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It sounds to me like she's trying to build another Google. It's really (almost impossibly) hard to dethrone innovators without actually doing any innovation. It's equally difficult keeping talent when the corporate culture isn't hacker-centric.

While buying your way into the party is a nice first step, what do you do when you don't have the talent pool to continue to innovate and can't even grow it? Especially when you don't allow remote work, and this industry is increasingly going remote (even if only part-time)?

I'm seeing a lot of big talk (primarily via money) from Yahoo, but I don't feel convinced that this is going anywhere. Without a focus on the people and innovation, what do you do after you buy a bunch of startups? So far Yahoo's response has been "buy them and let them operate independently." People go to work at Google to work at Google, not to work at a subsidiary of Google. So if I wanted to go work for Hulu, I'd want to work for Hulu, not Yahoo. Yahoo hasn't been an engineer's company for a very, very long time, and I don't see them taking strides to fix that, so it's hard to say what's going to happen.



In order to change the company's product trajectory, culture, and perception there are many stages that they must go through to get to the ultimate goal. At this point in time, Yahoo does not have the public perception that they are a cool company to work for, especially for engineers. This makes it a near impossible task to attract the talent necessary for internal innovation. However, if they buy cool companies, show that they are working on things internally (Flickr redesign), and prove that management is competent, they will be able to transition to internal innovation.

Of course, it is a big jump to go from buying companies to transforming their culture to match the perception that they are attempting to create. Perhaps removing the ability to work remotely was a bad first step, perhaps not. I imagine that Mayer knew what she was doing here and it will likely turn out to be a positive move. The big question is what other steps they take internally to truly change the culture. It could be a big flop, but if anybody knows a little something about company culture it would be Mayer.


> At this point in time, Yahoo does not have the public perception that they are a cool company to work for, especially for engineers.

That's the thing, it's all public perception and not based in reality. I've worked at Y! for ~4 years (software engineer) and love it. As Marissa has publicly stated, Y! is the world's largest startup, so there's a ridiculous amount of opportunity to work on fun and challenging problems.


> As Marissa has publicly stated, Y! is the world's largest startup

All CEOs state that because its the hot, sexy thing. Especially for the new, younger employee generation.

The problem is you don't want a culture with the public perception, at least for engineering, you're looking for the the same culture that are leaving the company now. So many awesome things came out of Y! but I feel much like they are going the ways of Sun.


> what do you do when you don't have the talent pool to continue to innovate and can't even grow it?

I'm sure Yahoo still has a big talent pool. Don't really know how they managed to do it as it doesn't really make sense, however if you want some proof of that, take a look at: http://developer.yahoo.com/everything.html (speaking of which, did you know that Apache Hadoop was initiated and is still led by Yahoo?)

> So far Yahoo's response has been "buy them and let them operate independently."

Actually that wasn't Yahoo's behaviour in the past. Delicious for example stagnated after they began rewriting/redesigning it, as they wanted Delicious to be "integrated" with Yahoo's network. Development eventually grinned to a halt. If Yahoo would have kept Flickr or Delicious operating independently, then both would be a lot bigger than they are today.

Yahoo also did a stupid move when they sold Delicious. But at the very least they sold it, instead of shutting it down, like Google did with Reader.

> People go to work at Google to work at Google, not to work at a subsidiary of Google.

Well, no, you're talking about the poor fools that go through that awful interview process without caring about what they'll end-up working on, being assigned on Calendar, or on fixing bugs of internal tools, or on some project destined for some African country that nobody will ever hear about, or on some other soul-sucking activity with the only thing to show for being a Google T-shirt.

Google is still a good brand among employers and it's still something to be able to say that you're working at Google, however, like all other big software companies, Google got too big and those with a minimal internal knowledge of how things work there know for a fact that it really isn't the glamorous place to work at, unless you're lucky.

> Yahoo hasn't been an engineer's company for a very, very long time, and I don't see them taking strides to fix that

I can't possibly imagine how in the world would you know that, unless you worked for them. Well did you?


> on some project destined for some African country that nobody will ever hear about,

Uh, bringing a billion people onto the Internet for the first time, and turning the 3rd world into the 1st world, isn't most people's definition of soul-sucking.


The Hadoop team quit Yahoo to start HortonWorks last year.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: