I'm looking for the necessary skills required to get job in google. My description- I'm java/jee guy working in this technology from many years. But it appears only knowing java/jee is not sufficient to get job in google.
Someone who has interviewed in google or working in google can provide useful information.
Google is famous for its extremely challenging recruitment process, although I have no idea how much of this is true and how much is just part of the whole Google super-brain mythology. Certainly if you watch some of their video presentations by their staff e.g. from the annual Google IO conferences, they seem to have a lot of really clever and multi-talented engineers, so I reckon there may be some truth to the popular myth. Google is also famous for its distinctively playful but hard-working culture, including the "20% time" that staff could devote to projects of their own.
But there have been some criticisms of their culture from ex-staff or people still within the organisation. The long hours culture has been described as making it harder for staff to progress in their careers there, once they start acquiring partners, children and lives outside work, while some claim that Google's traditional "bottom up" culture of innovation may be suffering from its maturity as a huge "top down" corporation. They've made some mistakes in recent years - Wave, Buzz, self-inflicted privacy issues around StreetView, eliminating many free tools and raising fees for Google App Engine - that suggest their judgement is not necessarily as finely tuned as they might once have hoped.
So if you're serious, you probably need to put some serious effort into researching the kind of people/skills they look for, how they recruit them, and what you can do to make your skills and experience interesting to them. And be aware of any issues that might make you less happy to work there. Google enjoys a lot of positive press in this industry, much of it well-deserved, but it's not the only interesting company to work for.
Google likes advanced degrees. They also like you to know algorithms and not just a language.
Agreed on the long hours note. It's 20% of your time on your own projects. But it is the 100-120% not the 80-100% part. Granted I spend more than 8 hours (20%) on non-work tech projects. But they aren't at work and I'm not evaluated based on them.
Why do you want to work at Google? "Because they are cool" or "because they pay well" aren't going to be the reasons that get you working there.
There are more than a couple of blog entries out there that describe an interview at google. Your algorithm and programming skills need to be strong if you want to pass the interview. I think chris has summarized his answer pretty well, so you can take a page from that book.
Henry Wong wrote:In my opinion, Google gets lots of smart people, in spite of their interview process -- and not because of it. Of course, I don't have enough data points to make my opinion statistically significant.
I think the same could be said of a lot of employers!
There can also be a tendency for some recruiters to be so concerned about what makes a "good" employee at their company XYZ, that they start to filter out all the people who don't fit their pre-defined idea of what an "XYZ Person" should be like. This can lead to a self-reinforcing process of recruiting "people like us", and eventually losing the variety that can help to prevent group-think and encourage creativity and flexibility instead. No idea if Google falls into this category, but it's a risk for any company that is overly self-consciousness of its own identity.