Google Management Flashcards

1
Q

A situation when you deprioritized your team’s work for other team’s work

A
  • Data logging format issue
  • SS Tableau
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

A situation when you went with a suggestion from your team even when it was different from your own

A
  • Docker for WD. I suggested the team to create off-line development environment. The team was sold on docker butt did not want to build this off-line system. Instead, they identified areas which was blocker for them or will be in the future and built a system around that.

SS release - System was causing a lot of issues; I jumped in and we discussed solutions. One was that we allow user to leverage data warehouse caching directly. Team felt that the other changes (threading and fixing bug with unnecessary calls) solves the problem and performance won’t be user visible anymore. Team was already tired working for 2-3 qtr so I agreed that it’s good enough.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the biggest challenges your team is facing now?

A

Outsourcing - lots of collaboration and challenges

Data Infra - Migrate quickly to solve dependency. Support existing system in parallel.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

How do you handle people who are not team players?

A

First clarify, what do you mean by not being a team player on one hand it could be someone not agreeing to the teams decision. on the other extreme it could be someone who is in like creating a cultural nuisance. For the latter case, I have zero tolerance, I will provide strong feedback and try to course correct or take action as needed for the situation where it’s a communication problem I need to dig deeper to understand the root cause, is there a simple communication issue with someone? Do we need to rethink our decision or do we need to disagree and commit?
Cultural issue example Edward
Communication issue, example Juan

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

A situation you went beyond to communicate

A
  • WD outsourcing. People (´・_・`) about job, tz issue and wlb, future of the product. Worked with leads on concerns; updates in all hands and meeting with each engineer and also separate meetings with individual functions.
  • todea development and updating the studios and r&d teams - release papers, all hands update, stakeholder meetings etc
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

How do you measure the success of your project?

A

Did we achieve our goals- objective
Did we complete the project properly - crash, estimates etc - mostly objective
Are people happy working on this project? - subjective via retrospective

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Situations where you had multiple solutions? How did you handle it?

A

Todea - benchmark

BQ v Snowflake v Spectrum

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

A situation where you pushed back

A

DI layoff
Ruins V2
Todea client team work
Todea quality vs speed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Describe some goals you set for yourself and how did you deal with them?

A
  • Train managers to lead indirectly
  • Identify future of war dragons and work staffing accordingly
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Tell me about a situation where you had to solve a difficult problem

A
  • Overhaul data infra
  • Recreate entire game servers in new ecosystem
  • Hiring expansions when previously failed
  • Solving WD’s profitability issue
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Tell me about a team project you worked on

A

ETL, BQ

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

We all deal with difficult customers from time to time. Tell me about a challenging client-facing situation and how you handled it.

A

Ss marketing

SS wd product - slow to adapt; can’t do auto-migrate. Worked with the whole group to identify some key features they were concerned about and planned out the migration.

PX tool kept asking for features - synced with product and set clear expectations on what we mean by support and how to prioritize requests

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Describe a time when you improved a process with a limited budget

A
  • DI FF slack bot
  • Rebel Sky docker
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Tell me about a time when you made sure a customer was pleased with your service

A

KS (constant feedback, documentation, presentation)

BQ (Migration tools)
Ss migration
API Atlas

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Describe a time when you found it difficult to work with someone from a different background

A

Jim (support team mentality and non Engineer)

Jim (RTB and feasibility issue)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Tell me about a time when you came up with a new approach to a problem

A

Redshift always crappy
DI FF slack bot
KS -> Todea aka central platform team
WD outsourcing to continue the product profitably

17
Q

Tell me about a time when you missed an obvious solution to a problem

A
  • Redshift issues
  • LSP needed caching
  • Data Platform performance issue
  • WD outsourcing eng skill mismatch
18
Q

Tell me about a time when you missed an obvious solution to a problem

A

LSP - Caching was necessary
Redshift
WD outsourcing language per engineer. We later realized better alternative is to split the tech stack per engineer instead of doing what we do best

19
Q

Tell me about a time when you took the lead on a difficult project

A
  • Management challenge: War Dragons team. Revenue going down, motivation low; identity how to continue cost cutting and find successor of this while making profits.
  • Todea: technically challenging and quite a large undertaking. Scale the team and incrementally build the infra and sdk to show business needs.
20
Q

Tell me about a time you recovered from a difficult situation

A

WD transition - I had data infra and creating todea when WD with 18 engineers was handed to me with 0 managers.
I fast tracked DI manager transition; I hired one manager and started training for another internal manager. Around the same time, VP asked to lose 33% of headcount to the new game.
It was a management nightmare. Train managers while maintaining a sense of stability in the team but also losing a significant headcount.

Todea collaboration issues - Chef had a ton of project requests. Most engineers were leading individual projects. Collaboration and integration was becoming a major headache.
I worked with the chef manager and identified ways to break the work into categories for multiple pods. We also agreed to create x-team pods with DRI for pm/TL and gave them full autonomy to manage their project. This was unique as the pods had no strict management chains. I continued collaborating with Chef manager to ensure things work smoothly from side.

21
Q

Give me an example of a time you faced a conflict while working on a team. How did you handle that?

A

Manager conflict: Layoff for DI, WD -> Chef, LSP tech choice

Peer conflict: Marketing SS, Runes V2

Report conflict: SS performance improvements, Docker for WD

Resolving conflicts: Juan, Yu Guan, Soul DU

22
Q

What’s your greatest strength? And weakness?

A

Strengths: Understanding root problems.
Mentoring people. Stakeholder management.

Weakness: Imposter Syndrome.
Direct communication.

23
Q

What is the most difficult decision you made and why was it difficult

A

Layoff - I trained them and even promoted a few. Not their fault. Had to be extremely objective to decide who stays.

WD outsourcing - First time in company history; jobs will be impacted; transition would be challenging.

24
Q

Tell me about the toughest decision you’ve had to make in the past six months

A

Letting Sol join WD team

25
Q

Describe a long-term project that you managed. How did you keep everything moving along in a timely manner?

A

Todea
Broke down the project into small chunks
Collective estimation
Build the roadmap and staffing plan
Checkup
Bi weekly update with team
Monthly leadership meeting for status and course correction prioritization

Learning
- risk assessment would be better if done by individual component
- Beyond 6/7 folks, staffing up has new challenges; specially when multi team/managers are involved.
- company Priorities changes and need to adapt

26
Q

An example when you had to push back to HQ or challenged a decision

A
  • DI layoff - success
  • LR tech decision - failed
  • WD reduced staffing plan before investing in automation ???
27
Q

Let’s say you’re working on a major project and you’re in the weeds. How do you find your way out?

A

Depends

28
Q

Tell me about a time when you were not able to meet a time commitment. What prevented you from meeting it? What was the outcome and what did you learn from it?

A
  • WD event release: UX complaint
  • Todea feature delays (unclear reqs) - focus on clearing the requirements from stakeholders with paper trails
29
Q

How would you convince your team to adapt a new technology?

A
  • Why do we need new tech?
  • ROI
  • Migration plan
30
Q

What is your project management philosophy?

A
  • Vision: Ensure everyone knows the goals and motivations of the project
  • Democratic: Planning and estimates are finally done by the team together
  • Execution: I work as a coach making sure people have everything they need and unblock them to prepare for the big win
31
Q

What is your project management philosophy?

A

Mentor people
ROI and impact-based prioritization
Lead team with a strong vision

32
Q

What is your project management philosophy?

A

ROI and impact-based prioritization
Build MVP and prototypes to test your theory
Continuously evaluate priority

33
Q

A situation when you acted based on your team’s feedback

A

WD docker - local development wasn’t needed; instead build content scripts

SS - enough work done. Let’s move on.