Evolution of Google’s Testing Organization and Career Paths for Test Engineers

Google’s Engineering Productivity (EP) team originated from the original Google testing group and has evolved dramatically over the years, as illustrated by the timeline below.

2001 : With over 200 software engineers, Google employed only three manual testers who performed hand‑crafted testing.

2005 : As the engineering staff grew to more than 1,000, the number of manual testers rose to over 50, scattered across product teams, primarily providing "Test Service" for manual testing. Testers who could code were eventually moved to software development roles.

2006 : Google began its software development model transformation, adopting the "Shift Left" testing approach. All testers were consolidated into a single department, partnering closely with product teams and taking on a QA role.

2007 : The first Google Automation Testing Conference (GATC) was held. Hiring standards shifted to require coding ability, and testing roles split into Software Engineer for Test (SET) and Testing Engineer (TE).

2010 : By the product release milestone, Google had largely completed the pre‑release development model shift (Testing Shift Left). Automated test case volume surged, and median code‑coverage across projects reached about 65%.

2013 : Google established a comprehensive automation testing ecosystem covering submission, testing, and release activities. However, the overall time from idea to feature launch did not shrink, prompting a broader focus on the entire product development lifecycle (EP2.0).

Since 2016, the long‑running GATC conference was discontinued as the Engineering Productivity department’s focus shifted entirely to building tools and infrastructure for software engineers (SETI).

The two primary career paths for Google test engineers are:

For those who enjoy software development: TE → SET → SWE.

For those who prefer solving product problems: SET → TE → PM.

In practice, TE and SET roles are not strictly separated; both require solid software engineering skills. Today, most TEs work in hardware and Android teams, while the Engineering Productivity department consists of SWE engineers focused on building productivity tools (Software Engineer on Tooling and Infrastructure, SETI).

Google SETI hiring requirements

Basic requirements :

Bachelor’s degree in Computer Science or related field, or equivalent practical experience.

Experience developing software in one or more general‑purpose programming languages.

Experience in at least one of the following areas:

Test automation

Code refactoring

Test‑driven development

Building infrastructure

Optimizing software, debugging, build tools, and test frameworks

Preferred qualifications :

Master’s or PhD in a computer‑related discipline.

Proficiency in languages such as Java, C/C++, Objective‑C, Python, JavaScript, or Go.

Scripting skills in Python, Perl, Shell, or other languages.

Job responsibilities

Lead/participate in engineering work from software design to delivery, focusing on developer productivity and speed.

Design and build advanced automation, testing, and release infrastructure.

Promote best practices for code health, testing, and maintainability.

Analyze complex software systems and collaborate across teams to improve testability.