Why Google, Handling a Rejection, and What You Expect From a Manager

This is a behavioral ("Googlyness") round for a software engineering role at Google. The interviewer asked two questions, each with follow-ups.

Clarifying Questions

• For the manager question, should the answer draw on managers you have worked with, on times you led others informally, or is a purely hypothetical answer acceptable?
• When the interviewer asks what you would do if you do not pass this time, are they probing how committed you are to this company or how you handle setbacks?
• In the delivery question, is "extra effort" about your own willingness, or about asking it of a team you manage?

Part 1 — Why Google, and what if you do not pass

Why do you want to work at Google? And if you do not pass this round of interviews, what will you do?

What This Part Should Cover

• A motivation specific to this company and role rather than one that fits any large tech company
• A plan after a rejection that shows reflection and a concrete next step, not bitterness or indifference
• Consistency between the stated motivation and the plan if this attempt does not work out

Part 2 — What you expect of a manager, and how you would act as one

If you were a manager, what would you expect from a manager, and how would you live up to that yourself? How would you handle project delivery, balancing the interests of upper management against those of your team, and putting in or asking for extra effort when it is needed?

What This Part Should Cover

• A small set of explicit expectations of a manager, each tied to an observable behavior
• How delivery commitments are set, tracked and renegotiated
• How a conflict between leadership's asks and the team's well-being is surfaced and resolved
• When extra effort is justified, how it is shared, and how it is kept from becoming the norm