Interviewing @ Google Zurich PgM

Interviewing @

Zurich

This guide is intended to add clarity to the role & responsibilities of a program manager at Google. It will also give a clear overview of the recruitment process and help you best prepare for your upcoming interviews with Google. If you have any questions, please don't hesitate to get in touch. OFFICE, PEOPLE & PROJECTS (Some information about the zurich office, the diversity of the office and the different projects that are worked on)

ROLE & RESPONSIBILITI RESPONSIBILITIES ES (A detailed description of what a software engineer at Google actually does)

RECRUITMENT RECRUIT MENT PROCESS PROCESS (A step by step guide to moving through the process and securing a role at Google)

INTERVIEW PREPARATION (How to prepare for the phone and onsite interviews at Google)

HOW TO PREPARE (Info on areas you should prepare for )

INTERVIEW TIPS (Our additional tips and tricks taken from our experience)

The office, people & projects

The office Zurich is Google’s largest engineering office in Europe, the Middle East and Africa. We like to think of ourselves as “the real Mountain View.” Not because we're the company’s engineering headquarters for EMEA, but because of the views out our top-floor Sky Lounge windows. Our office has a different design theme on each floor, massage stations, two gyms, micro-kitchens, a sleeping room and restaurant-quality food.

Useful links Office location & Streetview Office pictures Zurich information YouTube video Life @ Google

The people With Googlers coming from across the globe, Zooglers are an especially diverse bunch. Take a twominute walk through the cafeteria, and you'll probably hear more languages than you can count on both hands. The very high level of expertise among our Zooglers is one of the most appreciated facts why Googlers like to work in Zurich. We are proud to have an environment where everyone can learn from each other. You can also find some cool videos with Zooglers on the left.

The projects Googlers in Zurich do important work across our technology groups, and our launches have included Maps for EMEA, Search refresh, key Gmail f eatures like the priority inbox and account abuse protection, and content ID and monetization products for YouTube. Other key projects we have in Zurich include Shopping, Ads, Calendar and Spam & Abuse

The role & responsibilities of a Program Manager @ Google

The role Google's projects, like our users, span the globe and require managers to keep the big picture in focus. As a Program Manager at Google, you lead complex, multi-disciplinary projects. You plan requirements with internal customers and usher projects through the entire project lifecycle. This includes managing project schedules, identifying risks and clearly communicating goals to project stakeholders. Your projects often span offices, time zones and hemispheres, and it's your job to keep all the players coordinated on the project's progress and deadlines.

The responsibilities Useful links Google jobs Meet other Googlers Research @ Google Program Management in Emerging Markets

Program Managers at Google are responsible for identifying and proposing new projects (often based upon experience elsewhere in the world). You'll manage and deliver projects, executing them in time and budget, and with multiple stakeholders, in a specific country or region. Program Managers effectively operate with high energy and flexibility in a fast-paced, constantly evolving team environment, and effectively influence and communicate cross-functionally with all levels of management.

A Googler's perspective

"

“ On my very first day as a Program Manager in Google, I immediately interacted with various internal  stakeholders, getting up to speed with our products and how we execute in a global market. In my first  few weeks I learned so many things and worked with cross-functional teams on a regular basis, I ended up getting involved with aspects from product features all the way to vendor management in my first few months. I was in charge of my own projects, set my own working pace, and be fully responsible to drive their success. I enjoyed a rewarding experience and full of growth opportunities I wouldn't get elsewhere. .

"

The recruitment process

Hiring process Google's interview process is the same globally. This consistent global approach allows engineers the opportunity to develop their future career within Google both geographically and across project changes. You can find a quick overview of the hiring steps below. Your recruiter will conduct an initial call with you and be your partner during the whole process, keeping you updated throughout. Please bear in mind that things do take time. :)

Useful links Interviewing @ Google

Phone Interviews

Up to 2 x 45 min interviews with Program Managers.

On-Site Interviews

Up to 5 x 45 min interviews with a mix of Program Managers and Stakeholders.

Committee Review

All interview feedback is reviewed by an independent committee, who take a vote on whether we progress.

Offer Review

We will gather things like references, transcripts etc, and submit to management for approval locally and then in the US.

Offer!!!

If everything is approved, we will make you an offer and confirm this to you in writing.

Interview preparation

Before you start Before you get started preparing for your interview, you can get an overview of interviewing with us,  here. We highly recommend that you do your research about the interview process at Google, and a great place to start would be finding out How we hire. You can also check of Steve Yegge’s blog about Getting that job at Google.

Interview questions

Useful links

The interviewer is interested in knowing your project management aptitude and your experience with project management methodology. Other interview topics may cover analytical thinking, relationship management, leadership qualities, ability to take ownership, organization, strategic thinking and ability to demonstrate technical knowledge.

About us The Google story

What is Google looking for? Focus on demonstrating your project management and problem solving skills, applied to the question asked: if it's a project management question, providing an effective get things done approach to solve the problem is the key; if it's a general analysis question, show that you understand all particularities of the problem described and where applicable offer multiple solutions, discussing their relative merits. Every Interviewer ultimately wants to answer the question of whether they'd be comfortable working with you on their project.

How to prepare

The interviewing focus will depend on the specific role you’re applying for but these are general areas;

Role-related Knowledge: We’re looking for people who have a variety of strengths and

(Part 1)

passions, not just isolated skill sets. We also want to make sure that you have the experience and the background that will set you up for success in your role. For Program Manager candidates in particular, we’ll be looking to check out your project management skills.

Leadership: We’ll want to know how you’ve flexed different muscles in different situations in Useful links

order to mobilize a team. This might be by asserting a leadership role at work or with an organization, or by helping a team succeed when you weren’t officially appointed as the leader.

Cognitive Ability: We’re less concerned about grades and transcripts and more interested in How we hire Non Technical Interview Tips

how you think. We’re likely to ask you some role-related questions that provide insight into how you solve problems. Show us how you would tackle the problem presented--don’t get hung up on nailing the “right” answer.

Googliness: We want to get a feel for what makes you, well, you. We also want to make sure this is a place you’ll thrive, so we’ll be looking for signs around your comfort with ambiguity, your bias to action and your collaborative nature.

Knowledge: Domain knowledge and project management aptitude - basics / blocking and tackling.

Take Ownership: Problem solving - taking responsibility and ownership to rectify things or make systems and processes work smoothly.

Organised: Flexibility, persistence, drive, innovation and troubleshooting. Strategy: Understand Google’s competitive landscape and discuss the vision for Google, search market, the ad market, the internet, and technology in general as well as understanding markets specific to the role.

Interview tips

Interview tips ●

●

●

Useful links Interviewing Questions Getting that job @ Google

●

●

●

●

Make sure that you substantiate anything your CV/resume says – for instance, if you have specified you are an expert in a particular subject, questions about this are fair game and may be asked of you. Talk through your thought process about the questions you are asked. In all of Google's interviews, we are evaluating not only your technical abilities/role-related knowledge but also how you approach problems and how you try to solve them. Ask clarifying questions if you do not understand the problem or need more information. Many of the questions asked in Google interviews are deliberately underspecified because our engineers are looking to see how you engage the problem. In particular, they are looking to see which areas leap to your mind as the most important piece of the problem you've been presented. If you need to assume something, be sure to explicitly state it and check that it is reasonable. Think about ways to improve the solution that you present. In many cases, the first solution that springs to mind isn't the most elegant and may need some refining. It's definitely worthwhile to talk through your initial thoughts with the interviewer. At the end of the interview, most interviewers will ask you if you have any questions about the company, work environment, their experience, etc. It’s clever to have some preprepared for each interview. Remember that all of your interviewers have been through this process as well.

Sample questions ●

●

●

Tell me about a time when a project you were managing was running seriously behind schedule, and what did you do about it? How do you keep track of project information? If you were going to use a spreadsheet to track tasks, what columns would your spreadsheet include? How would you organize a project to do X? What tasks do you think would be important? What are the risks, and how would you mitigate them? How would you keep people informed of how the project is going?