1. Interview Questions
2. Engineering at Google
3. Career Levels and Compensation

Work life balance can be what you want it to be on most teams. (Some teams are in more competitive sectors and require more crazy hours all the time - but very few of them).If you work 40 hour weeks without putting in anything extra,you'll fall behind them as they advance and you stand still - and maybe that doesn't matter, so it works out for everybody. But at least know where you would realistically stand.If you excel and work your butt off, you'll be compensated and promoted.

Interview Questions

Learn to handle questions like these with the AlgoDaily course and curriculum.

Please ensure you read the disclaimer on the previous page reading the accuracy and sourcing of these problems.

Given a sorted matrix where the number below and right of you will always be bigger, write an algorithm to find if a particular number exist in the matrix. What is the running time of your algorithm?
Given a graph as input, write a method returning boolean True if the graph is bipartitie, else false.
Reorganize array of numbers in "s1 < s2 > s3 < s4 >.... " fashion. The numbers may include duplicates.
How would you find the longest substring of a string containing only one character?" this was then expanded to two characters, etc
You are given a starting position on a chessboard, as well as an end position. If you are only allowed to walk diagonally, how many steps do you need to take to get to the end position?
Given a bunch of points and a convex polygon in R^2. Determine if each point is inside the polygon.
Lonely Number: Given a list of number from 1 to N. All of them written three times, except one number (written 1 or 2 times). Find the unique number.
Find Shortest Palindrome Possible: Find the minimum number required to insert into a word to make it a palindrome.
Write an API to start Google Now, when saying "Ok Google".
How Deep Does It Go: Find the deepest node of a binary tree. If multiple nodes are at the deepest level, then return the rightmost node.

Engineering at Google

This information was sourced from reviews originally posted on Glassdoor.

They take very good care of their people. Lots of challenging work.More manual work than expected. People feeling very entitled, even though they are very nice. Scale and complexity of most of their systems. A significant portion of the people are focused on promotion.

Excellent stock & bonus, if you live on your salary you'll be making some serious bank towards retirement.Competition both to get in and to get promoted is severe and steep. You'll be making slow progress, if any, towards goals of advancement in title and responsibilities.

Amazing people to work with, exciting technology, high impact work.For a company that is all about scale, its biggest problem is scaling to the # employees and the expanding breadth of scope. Some areas are very top heavy.Don't lose the engineering focused culture of trust and openness.

Perks and benefits are awesome. Great people there, I made some friends for life.Systems are overengineered to an extent that making progress is very slow and painful. It's part of the company culture at this point, so when new systems are created they typically suffer from the same problem.Prevent your teams from reinventing the wheel over and over again. Replace the bottom layers of the stack (Kernel, Linux distro, base system daemons) with upstream. Embrace OpenCompute for servers, racks and other DC components.

Engineering Levels

Hover over to see details. This data was sourced from submissions at

$121,029 - Base
$41,690 - Stock
$19,841 - Bonus
$147,683 - Base
$78,940 - Stock
$29,357 - Bonus
Senior SWE
$178,805 - Base
$133,186 - Stock
$36,292 - Bonus
Staff SWE
$206,367 - Base
$187,333 - Stock
$67,867 - Bonus
Senior Staff SWE
$256,059 - Base
$286,176 - Stock
$83,294 - Bonus