Student Blog
Brought to you from your @GoogleStudents friends. From pre-university to PhD (and beyond), we got you.
The Google Test and Development Environment - Pt. 1: Office and Equipment
December 20, 2013
Re-shared from the
Google Testing Blog
.
When conducting interviews, I often get questions about our workspace and engineering environment. What IDEs do you use? What programming languages are most common? What kind of tools do you have for testing? What does the workspace look like?
Google is a company that is constantly pushing to improve itself. Just like software development itself, most environment improvements happen via a bottom-up approach. All engineers are responsible for fine-tuning, experimenting with, and improving our process, with a goal of eliminating barriers to creating products that amaze.
Office space and engineering equipment can have a considerable impact on productivity. I’ll focus on these areas of our work environment in this first article of a series on the topic.
Office layout
Google is a highly collaborative workplace, so the open floor plan suits our engineering process. Project teams composed of Software Engineers (SWEs), Software Engineers in Test (SETs), and Test Engineers (TEs) all sit near each other or in large rooms together. The test-focused engineers are involved in every step of the development process, so it’s critical for them to sit with the product developers. This keeps the lines of communication open.
Google Munich
The office space is far from rigid, and teams often rearrange desks to suit their preferences. The facilities team recently finished renovating a new floor in the New York City office, and after a day of engineering debates on optimal arrangements and white board diagrams, the floor was completely transformed.
Besides the main office areas, there are lounge areas to which Googlers go for a change of scenery or a little peace and quiet. If you are trying to avoid becoming a casualty of The Great Foam Dart War, lounges are a great place to hide.
Google Dublin
Working with remote teams
Google’s worldwide headquarters is in Mountain View, CA, but it’s a very global company, and our project teams are often distributed across multiple sites. To help keep teams well connected, most of our conference rooms have video conferencing equipment. We make frequent use of this equipment for team meetings, presentations, and quick chats.
Google Boston
What’s at your desk?
All engineers get high-end machines and have easy access to data center machines for running large tasks. A new member on my team recently mentioned that his Google machine has 16 times the memory of the machine at his previous company.
Most Google code runs on Linux, so the majority of development is done on Linux workstations. However, those that work on client code for Windows, OS X, or mobile, develop on relevant OSes. For displays, each engineer has a choice of either two 24 inch monitors or one 30 inch monitor. We also get our choice of laptop, picking from various models of Chromebook, MacBook, or Linux. These come in handy when going to meetings, lounges, or working remotely.
Google Zurich
Thoughts?
We are interested to hear your thoughts on this topic. Do you prefer an open-office layout, cubicles, or private offices? Should test teams be embedded with development teams, or should they operate separately? Do the benefits of offering engineers high-end equipment outweigh the costs?
Posted by Anthony Vallone
Post a Comment
Labels
A Day in the Life of a New Grad in Google Dublin
7
AdCamp
2
AdMob
11
Ambassador Program
14
APAC
7
Appy Trails
28
Back to School
4
Better Know a New Grad
1
Better Know an Intern
16
Better Know an Office
4
Black History Month
10
Caitlin Talks to an Engineer
9
Chrome Extensions
3
Chromebook
1
College Tips by Google
1
Community
14
Conferences
16
consortium
1
CSSI
5
Day in the Life
2
deSTEMber
1
Development Programs
1
Diary of a Business Associate Intern
1
Diary of a Summer Intern
41
Diary of a Summer Intern - Erika
9
Diary of a Summer Intern - Franklin
3
Diary of a Summer Intern - Jess
3
Diary of a Summer intern - Luke
3
Diary of a Summer Intern - Madelaine
4
Diary of a Summer Intern - Pablo
3
Diary of a Summer Intern - Rio
4
Diary of a Summer Intern 2012
18
Diary of an MBA Intern
2
Education
19
EMEA
44
Europe
7
Events
13
Exploring Design at Google
4
GHC15
6
Going Green
6
Gone Google
2
Google Code University
1
Google Code-in
1
Google Games
3
Google Japan
1
Google Lime Scholarship
1
Google on campus
2
Google Online Marketing Challenge
10
Google Science Fair
2
Google.org
1
Google+
6
Googlers
14
Googlers Beta
11
Grace Hopper
11
GradTips
9
Hangouts On Air
21
Inside ITRP
6
Intern Insights
31
Intern Program
73
Interns Making an Impact
7
Interviews
1
Jobs
5
just for fun
30
K-12 (Pre-university)
14
LATAM
2
Life at Google
17
Middle East
1
My Path to Google
26
My Summer at Google
15
My Summer at Google 2012
10
North America
4
Office Environment
4
Open Source
9
PhD
7
Products
94
Programs and Competitions
116
Recruiter Tips and Tricks
15
Rice Plus
4
Scholarships
56
Search
1
STEM
2
STEP
1
Student Tips
15
Students
13
Summer of Code
1
Teach Parents Tech
10
Tech Students
3
Tips and Tricks
27
Women in Engineering
20
Young Innovators
10
YouTube
2
Archive
2018
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2017
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2016
Nov
Oct
Sep
Aug
Jul
Jun
Apr
Mar
Feb
Jan
2015
Dec
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2014
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2013
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2012
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2011
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2010
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2009
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2008
Dec
Nov
Oct
Sep
Feed
Google
on
Follow @GoogleStudents
Interested in opportunities and programs for students? Visit
google.com/students
.
