376 karma · joined July 8, 2009
It might be a little uncomfortable for someone like me. I'd rather you ask, "what are your favorite qualities in your best employees" and then respond to that.
Maybe it's just my area of work but I can't imagine caring about previous experience, degree, or anything. I mean, the candidate has gotten past the resume screen already so you're just living up to that impression and other candidates at that point.
Maybe I just spend too much time listening to the radio and podcasts? Maybe it was growing up in an era where voice phone conversations were more common than texting and facetime?
It's good to see that maintenance is rewarded at Google at least occasionally. I only ever hear that it is only new products that are rewarded. And I notice new people piling on to issues in their product trackers that I've been following for years.
100% agree about probability and stats, that stuff is not intuitive nor easy to pick up outside of school.
Then your question is about optimizing on top of the usual architecture which hopefully is an infrequent source of pain that is worth the cost of making it faster. I could imagine some clever caching, Service A and Service B both subscribing to a source of events that deal with the data in question, or just combining Service A and B into one component.
Maybe it'd work best asked in an abstract, impersonal way: "I've had friends whose contributions have been dismissed because of their gender; what kinds of strategies can combat bias and create a positive environment for all employees?" Ideally this would lead into a nice 5 minute discussion where you could get a feel for their thinking.