I like working at Google as an SRE (Site Reliability Engineer) because it is a job that combines my skills as a professional software engineer and self-taught system administrator. The work I do is quite varied, so I don't get bored doing the same thing over and over like I have done at other companies.
Since Google is a well-established corporation, they can afford to provide some of the best benefits that other companies can't or don't provide. Unlike startups, you don't have to worry about the company going belly-up, nor do you have to work unreasonable hours.
We have free food in the form of many cafes all over the area, each with a varied menu of foods. There's even a "concern" program that allows employees to call certain specialists for free advice. For example, you can ask a lawyer for some legal advice or talk to a therapist, amongst other services.
The company even offers up to 3 months of paid medical leave.
Aside from benefits, job security, and exciting projects, everyone there is very intelligent, and good peers/team-mates are essential in any corporation.
Large corporations have a certain bureaucracy and more red tape than startups, naturally.
Promotions at Google require either someone to nominate you (which is rare) or self-nomination during regular performance review cycles.
Performance review cycles are a big pain and a context interrupt. Many share this view, though it is believed to be a necessary evil.
Not high up enough to have an opinion on this and get involved in company politics. I have only worked here about a year.
First, they gave me a phone interview and asked me two questions. Then, they told me I still need to pass an OA. The OA was pretty easy (maybe because I am a new grad). Finally, I came for an onsite interview. In total, there were four interviews, ea
The interview process included a phone interview followed by an on-site interview in Mountain View. The phone interview was 45 minutes long and covered topics related to hashing. The in-person interview covered variations on dynamic programming, bi
The process took quite long, about six weeks. I applied online and was a little bit surprised to get a response. There was one phone interview and four onsite interviews. It was a positive experience and has given me more interview experience.
First, they gave me a phone interview and asked me two questions. Then, they told me I still need to pass an OA. The OA was pretty easy (maybe because I am a new grad). Finally, I came for an onsite interview. In total, there were four interviews, ea
The interview process included a phone interview followed by an on-site interview in Mountain View. The phone interview was 45 minutes long and covered topics related to hashing. The in-person interview covered variations on dynamic programming, bi
The process took quite long, about six weeks. I applied online and was a little bit surprised to get a response. There was one phone interview and four onsite interviews. It was a positive experience and has given me more interview experience.