Tech Industry
Yesterday
1758
Always sell on vest is a financially ruinous advice
Health & Wellness
Yesterday
718
How do I stop being fatphobic?
Health & Wellness
Yesterday
880
Awkward question r: Terrible odor after pooping
2024 Presidential Election
Yesterday
430
Black, and thinking of voting for Biden?
Tech Industry
Yesterday
364
Nvidia vs Custom silicon
Hi folks, Few weeks back I got the opportunity to interview with Uber for senior engineering role. The interview loop started off with the phone screen, question was not from LC and I would categorise it as LC hard category, I was able to solve it without hint and all of my test cases passed. I got invited to virtual onsite. I had in total of five onsite rounds and I thought I nailed all of them. Here is brief summary of all : First coding round : Question not from LC but I would categorise it as LC medium hard, I was able to solve it without hint. All test cases passed. Interviewer asked for reducing time complexity which I talked through. Second coding round : Directly from LC hard, was able to solve it without hint. All test cases passed. First Design round : Popular design question, nailed it. Second Design round : Nailed it. HM round : went pretty good. I was pretty satisfied from my performance, all interviewers were friendly but two days after interview got rejection from recruiter saying I was not up to the mark in data structure and algorithm. Not sure what went wrong and I tried asking for detailed feedback and recruiter refused to give detailed feedback. I did some retrospective on my rejection and here is my thoughts : 1. I am not on H1B currently and got picked in H1b lottery. So, my H1B visa transfer process may take two months, it may be a red flag to HM as I may not be able to join sooner. 2. The position got filled. 3. I took some time to debug in one of the coding round but was able to fix it before time limit and any hint. 4. Uber is just being picky. Reaching out to community to know if any of you were in same boat or can help me figure out what went wrong ? #uber #interview #rejection
Maybe you didn’t explore alternatives in the coding rounds. Like talking about trading off memory for time. Or not proving correctness. Could be bad luck with the interviewers you ended up with. Do consider the results and feedback, but don’t get hung up on it. Interviewing is largely a numbers game.
valid point, thanks !
I just started a senior position at Uber and I agree with above points. My lc hard round I walked the interviewer through multiple possible solutions and gave the trade offs etc. But also maybe I was lucky because i had the exact qualifications they needed for the position. These are %50 luck in my opinion.
Mostly you suck at coding and don’t realize it.
Sometimes it's just indeed about other factors, like click with a team, fit, etc. In those cases, companies tend to keep the detailed feedback to themselves and reveal only the "skills" part of feedback to you. You can answer every question perfectly but the team might just not be a good fit.
It’s sometimes just a bit of luck. Keep applying. Sounds like you’re 90% of the way there
Does Uber really ask LC Hards for junior roles?
Yup, got LC hard in phone screen with 2 YoE
Was this for a 5b role or 6? The expectations increase a lot for them
That was for 5b
How much LC did you do to solve LC Hard without hints?
I had solved around 700 LC by that time
Exact same thing happened to me. I was told the design round did not go well even though I think I nailed it. The interviewer kept pushing me away whenever I was leading the interview and he did not have a clue on those things (I was still polite and calm and also discussed what he pushed towards) which gave me a hint he’s a dickhead and that’s what it ended up to I guess. So sometimes its not in your hands so let it be and move on :)
Hey OP, Did you receive rejection in a email or a phone call with recruiter? My recruiter from Uber has setup a 30 minute feedback call after virtual onsite, just wondering what it could be!
Recruiter scheduled call with me to convey result
@op: what was the coding qs asked ?
Don’t over analyze. It just wasn’t a fit. Move on and apply again later. Sometimes it’s not you. 🤷♂️
valid point, thanks !