If you want to create entrepreneurs you have got to change the way students are addressed, and give students control. However, academics don’t feel comfortable about this…
…Since there is no KPI [key performance indicator] for innovation it is difficult to have an EU instrument that is both satisfactory in terms of accountability and in terms of how innovation works
Think of “A Multiverse of Exploration: The Future of Science 2021” (PDF) as a star chart of possibility, pointing the way toward opportunities for wonder, knowledge, and insight. Use it to raise questions about how your life and work may change in light of the startling transformations that science may bring about in the next ten years. Indeed, every forecast could be rephrased as a “what if” question. What if you could record your dreams? What if you could design a life form? What if you could launch a company in orbit? Your answers to those questions can help inform decisions in the present. Inside this map, you’ll find plenty of space to think.
Caption: A girl walks past a tree covered in spider webs in a flood-affected area of K.N. Shah, located near Dadu in Pakistan’s Sindh province. The cocooned trees have been a side-effect of spiders escaping flood waters in the area. Although people in this part of Sindh have never witnessed this phenomenon, they report there are now fewer mosquitoes, thus reducing the risk of malaria. (Source: The Telegraph)
Fascinating system dynamics at work here!
What do software developers and water have in common? They’re both taken for granted by far too many people…especially MBAs!
Ireland has to have one of the most “agile” governments I know…one of the departments I deal with has been through three name changes in the three years I’ve been here…
The…
morphed into the…
which is currently the…
“One of the painful things about our time is that those who feel certainty are stupid, and those with any imagination and understanding are filled with doubt and indecision.”
- Bertrand Russell
Just discovered and am enjoying Jamestown Story, an alternative “easycore” band from Duluth, MN.
Business plans are fine for large companies where there is an existing market, product and customers, but in a startup all of these elements are unknown and the process of discovering them is filled with rapidly changing assumptions.
Google’s CFO, Patrick Pichette, recently reported that in the first quarter of 2011 over 600,000 people had applied for jobs @ Google, which is why I am humbled to recently have had the opportunity to interview for a Product Manager role with the Google team in Zürich. This post captures a few random thoughts on the experience which hopefully may be of use to other folks going through the process. But before diving in, a bit of housekeeping…
Why are you interviewing?
I think it’s important to start-off with the fact that I love my job. I get to work with absolutely brilliant folks who are researching the forefront of ridiculously cool digital technologies (you can get a glimpse here: http://www.cngl.ie/researchpub.html). I don’t need a new job nor do I necessarily want a new job which ironically enough is the perfect environment to consider new jobs because the bar is set so ridiculously high there is a low probability of taking a position for the wrong reasons…after all desperation is the codependent enabler of suboptimal decision-making!
Aren’t you worried your current employer will find out you are interviewing?
I have tried to be transparent about interviewing right from the get-go. Quite a few colleagues called my transparency “bold” and even Penelope Trunk says interviewing is one of the three times you should lie @ work! However despite what Penelope suggests, I think radical transparency is an increasingly important quality…especially as social media continues to erode the walls between work life & private life. Suppose it’s time for employers to just get used to it…kind of like how I got used to that whole all-knowing big brother, Google knows me better than myself thing! Cheers to progress!
Did you get the job?
Too early to tell…but with 600,000 applications I’m pretty sure there were folks much smarter than me who were interviewing!
UPDATE: Still too early to tell…but they are bringing me back for another round of interviews.
Enough already…tell me about the process!
Recruiter Screening:
It all started a few weeks ago with a phone screening with the recruiter. Was actually a fairly short 20 min. conversation with a few questions about my background, “why” Google and an explanation of their recruiting process.
Product Manager Screening:
From there I progressed to a 45 min. phone interview with an actual Product Manager. After a few perfunctory questions about my background the format switched to the standard case-based questions you so often read about. We only had time for two case questions, the first around product strategy and the second around analytics.
For the product strategy question I was asked how I would design a mobile application to increase literacy among a population of illiterate fisherman somewhere in the South Pacific. There was a good bit of dialogue between myself and the interviewer as he moved me through the case. Key points that came up in the discussion included things like the type of interface/UI, prototyping, network, bandwidth & device constraints, information requirements, cultural preferences, etc.
For the analytical question the interviewer explained I had 8 identical-looking balls, one of which was slightly heavier than the other 7 (all of which weighed the same). Using an old-fashioned balance he asked me to determine the heaviest ball in the least number of weighings (answer here). After answering his first question we then went back and forth as he asked me to try to identify patterns and a potential formula to calculate the least number of weighings for n=2,3,4,5… balls.
Ultimately I felt pretty good about my answers to the strategy question and while I didn’t give-up on the analytical question I felt that I should have performed better. Subsequently I was delighted when the following week I received an invitation to participate in the next round of interviews in Zürich.
In-Person Interview x3:
In Zürich I was scheduled for three 45 min. interviews each focusing on a different area:
The first two were with Product Managers and the third was with a software engineer.
During the product development interview I was given three questions. First I was asked how I would design a cell phone for the 10-15 year old segment of users. Key themes that I hit on included observational studies, emerging usage trends, novel features (ad-hoc mobile social networks using near-field communications), OS interface, physical design, etc. For the second question I was asked to provide general commentary on the Android/IOS market dynamics and secondly provide specific recommendations for both Apple & Google. Finally I was asked what issues I would like to address if I were to build a task management system from scratch.
For the analytical interview I was again walked through a set of three questions designed to gauge the ability to analyze Fermi problems. For the first question I was asked to estimate the digital storage requirements for all of the books in Ireland. Ultimately I did come up with a number but there were more interesting discussions around the assumptions I was making, ways to test & verify them and implications of the law of large numbers. For the second question I was asked to devise a strategy to verify the data quality of a new 3rd party information vendor (think local business YellowPage listings.) Ultimately I came up with three strategies (the crowd, comparisons with a gold standard and an automated process using speech synthesis/recognition) all of which relied upon a random statistical sampling of zip codes.
For the final question I was asked how I would increase participation in the authoring process on Wikipedia. My answer assumed a gaussian distribution of users with a long-tail of active contributors between 2σ-3σ. I was originally looking at strategies to encourage usage within a band of 1σ around the mean, but as I was working my way through the question I refocused on the band between 1σ and 2σ, with my reasoning being these were folks on the edge that could more easily be encouraged to engage by strategically leveraging some of BJ Foggs frameworks on persuasive computing.
During the final technical/engineering interview I was given another question very much styled after the one in my phone screen: assuming a person is standing at the bottom of six steps and can go up either one or two steps at a time, how many different ways are there for the person to get to the top? A relatively straight forward question which I would come to discover most people (including me) attempt to solve using factorial combinatorics. After arriving at the answer for n=6 stairs I was asked to find the pattern for n=2,3,4,5 and eventual 60 stairs, in which case factorials quickly become cumbersome. There is an amazingly elegant solution, which I didn’t pick up on, but I was somewhat comforted by the fact that when I got back to the office and presented the question to 3-4 post-doctoral researchers no one else saw it either!
Overall Thoughts:
Google is in a perpetual state of hiring which I imagine is a logistical nightmare, yet through the whole process the Recruiter and Recruiting Coordinate did a fantastic job keeping me briefed, explaining next steps and getting me to where I needed to be.
With the Product Manager roles it seems like Google is looking for 3-D intermediaries, folks who, while not necessary an expert in all of the areas, can operate across strategy, design and engineering disciplines. I get the impression they are looking for classic T-shaped people who have a diverse background and broad skillset.
I tend to be a lateral thinker, which means my answers can sometimes appear disjointed. If you are a lateral thinker I think it is worthwhile practicing linear techniques for case interviews, as they will help structure and increase the coherence of your answers as you work through the process.
Finally, perhaps I am weird, but I actually enjoyed the process. It was a refreshing and thought-provoking change from your standard “what are your top-3 strengths” style interviews. I can’t stress enough the importance of going in and trying to have a bit of fun through the process.
FYI: Don’t wear a black suit & tie to the interview! The lad that came in shortly after I arrived looked about as out of place as Richard Dawkins at a Discovery Institute strategy session!
Due to the interdisciplinary nature of interviews I think preparing for them is a challenge, however for those inclined here is a list of an additional 25+ Google-style questions I stumbled upon as I was prepping for the interview.
Google Interview Questions: Product Manager
In this installment of the Design Challenge we are pitting the European Commission against those ever sensible Swiss.
According to the estimates of people who specialise in estimating such things there are roughly 400,000 escalators in operation worldwide, which collectively generate a power bill North of $260 million a year (seems kind of low but since I’m not an escalator expert, lets just go with it!) As such energy-saving “sleep mode” escalators, which only begin operating as people approach, have become all the rage particularly in Europe. Seems like a win-win solution for everyone…we save the planet by reducing energy consumption and at the same time enable the ever expanding waistline of the world (SCORE!)
Here’s where things get interesting. When you approach a pair of normal escalators, which are 10’-15’ in front of you, your brain interprets explicit visual cues (one going up & one going down) and in a millisecond generates a P3a response which sends you along a trajectory in the right direction. Things start to get a bit fuzzy when you approach a pair of stationary “sleeping” escalators, which only begin operating after an infrared beam located ~5 feet from the first step is triggered.
Which brings us back to the two polaroids up above (click on the photo for a higher-res version). The picture on the left is from a European Commission building in Brussels. You can’t tell it from the resized picture but there are actually four escalators next to each other in the following arrangement:
Lower Flr - Upper Flr - Upper Flr - Lower Flr
I happened to be there for a conference and what I observed repeatedly over the course of three days were the results of shoddy design. In the absence of visual cues (moving stairs) people who wanted to go down to the ground floor would continually walk up to the “sleeping” escalator on the left, trigger the infrared beam @ 5’, and then almost trip as they stopped 1’ short of the first step which was going in the “wrong” direction (in this case up).

To be fair the escalator manufacturer must have recognised this would be an issue, so they implemented a replacement visual cue, but the design and placement of that cue was so poor it almost seems as if it was an afterthought. Based on observations it seems like the vast majority of people failed to recognise that small red “stop” light, which was behind the reflective plexiglass on the right and out of their direct line of sight, from 10’-15’ away. Of course that bright accent light on the blue walling, pulling eyes upwards didn’t help the situation either!
Contrast this to the picture on the right which was taken in Zurich Airport. As I was waiting for my flight I must have watched this escalator go on and off about 20 times while at least 100 people streamed down without issue. By simply moving those indicator lights 2’ forward and upwards to eye-level the designers were able to transform a halting and inarguable dangerous situation into a seamless experience that no-one (expect a design geek like me) thought twice about!
European Commission: 0 Flughafen Zürich: 1