World Conflicts
Yesterday
587
Is "From the River to the Sea" So Wrong?
Tech Industry
Yesterday
1203
This resume landed the guy a $500K job at Meta
Personal Finance
Yesterday
1442
Thank you AAPL and NVDA
World Conflicts
Yesterday
683
Israeli precision-guided munition likely killed group of children playing foosball in Gaza, weapons experts say
India
Yesterday
702
'Hindutva': The Radical Hindu Ideology That Seeks to 'Push Christianity Out of India’
I completed my virtual onsite sometime last week and the thing that surprised me were the Coding rounds. It was just 45mins with 5mins for introduction and 5mins at the end for any questions. So, we essentially get just 35mins to solve the problem, which is fine if they ask a LC med or LC med-hard type questions. But, they start with a basic question and take 5mins to explain the problem and when we get it right, they will bring out the follow up which is a LC hard. And, take another 5mins to explain the question. I was able to somehow come up with a suboptimal solution and the interviewers picked on the edge cases. If it was a 1hour interview, I would have all the time to clean up the code and cover all the edge cases but when you only get 25mins to solve a basic question + LC hard, I think it's kinda unfair. Is it just me or has Google started to look for people who spit out LC type solution? Or may be the bar is set so high(or I'm dumb) that the process seems unfair to me? P.S: I have nothing against the interviewers. They were super kind, friendly and polite. I'm just mad at the process. #tech #google #interview
It's very luck based imo, some people are getting LC mediums, some even easy, and some are getting hards.
Yeah that's unfair right? If you are going to ask LC hard, at least you should ask that straight away. Why waste time with a basic question? I thought it was used as an ice breaker or something. But even if that's the case, you shouldn't be expecting me to give a fool proof solution.
Life is never fair buddy
I got 2-sum on my Google interview lol
What the fuck
Is this 10 years ago or recent?
You don't have to solve everything they throw at you perfectly. The point is to find your limit. Even if you solve the hard one, I wouldn't be surprised if they ask another follow-up.
So, it's not bad that I missed the edge cases?
Yes. And the point is not even to find your absolute limit, but for the interviewer to collect as many signals as possible
You are right op, the process is bullshit, you should have your luck with you to get easy question or get known question, otherwise no ody can solve a LC hard problem in the stipulated time.
yup for me the initial question was trivial, just eats up some time to smack out. then the interviewer is fumbling tryna come up with the examples to set up the followup. I see where s/he is tryna go w/ it and help finish coming up w/ the examples that would necessitate the followup. Extra slow when doing ascii art instead if drawing on whiteboard if real onsite. So now we ain’t got much time left, and the followup is pretty hard. End result for the report is alls I did is a simple block that’s at the level of demo you’d do when first learning language features such as loops and if statements lol.
Wow that's even worse. And they ended up rejecting you for that interviewer's incompetence?
still waiting but it don’t bode well for me lol
I faced something similar. I was told that there will be two problems . (35mins for 2 problems combined ,5m intro,5m qs) Was asked a LC medium so I solved it using BFS at around 16-17min mark. Interviewer was happy with the code and asked follow up on coding it using DFS recursion. So that took another 12/13 mins to explain the logic and solution. With about 8/10 mins left I was asked LC hard and was expected to solve and code it in 10mins. I was able to come up with pseudo code and logic but clearly couldn’t finish code. Ofocurse failed
That's pretty rough. Did the interviewer had a specific solution in mind that was different from yours? Because that also happened for me for 2 rounds. They never gave any constraints so I gave solutions that were optimized for time and not space. The interviewer wanted a solution that was space optimized, of course they didn't say it out loud 🙄
OP. Before coding the BFS , I asked the interviewer if I can proceed to do BFS to which the person said yes go for it. No constraints were given. I was just a little taken aback that given 8 mins I was expected to come up with logic + Code for LC hard. It is what it is. I believe in the interviewers mind they were expecting DFS recursion, but frankly speaking I am very hesitant in terms of adding recursion to production level code due to how easy it is to mess it up and create huge issues
Google was the worst interview I gave from coding round. The interviewer gave a question which could be interpreted multiple ways. I clarified my understanding and explained why I feel the question question can be interpreted multiple ways and took a confirmation of what I was about to implemented. I finished my implementation with all corner cases and then when I was trying to optimize the interviewer asked why I need a particular function which raised suspicion to me so I reconfirmed what his expectations were. At that point 30 mins in he says that’s not the question. I rewrote the whole algorithm and made it work for his expectation but he gave negative feedback and cost me a job. I have provided the recruiter feedback about it.
Dang. What a 🤡.
The problem with Googlers is that interviewing is at least 50% of their job. Also the interviewers quite often don’t know what the need for the role is. If the interviewer had a real need to hire based on a critical gap for an essential timeline/project, then they would actually assess you on if you can do the job.
like u had to come up w/ followups not in the question description itself?
I guess only time will tell if those follow ups were just to fill time or was used as a data point to reject me.
Bar is high!!
🥲
gotRekt should be a bar raiser next time https://www.youtube.com/watch?v=6F9iygUoW64
Another perspective: maybe you are not well prepared.
Again, I was able to solve both questions in the given time. I just didn't have time to cover the edge cases as I was running out of time. Unless I saw that question before, no amount of preparation would have helped me.
It’s an interview not an exam. An interview is life cumulative and not semester cumulative you shill