Getting an User Experience Research Internship at Google

April 2017

GENERAL

There are two roles someone with a background in user research / HCI can take: One is the User Experience Researcher (UER) and the other one is the scientific researcher. The User Experience Researcher works closely with the product manager, engineers and designers on a particular product and helps to drive product design questions. The scientific researcher works on broader research questions that are often not specific to a product – their work often gets published. If you want to continue doing research similar to the projects you do at University, then scientific researcher may be best suited. If you want to work with real-world products and have direct impact on millions of users then User Experience Researcher may be best suited. All notes below are about the User Experience Researcher role but I would be happy to connect you with someone who just completed his DPhil and now works as a scientific researchers at Google.

 

Google’s HQ are in Mountain View (MTV) and most (interesting) work is done there. There are some other offices where User Experience Researchers work, including London. I recommend applying for a User Experience Researcher position in MTV. You can only apply in NA or Europe, not both. Once you started an application for one continent you can’t switch.

 

User Experience Research falls under “Engineering” (fields of work).User Experience Researchers  at Google are either qualitative or quantitative, or both. It’s okay to have a qual focus and not be strong in quant. Just make sure to point that out in your application and to your recruiter to manage expectations.

 

What kind of work you do in your internship depends on the team you are matched. I conducted eye-tracking studies, large-scale experiments, large-scale surveys, interviews and ethnographic field observations. I learned a lot in terms of methods and data analysis but also about effectively collaborating with stakeholders to operationalise research findings (something we academic researchers often have little experience in).

 

Some of the things that stood out to me during my User Experience Research internship in MTV was a culture where user research was understood to be crucial and highly appreciated (which is unfortunately often not common in other organisations or even Computer Science). There are hundreds of UERs working at Google and they have weekly/monthly/yearly meetups. The support for user research studies was outstanding. Google has dedicated teams that help with conducting studies (e.g. participant recruiting, legal aspects, etc.). This support goes so far that you can even have certain types of research studies completely conducted for you if you choose to. This frees up time for you to fully focus on designing studies and integrating research findings.

 

The infrastructure is also outstanding. Example; Google builds their own labs and fleet of user research vans all around the globe. And the financial support for studies is also fantastic. I got granted $1.000 for participant reimbursement within an hour, for example. This support is available to all UERs and interns. This lead to a role that could be described as ‘senior’ User Experience Researcher in other organisations – where you have teams working for you, to ‘enable’ your research. You can concentrate on the fun parts like designing studies, analysing and integrating findings.

 

The people are also genuinely nice and supportive – to a degree that I haven’t experienced in any other organisation.

 

One aspect that an academic researcher may be perceived as a drawback when working as a User Experience Researcher at Google is the product-centred nature of the work. While you still can publish papers, most of your work will be about improving the user experience of a product. If this is a strength or weakness will depend on your attitude/definition of ‘impact’.

 

To summarise, you will face a research environment that truly appreciates user research, uncomparable support in terms of infrastructure, finances and work force to conduct research studies, and interesting and motivated people.

 

How User Experience Research work differs from our academic work

As you may have sensed from the description above, the work focus shifts somewhat from analysing data to designing studies purposefully and feeding findings effectively back. Your main responsibility is not only to analyse data but to design studies appropriately so they will lead to impact on your product. You will need to collaborate closely with the product team and understand what research questions are most pressing, and then to communicate findings in a way that they will lead to actual impact. In our academic work, the analysis of data may be most ‘challenging’. The challenges I faced as a User Experience Researcher shifted more towards understanding what findings would be needed to drive pressing product decisions and how to effectively communicate them to product managers and engineers and work with designers to incorporate them into the product. It is not enough to have ‘interesting’ findings if they lead to no impact on the user experience.

 

UX and UX Research at Google

 

 

You will need a reference from someone working at Google otherwise your application will get lost. A reference will increase your chances of getting to the interview stage. You will need a tailored CV and motivational statement. A portfolio showcasing some of your work is not necessary but can help.

 

Interviewing tips

I am happy to answer any questions you may have!

Jan

 

Analysing the freelancing market (ODesk & Elance)

[WORK IN PROGRESS]

Hi all, I am Jan and I am passionate about human-computer interaction, product design and entrepreneurship. I am currently reading for my PhD in Computer Science at the University of Oxford, where I am researching (together with the MoD and Airbus) ways to improve the situational awareness of our nations’ cyber defenders by conceptualising the management of cyber threat intelligence and developing technologies that support their practices.

I used Kimono for my research, to efficiently put a database of cyber security companies together that I then used to reach out to selected organisations for a potential collaboration (it was very helpful). Right now, I am experimenting with ways to help me track and analyse the freelance market (Elance and ODesk) in regard to supply and demand. This has nothing to do with my research and is just out of curiosity. I am interested in the concept of productised services and explore the usefulness of transferring some of the concepts of keyword analysis (from SEO) to this domain.

But on a bigger picture, I want to explore the usefulness of web data extraction approaches that support day-to-day/operational and also strategic decision making in SMEs (small and medium-sized enterprises).
I would love to talk to anyone who has an opinion, experiences or ideas in this area.

 

So here is what I did:

 

1. Find the pages that output “all results”

For Elance, this is https://www.elance.com/r/jobs/sts-0
/sts-0 displays jobs with “any status” and doesn’t limit the results to jobs which “hiring (is) open”. If I would only scrape jobs that are open, I will miss a great deal of data, since we will scrape on an hourly basis and jobs are often allocated within minutes.

For ODesk, this is https://www.odesk.com/o/jobs/browse/st/-1/
The same holds for ODesk. /st/-1/ displays all jobs independent of their hiring status.

 

2. Configuring Kimono (the web scraping application)

Click on the fields that you want to collect and give them a variable name. Easy. See here for help how to use Kimono.

 

2. Scraping the base data set 

I want to scrape all displayed results once (these will be around 47.000 results for ODesk and 26.000 for Elance). This will give me the data set that I will add to with later scrapes and mirrors the current job openings on these platforms. Important here is to set the pagination correctly in Kimono (here for more information) and set “pagination limit” to “10000 pages max” under the “CRAWL SETUP” tab of both APIs. And I had the “AUTO-RUN FREQUENCY” on “manual crawl” – I only need the base set scraped once.

The first crawl may take a while to run through. I looked at the results of this scrape and made sure the outputs were as expected.

 

3. Setting up the auto-run feature to track new jobs

To determine the crawl frequency in regard to pagination limit, I went to the Elance and ODesk pages and checked several times a day through how many pages new job posting from within the last 60 would stretch. On Elance, job posting from the last 60 minutes will stretch through an average of 6 pages. On ODesk, this is 1 page.

I went back to the “CRAWL SETUP” and changed the “pagination limit” to “10 pages max” for Elance and “1 page max”.

 

 

Implications for design (Kimono)

  1. Ability to set a custom number for the pagination limit.
  2. Ability to add-to previous crawls when using the auto-run frequency.

 

[WORK IN PROGRESS]

 

Open Education at Oxford Entrepreneurs

Today I had a meeting with two brilliant minds; John Burk Stringfellow, the new President of Oxford Entrepreneurs and Yuning Chai, an Associate Intern at McKinsey and also a committee member. Oxford Entrepreneurs is the largest student society at Oxford University and the largest student society promoting entrepreneurship in the world. As of September, I will be honoured to become part of the committee and begin working on some exciting projects. One will be OE Podcasts, an initiative that draws upon the principles of open education. The concept for the upcoming online series came up when John asked me for ideas for the upcoming year. I pitched him the following high-level concept:

“Oxford Entrepreneurs’ (OE) mission is to inspire and educate on the highest level, and provide an outstanding network, competition and support. In order to achieve our mission and continuously become better, we are dependent on the following:

Moving to Britain and the Motivation Behind my Studies

Quite a few exciting things happened over the course of the last months. I graduated from university, did an internship in Silicon Valley and started my Master’s degree at the University of Birmingham in Britain.

Graduating university with a major in Computer Science and a minor in Game Development, my coursework and work experiences increased my interest in the relationship between humans and computers, clients and end-users. I realized by way of my studies of Game Development, that games are different to traditional software systems in the sense that most software is designed with the purpose of either rendering the user obsolete, or of supporting a user in performing a task. Games on the other hand are solely developed for entertainment or educational purposes. For me, this is a very intriguing aspect, as user experience and satisfaction should therefore play an even more significant role.

 

Read More

The Miracle of Customer Feedback

The reason I choose to work as a Community Manager at Gameforge back in 2011 was the ability to study the behavior of customers in the context of product failure. And that’s what it was, serving 300 customer tickets a day as the initial point of contact for inbound requests, I was supposed to “creatively and proactively assist users”. But apart from helping customers with questions, difficulties, bugs and trying to knock out negativity with sheer kindness, I also received once in a few weeks user feedback on the product.

At first I was agitated and upset when faced with negative feedback like this one: “The login process is completely counter intuitive! I am not able to login with my username! What are these guys thinking!” I was upset because the user was venting and had simply not realized that you need to login using your email address, because usernames in our system were redundant.

But now, a year later, working at a startup and proactively looking for feedback from users and investors, I realized the following:

If I had lined up our visitors per month shoulder to shoulder, they would have reached over 100km. Now imagine driving past at 50km/h, trying to look at each and every face swishing by one at a time. After 30 minutes I would be absolutely numb trying to see that many faces. Imagine how big that group is! Out of all of those people, how many are going to reach out to us and give us feedback on our product? Looking at the sheer size of that group, how many would contact us to complain if something was wrong? Even 0.1% would be thousands of people giving us feedback. Which clearly does not happen. Of all those faces, all those customers, it is less than one in a million who take the time to contact us to anything personal about what we are doing.

On the first impression, identical to the other requests, feedback does distinguish in the underlying motivation of the user. Unlike a particular action or information a customer is trying to receive by contacting us (e.g. getting to run the software after an update or to revoke an account suspension), the customer has no other intention but to interact with us when giving feedback (e.g. how our new product update completely sucks or telling about how awesome feature XY is).

This is a miracle.
Of all the things the coustomer could have been doing in that moment, like quitting the application or searching for an alternative product from our competition, he chose to interact with us. This is a miracle. The fact that he took the time to say anything, whether positive or negative, makes him extremely special.
In my role at Fair Observer, I am currently trying to get a grasp of our stakeholders perceptions to improve our product. Getting feedback is highly valuable, especially at our current seeding stage. We should treat any feedback we receive as a miracle and get a warm feeling when thinking about all of our disgruntled web site complainers.