EP39 - Interviewing For Google For With Mohamed Tayseer

Published: Jan. 18, 2015, 9:36 p.m.

b'\\u0627\\u0644\\u062d\\u0644\\u0642\\u0629 \\u0627\\u0644\\u062a\\u0627\\u0633\\u0639\\u0629 \\u0648 \\u0627\\u0644\\u062b\\u0644\\u0627\\u062b\\u0648\\u0646 \\u0645\\u0646 \\u0631\\u0627\\u062f\\u064a\\u0648 \\u0627\\u0633\\u0623\\u0644 \\u0645\\u0637\\u0648\\u0631, \\u0641\\u064a \\u0647\\u0630\\u0647 \\u0627\\u0644\\u062d\\u0644\\u0642\\u0629 \\u0646\\u0633\\u062a\\u0636\\u064a\\u0641 \\u0627\\u0644\\u0645\\u0647\\u0646\\u062f\\u0633 \\u0645\\u062d\\u0645\\u062f \\u062a\\u064a\\u0633\\u064a\\u0631 \\u0627\\u0644\\u0645\\u0646\\u0636\\u0645 \\u062d\\u062f\\u064a\\u062b\\u0627\\u064b \\u0644\\u0641\\u0631\\u064a\\u0642 \\u0639\\u0645\\u0644 \\u062c\\u0648\\u062c\\u0644 \\u0641\\u064a \\u0645\\u062f\\u064a\\u0646\\u0629 \\u0632\\u064a\\u0648\\u0631\\u062e \\u0641\\u064a \\u0633\\u0648\\u064a\\u0633\\u0631\\u0627, \\u0644\\u064a\\u0634\\u0627\\u0631\\u0643 \\u0645\\u0639\\u0646\\u0627 \\u062e\\u0628\\u0631\\u0627\\u062a\\u0647 \\u0648 \\u0646\\u0635\\u0627\\u0626\\u062d\\u0647 \\u0644\\u0645\\u0646 \\u064a\\u0631\\u064a\\u062f\\u0648\\u0646 \\u0627\\u0644\\u062a\\u0642\\u062f\\u0645 \\u0641\\u064a \\u0627\\u0644\\u0648\\u0638\\u0627\\u0626\\u0641 \\u0627\\u0644\\u0645\\u0645\\u0627\\u062b\\u0644\\u0629.\\n\\nWhy do you want to join Google?\\nTechnical career path\\nInnovative\\nMove to another country\\nYou will not lose anything if you fail. There is no such thing as blacklist\\n\\nWhat they are looking for in a candidate?\\nSmart & get things done\\nGoes the extra mile (open-source, side projects, \\u2026)\\nMeasurable achievements\\nCollege degree is not required\\nPersistence: I failed the 1st interview but passed the 2nd\\n\\nHow to pass the interview?\\nRelax. It\\u2019s not the end of the world\\nAlways keep the communication line open. In other words, always think out loud. Don\\u2019t stand there silently while you are thinking\\nValidate your assumptions with test cases & ask about edge cases to make sure you understand everything. The problem might be simpler than you think\\nApply for all suitable positions, not just one or two (follow @googlejobs on twitter)\\nPrepare well (Project Euler, Top Coder, ACM, \\u2026)\\n\\u201cAlgorithm Design Manual\\u201d is a good book, but it\\u2019s heavy for some people. Go with it when you feel you have a good understanding of basic data structures\\nSee more references below\\n\\nThings to consider\\nIt takes time to pass the interviews, get visa & start working\\nGoogle helps with relocation: papers, travel tickets, temp accommodation, but this doesn\\u2019t mean the visa is guaranteed. \\nThe imposter syndrome: I\\u2019m not good enough\\n\\nReferences\\nSteve Yegge blog post is the best resource. http://steve-yegge.blogspot.ch/2008/03/get-that-job-at-google.html \\nEvent by Ahmad Aly https://www.facebook.com/events/252191538310698/?ref=22\\nRequired courses http://uk.businessinsider.com/skills-for-google-engineering-jobs-2014-10?r=US\\nAnother reference http://www.businessinsider.com/qualities-google-looks-for-in-job-candidates-2014-4?IR=T \\nThere were some sessions in EgyptScholars group telling you how to prepare for Google interview https://www.facebook.com/EgyptScholars'