2 ms·

I recently had the almost the exact same experience with Google recently. First phone interview they called the wrong number and I clarified that they had the w

I recently had the almost the exact same experience with Google recently. First phone interview they called the wrong number and I clarified that they had the wrong number and I was told that it was fixed. Second phone interview the exact same issue happened again. Both interviews were shorter than they were supposed to be. But after going on to the rest of the interviews I cannot say that Google has the dumbest interview process. Going into it I knew that there would be no feedback. In the end I was rejected too but I feel like in a year I will be much more prepared to get that job if desired because preparing for a Google interview forced me to go back to the fundamentals of computer science algorithms/data structures. The materials given to candidates should be mostly review and I will admit I had to learn most of the materials given to me

starlineventure 12y ago
There are much more efficient ways to find engineers that build high quality applications. I wish you good luck my friend. I hope you do get the job honestly and I'm sure they are a great company to work for. I think it's easier to get hired on through an acqui-hire. My suggestion is don't waste your time trying to impress thrm. Build an application. Get some users. Monetize it. Or move out to Silicon Valley to get a taste of being an engineer at fast paced startup. If you spend the next 12 months solving problem sets versus building applications I think you will havd fallen into a trap. Hopefully not. The title of the article does provide some shock value...I'm sure there are dumber interview processes.