Good office (cafeterias, gym, swimming pool) and good perks.
There are challenging and interesting projects at Google in principle.
Depending on the team, the employee experience can vary drastically from excellent to extremely bad. Late meetings, pings, etc. are unfortunately quite common.
Internal mobility opportunities were always very limited in the Dublin office. Basically, your only options in engineering are to transfer between different SRE teams, which is not comparable to the USA. However, after more recent events, it became next to impossible. A lot of teams are not open to working remotely or even working from a different office on a permanent basis.
Getting things done is next to impossible without a meeting. Working via emails, tickets, or docs is basically not an option, which is another reason why working remotely at Google is quite difficult. Meetings tend to be quite inefficient as well.
Be more open to remote work. Develop a culture where people don't have to stay late just to attend a meeting with the USA to get things done.
I passed all the interviews. However, due to their restructuring phase in 2022, they could not offer any positions in my preferred locations: Dublin, London, and Munich. Therefore, we closed the application.
I was contacted by a recruiter for an SRE position. I finished the first technical QA phone call with the recruiter. The questions were similar to those already posted by other candidates. I booked a phone screen after the short interview but did
5 phone screens and 5 on-site interviews. First screen with HR, asking quick questions (e.g., what's the opposite of malloc?). Multiple shared document programming tests in C and Python. On-site: * 3 programming interviews (2 in C, 1 in Python) *
I passed all the interviews. However, due to their restructuring phase in 2022, they could not offer any positions in my preferred locations: Dublin, London, and Munich. Therefore, we closed the application.
I was contacted by a recruiter for an SRE position. I finished the first technical QA phone call with the recruiter. The questions were similar to those already posted by other candidates. I booked a phone screen after the short interview but did
5 phone screens and 5 on-site interviews. First screen with HR, asking quick questions (e.g., what's the opposite of malloc?). Multiple shared document programming tests in C and Python. On-site: * 3 programming interviews (2 in C, 1 in Python) *