Google interview notes, page 101 of 215

“My first instinct was recursion but I fumbled explaining it out loud.” The rest of the author's notes on Software Engineer interview at Google, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight to regex and said we could just compile each pattern and run them all.” The rest of the author's notes on Software Engineer interview at Google, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is basically two questions stitched together and they expect a real answer, not just 'scale and impact.' I fumbled a bit because I hadn't thought hard enough about what actually separates Google Research from the other big labs.” The rest of the author's notes on Software Engineer interview at Google, Recruiter / HR Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight into the story and forgot to set up why the engineers were skeptical in the first place, which is kind of the whole point of the question.” The rest of the author's notes on Product Manager interview at Google, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The counting part felt approachable once I framed it as a DP over positions in the string, basically dp[i] = number of ways to decode the first i characters.” The rest of the author's notes on Software Engineer interview at Google, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I spent too long on the 'should they do it at all' part and barely got to the pricing mechanics, which was clearly the more interesting half of the question.” The rest of the author's notes on Product Manager interview at Google, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight for a star schema with a fact table for orders and dimensions for products, customers, time, and sellers.” The rest of the author's notes on Software Engineer interview at Google, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with US air travel volume and tried to work down to SFO's share based on it being a major west coast hub.” The rest of the author's notes on Product Manager interview at Google, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“One of the panelists lit up about the storytelling structure, which was a relief because I'd spent way too long agonizing over the deck flow.” The rest of the author's notes on UX Designer interview at Google, Onsite - Multi Round round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The multi-example part is what gets you.” The rest of the author's notes on Software Engineer interview at Google, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.