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

Also to chime in with the other Googlers here: apply. Apply. Apply. Apply.

There is a lot of varied work going on internally at Google. As well as the hard-core, intense, "pure" software engineering work that everyone thinks about going on at Google (search, self-driving cars, android, machine learning etc etc), there is also a lot of ... how can I put this nicely? erm ... lets say "less-pure" software engineering going on.

The hiring-bar is understandably high for the pure software engineers, but there are other roles. I am not a "software engineer" at Google (I am in another "less-pure" engineering role in the same office that was in the pictures in the article) but I still spend all day every day coding using the same equipment, tools, technologies and infrastructure as the "pure" engineers and we all get the same perks. The difference is that my work is mostly internal-only and generally wont get used by our end-users. And even if you're not a coder, there are still lots of roles that require technical skills to help our customers sort out their own technical problems.

Pre-emptive answers to potential questions:

* I just applied from the website for a job that sounded like a reasonable fit (not referral, no prior contact). The recruiters took it from there. Prior experience was a few years at IBM and a CompSci degree.

* Perks are good but I still do 8:30 - 5 each day, sometimes I work from home if I am feeling lazy. In my London office some people stay late, but usually just because it is easier to schedule meetings with team members in the US (time overlaps etc)

I want to work with eager, intelligent people so please I really do encourage anyone reading this to go take a look and apply. https://www.google.com/about/careers/

Good luck!



Would you be able to give some examples of job titles for positions that you would consider "less-pure"?


Sure - Technical Solutions Engineer, Customer Solutions Enigneer, Web Solutions Engineer, Application Engineer, Developer Relations Engineer are a few off of the top of my head.


From a SWE that's worked a lot with DevRel: these guys do the Lord's work; I have them in a pedestal. Cloud without DevRel would be like a pharma company researching new drugs, but without doctors that know how to diagnose patients and choose and explain the appropriate combination of treatments.

And they're also the ones that get to appear in most dev tutorial videos!


Why would you tells someone on HN who is probably a software engineer to apply to google for non software engineer roles?


I didn't read the comment as such. Comment author assumes (correctly I'm sure) that some people reading feel like they aren't good enough to work at Google because they aren't hardcore software engineers. The point was you can still code and get the perks even if you aren't that, you just won't be on the self driving cars or customer facing projects.


The point I was trying to make is that you do not need to be at the absolute top-end of software engineers to apply for and work at Google.

If you are, then great! But if you are not the very best-of-the-best that is fine as there are still options for you to work at Google and write code for a living, just you probably wont be working on the sexiest world-changing products.




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

Search: