Taro Logo

Software Test Engineer Interview Experience - United States

January 4, 2023
Positive ExperienceNo Offer

Process

The first round contained a behavioral Google Meet screening.

This was followed by a second round coding interview, which featured a LeetCode hard question that required catching potential exceptions.

The third and fourth rounds consisted of technical and HR screenings.

Questions

How would you test Google Maps? Name the various types of testing you can do and provide 1-3 examples for each. For instance:

  • Performance Testing:
    • Load testing the map rendering speed with many users.
    • Stress testing to see how the application handles extreme traffic.
  • Database Testing:
    • Verifying the accuracy and integrity of map data storage.
    • Checking the efficiency of database queries for location data.
  • API Testing:
    • Testing the endpoints for geocoding and reverse geocoding.
    • Validating the response structure and data from routing APIs.
  • UI Testing:
    • Ensuring map tiles load correctly and are displayed without visual glitches.
    • Testing user interactions like zooming, panning, and marker placement.
  • Functional Testing:
    • Verifying that searching for a location returns the correct results.
    • Testing the accuracy of navigation directions between two points.

Was this helpful?

Interview Statistics

The following metrics were computed from 13 interview experiences for the Google Software Test Engineer role in United States.

Success Rate

0%
Pass Rate

Google's interview process for their Software Test Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive31%
Neutral38%
Negative31%

Candidates reported having mixed feelings for Google's Software Test Engineer interview process in United States.

Google Work Experiences