These examples are weak! They're common questions asked over and over... Things you can just look up if you use blind, levels.fyi, glassdoor. "What's the size of the company?" Come on...<p>Don't burn your time with filler. Instead, make yourself stand out in the last moments:<p>The questions should be softball, but detailed and enjoyable for the interviewer to answer. Allow them to paint the role and company positively. i.e. don't dig into Google's stance on user privacy.<p>Use questions to show your enthusiasm-- that you're here for <i>this</i> job and not a job.<p>You should do research on the company and interviewer before the session. What they are involved in? (languages, concepts, methodologies). Usually blogposts, GitHub and LinkedIn content is useful.<p>Try to impress the interviewer with your knowledge about said role, company, or relevant topic. Mention a change or new beta product you've been testing. Ask for their thoughts on something you know they like to talk about.<p>Examples:<p>Does google have plans to expand the usage of Go in their cloud stack?<p>What benefits were there after switching from Borg to Kubernetes?<p>How do people get new ideas get onto the Pub/Sub team's radar when they are busy shipping features at breakneck speed?<p>How did the team architect the new protobuf API while maintaining compatibility with the old one?