I love how specific your video is, no blabber or no generic stuff, and the experience you had sucks man. But, the saying "only worry about things that are in your control and nothing else" is as true as it sounds a cliche.
My thoughts exactly. Maybe he's too partial to Donald Trump or conservative values, or just not "liberal" enough? I'd never consider working for Google or Facebook.
Hey Keep on Coding (not sure what's your name lol), thanks for sharing & never turn yourself down no matter whatever you been told. :) you did great, be confident!
Its internal hiring, there's a HUGE risk management reason to choose an internal employee over new comers. I've been declined twice over a very much same narrative, I just happen to know the hiring management in both cases to get the inside scoop (unofficial reasons). "2-3 years" just means someone of equal or better experience wanted the job internally. Best of luck.
Companies always want to move employees up the skill tree and hire the lower position because it allows them to casts a wider net of potential new hires with less risk. Popping a new hire in the middle of the skill tree can disrupt those already there who have gotten comfortable with the groove. It's pretty likely this is exactly what happened even if the internal person getting hired had less skill than all the other applicants.
Thanks for sharing this info. It makes me question the process. Who is likely to be hired: a TVC that works at Google or a true external candidate from Apple or Facebook? Even though TVCs are considered external, we are there immersed in the culture, know the rules and values of the company. Who is more likely to get a hired: a TVC who has worked in that department or with that department for the role or a Google FTE who has no experience in that department at all?
Yo, I thought my rejection story was bad. The interview process took a couple weeks and in the end, the recruiter told me it was really close and that I didn't get the position. I was super down and couldn't function well for a week but hearing your story it's so much worse. Thank you for sharing this!
The final resolution of your application sounds pretty unprofessional to me, especially coming from a company like Google. You basically passed the whole interview process and even had a match with a team whose manager was really interested in having you. And then, all of a sudden, at the very last stage where you rarely get rejected, rather than an offer you get a rejection with no further explanation. Just like that. We've been giving you super positive feedback for two months, but now we're rejecting you and can't say why. Honestly be it Google or a no name company, you don't do that to a person. I really appreciate the way you got over it without making so much of a big deal out of it. The level of maturity you showed in that situation, to me, is worth having you in any company.
@@goguma-cr3di I find it impossible to believe that google can be google and only find out about a YT channel that late in the process. Then again, it would make sense that they wouldn't want google employees talking about it publicly all the time
@@magnusanderson6681 I seem to recall certain big companies having issues with employees running RUclips channels, so it’d make sense considering the precedents Edit: I just remembered that it was TechLead who got fired from Facebook for having a RUclips channel
This is the one thing I hate in the hiring process. Not the rejection itself, but I hate that no full details are provided on why they rejected an individual. Piece of information that can better someone. Instead you get the bull get more work experience, we found a candidate more inline with our blah blah blah, or nothing back at all. This is the only part I fully with a passion hate. Can't do nothing about it either, can be biased as they want and cover it up. Keep up the good work and inspiration to people man!
'undefined' enables them to hide bias and all sorts of prejudice under this category - 'external factors', 'we've decided to go in another direction'...whatever.
big corporations take interviews on regular basis,not because they need an employee but because there are a lot of clients/companies who doesn't like to interview a random person and are afraid to fail at getting a right employee...so companies like google come in with recommendations of an employee and charge a broker fees for there service. It a Business, sometimes run secretly by handful of HR employees of companies(this is a example of passive income).
This meant a lot to me....struggle began since my college days. Then after facing rejection in more than 12 companies, I began working at a startup. There I learned many technologies. Now I'm in Infosys. But I really need to grow more and achieve a better place to work with better mindsets. You've inspired me so much!
It's indeed "strange" how they were saying "something came up, external issue, it's not you it's me"... lol. and then a remark, "have 2-3 years more experience". well if they can't give me a proper feedback, google or not, I wouldn't go somewhere where they're bullshitting me. I'd personally think they tracked me down and found something personal they didn't like about me, just didn't have the backbone to tell me basically.
Alexander Phoenix sadly it’s not about having a backbone. It’s about not getting sued. If they give strict feedback they could possibly open themselves up to a lawsuit.
@@dkchen Very much this, a problem that happens more today then ever is that a company is not just looking for someone with the skill, but someone who has a history of not causing a drama....and is from a clean social circle. Honestly the hiring process that those larger companies use is very much like getting a security clearance. They will do background checks, they are going to look to see if you have a history of doing the stupid, they are going to pay attention to how many unsavory types you have associated with. If your sister is a drug addict and your father laundered money for the mob then you might be in for a hard time. Those are both situations that bring a potential liability. And a major concern is trustability. Employees of any ilk are given access and the chance of access to very valuable assets that do indeed have a market value, so if you are a ghost in the system with little to no family...it is likely that that right there may flag you. (although to be fair, that can also be a very employable trait, but let's not think on that one too much) I was told once when I was younger that when it comes to a security clearance is that they are not as worried about you getting a dui (still don't) but how you handle it. If you have a record for doing the stupid and trying to deflect and make it painful for all involved or shift the blame (and word gets around, you would be surprised what people are willing to disclose on even a casual cold call) well, those things are major red flags. But...if you do the stupid and then try to make it right...well it shows and decision makers are very aware that not everyone is perfect and that right there gives them an insight on how you will behave if there is a mess that happened inhouse that you were a part of.
I know from being an insider that Google plays dirty when it comes to 'reference checking'. A lot of what the hiring managers do is actually illegal as far as labor law goes. And the worst part is it's not just Google that does it. If they aren't committed to hiring you, they can find any reason not to.
That feedback may be harsh, but its true. You cant fake experience. Also part of the reason they stretch out the entire process is in case someone better comes along, which is most likely what happened.
This was a good heartfelt talk. I think you've helped a lot of peeps by your insights and resiliency. You got a long career(s) ahead of you and you'll find that it may have been for the good. I think that they may have found someone internally. I had a similar experience with a University position once. I had passed all of the departmental interviews and was told I was to be given an offer, only to be told a week later that the offer was rescinded. I asked my friend who was an admin and she told me that they had people who were already in the pipeline for that position from within the University. I went onto finance/math and as brutal as it was, at least I knew the rules of the game.
Former Googler here, wouldn't take much notice of this. Could have been pretty innocent, like headcount got diverted/reallocated, demands of the role changed (ie. what was originally an L4 role could have been bumped to L5). There's a myriad of reasons beyond them digging up skeletons from your closet.
Are all the reasons you listed considered "external" reasons? Because he said they told him something "external came up" and I am not sure if that means they found something out about him since he is no in google so he was being considered "external" or if that means what you listed. Thanks!
@@xo.Frenchie It seems like it's based on skillset, as in he was going for a relatively niche team and there might not have been a lot of openings for related skillsets. That being said, it's very possible that your chances could depend heavily on the recruiter you're with. The person I know who is reaching the offer stage has had a wonderful recruiter. Didn't give up despite the applicant going through 11 team fit interviews lol. Very communicative and on top of things, plus recognized the applicant's talent. Maybe others aren't as lucky :/
@@26Sundrops yeah, recruiter definitely matters. but the thing I feel weirdest is 'after 2-3 years'. why that? after such a long time, one can lose interest in that completely and might have already been going through another path.
Just terrible that they wont save his application and if another position opens for the same role, bring him on. Instead they will make you start over and cold apply. It will be all different people interviewing no one will know you already progressed through. It sucks it feels like starting all over again from scratch from the beginning.
Keep on coding, just wanna say the underdog software engineers are inspired by your experiences and they keep us going through the long headaches of algorithms and trying to crack the coding interview. Thank you.
Hey man!) I also got an onsite interview with Google and ended up being rejected. I truly feel what u felt at that moment and it's really cool that u r not giving up.
@@KeepOnCoding There are many better professions than coding . I am not telling to give up but just change your field and apply for jobs which pay better and are stable
My experience: Interviews depend mostly on sympathy. If you fit into the team, a company will accept a few knowledge weaknesses because you can learn that
this is one of the main reasons, kinda the same happened to me, it's just a waste of time, preparing your self, and at the end, just getting rejected. I feel sorry for your bad experience, but at least you now know you're capable to join any company :), keep the good work!
I've had a similar experience, it's was so disappointing at the time... Looking back you can't know what would have been best for you, so there's no sense of obsessing over it, just knowing you did your best like you said you did. Keep on keeping on, do the best you can to enjoy your workplace, and be sure that new opportunities emerge
Google's last-minute rejection is super frustrating. You may want to double-check any references you gave them. There is a service that does that for you. They do it for companies, but they also do it for private individuals that want to check their own references.
I feel you man, that absolutely sucks. It's definitely strange that they didn't give you any other options other than "come back in 2-3 years". I just failed my Facebook interview and when I got the e-mail back, my heart sank to my stomach like you said. I thought I had it because I nailed every algorithm question but turns out I came up a bit short on the design interview and I'm still regretting not saying more during that portion. Nothing you can do except come back stronger!
I applied online to Google for the University Graduate Software Engineering role, then about a month later I was contacted to do a timed online coding exam. A few weeks after I got another email from a recruiter about setting up a technical interview over the phone. I responded immediately and gave my availability like they asked..... no response from the recruiter. After a few days I followed up and the recruiter replied with, "we are winding down our hiring for University Graduate Software Engineering roles" and "we will not be able to move forward at this time". No reason. What a waste of my time. Luckily I had other offers on the table like yourself.
I wish you all the best. I failed Amazon interview (after f2f) a couple of months back and it still hurts. I am an engineering manager in a company and failed due to lack of preparation of leadership principles. I didn't explicitly named them while quoting examples which probably led to the failure.
and amazon block you from further interviews for a yer after you fail one apparently. At least you now why you failed.,, Or do you? Was that a guess or did you actually get some (unofficial) feedback?
I totally agree with you, it is quite disappointing to hear NOT being selected after all the hard work and attending series of interviews. I received another job offer after two weeks and accepted that.
the big thing about amazon, that they don't tell you up front is that if you fail to get past the onsite interview they ban you from doing other inteviews for 6 to 12 months. The details are not clear but I've had it confirmed by amazon friends.
I recently had attended Facebook interview in a similar situation, I thought I did very well BUT I was not selected. They match exact words to answers, and if we don't speak those words while answering they don't select / make an offer. IT is like word-to-word match of answers they expect to hear. Especially on Leadership qualities and situation-based interviews.
I did a phone interview with Google. I nailed the coding problem without much effort, but it turns out the interviewer showed up with **2** problems to solve -- not what I had been told would happen, nor did he say so up front. Following the advice I saw everywhere, I started with the "naive" (i.e. bad) solution and moved to the good solution. He stopped me at multiple points to discuss the complexity/Big-O of the solutions, etc. So he failed me because I "didn't solve the problem fast enough." My recruiter was happy to set up a re-do, but in the meantime, I had decided that I wasn't sure Google was a good fit for me, anyway (open office, structure, etc.) and they were _really_ pushing positions in the Valley over better options for me like Seattle. I also don't really dig their process, which is so time-consuming and such low odds even if you're a great hire. So I decided it probably wasn't the right move -- for me, at least -- and skipped. I'd reconsider it now that a few years have passed, but honestly, I still don't think they'd be willing to pay me enough to make the Valley worth it, so it would have to be another location.
I wouldn't apply even if I was a good candidate. The hiring process is too insane. If they paid me for the interview process maybe but they are wasting your time as their screening process. No way.
I can see the disappointment or just a lack of proper sleep in your eyes. After all, you almost got the job at Google which seems impossible to me. I guess having all those interviews and solving the problems was more exciting than the actual job at Google or any other big corporation. Subscribed!
The good thing is you made it through a lot of hurdles many don't. Its messed up that it didn't workout for you. But you did get some great experience and thank you for sharing it with us.
Getting rejected at such late stage sucks, so sorry it didn't work out. If I may add my two cents, a three round of onsite at google is unheard of especially only one round is coding. So you had a super easy interview. According to my recent experience (about a year and half ago), I interviewed for front end engineer and it was 5 rounds plus lunch, it goes like 1. Build UI component (multifunctional table/list) using API/js/HTML; 2. Algorithm; 3. Lunch; 4. Design client side of a google product; 5. Puzzle + algorithm; 6. Algorithm; The worst part is you don't know what category for each round before you go in. So in my case, when I stepped in the last round, I was expecting a behavioral round but just more coding and I didn't reserve any energy left, I walked in at 9 and left at 5, I was told things like: since transfer team is easy at google so we need to test your backend knowledge as well; or I see you have some coding rounds let's do one more; or I know there is no behavioral round because google is engineer oriented and we care about your coding/problem solving ability more than anything. So I did poorly for the last round though the rest I did well, I was rejected. Comparing Google, Amazon, MSFT and Facebook, I'd say facebook really did a good job to prepare you by providing information needed for each round of your onsite, Amazon is a close second, MSFT prefer to mix behavioral in each round so every round is 45 mins coding + behavioral if there is time, the experience varies a lot like interview a front end dev but asked to design a database backup system; or you are told to use the language you are comfortable but you learned that the principle engineer is not comfortable with javascript after you are done, so all the time spent to explain syntax and nature of js but talk about test which you learned was the meat of the round. All in all, I feel interview is just a numbers game. If you do some prep work and keep trying, eventually you will get what you wanted.
As he said in the video, he's applied before but was ignored but this time it seems the referral got him an interview, so unless he can get another one his chances don't look good.
This video came up like 20 times , finally after seeing it so many times I had to watch it lol. Thanks for the video , pretty cool. I interviewed for exxon , almost got hired lol.
Hiring manager probably fired after interview for something unrelated or they got someone that might have rejected in the past and later decided to join that they really wanted.
Thanks for sharing your experience....I’ve been rejected many times in multiple interviews in my life and each experience has made me stronger and better in future interviews....I’m glad you had that positive mindset to to keep yourself going....👍
Its a very nice video, regarding google job I have ever come through. I urge you to make more videos like this on future. Maybe with your colleagues sharing their experience of accept/reject in Google, Microsoft, Amazon etc.. Thanks for sharing your experience
Thanks for sharing about your interview experience!!! I do learn a lot from your sharing.. The world is big and there are many great opportunities out there.
I feel your pain. I was also rejected at the offer review stage recently, which is indeed rare. For me it had to do with a culture fit mismatch, but they didn't give me any details. 🙁
@@chuckitaway466 I can't really blame them, honestly. False positives are a lot more expensive for them than false negatives. And they get a ton of candidates, so they can afford to be picky and wait for a perfect match. I think I would've fit in well, but they only got a handful of hours to get to know me. In the end they got some combination of signals from me, or a lack of signals, that made me a risky hire. Luck plays a role there too. Anyway, I went on to apply to Facebook and Amazon (among others), and I'm now getting job offers from both of them. 🙂
I don't think you nailed the slow website question. You need to ask questions about the "specific" client. Are there logs available? Is it affecting more than just this user? Identifying the scope of the problem is step 1. Based on what the user experienced, you want to understand that interaction exactly. This would help identify why this specific user is having a poor experience. If the request, for example, is not making it to the back-end (and stuck on the client), then it's a user-specific issue -- (browser or local system issues). However, if you have logs (and for enterprise systems, you should assume this is the case), then diagnosing through an enterprise logger would be my first step. Anyways -- the key to ambiguous questions (scenarios) is to ask questions. Don't make assumptions about the context -- clarify the context.
Great point....thanks for sharing....after being rejected some people would just blow off the company and say they are not worth working for or find excuses....but you have to learn from your experience and try to understand which areas you didn’t do well in and go forward with the next interview with that knowledge
You failed the 2nd part of your first interview (figuring out why the web app was slow). The correct answer is to first collect information from the user about specifics of what they are doing, when it occurred, what device were they on, was there a specific part of the app that was slow, etc. You basically gave the "i'll just dive in randomly and try to fix it, without fully understanding the problem" answer, which means you lacked critical information that might lead you directly to the problem.
I'm not an expert, but I'd have to agree. Things that come to mind immediately: "have you tried turning it off and back on again" vs "what were you doing when it happened?" That, and blindly grasping for solutions is obviously a massive waste of time, which in turn, is a massive waste of money and resources.
Man, honest history to hear from some one man, I like your strength of sharing your experience on public. I just a can say you that I failed one time in second interview Facebook, one online in Amazon, then 1 on-site interview on Microsoft about 5 interviews in a day, and then finally 1 on-site interview on Google Cloud, again 5 interviews in a day.. that one was the must heart braking experience of my life.. I just can say you that after all that pursuing of happiness on top-5 tech companies, I do not understand what the heck is wrong with me on those loops. If there is something that I'll like from those companies is: "Please give a real feedback about", something that really helps you to grow on top..
cheer up.. not all big companies fit; sometimes small companies are the best way to go... and who knows.. you get more years under your belt and start your own tech company and then you'll be google's customer instead of employee :)
I finished 5 virtual onsite interviews after 1 phone interview and failed. I received a negative feedback by one of the interviewers since I cannot solve a greedy problem. He keeps saying that it is EASY, which makes me too nervous to think peacefully. But greedy solution is something like "it is pretty easy, only if you know the direction" Still, I don't have strong enough mind to be clam. After that I ace-ed the following interviews in other company. pretty smooth. Please don't take the rejection as a rejection to your life. keep fighting.
i also did not notice how 17 min passed. Thanks for sharing. Wish you all the best for next time. One of my friends was not accepted first time but second time he got the job at Google.
This is giving me anxiety! Just did team matching at a company and have an update call with a recruiter tomorrow. I stumbled on this video at the worst time!
Hi Sam! Thank you for sharing your story! You tried your best and in the end that is what counts. This is going to be another valuable learning experience that will help you, life doesn't happen to us, it happens for us. My behind was handed to me on my 1st interview because I was stone cold frozen - couldn't talk and that actually motivated me to go to toastmasters and then volunteered to do public speaking for the Make A Wish foundation. I didn't believe it before but out of each of my disappointments came triumph! Keep rocking Sam, maybe one day you'll own Google!
I ’m about to graduate with a CS degree…you are super knowledgeable…I’m in a panic about my job prospects . that interview process sounds absolutely rough .
You are the best, allowed me to feel normal, and to get rejected and most importantly to keep trying ( and guess what -> that's what your youtube channel says :-) )....you really kindled me...Thanks for uploading once again.
They keep telling us that the market needs more software developers but the reality is exactly the opposite -- there are TOO MANY developers on the market nowadays and getting a job will be harder every year...
As someone who interviews developers, there are too many developers...many of whom call themselves developers but can't code a complex for loop, depth first search, or analyze an algorithm. Nowadays, I've seen more good than bad though, so that's a good sign.
darksteel78 who told you you need to know all the school book algorithms to be a good developer? I know many of them doing heavy kernel code both in FreeBSD project or Linux who would not pass a Google whiteboard test, but they are very respectable committers and experts in their field of interest. Whiteboard tests are suited for young CS graduates and thats whom upper management wants to hire only; along with "minorities". This whole IT market is sick nowadays...
@@spearPYN I agree. You barely use any of the major school book algorithms. I can't tell you the last time I needed Dijkstra's algorithm or depth first search in practice; however, I'm mainly referring to people who can't use the basics as building blocks to design a working system. Saying someone would not pass a whiteboarding interview doesn't actually mean that much, ironically. It's a mix of skill and luck. I've interviewed people who were brilliant and still didn't get hired because 2+ other interviewers asked "weird" questions IMHO, especially for the areas the person was being hired for. Why are you asking a front end candidate about the intricacies of database caching? They should know about caching, sure. They should know some backend concepts, sure. But they don't need to re-design Redis from scratch! If I'm hiring you to work on a kernel, you should know how the system you're working on is structured and how to make improvements to structures you normally encounter in that system. In that case, I'm talking drivers, threads, processes, pipes, locks/mutexes, etc. If you come in as a "general" engineer, I can't gear my questions to your expertise which results in a mix of real-world design questions and school book algorithms that are occasionally useful. If you haven't developed an area of expertise, your knowledge is...general. So, here's a general school textbook interview question for you. What else can I do to judge your skill level?
darksteel78 yup. But the sad story is that I noticed most big companies just dont care about hiring experts... they throw the same textbook questions at everybody regardless of their real world experience. It has become an industry itself -- learning how to pass whiteboard tests... :)
@@spearPYN Yeah. It's a problem. Up to a certain point, I understand their use. If you're fresh out of college, it's more likely you'll get these kinds of questions. And sometimes (a very loose use of "sometimes" here), you may realize a problem you've studied for appears in the real world. If you're an industry veteran (5-10+ years in Silicon Valley specifically), you will get fewer and fewer of these schoolbook questions (that's my experience at Google anyway) and more high level systems design and management questions. Don't get me wrong. Those kinds of questions will still be there...just fewer in number and more complex than new grad candidates. This is especially true if you're going in as general software engineer where you could be thrown on any kind of project from OS development (Linux/Android/Fuchsia) to voice assistant w/ ML research (Google Search/Assistant) to self drivering cars (Waymo). This is really a "consolidation of projects problem" in Silicon Valley where a few companies are doing 50,000 things and can't gear interviews for specific types without clogging up the interview pipeline due to the high turnover rate and preference for younger employees because, you know, less money.
i’m about to graduate with a CS degree…ur super knowledgeable… more than me and now i’m in a panic about my job prospects 😅. that interview process sounds absolutely insane.
I got offered a Google support role in 2015 but ended up rejecting then last minute based on role mismatch, health scare and IP rights conflict. I also didn't want to work for Google straight out of college. And initially the recruiter said I had to wait 2-3 years to finish my degree and they contacted me back then but by then I was so over the role.
I think because you didn't complete the last xcoding interview, the one where you short 10 minutes?! That was the one that set you back a step. They probably wanted to see you solve and type in each code on whiteboard or computer and explain each step as you proceeded along. If you were allowed to complete that step then you would probably have gotten the job for sure. Some people try many times before getting accepted by their ideal dream job. If you really want to get hited with the company, keep practicing and critiquing and honing your knowledge and skills and reapply again until you receive an employment with the company of your dream.
Do not feel bad man, pretty sure someone told this to you, but sometimes it is just luck. :) Or sometimes destiny :) just keep exploring and move forward. It is a lot better to fall forwards than backwards :) Thank you for your video. :)
man that's really shitty. I genuinely wish you best of luck. I'm super positive that something even better will turn up! In the meantime Keep On Coding!
could you talk about what you and that manager who was trying to convince you to get on her team talked about? What exactly made you feel like you guys vibed well? It seemed like you were sure that they would've wanted you on their team
Two possibilities come to mind: (1) the team that wanted you somehow lost their headcount (i.e. number of additional people they can hire), though I don't know why they would avoid telling you that (2) somebody caught on (late) to the fact that you were asked the same question twice in the interview process, and didn't say anything the second time. You're supposed to say something if you've already seen the question. The interviewer is supposed to have a back-up question for that case. (I mean, the interviewer is also supposed to double-check what you've already been asked, but they can't unhire him for that) They also don't like it when you publicly disclose your interview questions, incidentally. Especially not along with the answers. So if they somehow suspected that you might be a person likely to do that, say, on your youtube channel, that might also be a big red flag. And yes, they do (or at least they are supposed to) tell you not to do those things as part of your interview process.
What kind of BS response is this? (1) the team that wanted you 'somehow' lost their headcount. If this is the case, then that 'somehow' is due to the company/management's ineptness. 'Though I don't know why they would avoid telling you that'; as if they would indulge in admitting ineptness. (2) somebody caught on (late) to the fact that you were asked the same question twice in the interview process, and didn't say anything the second time. You're supposed to say something if you've already seen the question. Again, it would be more of the ineptness of the interviewing side. And, as if there is a hard-fast rule that you are supposed to say something. 'If you already seen the question?' He was asked the question, twice. He was not "shown" the question. 'The interviewer is "supposed" to have a backup question?' That may or may not be case. I'm retired now, but as an engineer, I had been through interviews where the same question may have been asked not just twice, but multiple times, even during the same interview. This is useful to determine if a different or dissimilar answer is given for a particular question. 'They also don't like it when you publicly disclose your interview questions, incidentally.' Nowhere does it state that this person made this video just prior to being rejected. That is conjecture on your part. 'They somehow suspected that you might be a person likely to do that'. So, they can foresee the future, but not able to mitigate simple procedural mistakes, on their part? 'And yes, they do (or at least they are supposed to) tell you not to do those things as part of your interview process'. Again, conjecture, but maybe another sign of ineptness on their part, don't you think? The Dunning-Kruger effect.
@@pintorpi333 I don't know how any of that, even if it were true, makes my response a "BS response". I'm simply suggesting some possibilities of what could have happened, based on my personal experience "from the other side of the veil". I'm not endorsing these possibilities as a perfectly rational response on the part of a huge disconnected entity. Yes, surprise, a big company has many idiosyncrasies and sometimes (often) they affect people outside of that company. Getting an understanding those idiosyncrasies is still useful, regardless of whether you consider them signs of "incompetence" on the part of a company you are anthropomorphizing as if it's some kind of single entity that can be competent or incompetent. While also apparently somehow conflating me with that entity, simply because I ventured to express some ideas about it. For my part - again, from firsthand experience - I would call it more "bureaucracy" and "tragedy of the commons" than "incompetence".
You'll never know why they reject you. Keep it up. Still full of hopes. Not the end of the world. I can definitely feel you as I also went through a lot with several big tech giants in Silicon Valley. Trust in God. Cheers!
1. BROOO LMFAO I WHY WAS I SO HYPE DURING THIS I WAS LIKE *OMG OMG HE'S GONNA GET THE JOB* BUT LMAOOOOO I FORGOT ABOUT THE TITLE BAHA 2. AHHHGFGG DUDE THERE IS SO MUCH KNOWLEDGE AND THINGS TO LEARN I FEEL LIKE ITS TOO MUCH AND LIKE HOLY CRAP U KNOW SO MUCH AGH this is wild
Q. - What do you do if someone calls and says that the website is slow: A: - 1. - Check if the user has a slow computer by asking them questions about their hardware & OS. 2. - Find out if their ISP is having problems in their area by asking if they previous had slow problems with other site or their internet & checking their ISP twitter & website for info. 3. - Ask them to do a tracert to the site on their computer too see how their router behaves during connectivity & also ask them to do a speed test on their network.. 4. - Ask them if they are using hardware firewalls & what kinds of ad blocking softwares they have on their browser. 5. - Ask them if they are using any kind of VPN. and what DNS they are using if they are using a different one like Google 8.8.8.8. or OpenDNS site. 6. - Ask them if what speeds package they have on their ISP and if they are using Wireless or Cell network to connect to the internet or if they are in a public network. 7. - Ask them to do a netstat on their computer to find live connections from their computer. 8. - Ask them if they are streaming or transferring files of any type during the visit of the website. 9. - Ask them if they are using pfSense or OpenSense software firewalls and also ask them if they are using VM's or hypervisors. You'd be surprised on the people that are still using very old laptops these days and they expect it to work like new computers of 2019......LOL Most of the time when a user calls in regarding speed problems its usually on their end. - You can also check special website & google to find out what websites are down or having problems. Once you checked all this on their end, THATS when you start checking things on your end like APIs and stuff....LOL Ive been studying for the Cisco Network Certification.......LOL
For search bar they would probably expect terms like ajax and JavaScript and for slow site they would want to hear indexing the db tables and load balancer first... Thanks for sharing your experience
Wow, that’s really disappointing and most disappointing not knowing why after coming so close. If you can’t think of any red flags , I would assume one of your former employer stained your background somehow. Glad you recovered from that rejection and continue to move forward.
Man this seems rough. I know we can never know but Im guessing they found someone else (most likely internally) and didn't want to hire someone they didn't already know. Total guess I could be wrong, but I think you just got unlucky. Hopefully you aren't too hard on yourself best of luck! I know the feeling of getting rejected from Google....it fucking sucks.
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
I failed 7 interviews and then magically cleared Uber. A lot depends on your luck. Don't lose heart it's mostly random.
so how many rides do you do a day?
Lmfao^
Bot 13 - Ouch 😂🤣😅
Bot 13 Gotttemm
@@HK-sw3vi lmaooooooo
I love how specific your video is, no blabber or no generic stuff, and the experience you had sucks man. But, the saying "only worry about things that are in your control and nothing else" is as true as it sounds a cliche.
Thank you Arun. I’m glad you enjoyed the video.
Simple. They looked at your search/browsing history.
lol if they looked at my search/browsing history probably lot of porn website would pop up
My thoughts exactly.
Maybe he's too partial to Donald Trump or conservative values, or just not "liberal" enough?
I'd never consider working for Google or Facebook.
@@nribackpacker Hmm no good. Stay away from pornography!
lmao )
@@JD-kf2ki 😆😆😆
Let’s please keep the comment section positive! Have an amazing day!
Hey Keep on Coding (not sure what's your name lol), thanks for sharing & never turn yourself down no matter whatever you been told. :) you did great, be confident!
You don't want to do that, opposites attract!
Gonna be soooo much negativity here in a minute
I felt the pain, it sucks man.
The important part that you passed the interview process, I will feel so proud of myself for that
Its internal hiring, there's a HUGE risk management reason to choose an internal employee over new comers. I've been declined twice over a very much same narrative, I just happen to know the hiring management in both cases to get the inside scoop (unofficial reasons). "2-3 years" just means someone of equal or better experience wanted the job internally. Best of luck.
Why bother posting the job if they are just going to go with an internal candidate. It's a waste of everyone's time.
Companies always want to move employees up the skill tree and hire the lower position because it allows them to casts a wider net of potential new hires with less risk. Popping a new hire in the middle of the skill tree can disrupt those already there who have gotten comfortable with the groove. It's pretty likely this is exactly what happened even if the internal person getting hired had less skill than all the other applicants.
@@zonk1477 well, they probably didn’t realize it, or had certain kinks to work out before those options reveal themselves to be even possible
It is okay to give the position to an existing employee..but then why advertise externally...wast of time and resources if you ask me😞
Thanks for sharing this info.
It makes me question the process.
Who is likely to be hired: a TVC that works at Google or a true external candidate from Apple or Facebook?
Even though TVCs are considered external, we are there immersed in the culture, know the rules and values of the company.
Who is more likely to get a hired: a TVC who has worked in that department or with that department for the role or a Google FTE who has no experience in that department at all?
Yo, I thought my rejection story was bad. The interview process took a couple weeks and in the end, the recruiter told me it was really close and that I didn't get the position. I was super down and couldn't function well for a week but hearing your story it's so much worse. Thank you for sharing this!
Which company you went for interview? Google?.
The final resolution of your application sounds pretty unprofessional to me, especially coming from a company like Google. You basically passed the whole interview process and even had a match with a team whose manager was really interested in having you. And then, all of a sudden, at the very last stage where you rarely get rejected, rather than an offer you get a rejection with no further explanation. Just like that. We've been giving you super positive feedback for two months, but now we're rejecting you and can't say why. Honestly be it Google or a no name company, you don't do that to a person. I really appreciate the way you got over it without making so much of a big deal out of it. The level of maturity you showed in that situation, to me, is worth having you in any company.
Doubt it. Think him having his YT channel might have something to do with it.
@@goguma-cr3di I find it impossible to believe that google can be google and only find out about a YT channel that late in the process. Then again, it would make sense that they wouldn't want google employees talking about it publicly all the time
@@magnusanderson6681 I seem to recall certain big companies having issues with employees running RUclips channels, so it’d make sense considering the precedents
Edit: I just remembered that it was TechLead who got fired from Facebook for having a RUclips channel
@@goguma-cr3di me too
May be he said somwthing at the very final stage, which was not said before.
Could be him having YT channel..
This is the one thing I hate in the hiring process. Not the rejection itself, but I hate that no full details are provided on why they rejected an individual. Piece of information that can better someone. Instead you get the bull get more work experience, we found a candidate more inline with our blah blah blah, or nothing back at all. This is the only part I fully with a passion hate. Can't do nothing about it either, can be biased as they want and cover it up. Keep up the good work and inspiration to people man!
It's ironic how interviewing in software development is so full of undefined behavior.
It's because the interview process is really stupid.
'undefined' enables them to hide bias and all sorts of prejudice under this category - 'external factors', 'we've decided to go in another direction'...whatever.
A lot of segmentation faults
Programmers are often illogical when dealing with humans.
big corporations take interviews on regular basis,not because they need an employee but because there are a lot of clients/companies who doesn't like to interview a random person and are afraid to fail at getting a right employee...so companies like google come in with recommendations of an employee and charge a broker fees for there service. It a Business, sometimes run secretly by handful of HR employees of companies(this is a example of passive income).
This meant a lot to me....struggle began since my college days. Then after facing rejection in more than 12 companies, I began working at a startup. There I learned many technologies. Now I'm in Infosys. But I really need to grow more and achieve a better place to work with better mindsets. You've inspired me so much!
You can do it buddy! I've been rejected so many times I can't keep track, but I always keep coming back.
It's indeed "strange" how they were saying "something came up, external issue, it's not you it's me"... lol. and then a remark, "have 2-3 years more experience". well if they can't give me a proper feedback, google or not, I wouldn't go somewhere where they're bullshitting me. I'd personally think they tracked me down and found something personal they didn't like about me, just didn't have the backbone to tell me basically.
Alexander Phoenix sadly it’s not about having a backbone. It’s about not getting sued. If they give strict feedback they could possibly open themselves up to a lawsuit.
@@dkchen Very much this, a problem that happens more today then ever is that a company is not just looking for someone with the skill, but someone who has a history of not causing a drama....and is from a clean social circle. Honestly the hiring process that those larger companies use is very much like getting a security clearance. They will do background checks, they are going to look to see if you have a history of doing the stupid, they are going to pay attention to how many unsavory types you have associated with. If your sister is a drug addict and your father laundered money for the mob then you might be in for a hard time. Those are both situations that bring a potential liability.
And a major concern is trustability. Employees of any ilk are given access and the chance of access to very valuable assets that do indeed have a market value, so if you are a ghost in the system with little to no family...it is likely that that right there may flag you. (although to be fair, that can also be a very employable trait, but let's not think on that one too much) I was told once when I was younger that when it comes to a security clearance is that they are not as worried about you getting a dui (still don't) but how you handle it. If you have a record for doing the stupid and trying to deflect and make it painful for all involved or shift the blame (and word gets around, you would be surprised what people are willing to disclose on even a casual cold call) well, those things are major red flags. But...if you do the stupid and then try to make it right...well it shows and decision makers are very aware that not everyone is perfect and that right there gives them an insight on how you will behave if there is a mess that happened inhouse that you were a part of.
"how you know da TRUTRU?"---Tom Hanks/Cloud Atlas
I know from being an insider that Google plays dirty when it comes to 'reference checking'. A lot of what the hiring managers do is actually illegal as far as labor law goes. And the worst part is it's not just Google that does it. If they aren't committed to hiring you, they can find any reason not to.
That feedback may be harsh, but its true. You cant fake experience. Also part of the reason they stretch out the entire process is in case someone better comes along, which is most likely what happened.
wow i didn't notice when 17 min passed.
Not even kidding, video ended and I saw it was 17 min and kinda did a double take.
Because he is a good story teller
It was a very vivid experience for me so it was easy to talk about :)
Thanks for sharing - it’s always difficult to get rejected on an offer and I know the feeling, but you got the right attitude.
I really like how positive you are despite such a terrible experience! I hope you find your dream job soon if you haven't already! Cheers man.
Thanks for watching and thanks for your support!
This was a good heartfelt talk. I think you've helped a lot of peeps by your insights and resiliency. You got a long career(s) ahead of you and you'll find that it may have been for the good. I think that they may have found someone internally. I had a similar experience with a University position once. I had passed all of the departmental interviews and was told I was to be given an offer, only to be told a week later that the offer was rescinded. I asked my friend who was an admin and she told me that they had people who were already in the pipeline for that position from within the University. I went onto finance/math and as brutal as it was, at least I knew the rules of the game.
I'm so sorry , honestly though for you to get that far you should be proud of yourself !! Not many get that far keep grinding !
Thanks brother. I appreciate your support!
Former Googler here, wouldn't take much notice of this. Could have been pretty innocent, like headcount got diverted/reallocated, demands of the role changed (ie. what was originally an L4 role could have been bumped to L5). There's a myriad of reasons beyond them digging up skeletons from your closet.
That's what I was thinking too. But why close his application? He went through a lot of interviews : /
Are all the reasons you listed considered "external" reasons? Because he said they told him something "external came up" and I am not sure if that means they found something out about him since he is no in google so he was being considered "external" or if that means what you listed.
Thanks!
@@xo.Frenchie It seems like it's based on skillset, as in he was going for a relatively niche team and there might not have been a lot of openings for related skillsets. That being said, it's very possible that your chances could depend heavily on the recruiter you're with. The person I know who is reaching the offer stage has had a wonderful recruiter. Didn't give up despite the applicant going through 11 team fit interviews lol. Very communicative and on top of things, plus recognized the applicant's talent. Maybe others aren't as lucky :/
@@26Sundrops yeah, recruiter definitely matters. but the thing I feel weirdest is 'after 2-3 years'. why that? after such a long time, one can lose interest in that completely and might have already been going through another path.
Just terrible that they wont save his application and if another position opens for the same role, bring him on. Instead they will make you start over and cold apply. It will be all different people interviewing no one will know you already progressed through. It sucks it feels like starting all over again from scratch from the beginning.
I love how Google's video chat didn't work.
Keep on coding, just wanna say the underdog software engineers are inspired by your experiences and they keep us going through the long headaches of algorithms and trying to crack the coding interview. Thank you.
I don't know why but yes I love the way you are talking
Hey man!) I also got an onsite interview with Google and ended up being rejected. I truly feel what u felt at that moment and it's really cool that u r not giving up.
Yeah it was one of the most disappointing things I have experienced. Giving up is never an option though. As my name states, Keep On Coding!
@@KeepOnCoding There are many better professions than coding . I am not telling to give up but just change your field and apply for jobs which pay better and are stable
My experience: Interviews depend mostly on sympathy. If you fit into the team, a company will accept a few knowledge weaknesses because you can learn that
this is one of the main reasons, kinda the same happened to me, it's just a waste of time, preparing your self, and at the end, just getting rejected. I feel sorry for your bad experience, but at least you now know you're capable to join any company :), keep the good work!
I've had a similar experience, it's was so disappointing at the time...
Looking back you can't know what would have been best for you, so there's no sense of obsessing over it, just knowing you did your best like you said you did.
Keep on keeping on, do the best you can to enjoy your workplace, and be sure that new opportunities emerge
Google's last-minute rejection is super frustrating. You may want to double-check any references you gave them. There is a service that does that for you. They do it for companies, but they also do it for private individuals that want to check their own references.
I feel you man, that absolutely sucks. It's definitely strange that they didn't give you any other options other than "come back in 2-3 years". I just failed my Facebook interview and when I got the e-mail back, my heart sank to my stomach like you said. I thought I had it because I nailed every algorithm question but turns out I came up a bit short on the design interview and I'm still regretting not saying more during that portion. Nothing you can do except come back stronger!
I applied online to Google for the University Graduate Software Engineering role, then about a month later I was contacted to do a timed online coding exam. A few weeks after I got another email from a recruiter about setting up a technical interview over the phone. I responded immediately and gave my availability like they asked..... no response from the recruiter. After a few days I followed up and the recruiter replied with,
"we are winding down our hiring for University Graduate Software Engineering roles" and "we will not be able to move forward at this time".
No reason. What a waste of my time. Luckily I had other offers on the table like yourself.
I wish you all the best. I failed Amazon interview (after f2f) a couple of months back and it still hurts. I am an engineering manager in a company and failed due to lack of preparation of leadership principles. I didn't explicitly named them while quoting examples which probably led to the failure.
and amazon block you from further interviews for a yer after you fail one apparently. At least you now why you failed.,, Or do you? Was that a guess or did you actually get some (unofficial) feedback?
Thank you for sharing your story; my heart sank to towards the end. Very insightful!
It was my dream job but life goes on. I appreciate your support brother!
I totally agree with you, it is quite disappointing to hear NOT being selected after all the hard work and attending series of interviews. I received another job offer after two weeks and accepted that.
Thanks brother for your message. Looking back is not an option. This is really inspirational for me. I desperately needed this right now. Thanks 😊
It’s heart breaking. I had similar experience with Amazon it probably took me over a week to recover from it.
the big thing about amazon, that they don't tell you up front is that if you fail to get past the onsite interview they ban you from doing other inteviews for 6 to 12 months. The details are not clear but I've had it confirmed by amazon friends.
@@julianelischer that is not true, I haven't passed an amazon interview once and did another after 2 months
I recently had attended Facebook interview in a similar situation, I thought I did very well BUT I was not selected. They match exact words to answers, and if we don't speak those words while answering they don't select / make an offer. IT is like word-to-word match of answers they expect to hear. Especially on Leadership qualities and situation-based interviews.
Did they tell you whey you were rejected ?
Like a robot
I did a phone interview with Google. I nailed the coding problem without much effort, but it turns out the interviewer showed up with **2** problems to solve -- not what I had been told would happen, nor did he say so up front. Following the advice I saw everywhere, I started with the "naive" (i.e. bad) solution and moved to the good solution. He stopped me at multiple points to discuss the complexity/Big-O of the solutions, etc. So he failed me because I "didn't solve the problem fast enough." My recruiter was happy to set up a re-do, but in the meantime, I had decided that I wasn't sure Google was a good fit for me, anyway (open office, structure, etc.) and they were _really_ pushing positions in the Valley over better options for me like Seattle. I also don't really dig their process, which is so time-consuming and such low odds even if you're a great hire. So I decided it probably wasn't the right move -- for me, at least -- and skipped. I'd reconsider it now that a few years have passed, but honestly, I still don't think they'd be willing to pay me enough to make the Valley worth it, so it would have to be another location.
I wouldn't apply even if I was a good candidate. The hiring process is too insane. If they paid me for the interview process maybe but they are wasting your time as their screening process. No way.
I can see the disappointment or just a lack of proper sleep in your eyes. After all, you almost got the job at Google which seems impossible to me. I guess having all those interviews and solving the problems was more exciting than the actual job at Google or any other big corporation.
Subscribed!
Thank you!
The good thing is you made it through a lot of hurdles many don't.
Its messed up that it didn't workout for you. But you did get some great experience and thank you for sharing it with us.
Thanks Mirko!
Getting rejected at such late stage sucks, so sorry it didn't work out. If I may add my two cents, a three round of onsite at google is unheard of especially only one round is coding. So you had a super easy interview. According to my recent experience (about a year and half ago), I interviewed for front end engineer and it was 5 rounds plus lunch, it goes like 1. Build UI component (multifunctional table/list) using API/js/HTML; 2. Algorithm; 3. Lunch; 4. Design client side of a google product; 5. Puzzle + algorithm; 6. Algorithm; The worst part is you don't know what category for each round before you go in. So in my case, when I stepped in the last round, I was expecting a behavioral round but just more coding and I didn't reserve any energy left, I walked in at 9 and left at 5, I was told things like: since transfer team is easy at google so we need to test your backend knowledge as well; or I see you have some coding rounds let's do one more; or I know there is no behavioral round because google is engineer oriented and we care about your coding/problem solving ability more than anything. So I did poorly for the last round though the rest I did well, I was rejected.
Comparing Google, Amazon, MSFT and Facebook, I'd say facebook really did a good job to prepare you by providing information needed for each round of your onsite, Amazon is a close second, MSFT prefer to mix behavioral in each round so every round is 45 mins coding + behavioral if there is time, the experience varies a lot like interview a front end dev but asked to design a database backup system; or you are told to use the language you are comfortable but you learned that the principle engineer is not comfortable with javascript after you are done, so all the time spent to explain syntax and nature of js but talk about test which you learned was the meat of the round.
All in all, I feel interview is just a numbers game. If you do some prep work and keep trying, eventually you will get what you wanted.
just apply again this year, you'll get it.
As he said in the video, he's applied before but was ignored but this time it seems the referral got him an interview, so unless he can get another one his chances don't look good.
This video came up like 20 times , finally after seeing it so many times I had to watch it lol. Thanks for the video , pretty cool. I interviewed for exxon , almost got hired lol.
Hiring manager probably fired after interview for something unrelated or they got someone that might have rejected in the past and later decided to join that they really wanted.
Thanks for sharing your experience....I’ve been rejected many times in multiple interviews in my life and each experience has made me stronger and better in future interviews....I’m glad you had that positive mindset to to keep yourself going....👍
Thank you, friend. Now, I received to enter interview in Google. I am now feeling exciting. Thank you for your suggestions.
Its a very nice video, regarding google job I have ever come through. I urge you to make more videos like this on future. Maybe with your colleagues sharing their experience of accept/reject in Google, Microsoft, Amazon etc..
Thanks for sharing your experience
Thanks for sharing about your interview experience!!! I do learn a lot from your sharing.. The world is big and there are many great opportunities out there.
Just recently had a similar experience with a company, got selected and at the end, they rolled back the offer. Heartbroken.
I feel your pain. I was also rejected at the offer review stage recently, which is indeed rare. For me it had to do with a culture fit mismatch, but they didn't give me any details. 🙁
Fuck them, there are other companies out there.
Culture fit...jeez...this is scary....what is the brainwashing u need to get accepted at Google
@@chuckitaway466 I can't really blame them, honestly. False positives are a lot more expensive for them than false negatives. And they get a ton of candidates, so they can afford to be picky and wait for a perfect match. I think I would've fit in well, but they only got a handful of hours to get to know me. In the end they got some combination of signals from me, or a lack of signals, that made me a risky hire. Luck plays a role there too.
Anyway, I went on to apply to Facebook and Amazon (among others), and I'm now getting job offers from both of them. 🙂
@@mhelvens That's great!
@@mhelvens what does "culture fit" even mean??
I don't think you nailed the slow website question.
You need to ask questions about the "specific" client. Are there logs available? Is it affecting more than just this user?
Identifying the scope of the problem is step 1. Based on what the user experienced, you want to understand that interaction exactly. This would help identify why this specific user is having a poor experience. If the request, for example, is not making it to the back-end (and stuck on the client), then it's a user-specific issue -- (browser or local system issues). However, if you have logs (and for enterprise systems, you should assume this is the case), then diagnosing through an enterprise logger would be my first step.
Anyways -- the key to ambiguous questions (scenarios) is to ask questions. Don't make assumptions about the context -- clarify the context.
Great point....thanks for sharing....after being rejected some people would just blow off the company and say they are not worth working for or find excuses....but you have to learn from your experience and try to understand which areas you didn’t do well in and go forward with the next interview with that knowledge
My heart sank for you as well man but glad you were able to be at a place that you're happy with!
You failed the 2nd part of your first interview (figuring out why the web app was slow). The correct answer is to first collect information from the user about specifics of what they are doing, when it occurred, what device were they on, was there a specific part of the app that was slow, etc. You basically gave the "i'll just dive in randomly and try to fix it, without fully understanding the problem" answer, which means you lacked critical information that might lead you directly to the problem.
I'm not an expert, but I'd have to agree. Things that come to mind immediately: "have you tried turning it off and back on again" vs "what were you doing when it happened?"
That, and blindly grasping for solutions is obviously a massive waste of time, which in turn, is a massive waste of money and resources.
Excellent comment. There are many reasons why an app may slow down. You can't attack the problem until you know what is causing it.
First you have to ask the user to turn the WIFI router OFF and ON again
it is rather easy to write than say. trust me you would be excited and many things would come to your mind at that moment.
Man, honest history to hear from some one man, I like your strength of sharing your experience on public.
I just a can say you that I failed one time in second interview Facebook, one online in Amazon, then 1 on-site interview on Microsoft about 5 interviews in a day, and then finally 1 on-site interview on Google Cloud, again 5 interviews in a day.. that one was the must heart braking experience of my life..
I just can say you that after all that pursuing of happiness on top-5 tech companies, I do not understand what the heck is wrong with me on those loops.
If there is something that I'll like from those companies is: "Please give a real feedback about", something that really helps you to grow on top..
cheer up.. not all big companies fit; sometimes small companies are the best way to go... and who knows.. you get more years under your belt and start your own tech company and then you'll be google's customer instead of employee :)
Thanks for the kind words Cindy! 🙂
Bro I can understand your feeling… don’t loose your hope..
I finished 5 virtual onsite interviews after 1 phone interview and failed. I received a negative feedback by one of the interviewers since I cannot solve a greedy problem.
He keeps saying that it is EASY, which makes me too nervous to think peacefully.
But greedy solution is something like "it is pretty easy, only if you know the direction" Still, I don't have strong enough mind to be clam.
After that I ace-ed the following interviews in other company. pretty smooth.
Please don't take the rejection as a rejection to your life. keep fighting.
Thank you for sharing your story, it really helps getting insight into the process. I wish you all the best on your journey ahead!
Amazing. Clean, fun to watch and SO educational. Great job! Thanks you so much!!!!
Keep your head up.
i also did not notice how 17 min passed. Thanks for sharing. Wish you all the best for next time. One of my friends was not accepted first time but second time he got the job at Google.
Google's loss.
This is giving me anxiety! Just did team matching at a company and have an update call with a recruiter tomorrow. I stumbled on this video at the worst time!
Hi Sam! Thank you for sharing your story! You tried your best and in the end that is what counts. This is going to be another valuable learning experience that will help you, life doesn't happen to us, it happens for us. My behind was handed to me on my 1st interview because I was stone cold frozen - couldn't talk and that actually motivated me to go to toastmasters and then volunteered to do public speaking for the Make A Wish foundation. I didn't believe it before but out of each of my disappointments came triumph! Keep rocking Sam, maybe one day you'll own Google!
Good point - life happens for us! Remember when one door closes another one opens
Never give up friend , I got rejected several times before getting a job in the end. All my friends got jobs before me but I didnt stop
Takes a lot of courage to share such experience. Really inspiring.
One of the best videos on this subject. Thanks for sharing your experience.
I had the same experience with Toptal, I've been rejected. Your video make Me keep up. I'll not give up
I ’m about to graduate with a CS degree…you are super knowledgeable…I’m in a panic about my job prospects . that interview process sounds absolutely rough
.
Thanks for the summary bro
Lots of valuable information. Thanks for sharing. ^_^
Thanks for watching!
You are the best, allowed me to feel normal, and to get rejected and most importantly to keep trying ( and guess what -> that's what your youtube channel says :-) )....you really kindled me...Thanks for uploading once again.
Thanks for watching Ayan :-)
They keep telling us that the market needs more software developers but the reality is exactly the opposite -- there are TOO MANY developers on the market nowadays and getting a job will be harder every year...
As someone who interviews developers, there are too many developers...many of whom call themselves developers but can't code a complex for loop, depth first search, or analyze an algorithm. Nowadays, I've seen more good than bad though, so that's a good sign.
darksteel78 who told you you need to know all the school book algorithms to be a good developer? I know many of them doing heavy kernel code both in FreeBSD project or Linux who would not pass a Google whiteboard test, but they are very respectable committers and experts in their field of interest.
Whiteboard tests are suited for young CS graduates and thats whom upper management wants to hire only; along with "minorities".
This whole IT market is sick nowadays...
@@spearPYN I agree. You barely use any of the major school book algorithms. I can't tell you the last time I needed Dijkstra's algorithm or depth first search in practice; however, I'm mainly referring to people who can't use the basics as building blocks to design a working system.
Saying someone would not pass a whiteboarding interview doesn't actually mean that much, ironically. It's a mix of skill and luck. I've interviewed people who were brilliant and still didn't get hired because 2+ other interviewers asked "weird" questions IMHO, especially for the areas the person was being hired for. Why are you asking a front end candidate about the intricacies of database caching? They should know about caching, sure. They should know some backend concepts, sure. But they don't need to re-design Redis from scratch!
If I'm hiring you to work on a kernel, you should know how the system you're working on is structured and how to make improvements to structures you normally encounter in that system. In that case, I'm talking drivers, threads, processes, pipes, locks/mutexes, etc. If you come in as a "general" engineer, I can't gear my questions to your expertise which results in a mix of real-world design questions and school book algorithms that are occasionally useful. If you haven't developed an area of expertise, your knowledge is...general. So, here's a general school textbook interview question for you. What else can I do to judge your skill level?
darksteel78 yup. But the sad story is that I noticed most big companies just dont care about hiring experts... they throw the same textbook questions at everybody regardless of their real world experience. It has become an industry itself -- learning how to pass whiteboard tests... :)
@@spearPYN Yeah. It's a problem. Up to a certain point, I understand their use. If you're fresh out of college, it's more likely you'll get these kinds of questions. And sometimes (a very loose use of "sometimes" here), you may realize a problem you've studied for appears in the real world.
If you're an industry veteran (5-10+ years in Silicon Valley specifically), you will get fewer and fewer of these schoolbook questions (that's my experience at Google anyway) and more high level systems design and management questions. Don't get me wrong. Those kinds of questions will still be there...just fewer in number and more complex than new grad candidates. This is especially true if you're going in as general software engineer where you could be thrown on any kind of project from OS development (Linux/Android/Fuchsia) to voice assistant w/ ML research (Google Search/Assistant) to self drivering cars (Waymo).
This is really a "consolidation of projects problem" in Silicon Valley where a few companies are doing 50,000 things and can't gear interviews for specific types without clogging up the interview pipeline due to the high turnover rate and preference for younger employees because, you know, less money.
Never let anyone make you feel down. Not even the biggest company. Always keep your head up !
I will!
i’m about to graduate with a CS degree…ur super knowledgeable… more than me and now i’m in a panic about my job prospects 😅. that interview process sounds absolutely insane.
Sad to hear that ,
But there are many other things in life that are important than working for somebody.
Thank you and I agree.
Thanks for sharing your story, I hope you get your dream job soon.
ashish kumar Thank you! 🙏🏼
Lmao I read this as, "I hope you get your dream job son." Was quite confused to say the least.
I got offered a Google support role in 2015 but ended up rejecting then last minute based on role mismatch, health scare and IP rights conflict. I also didn't want to work for Google straight out of college. And initially the recruiter said I had to wait 2-3 years to finish my degree and they contacted me back then but by then I was so over the role.
Thank you for sharing your experience.
I wouldnt sweat it.
If you passed with them you can basically make it in any other big tech company easy.
Is it possibly because they found out later you have a popular channel. You are obviously a great programmer
I think because you didn't complete the last xcoding interview, the one where you short 10 minutes?!
That was the one that set you back a step.
They probably wanted to see you solve and type in each code on whiteboard or computer and explain each step as you proceeded along.
If you were allowed to complete that step then you would probably have gotten the job for sure.
Some people try many times before getting accepted by their ideal dream job.
If you really want to get hited with the company, keep practicing and critiquing and honing your knowledge and skills and reapply again until you receive an employment with the company of your dream.
Do not feel bad man, pretty sure someone told this to you, but sometimes it is just luck. :) Or sometimes destiny :) just keep exploring and move forward. It is a lot better to fall forwards than backwards :) Thank you for your video. :)
Thank you so much for sharing your experience and all this info! It is very helpful. Best of luck!
man that's really shitty. I genuinely wish you best of luck. I'm super positive that something even better will turn up! In the meantime Keep On Coding!
love it, thanks you and @keep on coding
RESPECT.. I felt your pain bro! It hurt me a lot too....
Very interesting story, man. I wonder how many times this kind of thing happens? Thank you for your videos.
I have friends at Google and they’ve never heard of something getting rejected after team match.
@@KeepOnCoding this is crazy, i hate the interview process, just finished up 2 months ago
could you talk about what you and that manager who was trying to convince you to get on her team talked about? What exactly made you feel like you guys vibed well? It seemed like you were sure that they would've wanted you on their team
Two possibilities come to mind: (1) the team that wanted you somehow lost their headcount (i.e. number of additional people they can hire), though I don't know why they would avoid telling you that (2) somebody caught on (late) to the fact that you were asked the same question twice in the interview process, and didn't say anything the second time. You're supposed to say something if you've already seen the question. The interviewer is supposed to have a back-up question for that case. (I mean, the interviewer is also supposed to double-check what you've already been asked, but they can't unhire him for that)
They also don't like it when you publicly disclose your interview questions, incidentally. Especially not along with the answers. So if they somehow suspected that you might be a person likely to do that, say, on your youtube channel, that might also be a big red flag.
And yes, they do (or at least they are supposed to) tell you not to do those things as part of your interview process.
What kind of BS response is this?
(1) the team that wanted you 'somehow' lost their headcount.
If this is the case, then that 'somehow' is due to the company/management's ineptness. 'Though I don't know why they would avoid telling you that'; as if they would indulge in admitting ineptness.
(2) somebody caught on (late) to the fact that you were asked the same question twice in the interview process, and didn't say anything the second time. You're supposed to say something if you've already seen the question.
Again, it would be more of the ineptness of the interviewing side. And, as if there is a hard-fast rule that you are supposed to say something. 'If you already seen the question?' He was asked the question, twice. He was not "shown" the question. 'The interviewer is "supposed" to have a backup question?' That may or may not be case. I'm retired now, but as an engineer, I had been through interviews where the same question may have been asked not just twice, but multiple times, even during the same interview. This is useful to determine if a different or dissimilar answer is given for a particular question.
'They also don't like it when you publicly disclose your interview questions, incidentally.' Nowhere does it state that this person made this video just prior to being rejected. That is conjecture on your part. 'They somehow suspected that you might be a person likely to do that'. So, they can foresee the future, but not able to mitigate simple procedural mistakes, on their part? 'And yes, they do (or at least they are supposed to) tell you not to do those things as part of your interview process'. Again, conjecture, but maybe another sign of ineptness on their part, don't you think?
The Dunning-Kruger effect.
@@pintorpi333 I don't know how any of that, even if it were true, makes my response a "BS response". I'm simply suggesting some possibilities of what could have happened, based on my personal experience "from the other side of the veil". I'm not endorsing these possibilities as a perfectly rational response on the part of a huge disconnected entity. Yes, surprise, a big company has many idiosyncrasies and sometimes (often) they affect people outside of that company. Getting an understanding those idiosyncrasies is still useful, regardless of whether you consider them signs of "incompetence" on the part of a company you are anthropomorphizing as if it's some kind of single entity that can be competent or incompetent. While also apparently somehow conflating me with that entity, simply because I ventured to express some ideas about it. For my part - again, from firsthand experience - I would call it more "bureaucracy" and "tragedy of the commons" than "incompetence".
You'll never know why they reject you. Keep it up. Still full of hopes. Not the end of the world. I can definitely feel you as I also went through a lot with several big tech giants in Silicon Valley. Trust in God. Cheers!
Thank you!
Thanks for sharing info I am going to attend next month .
How was it, is it going on right now ?
1. BROOO LMFAO I WHY WAS I SO HYPE DURING THIS I WAS LIKE *OMG OMG HE'S GONNA GET THE JOB* BUT LMAOOOOO I FORGOT ABOUT THE TITLE BAHA
2. AHHHGFGG DUDE THERE IS SO MUCH KNOWLEDGE AND THINGS TO LEARN I FEEL LIKE ITS TOO MUCH AND LIKE HOLY CRAP U KNOW SO MUCH AGH this is wild
Lol imagine what I was feeling when it was actually happening. It's really hard to get into Google.
good lord take a xanax
What kinds crack u sniffin bro lmao
Q. - What do you do if someone calls and says that the website is slow:
A: -
1. - Check if the user has a slow computer by asking them questions about their hardware & OS.
2. - Find out if their ISP is having problems in their area by asking if they previous had slow problems with other site or their internet & checking their ISP twitter & website for info.
3. - Ask them to do a tracert to the site on their computer too see how their router behaves during connectivity & also ask them to do a speed test on their network..
4. - Ask them if they are using hardware firewalls & what kinds of ad blocking softwares they have on their browser.
5. - Ask them if they are using any kind of VPN. and what DNS they are using if they are using a different one like Google 8.8.8.8. or OpenDNS site.
6. - Ask them if what speeds package they have on their ISP and if they are using Wireless or Cell network to connect to the internet or if they are in a public network.
7. - Ask them to do a netstat on their computer to find live connections from their computer.
8. - Ask them if they are streaming or transferring files of any type during the visit of the website.
9. - Ask them if they are using pfSense or OpenSense software firewalls and also ask them if they are using VM's or hypervisors.
You'd be surprised on the people that are still using very old laptops these days and they expect it to work like new computers of 2019......LOL
Most of the time when a user calls in regarding speed problems its usually on their end. - You can also check special website & google to find out what websites are down or having problems.
Once you checked all this on their end, THATS when you start checking things on your end like APIs and stuff....LOL
Ive been studying for the Cisco Network Certification.......LOL
Great input. Thanks for sharing!
For search bar they would probably expect terms like ajax and JavaScript and for slow site they would want to hear indexing the db tables and load balancer first... Thanks for sharing your experience
I just got refused by some FinTech company today. Got really upset after three rounds phone interviews.
I know the feeling. Keep your head up!
@@KeepOnCoding Thanks for your reply. Really encouraging. Keep fighting on.
Wow, that’s really disappointing and most disappointing not knowing why after coming so close. If you can’t think of any red flags , I would assume one of your former employer stained your background somehow. Glad you recovered from that rejection and continue to move forward.
I think you're right. Thanks for the support brother!
Man this seems rough. I know we can never know but Im guessing they found someone else (most likely internally) and didn't want to hire someone they didn't already know. Total guess I could be wrong, but I think you just got unlucky. Hopefully you aren't too hard on yourself best of luck! I know the feeling of getting rejected from Google....it fucking sucks.
I have my third round interview today. Wish me luck!
4:52 - I've received same question on many interviews.
Thanks for sharing! Hang in there. Never know what the future has in store.
Sorry to hear that man -- what a shame.
The interview process is so drawn out, don't they realize people need to work and have bills to pay?
Aaaand do you think they have a reason to care? Probably not, especially being as prestigious and sought after as they are in the job market.