I interviewed last year as well but was unprepared. For the last one year I prepared for 2 hours a dat and 4 hours a day on weekends but I still could not make it. Any tips on how to do better?
13 replies (most recent on top)
google will one day cure death. if it happens in your lifetime, you could get rejected by google for eternity. Chin up, my friend!
And yes, Google is one of the more fairer interview places. The interviews are difficult, but they are consistent.
@FSdqWiT-2bib. What's a cover letter? Oh one of those old relics. Never wrote one in the past 15 years. This is how I usually find my next job...
Dr Mr. ABCDFZ,
One of your colleagues (blah blah blah) suggested we contact you. I'm Blah Blah Blah Recruiter. We saw your profile on LinkedIn and were impressed by your credentials and experience in mobile software and we are looking for someone that is an expert with (Android/iOS/Both Android and iOS). We were wondering if you would be interested in considering (Google/Facebook/Apple/Amazon) in (Bay Area/Los Angeles/Orange County/Seattle). If you are interested, please reply to me and send me a copy of your latest resume, and we'll arrange for an immediate (phone screen/on site interview).
And usually my response is,
Dear Blah Blah Blah,
Thank for you contacting me about the possibility of a wonderful opportunity at (Apple/Facebook/Google/Amazon/etc). The position you describe is sounds incredibility interesting. Unfortunately, as tempting as these opportunities sound, at this current moment, I would like to remain in San Diego , as both my family and myself are happy here. We are well established down here, both financially and professionally, and none of us have considered relocating, as this point in our life. So unless there is a possibility of remotely working from San Diego, I'm afraid I am going to have to pass up this opportunity. I do thank you for reaching out to me, and I would like to keep in touch with you, if either of our situations change. If I hear anyone else that I personally can recommend that is interested in relocating, I will definitely put them in contact with you.
Sincerely,
Blah blah blah.
One of the aforementioned companies, I got an offer from before I sent them a copy of my resume. They simply went off of my linkedin profile, which was basically what I used to create a resume from after I got an offer. I declined the offer, because it really wasn't that much better than how I'm compensated in San Diego, even in absolute dollars. Inflation adjusted dollars, I would be worse off moving to the Bay Area.
2lvd: And sometimes they sit there writing something entirely unrelated to the interview. Unless you can read upside down, or see the screen, you won't know. During my interview they appeared fully engaged, and usually didn't write much, except to change a problem to make it more challenging. I'm sure they sent their impressions to the hiring committee. But as I understand it, it's part of a "portfolio" of information they have from you. The further up the management "food chain" the decision is made, the less technical the managers may be, and more likely the desicion makers are to be influenced by how good or bad your resume and cover letter are. And it's not just about perfect spelling and grammar--although for god's sake, if you have Windows Office, your computer will do that for you. Your cover letter should convey, in two or three sentences, that you understand the core business of the division you are applying for.
@FSdqWiT-1xaj. No engineering company gives a shit about a perfect resume. Wall street, yes. Law firm, yes. Engineering company, nope.
The Google interview process is actually interesting because the people.interviewing you aren't the only people making the decision. They take notes on what you said and what you wrote, and then.they send it.to a panel.
OP: Take the time to make sure your cover letter and resume are grammatically perfect. I'm serious--don't underestimate this. Google can hire anyone. They not only want people who have technical expertise, but who can document their work, and who can at least send emails to coworkers that are easily comprehensible by any ESL who graduated from an American university. It's amazing how many screw-ups occur in a company because people don't understand the instructions they were given, but are afraid to ask for clarification for, because they might seem stupid. Communication is Key.
That's too bad OP. I hear they sit around and jerk each other off resolving solved undergrad CS problems
@FSdqWiT-afw. Uh, that court case was settled (my frriend got a settlement check). And no, Qualcomm wasn't one of the companies part of the conspiracy, so that wouldn't be the reason why Google isn't hiring you...Especially since there has been plenty of Qualcomm people that were hired by Google.
Let's face it, there are some people that can do these problems easily and some people that can't.
Instead of wasting your time trying to pretend to be someone you are not, you should focus your time on what you are good at and what you enjoy.
There was a period of time when I was in college and I wanted to be a derivatives trader for Goldman Sachs. Again, it takes a certain personality and skill to do that too. Just like sales. I ended having to take my backup job at qualcomm as a freak and geek when employee count was < 3500.
Life isn't fair. Get over it. Move on.
Do not feel bad, statistically it is easier to get into Harvard than Google.
Some Tech Companies have illegally conspired not to hire each other's employees.
I got rejected too :(
I am a kick ass engineer. Made it all the way to hiring committee.
Wish I could be given another try.
I got rejected there too.. I went there for a embedded job, but realized all my interviewers there were all just SW guys, not really embedded guys..
Yeah there were great at asking interview questions and very through and all that, but I don't think they really had that much embedded experience..
In any case prepare well on basic sw questions, maybe work on answers to all the intger problems that some guy here keeps posting.