Testing Blog

Test Engineers @ Google

Monday, January 14, 2013
Share on Twitter Share on Facebook
Google
Labels: Jobs , Yvette Nameth

20 comments :

  1. hanumanJanuary 15, 2013 at 4:23:00 AM PST

    Hi Anthony,
    Thanks for this nice writing. I have couple of questions here.
    1. As far as i know there is a huge difference between Test Engineers and Software Engineers in Test.
    Q. For which role this article is applicable.

    2Q. Which language test engineers has to code in.

    ReplyDelete
    Replies
    1. AnimeshJanuary 19, 2013 at 11:03:00 AM PST

      Even I do Agree.So basically top coders will be placed here.mostly the test engineers have a different skill set than Software Engineers in Test. Looks like google is looking for coders.

      Skill set Ref is taken from the site...<a href="http://www.askqtp.com/>AskQTP</a>

      Delete
      Replies
        Reply
    2. AnonymousJanuary 22, 2013 at 10:37:00 AM PST

      @hanuman:

      1) Yes, within Google we have two different roles in the test category: Software Engineer in Test (SET) and Test Engineer (TE). This article is written regarding the role of the Test Engineer.

      I didn't mention any of the general traits of an SET since I was trying to highlight what makes up a Google Test Engineer. I find that SETs and TEs have some overlap, but there is quite a big difference in the jobs as well since the roles are meant to be complementary and ideally TEs and SETs would work together to create a supremely awesome test environment.

      2) Test Engineers need to code in a wide variety of languages; I can't pinpoint just one or two. The differences above highlight "The Type of Product" and how that impacts the technologies we use. Part of this is the languages that we tool in or add test cases in.

      I personally have written in the following languages over my time at Google: Java, C++, Python, Javascript and Eggplant. I didn't do all of these for a single product though. I've worked in both Ads and Maps so when the product I was working with required me to change tools/languages, I did. I bet I could find a TE at Google who's coded in only a single language, or one who's used even more than I have.

      Delete
      Replies
        Reply
    3. Reply
  2. UnknownJanuary 21, 2013 at 9:32:00 PM PST

    why does not have the test engineer in China?

    ReplyDelete
    Replies
      Reply
  3. AnonymousJanuary 27, 2013 at 7:01:00 PM PST

    Hi Liang, I am a TE at Google's Beijing, China office. Google hired TEs in the first two years when Google began to set up the Beijing office in China. Google may not be hiring TEs in China right now, but you should check the job site periodically.

    In the Beijing office, there is little difference between TE and SET. You will be assigned to a project based on your skills, your interests, and the project's requirements (eg. project priority). Both TEs and SETs manage the test/release process, write test cases, write automation scripts, and implement test tools which can accelerate the test/development/release process.

    ReplyDelete
    Replies
    1. UnknownJanuary 29, 2013 at 9:38:00 PM PST

      Hi Xiazhang(or Xia?), Thanks! I am based on Shanghai. I am interested in how google test engineer works. Do you write testing tools by yourselves? And do you focus on black box testing or white box testing?

      Delete
      Replies
        Reply
    2. Reply
  4. JMonty42February 21, 2013 at 9:48:00 AM PST

    How does the salary of a TE compare to that of an SET or SWE?

    Are TE's considered to be less technical than SET's or SWE's?

    ReplyDelete
    Replies
      Reply
  5. Anthony ValloneFebruary 25, 2013 at 11:31:00 AM PST

    @JMonty42: Compensation at Google is a function of multiple factors. Without going into specific details, it's safe to say that comp is a function of geography, prior experience, tenure in role, and most importantly impact. The coding bar at Google does differ between TE and SET, however we do see blending across roles when it comes to coding capability.

    ReplyDelete
    Replies
      Reply
  6. PramodMarch 20, 2013 at 2:06:00 AM PDT

    Can an experienced test engineer who knows the product very well move on to being a software engineer?

    ReplyDelete
    Replies
      Reply
  7. TravellingcameraJune 2, 2013 at 9:51:00 PM PDT

    I appreciate the effort of putting this nicely with appropiate details.

    I can very well relate to it that describing the job of a test engineer is difficult at times. I feel lucky to work with some of the great folks in indurty and companies like Adobe, which provided the similar culture.

    Thanks Again ! I am inspired to blog about similar stuff soon.

    ReplyDelete
    Replies
      Reply
  8. UnknownJune 5, 2013 at 3:35:00 PM PDT

    I just wanted to add that there is a common mindset out there held by many that the "rite of passage" for a test engineer is to transition into a software engineer. I actually was a software engineer for 5 years before making the transition to a test engineer and have never regretted it. I think I like the test engineer role because on most teams I've been part of, I've felt more like a full stack developer in the sense that I get to work with everything from HTML/Javascript to the Backend and even DB. Most of the software engineers I work with are isolated to one language and often just one focus area of the app. I found that rather boring. Wearing multiple hats is much more interesting to me.

    ReplyDelete
    Replies
      Reply
  9. PRO IT Online TrainingSeptember 23, 2013 at 4:32:00 AM PDT

    Hi,
    Nice one! You have kept in a well versed manner about the role of a tester, Not only in Google but anywhere testers need to foresee the situations the application or product will be and test accordingly. Anyway working for Google will provide vast options to explore..

    ReplyDelete
    Replies
      Reply
  10. Always TestingNovember 11, 2013 at 2:19:00 PM PST

    Does Google have a 'Systems Integration Test Engineer' position (or something like it?)

    ReplyDelete
    Replies
      Reply
  11. VikasApril 6, 2014 at 9:54:00 PM PDT

    Hi there,
    I looked at the google jobs but I couldn't find even a single job for a Test Engineer. All of them were for Software Engineer in Test or Test Lead. Please can anyone help me with these questions:

    1. What is the skill set required for Test Engineer role? How different it is from Software Engineer in Test?
    2. How to prepare for a Test Engineer job interview?
    3. What is the career path for a Test Engineer and Software Engineer in Test working for Google?

    Thanks in advance.

    Regards,
    Vikas

    ReplyDelete
    Replies
      Reply
  12. UnknownMay 14, 2015 at 1:53:00 AM PDT

    I'm working as automation and manual tester in Accenture.. is there any chance in Google ?

    ReplyDelete
    Replies
      Reply
  13. UnknownSeptember 18, 2015 at 11:06:00 PM PDT

    I am working as a functional tester since last 4 years and would like to work in google. What are the chances and which skills will be required?

    ReplyDelete
    Replies
      Reply
  14. UnknownFebruary 1, 2016 at 2:01:00 AM PST

    Hi , I have 3+ year experience in Manual and Automation (Selenium Web Driver) Tester and I have good knowledge in Hadoop. I worked in Capgemini India and HP India. And I learning Android Testing as well . Is there any chance for me to be a part of Google family.

    ReplyDelete
    Replies
      Reply
  15. UnknownMarch 31, 2016 at 8:32:00 AM PDT

    Thanks for the awesome sharing!

    ReplyDelete
    Replies
      Reply
  16. mahmoudJuly 22, 2017 at 7:34:00 AM PDT

    can any one give me an email or tell me how to apply at google as software testing engineer ! ?

    ReplyDelete
    Replies
      Reply
  17. UnknownNovember 28, 2017 at 7:58:00 AM PST

    What sort of coding interview questions are expected for a typical TE in wearable's team ?

    ReplyDelete
    Replies
      Reply
Add comment
Load more...

The comments you read and contribute here belong only to the person who posted them. We reserve the right to remove off-topic comments.

  

Labels


  • TotT 104
  • GTAC 61
  • James Whittaker 42
  • Misko Hevery 32
  • Code Health 31
  • Anthony Vallone 27
  • Patrick Copeland 23
  • Jobs 18
  • Andrew Trenk 13
  • C++ 11
  • Patrik Höglund 8
  • JavaScript 7
  • Allen Hutchison 6
  • George Pirocanac 6
  • Zhanyong Wan 6
  • Harry Robinson 5
  • Java 5
  • Julian Harty 5
  • Adam Bender 4
  • Alberto Savoia 4
  • Ben Yu 4
  • Erik Kuefler 4
  • Philip Zembrod 4
  • Shyam Seshadri 4
  • Chrome 3
  • Dillon Bly 3
  • John Thomas 3
  • Lesley Katzen 3
  • Marc Kaplan 3
  • Markus Clermont 3
  • Max Kanat-Alexander 3
  • Sonal Shah 3
  • APIs 2
  • Abhishek Arya 2
  • Alan Myrvold 2
  • Alek Icev 2
  • Android 2
  • April Fools 2
  • Chaitali Narla 2
  • Chris Lewis 2
  • Chrome OS 2
  • Diego Salas 2
  • Dori Reuveni 2
  • Jason Arbon 2
  • Jochen Wuttke 2
  • Kostya Serebryany 2
  • Marc Eaddy 2
  • Marko Ivanković 2
  • Mobile 2
  • Oliver Chang 2
  • Simon Stewart 2
  • Stefan Kennedy 2
  • Test Flakiness 2
  • Titus Winters 2
  • Tony Voellm 2
  • WebRTC 2
  • Yiming Sun 2
  • Yvette Nameth 2
  • Zuri Kemp 2
  • Aaron Jacobs 1
  • Adam Porter 1
  • Adam Raider 1
  • Adel Saoud 1
  • Alan Faulkner 1
  • Alex Eagle 1
  • Amy Fu 1
  • Anantha Keesara 1
  • Antoine Picard 1
  • App Engine 1
  • Ari Shamash 1
  • Arif Sukoco 1
  • Benjamin Pick 1
  • Bob Nystrom 1
  • Bruce Leban 1
  • Carlos Arguelles 1
  • Carlos Israel Ortiz García 1
  • Cathal Weakliam 1
  • Christopher Semturs 1
  • Clay Murphy 1
  • Dagang Wei 1
  • Dan Maksimovich 1
  • Dan Shi 1
  • Dan Willemsen 1
  • Dave Chen 1
  • Dave Gladfelter 1
  • David Bendory 1
  • David Mandelberg 1
  • Derek Snyder 1
  • Diego Cavalcanti 1
  • Dmitry Vyukov 1
  • Eduardo Bravo Ortiz 1
  • Ekaterina Kamenskaya 1
  • Elliott Karpilovsky 1
  • Elliotte Rusty Harold 1
  • Espresso 1
  • Felipe Sodré 1
  • Francois Aube 1
  • Gene Volovich 1
  • Google+ 1
  • Goran Petrovic 1
  • Goranka Bjedov 1
  • Hank Duan 1
  • Havard Rast Blok 1
  • Hongfei Ding 1
  • Jason Elbaum 1
  • Jason Huggins 1
  • Jay Han 1
  • Jeff Hoy 1
  • Jeff Listfield 1
  • Jessica Tomechak 1
  • Jim Reardon 1
  • Joe Allan Muharsky 1
  • Joel Hynoski 1
  • John Micco 1
  • John Penix 1
  • Jonathan Rockway 1
  • Jonathan Velasquez 1
  • Josh Armour 1
  • Julie Ralph 1
  • Kai Kent 1
  • Kanu Tewary 1
  • Karin Lundberg 1
  • Kaue Silveira 1
  • Kevin Bourrillion 1
  • Kevin Graney 1
  • Kirkland 1
  • Kurt Alfred Kluever 1
  • Manjusha Parvathaneni 1
  • Marek Kiszkis 1
  • Marius Latinis 1
  • Mark Ivey 1
  • Mark Manley 1
  • Mark Striebeck 1
  • Matt Lowrie 1
  • Meredith Whittaker 1
  • Michael Bachman 1
  • Michael Klepikov 1
  • Mike Aizatsky 1
  • Mike Wacker 1
  • Mona El Mahdy 1
  • Noel Yap 1
  • Palak Bansal 1
  • Patricia Legaspi 1
  • Per Jacobsson 1
  • Peter Arrenbrecht 1
  • Peter Spragins 1
  • Phil Norman 1
  • Phil Rollet 1
  • Pooja Gupta 1
  • Project Showcase 1
  • Radoslav Vasilev 1
  • Rajat Dewan 1
  • Rajat Jain 1
  • Rich Martin 1
  • Richard Bustamante 1
  • Roshan Sembacuttiaratchy 1
  • Ruslan Khamitov 1
  • Sam Lee 1
  • Sean Jordan 1
  • Sebastian Dörner 1
  • Sharon Zhou 1
  • Shiva Garg 1
  • Siddartha Janga 1
  • Simran Basi 1
  • Stan Chan 1
  • Stephen Ng 1
  • Tejas Shah 1
  • Test Analytics 1
  • Test Engineer 1
  • Tim Lyakhovetskiy 1
  • Tom O'Neill 1
  • Vojta Jína 1
  • automation 1
  • dead code 1
  • iOS 1
  • mutation testing 1


Archive


  • ►  2025 (1)
    • ►  Jan (1)
  • ►  2024 (13)
    • ►  Dec (1)
    • ►  Oct (1)
    • ►  Sep (1)
    • ►  Aug (1)
    • ►  Jul (1)
    • ►  May (3)
    • ►  Apr (3)
    • ►  Mar (1)
    • ►  Feb (1)
  • ►  2023 (14)
    • ►  Dec (2)
    • ►  Nov (2)
    • ►  Oct (5)
    • ►  Sep (3)
    • ►  Aug (1)
    • ►  Apr (1)
  • ►  2022 (2)
    • ►  Feb (2)
  • ►  2021 (3)
    • ►  Jun (1)
    • ►  Apr (1)
    • ►  Mar (1)
  • ►  2020 (8)
    • ►  Dec (2)
    • ►  Nov (1)
    • ►  Oct (1)
    • ►  Aug (2)
    • ►  Jul (1)
    • ►  May (1)
  • ►  2019 (4)
    • ►  Dec (1)
    • ►  Nov (1)
    • ►  Jul (1)
    • ►  Jan (1)
  • ►  2018 (7)
    • ►  Nov (1)
    • ►  Sep (1)
    • ►  Jul (1)
    • ►  Jun (2)
    • ►  May (1)
    • ►  Feb (1)
  • ►  2017 (17)
    • ►  Dec (1)
    • ►  Nov (1)
    • ►  Oct (1)
    • ►  Sep (1)
    • ►  Aug (1)
    • ►  Jul (2)
    • ►  Jun (2)
    • ►  May (3)
    • ►  Apr (2)
    • ►  Feb (1)
    • ►  Jan (2)
  • ►  2016 (15)
    • ►  Dec (1)
    • ►  Nov (2)
    • ►  Oct (1)
    • ►  Sep (2)
    • ►  Aug (1)
    • ►  Jun (2)
    • ►  May (3)
    • ►  Apr (1)
    • ►  Mar (1)
    • ►  Feb (1)
  • ►  2015 (14)
    • ►  Dec (1)
    • ►  Nov (1)
    • ►  Oct (2)
    • ►  Aug (1)
    • ►  Jun (1)
    • ►  May (2)
    • ►  Apr (2)
    • ►  Mar (1)
    • ►  Feb (1)
    • ►  Jan (2)
  • ►  2014 (24)
    • ►  Dec (2)
    • ►  Nov (1)
    • ►  Oct (2)
    • ►  Sep (2)
    • ►  Aug (2)
    • ►  Jul (3)
    • ►  Jun (3)
    • ►  May (2)
    • ►  Apr (2)
    • ►  Mar (2)
    • ►  Feb (1)
    • ►  Jan (2)
  • ▼  2013 (16)
    • ►  Dec (1)
    • ►  Nov (1)
    • ►  Oct (1)
    • ►  Aug (2)
    • ►  Jul (1)
    • ►  Jun (2)
    • ►  May (2)
    • ►  Apr (2)
    • ►  Mar (2)
    • ▼  Jan (2)
      • The Deadline to Signup for GTAC is Jan 23
      • Test Engineers @ Google
  • ►  2012 (11)
    • ►  Dec (1)
    • ►  Nov (2)
    • ►  Oct (3)
    • ►  Sep (1)
    • ►  Aug (4)
  • ►  2011 (39)
    • ►  Nov (2)
    • ►  Oct (5)
    • ►  Sep (2)
    • ►  Aug (4)
    • ►  Jul (2)
    • ►  Jun (5)
    • ►  May (4)
    • ►  Apr (3)
    • ►  Mar (4)
    • ►  Feb (5)
    • ►  Jan (3)
  • ►  2010 (37)
    • ►  Dec (3)
    • ►  Nov (3)
    • ►  Oct (4)
    • ►  Sep (8)
    • ►  Aug (3)
    • ►  Jul (3)
    • ►  Jun (2)
    • ►  May (2)
    • ►  Apr (3)
    • ►  Mar (3)
    • ►  Feb (2)
    • ►  Jan (1)
  • ►  2009 (54)
    • ►  Dec (3)
    • ►  Nov (2)
    • ►  Oct (3)
    • ►  Sep (5)
    • ►  Aug (4)
    • ►  Jul (15)
    • ►  Jun (8)
    • ►  May (3)
    • ►  Apr (2)
    • ►  Feb (5)
    • ►  Jan (4)
  • ►  2008 (75)
    • ►  Dec (6)
    • ►  Nov (8)
    • ►  Oct (9)
    • ►  Sep (8)
    • ►  Aug (9)
    • ►  Jul (9)
    • ►  Jun (6)
    • ►  May (6)
    • ►  Apr (4)
    • ►  Mar (4)
    • ►  Feb (4)
    • ►  Jan (2)
  • ►  2007 (41)
    • ►  Oct (6)
    • ►  Sep (5)
    • ►  Aug (3)
    • ►  Jul (2)
    • ►  Jun (2)
    • ►  May (2)
    • ►  Apr (7)
    • ►  Mar (5)
    • ►  Feb (5)
    • ►  Jan (4)

Feed

  • Google
  • Privacy
  • Terms