I feel like I’m going to bomb my iOS interview with Uber next week. I’ve been an iOS engineer for 4 years and the thought of interviewing again makes me want to vomit (seriously though I get bad anxiety). However, I know I can do the job. I haven’t looked at Leetcode as that’s a terrible way to gauge if someone is good for a position. But based on chats I’ve seen on here, you have to gain a certain score on CodeSignal to move forward. There are a million different resources online to prep and that alone is overwhelming Is it in my best interest to do the interview anyway and gain experience or not waste anyone’s time? TC: $150k (Comcast is notorious for crap pay) @uber #uber
Do your best, I believe in you! Sometimes you feel as though you are not prepared but actually do very well! Right after the interview take lots of notes on things you think you did well and poorly. If you do not get the role try to improve for the next one 😄
Thank you! Yes I can be hard on myself as I’m a bootcamp grad and never had to dive into CS concepts. So I’m all in my head when it comes to speaking to senior engineers about CS concepts
Fellow iOS dev with the SAME issue anxiety & similar YOE here🖐️ Is this the phone screen? If yes: push further out if you’re confident you can dedicate a little more time to Leetcode to have at least a 50\50 shot at passing the phone screen. Onsite? Just take it & fail it. Why? For the experience? Sure. But really it will help your anxiety for your next interview. Especially if you’re not desperate for a new role, failing an interview is not the end of the world. Think about it, you could still FAIL the interview even when you think you’re fully prepared and that’s even more devastating. I wish I applied this mindset a couple weeks ago before allowing myself to slip into weeks of isolation & high anxiety because I was desperate to leave my current job and scared of failing these interviews. In terms of the prep resource overload: I feel ya. My advice though is narrow down prep resources that fit your learning style and only focus on those. For example, I assimilate faster through visuals/audio over reading texts so my main resource was YouTube/Neetcode videos, Raywenderlich iOS videos. For system design, focus primarily on mobile; the only one I’m aware of atm is Weebox’s Repo on Github. Skip Alex Xu (not a bad resource though) if you’re feeling overwhelmed bc it’s primarily targeted at Backend. Goodluck!
Thank you! This is really helpful advice
I am iOS at Uber. So much depends on your interviewer. Some phone screens are easy, others are hard, but it’s always a leetcode question. So, practice as much as you can before you do the interview, and hope for the best. It’s all a crapshoot anyway.
thanks for the inputs, do you have any tips for Uber system design?
It’s usually pretty open ended. Alway talk about trade offs, ask questions but not too many that you seem ignorant. Talk about calls you would make and why, lead the talk. Start high level then work your way down to the details. Everyone asks a different question too, so also depends what interviewer you get.
What level is this for?
I want to say 2 or 3. Recruiter initially reached out about a senior iOS role and I made it clear I don’t believe I’m senior as there are many aspects of iOS development I haven’t touched.
Im on the same boat, they said it’s senior but I think it’s L4/L5 flexible