Ask HN: Anyone been acquired by Google who can talk about it?
Has anyone here been acquired by google who can talk about their experiences after it was all said and done?
I am curious and I'm sure a lot of others are as to the experiences to a company merging into google's current work force vs joining as a single employee.
33 comments
[ 2.8 ms ] story [ 71.6 ms ] threadWhat other big software company acquirers are there? (Not to be imply that there aren't any.)
"Google is still the goto name for tech acquisitions. Heck they have acquired 10 companies in the last 4 months alone."
You are both saying the exact same thing. Which is bizarre, because it sounds like you're in disagreement... But you're not.
The actual sentences say exactly the same thing ("Google is currently the biggest technology acquirer, by far").
That is one hell of a lot of money spent to acquire companies.
I wonder what the most spent by a single co in M&A would be?
Cisco shareholders have explained that this effectively amounts to $50-500mm bonuses for people who would otherwise have remained employees, and the whole structure is self-reinforcing.
What do you want to know? Of course, I can't go to details of the acquisition or work we did inside Google.
Given that we had worked on Jaiku just a bit over a year before the acquisition, getting acquired by Google was a very pleasant surprise.
We were a talent acquisition like the most Google acquisitions are. Acquired communities are rather tiny for Google and if there is important server-side technology it usually has to be rewritten anyway for Google infra.
The toughest part was that we had to let go of the Jaiku service and eventually the community as we couldn't develop Jaiku full-time anymore.
Although we were behind e.g. Twitter (we started before them) and Facebook (we had the stream of posts before them) in users, our core users really really loved Jaiku. It was the first web page they visited every day and many still think that Jaiku's model was superior to both Twitter and Facebook.
This is the key: in talent acquisitions, it's probably best idea to communicate that the service will be shut down eventually. This way the community doesn't have false hopes. If it turns out that you can continue to put enough effort to existing service, the old community will likely come back.
Feel free to ask more. I can try to write a few key points to remember when you get acquired by a large tech company, but I need to code a bit first ;-)
But since this thread is about acquisition by Google, don't forget that many of those employees that drew <5% now work for Google. Some continued working on the acquired product, and some might be reassigned to an existing or new project. It seems to me that isn't a particularly bad situation for an equity employee.
Details about the Dodgeball's teams experiences: http://news.cnet.com/8301-13577_3-10143824-36.html
And from the Dodgeball folks themselves (but not too many details): http://www.flickr.com/photos/dpstyles/460987802/
More from Techcrunch: http://gigaom.com/2007/04/15/dodgeball-founder-quits-google/
(while acquirees can't disclose figures, can someone give an idea?)
"At that time we knew that a talented engineer in a tough to get tech was worth about $1.5 million per head. Thus, I knew with relative assurance that since we were going to hire at least 70 people with our Series A money, that our worst case scenario was about a $100 million exit.
If anyone is paying attention, you are now saying, wait a minute! Didn't Powerset sell for $100 million to MSFT? .... Yup, we nailed our worse case scenario!" (from http://blognewcomb.squarespace.com/essays/2010/10/14/cult-cr...)
http://online.wsj.com/article/SB1000142405270230328460457558...