Uber's Staff Software Engineer Interview Exposed

In this video, I share my recent interview with Uber for a Staff Software Engineer role.
Recruitment: Learn how Uber's recruiter contacted me via LinkedIn, discussing the promising initial stages.
Coding Screening: Discover the LeetCode medium-level challenge and my performance.
Online On-Site Interviews: Explore the five interviews over three days, covering coding, iOS, system design, collaboration, and leadership.
Challenges and Triumphs: Insights into specific interviews and my experience.
The Outcome: Understand Uber's decision and the feedback provided.
Key Takeaways: Lessons learned, emphasizing preparation and resilience in interviews.
Join me for a detailed look at my interview process and gain insights into tech job interviews. Like, subscribe, and share your experiences in the comments.
Chapters:
0:00 Intro
0:14 Recruiter reach out
0:41 Screening coding interview
1:23 Prep Call & Interview Structure
2:10 iOS Domain Coding
3:36 Collaboration & Leadership
4:05 Algoritm Coding
4:45 iOS System Design
5:13 Backend System Design
7:05 Interview Feedback
8:23 My Learnings

I am a staff software engineer because I have been with the company for like 14 years. I would never pass these interviews. This is scary as hell for me. I have never encountered a problem that even resembles the Leetcode problems.

[@IgorGuerrero]

But he aced that... He failed the practical interview which most people would pass, I'd say he wants to be an educator instead of an engineer if I was interviewing him.

[@BillClinton228]

Senior hiring managers were expected to select CV's out of a pile in a FAANG company, all the CV's they rejected turned out to be their own CV's with obvious changes like the name, education and work history so the managers wouldnt recognize them. Conclusion, they would not hire themselves with their current requirements. The elitism and gatekeeping is off the charts in software.

[@mmuekk]

Do you have a news article link?

[@artemkalinchuk]

The interview process seems broken

[@IgorGuerrero]

@@BillClinton228 funny I wanna read that one link us

[@_cocoalabs]

It’s silly to reject someone who is a mobile developer for not developing the best system design for a back end. This industry has gotten out of hand.

[@zshn]

See there lies the problem. Companies test & hire for 'Software Engineers'. What you have experience in does not matter. You should be a 'Software Engineer' with mobile development experience. Start looking at expertise as an extension not core. At the core everyone should be a 'Software Engineer' which includes being good at the stack or atleast having sound conceptual knowledge. Google 'T shaped skills'.

[@perc-ai]

No he was just incompetent.

[@ny8762]

Do you know what does staff mean

[@lr7815]

In a real scenario you will do research to come up with the best design, these system design interviews are stupid. If you don’t recite the exact design they use or have in mind you’ll fail

[@Wiz1112222]

@zshn. So by your logic it's okay to asks surgeon about psychology? Because, you know, surgeon is just an extension of doctor

[@user-fx3ou2jh9k]

No matter your experience level, technical interviews are a nightmare.

[@nabihbawazir8019]

Becouse the higher your experience level the higher the bar

[@ahaaha8462]

Most of them hardcore interview crackers are in hedge fund these days

[@BillClinton228]

Especially interviews on Hackerrank, if your application works but not exactly the way HR expects then you have failed. Also most of that questions dont make sense and the examples they give are terrible like arrays or varibles that arent being declare anywhere and having to write api consuming functions without knowing the data structure in the jso, because remember opening a new tab and checking an api json is illegal according to their rules, and googling a problem is out of the questions.

[@theashenone564]

That's why you open gpt4 in another monitor and use a audio to text translator 🫣🫣

[@ViralKiller]

You get rejected for these interviews, then you realise the guy that didn't hire you, put a modal over the hamburger menu, so you can't click it 75% of the time...I'm better than most these people

[@andrey_tech]

🥲

[@reeldeelz2940]

yup.. the easiest way to get in is to know someone on the inside..

[@dreadsocialistroberts]

Interviewed with Uber twice. Both times had to deal with a hostile interviewer. It was clear they didn't want to interview me (or just in general - I know interviewing people can suck if you're doing it a lot). I took the loss as a win that I wouldn't be around someone like that. There used to be a "no asshole rule" in tech. That idea seems to have been victim to defenestration.

[@pieflies]

There has never been a “no asshole rule” in tech. You should try not to be an asshole anywhere but there are always going to be assholes everywhere.

[@someguy6075]

No assholes? Except for Steve Jobs and all the rest?

[@cornoc]

@@pieflies yes sadly some assholes are too useful to get rid of, or they turn into assholes once they become established and comfortable

[@siliwhiz]

Thought you have to be an asshole to work at Uber. Maybe he/she was gauging your level of assholery 😂 #SuperPumped

[@Ch17638]

Ever posted questions on Stackoverflow? I often wonder how people work with devs like that or if they actually have the stones to be like that in person.

[@markeissler]

100% issue with the industry is that unless you have been working with their exact stack they see it as a disadvantage. And with so many variations available it makes the entire situation unnecessarily difficult. No other industries work this way. The value is in the individual’s potential over the long term and not in what they can provide within the first 30m on the first day.

[@andrey_tech]

I absolutely agree

[@ShopperPlug]

What’s crazy is that they looked and searched him to recruit him only to deny him. That is just wrong. So I can’t blame him for “picking” the wrong job role. No developer should ever be “ Dinner for Schmucks”.

[@TedBouskill]

@@ShopperPlug Amazon does it better. They are trying to screen you out in a phone interview and online code test. Once you get the Amazon loop they think you will pass and it's too confirm it. After all, why spend all the interviewing time (and money) to only reject a candidate?

[@EikTuKaTu]

I am a contractor, so I go to these interviews regularly say at least once a year and sometimes interview for 3-4-5 positions at once until find something interesting. A lot of times I can say the interview questions, especially on the algo design side are much much more complex than anything you need to do in the actual work, which is bizarre. I don't understand why I need "google" level engineer skills for an interview, just so I could do boring CRUD style API afterwards. I also think, that people who design these interviews usually work for 10+ years in the firm and hence have never themselves went to interviews. As say one of the questions I was solving, was to right an algorithm to buy/sell stocks for most profit - time limit 10 minutes and unit tests 7 out of 10 are hidden :) Very realistic scenario! Conclusion would be, keep interviewing and dont feel bad about failing, as there are 1000's of algo questions and only so many you can remember, so a bit of luck is needed. And I know you shouldn't memorise algos, you should learn to solve them, but I would argue within interview time constraints at lot of times that is simply not possible, as usual time limit per question is 15-45 mins, depending on the firm.

[@jonintc]

As a software engineer with nearly 20 years experience, I did the leetcode grind earlier this year for the first time. The stock algorithm you listed was one of the problems I solved. I already forgot how I solved it and would not pass today unless I had a lot of time. The same goes for leetcode 211 which was mentioned in the video -- I immediately recognized it as a trie data structure but completely forgot how I implemented that. I would recommend solving leetcode for practice though. It keeps me sharp in the language of choice, and it is great focus on a core problem as opposed to the frequent multitasking and/or context switching we have to do day-to-day in our jobs.

[@RohitPatil_Tech]

Thanks for sharing your experience Andrey. "There is a price you are paying everytime you are interviewing." 100% true - same experience interviewing for Senior iOS Engineer.

[@ahmedalsaedi3849]

I love how specific you are with the experience, going above and beyond to the leetcode number

[@andrey_tech]

Thanks!!

[@israelmanzo8725]

The industry has undergone a transformation due to ineffective leadership. Even a seasoned Meta iOS developer, exposed to one of the largest mobile app codebases, faces unwarranted scrutiny. Companies often claim they want candidates to succeed, but their actions seem to set them up for failure. I've had a similar experience in my case, whether it's for a Staff iOS position or even a Senior role. The interview process itself feels like a full-time job. Thanks Andrey for the video.

[@hanchen8106]

I love how thorough you are with the process while being concise. Thanks for the wonderful insight!

[@andrey_tech]

Thanks! That's exactly how I like my content

[@thewholetruth34]

i had a nearly identical experience to your "bar raiser" interview a couple months ago. I thought the guy was trying to test me but realized later he was just being rude and aggressive. Crazy

[@andrey_tech]

It happens... Thanks for sharing = )

[@tongobong1]

@@andrey_tech The most important interview question you should answer: when you are so good at a hard interview and they reject you what this means tip - what is the current state of IT industry?

[@DriveandThrive]

These positions are ridiculously hard to get into. They pay a lot but man what a hassle.

[@SweepAndZone]

Why do you think they pay so much ☠️

[@FA-sr6lx]

​@@cayennetaright

[@therealnotanerd_account2]

They don't pay that much really. At least here in Europe.

[@SweepAndZone]

@therealnotanerd_account2 yea, they don't pay much for css scrubs, if you get past that, they have decent salaries

[@dave24-73]

You are better off creating your own company and being a consultant, than chasing these opportunities. Consultants are the highest paid in the industry in most countries.

[@andrey_tech]

Good advice, thank you

[@darkopz]

Consultants still have to sell themselves. But it’s typically to a different group of people within the company.

[@dave24-73]

@@darkopz usually once you have 2 or 3 good clients, the selling takes care of itself, it’s true you have more job security working for someone as they take the risk of keeping work coming in, but that’s also why most consultants make 2-3 years income in one job, so the risk is balanced. Also in the IT Industry consultants only get it right 30% of the time, so yes they fail 70% of the time, try doing that in your usual job. So consultants do less work, are in high demand, earn considerably more, and have a high failure rate.

[@dchardin1]

@dave24-73 Can you point me to any sites or contacts of people you know who have done that? I am actually considering making this move. I have been in software development for years. Even after refreshing all of my skills and slaying interviews, I am constantly passed over. It's been this way ever since the Pandemic. I've always dreamed of getting into the business side of things and selling my services. Now may be the time to make the leap.

[@EditioCastigata]

@@dchardin1 No idea about cold sales, but it helps having some industry experience and contacts from getting it. Then you're known for something, and the clients come to you with their problems. And you're in a good position to sell to adjacent markets. After 20yrs working, 15 as consultant, I switched to being an employee at megacorp -- were it not for my plan to start my own company, sell a product instead of knowledge or time, I'd become a consultant again no question. And yeah: Everyone and their dog projects their wishes and traumata onto the interview process; most of their staff would fail. The goal is not to discover how much you don't know, after all.

[@hs6910]

First time at this channel, I like how positive your mindset is Andrey! Bad interviews often destroy a person's courage. One question though, I believe you've made a couple of switches between companies in your career. Do you believe long notice periods have an effect on whether or not you'll be hired at the place you're being interviewed at?

[@andrey_tech]

Hello, thanks for the comment! It depends on the company and the urgency of the particular position. Big tech companies usually move slower, and they typically don't mind a 1-2 month notice period. Startups and smaller companies, on the other hand, might be more inclined to seek someone to hire as soon as possible.

[@nerdobject5351]

There is a lot of gate keeping during the interview processes I have found senior level engineers want to impose their seniority and whatever their egos feels like.

[@gerardsk8ordie]

Very helpful explanation. Thank you very much. I'll follow you.

[@binks3371]

software engineering industry is turning into something to avoid if you wish to keep your mental and physical health

[@johnlime9065]

Unfortunately, yes this process is slowly destroying the profession altogether.

[@AlejandraStamato]

Ty for sharing your experience , i loved your video and overall attitude

[@denischudinov2379]

Thanks for sharing your experience! Wish you success in landing the dream job

[@andrey_tech]

Thanks 👍

[@reeldeelz2940]

The dream "job" is working for yourself

[@someguy6075]

So let's see, the two interviewers who didn't like you... One expected you to hit the ground running on a very domain specific thing under extreme time pressure. An engineer at your level (new viewer but you seem competent and got in the door for a staff interview to begin with) can be trained up on that stuff in a couple days, and building a working UX in 50 minutes is a bit crazy regardless. And for backend design, can't say whether the interviewer was right on technical issues not knowing the specifics, but he sounds like kind of an asshole. Maybe you dodged a bullet.

[@andrey_tech]

Thanks for the comment! Yeah, You're right. I'm not trying to justify a bad feedback in this video, I just wanted to show a real picture of how the interviews are going and what to expect

[@SomethingEternal]

I can program an entire game system in 2 days. I'll spend a week designing the UX. 50 minutes? Seems like they're seeking an emergency role for when they botch something worldwide and need you to save the company.

[@manonamission2000]

sometimes when faced with someone more qualified than they are, they have no choice but to rig the interview... that or the role was intended for outsourcing

[@joesoultanis3724]

Harsh reality of any iOS interview is that you need to prepare a lot for the first type of question. That is standard. The BE architecture Bar Raiser seemed to maybe in a bad mood - that's just bad luck.

[@kokalti]

This field is ridiculous. It's like you are being selected to be an astronaut. At the end of the day this is a desk job.

[@andrey_tech]

haha love this comment, totally agree

[@brinckau]

The yearly salary of an astronaut ranges from $104,898 to $161,141 according to NASA. A staff developer may actually have a comparable, if not higher, salary. Therefore, they are entitled to be demanding, I suppose.

[@samuraijosh1595]

@@brinckauno thats not true. an astronaut gets paid higher, one. two, staff developers dont even make 110k.

[@brinckau]

@@samuraijosh1595 Try to search about this on Google, you will find official sources on governmental websites. An astronaut can get paid higher, but not necessarily. The salary range I mentioned seems to be correct. You can try a similar search for staff developers.

[@SweepAndZone]

​@samuraijosh1595 maybe in India where you are from. But in most places experienced developer can easily break 100k

[@datapro007]

Thanks Andrey, great video. I think all of us have had negative interview experiences. Sigh.

[@kareemdasilva]

Thank you for this video so much Andrey Tech!

[@arunraj2527]

Don't do it in one day. I did it for the Uber staff engg same position. Started at 9 am and ended at around 6. The breaks in the middle did not help me. I was so exhausted and unable to think not mentioning I didn't get a good sleep that day. It was horrific but the interviewers were nice.

[@andrey_tech]

Makes sense! Thanks for sharing your experience.

[@arunraj2527]

I was in EST timezone. They did gave me an opportunity to split.

[@atmamont]

The track for “just” a senior position is the same. I did sound exhausting when I was talking to a recruiter and your experience confirms this. So I’m flipping the coins now, let Uber be the last one :)

[@rafabertholdo]

You saved yourself from dealing with a code base bigger than the Linux kernel to request a car.😅

[@nathanlopez3918]

Oh wow, I’m glad I’ve found your channel. ❤ new subscriber

[@andrey_tech]

Cool! Thanks =)

[@theolivebella]

I recently discovered your channel and I am loving your content. Would it be possible to do a video about designing a notification system?

[@andrey_tech]

Hey, thanks for the message. What kind of notification system? Push-notifications? Pub/sub?

[@theolivebella]

@andrey_tech I should have been more specific. Mobile push notifications - FCM is a popular choice but not sure if companies like Meta use it or have their own infrastructure for this. Let's assume they don't use FCM. Then do the clients use http long polling, keep persistent connections to receive notifications? That would mean millions of persistent connections that the servers need to maintain. What if there are multiple apps(think FB, instagram etc) on a device - would each client open a connection to the server? - which is clearly not scalable Also, what happens in scenarios where the mobile app is killed by the system. How do devices get notifications then?

[@andrey_tech]

​@@theolivebella Ok, thanks, now I understand the question. Yeah, interesting problem. I'll come back later to this one.

[@Ch17638]

Technical interviews can be hard as you often have to deal with Lead devs with a certain mindset, this mindset is more often than not very set in their ways, I often ask about their reasoning and see them immediately switch off when a new idea is introduced. Then when asked to elaborate on why they don't think something will work there are often pauses and 3rd party blame like 'I don't think they will go for it'. I was fortunate enough to work with many different lead developers and technical architects who can explain in great detail their reasoning and I have always learned something new from each of them, but there simply are just some devs in companies that have been there for too long, didn't have much of an interview process when they joined and is fine with coasting on what they know and will aggressively push against anything that challenges their comfort zone, those are the companies to avoid.

[@NotMarkKnopfler]

You know something...? You can make as much money doing plumbing or being an electrician. Screw 'em. I'm 53, and have been working in software and being paid for it since 1988. When I attend an interview, a lot of the people interviewing me weren't even born when I was writing software. There's nothing wrong with that, of course. But a lot of the interviewers aren't interested in _experience_ any more. They are interested in niche, esosteric areas of algorithmic programming and computer science. I'm not an uber programmer - I've worked with enough of them over the years to know that I'm not. But I have a LOT of experience. More than most. So I know bullshit when I encounter it. The great thing about being my age is, I can call them out on it in interviews and genuinely not care one way or the other what the result of the interview is. So, when given some BS algorithm to write, I like to ask them under what application or scenario such an algorithm would apply _to their business or core application_ . If they can't give me an answer, then I ask them why are they testing applicants on niche areas of knowledge that are not applicable to their core business? I've already lost the job at that point, so I don't care. Like I say, screw 'em. You'll all come to the same conclusion as you get older. Trust me. Software development is BS on steroids. The majority of software teams are over resourced, and under utilised, with 40 or 50 people being employed to produce bloated, bug-ridden, poor performing software that runs on massively complex, and expensive hardware platforms that a team of 5 guys working in a shed could do a better job of. As you can tell, I'm pretty disillusioned with the software development industry. But again, my opinions are based on my _experiences_ over the last 35 years. And my _experience_ tells me that the software we are writing today consumes 1000x the computing resources of the systems we were using in, say, 1989, and _does nothing that the old systems from the 1980's couldn't do_ - the only difference is the presentation is much nicer these days! It's not even necessarily any faster these days, even on modern distributed hardware platforms. In fact, I'd take a small wager that it is _slower_ . Anyone that's worked in banking applications will know what I mean.

[@johnlime9065]

This is so spot on. Although, I don't think "They are interested in niche, esoteric areas of algorithmic programming and computer science" is actually true. Before this process strange puzzles were used with the same lies about how they need to filter and avoid bad hires. In my experience this new hazing method is used in the same way. To get around discrimination laws. This hurts my sole as this profession has been my whole life and it might be best to leave it behind.

[@Andrew-ua772]

Thank you for such a fair story. Good luck next time!

[@leniwolf]

This experience mirrors almost entirely my experience with my last game dev interview. everything was 100% dandy and smooth until the very last interview. I got a lot of great feedback at the end though.

[@dragonborn1996]

3:05 As someone going through interviews right now, what you said made me laugh and it is so relatable lol

[@MuttleyGames]

An older friend of mine with experience says that it's as much of an interview for the company as it is for the worker. If you see that the people are unpleasant, you can say that there is no point in continuing the interview and end it there. He sometimes goes to interviews to see how rusty he is and what are the offerings on the market.

[@andrey_tech]

I agree with this approach. Thanks for the comment

[@C6Silver]

If doing iOS UI, especially under time pressure, SwiftUI is the only answer. Bringing up a Storyboard should be an immediate disqualifier. Thanks for sharing your experience!

[@dchardin1]

If you are going to get passed-on, then this is the way to do it. I have a feeling that they were very close to bringing you on. I am currently aspiring to get to your level but I am not there yet.

[@andrey_tech]

Yeah probably. I hope you succeed!

[@dilibau]

“Passed on “😂😅

[@ZettaiKatsu2013]

please guys : reject abusive conditions and demands. It's just about demand and supply.

[@DrewConley]

Great video - Thanks for sharing your experience!

[@andrey_tech]

Thanks

[@atienejonathan3139]

😆 "i had flashbacks to those hello world days, but this time the world was not that friendly"

[@dawidos0095]

Thank you for sharing this.

[@Baba12xr56]

"Interview was 5 sections, each lasting 60 minutes!" F*** that, I would walk out, that's ridiculous. I bet I can come up with questions the interviewers would be dumbfounded and would crap in their seats

[@andrey_tech]

lol

[@mrwillis5339]

Going to say one other thing. I told a friend who is a psychiatrist about a lot of these shenanigans such as agile scrum, hostile interviews, throwing each other under the bus, etc. Her conclusion was that these were terrible on mental health, and in many situations mimicked social experiments. Even in your short account, we can tell you experienced trauma from some of the process - especially the hostile interviewer. It if better to not feed the beast.

[@tongobong1]

Yes but he still needs a job so how to get one without going to experience it again?

[@CoreDump451]

@@tongobong1 Don't apply to FAANG or similar companies

[@user-uf3em3on7v]

Hello, Andrey! If you want to find any ideas for video, pls make one more video about system design interview for app like e-payments. Looking forward for your reply!

[@andrey_tech]

Hey, thanks for the idea! =)

[@roh9934]

Hey Andrey, I saw the leetcode problems you mentioned and i got confused. Do you have some list of leetcode problems you'll recommend that is less in number but more effective to nail these rounds?

[@andrey_tech]

Hey, I would recommend solving 75 leetcode problems. There're lots of different lists. I like this one, it is called Blind75 - leetcode.com/discuss/general-discussion/460599/blind-75-leetcode-questions

[@stopthecap2644]

It’s crazy how much time is wasted at these companies on both sides… imagine spending 1 full day+ across loads of people for every job opening… and many of these companies tend to have high turnover rate

[@andrey_tech]

True. Most Google employees quit after 1.1 years (on average)

[@stopthecap2644]

@@andrey_tech I've known/met many of them. The common complaint is that they're either let you go for reasons like you not being a "good fit" ie they want you to think and talk like them, or they quit due to being overworked as the demands are incredibly high and many times completion unreasonable expectations in result.

[@FatherPhi]

the cost of working with a bad hire is much worse imo

[@johnlime9065]

@@FatherPhi This hiring process does not eliminate bad hires. I have had to help a company re-organize because of a high amount of incompetent engineers. I have direct experience with a company unable to hire (copying FAANG hiring processes) and loose 30% of it's wealth. I have seen companies hire bad hires and then promote those same people ("Peter Principle") and then end up bankrupt or unable to grow past the startup phase. If anything code interviews are directly responsible for bad hires as they often favor actors able to probe to find the tablet solution presented by the interviewer. Huge companies are able survive with a lot of turnover and incompetency but it really doesn't benefit anyone.

[@jimmiejohnsson2272]

Its gotten way out of control at the big popular tech companies. With this exhaustive testing of areas that areas that are huge it ultimately comes down a lot to luck - did you get an algo question on something that you worked on a lot or not? Did you also happen to have experience with some framework that they throw at you? I remember a really ridiculous interview question on data compression that was basically relying on you knowing that there is a template specialisation for boolean types that stores them as bits. I didnt know that but mustered on using bitwise operators, which is something I very rarely encounter and is just an odd as hell question to use for an interview. The pickiness of the interview questions are just ludicrous these days, guess there are just to many applicants per job for the hot tech companies…

[@andrey_tech]

Yeah, that's a really strange interview question!

[@translatingIdeasIntoCoding]

You're becoming our hero Andrey. I've a few questions: 1. BE system design: was it compulsory to be backend or you requested it? Can we select 2 mobile SD interviews? 2. iOS app: They required you to use contact kit or just dummy data? Tech stack is optional? Can you use swiftui/ async-let etc.. ? Pls keep sharing your experiences...

[@andrey_tech]

Hey, thanks for the comment 🤟 1. They ask to choose any interesting large-scale project you previously worked on. So you can go with another mobile system design. I decided to go with backend system design because I had a prepared solution. 2. Dummy data. Tech stack is optional. You can use swiftui etc.

[@mosheyankel5017]

Андрей, привет! Спасибо тебе за контент! 2 дня назад я проходил system design в такой же по размеру компании. Все прошло хорошо, но за два следующих рабочих дня не получил фидбэк (в оба предыдущие этапа ответили максимум на следующий день). Означает ли это, что я уже не прошел?

[@andrey_tech]

Привет. Я бы сказал, что два рабочих дня это нормальное время ожидания. Если дольше недели не дают фидбек, то тогда уже шансов маловато. Удачи с результатами!

[@kd-wk8nd]

I wouldn’t lose any sleep over not ending up in Uber..

[@andrey_tech]

Of course, I just wanted to share my experience, maybe it will be useful to someone

[@MrSimcas]

Hello, I'm sorry to hear that it didn't work out, I wish you good luck in your future interviews. Something I wanted to ask you as a Mobile Developer, is how do you manage to answer or study about backend system design interviews? Because I heard that most big tech ask about backend system design interviews and as a Mobile engineer I know too little. Thank you.

[@andrey_tech]

Hi, thanks for the comment. I would recommend reading "Grokking the system design interview" materials. github.com/Nitin96Bisht/System-Design/blob/master/Grokking%20System%20Design%20Interview.pdf

[@usptact]

I still remember that interview where they were looking for a data scientist yet almost all questions were about pure software development.

[@user-mp9um5qj3u]

Hi Andrey. I am an Junior Android Developer and I watch your system design videos. If possible, can u tell us about the way android interviews happens at meta. BTW your videos are good.

[@andrey_tech]

Hi, thanks for the comment. Take a look at the "Meta interview story" video. I talk about iOS interview there, but it is very similar for Android. I will try to shoot some videos for Android developers in the future too.

[@user-mp9um5qj3u]

@@andrey_tech Thanks for your advice. 👍

[@xtu373]

Please make some course of data structures and algorithms in Swift

[@andrey_tech]

Hey, thanks for the comment. Maybe in the future. Btw, take a look at this repo - github.com/kodecocodes/swift-algorithm-club

[@aintnoDat]

I think they get them or ask the bar raiser interviewer to be like that on purpose. I had 2 bar raiser on 2 different occasions and the interviewer was extremely rude. One of them just ended the call saying I'm not satisfied by this answer and left.

[@ghijjhhjjuh4950]

Nice video very helpful

[@andrey_tech]

Happy to hear!

[@stanislavkindiakov6334]

I am a principal engineer, time to time I go to interviews to other companies like Delivery Hero, Hello Fresh, Zalando, etc. Interviews are usually bizarre, interviewer tells you that they don’t expect much coding at such a top position, therefore you need to implement a complex algo online in 40 min. Logic? No)) Or interviewer comes to design challenge in a bad mood, so you know you failed before the interview started. As result, my pass rate is about 50/50. Of course, you should prepare, but there are many pitfalls you have no influence over.

[@andrey_tech]

True! Thanks for the comment

[@EditioCastigata]

Challenge designed spontaneously or on a whim = wouldn't pass managerial oversight since the result would be arbitrary, at least not comparable to that of other candidates. But yeah, chances that you get a second chance after making their manager aware are pretty nil.

[@sunrae3971]

It does not matter what industry just fire 75% of HR and the skilled Worker Crisis in the West ends. That never ending interview process sounds like unpaid torture.

[@theashenone564]

*skilled worker crisis in the world ends

[@gencymeri8770]

Still the pay is no where close to what a plumber or electrician makes. It's getting ridiculous. Software industry is an over saturated field with extremely talented people available on the market thus the companies can torture us like racing horses or better like greyhounds. I have been working 20 years as a SWD, once a person works for 2-3 years in the same company, the focus is 98% on that company business domain, everything else get forgotten or rusty at best. I'm surprised you did that well.

[@nhanimaah786]

Who cares? Software is not even cool anymore. Can't wait to transition into a grown up field.

[@sepg5084]

​@@nhanimaah786you cared enough to comment, you cared enough to be in software too. Grow up, kid

[@gencymeri8770]

@@nhanimaah786 Who cares? Generations of people who have invested decades in software education as well their careers. Cool is subjective, mostly for not grown up adults, the compensation on the other side though, it is not subjective, it's easily a measurable artifact.

[@nhanimaah786]

@@gencymeri8770 okay cool then keep up the chase and stop complaining. Go for those rounds of interviews apply for 5000 jobs and get ghosted. The truth is software devs are not special anymore and companies know this. They know they can ask you for 9 rounds of interview and if you do not do it, there are tens of thousand others willing to do it. It is obviously a dying field. Nearly a million people laid off in the bast 18 months. The job market for software is a mess. This is why I advise younger ones to learn blue collar skills or get a job in the medical / health care field. The demand there is crazy. I know many people with computer science degrees from great universities who cannot even get a basic dev job. Software dev is an overrated garbage job.

[@gencymeri8770]

@@nhanimaah786 You are swinging your position way too much. Now you made some valid points which I already addressed in my first original comment.

[@matisscukurs5535]

Thanks Andrey!

[@user-fn8qj6rn3x]

Sometime interview is actually also based on the interviewer attitude as well, this is a double side selection also. I recently interviewed with Monzo bank, and rejected by the coding stage. The guy can not say anything about valuable feedback on my worked solution. Instead ask me why u want to implement Protocol on time limit tasks? 😮 I thought this is a simple clean way to do so. And in then end I asked they interviewer, what u don’t like in Monzo, he said well, I don’t like others review my proposal it take time and waste. And for other questions he just answer mess. I start from this stage I found out this is not the company I will like also😂

[@the_teemo1]

Thanks for sharing! A little controversial, but just wanted to get your thoughts if LLMs like GPT could potentially solve these interview questions in the (near) future?

[@andrey_tech]

They can solve interview questions right now, but you can't use them in an interview 🙃

[@EmoPorEmilio]

I recently had such a similar experience for a senior swe role. Heartbreaking. I had never before spent so much time in an interviewing process, and they told me no after the last possible interview (culture). Now I don't know if I have the guts to keep on trying.

[@andrey_tech]

Wow that's sad! =( Take a break. After that keep on trying...

[@tongobong1]

you should wait for better times.

[@AFellowGentleman]

Of course, they don’t want you to spend two weeks learing on the job. Thats too expensive. They rather have 5 people spend a month looking for the candidate who can land on his feet running at the job.

[@andrey_tech]

ahahah

[@marvelousvids.9600]

I recently had an initial interview with one of their "head of.." and it was the most unprofessional and unpleasant call I have ever experienced. He was 15 minutes late (I almost canceled the call) without offering an apology, asked a lot of silly questions to which I provided examples, and he yawned throughout, giving off an impression of disinterest in hiring anyone. It seemed like they may have conducted the interview just to fulfill their internal recruitment procedures. If this is the representation of the company, I can't think the level of toxicity within.

[@exapsy]

Ive been in such interview, but without the leetcode I had an actual code-challenge which was about the actual job and one where there was no coding test but the interviewer was rude as hell and antagonistic with me. It's like he didn't like me from the start. And his colleague, yes there was a colleague and a SCRUM "Trainer" there, his colleague was barely speaking even when asked to say something. Which was really kinda rude. Like the backend colleague asked the frontend one "you can ask your questions now", "ah, I dont know, how would you structure your css folder". I was blasted, wtf? That's your question? For literally the biggest at the time food delivery app at my country, that was rude as hell to me. It's not like he was testing me, they proved themselves to be just ... rude. And the job was for Backend, but what kind of question was that. Why does it even matter how I structure my CSS folder. It was the rudest most antagonistic interview Ive had, I felt like the dude was trying to fight me but I remained gentle and relaxed

[@jeanmas4197]

Principal software engineer here with 40 years + experience. In my experience, there's 3 types of technical interviews: 1. They want to know what you can do and how you think. This is the one you can pass. People are usually friendly and encourage you. 2. They want to know if you do things the way they do things. This is hard to pass and they'll often be rude. You don't do things like they do so you suck and they want you to know it. 3. They want to know what you cannot do (the opposite of 1). What you are good at is not interesting, they want to know what you suck at (in their opinion). The interview is focused on this. As soon as you seem to know what you are doing/talking about, they want to move to something else. They will be rude and will fail you. It's unlikely to pass 2 and 3. I once interviewed for a position with no DB experience required. Interview was of type 3. I nailed every question and exercise so the guy started to ask about DB queries (again DB not required for position). What's the query if you want to do this or that? I nailed most of them until he finally found one query question where I wasn't too sure. You could clearly see how happy that made him so he could finally fail me. With more experience now, when I feel this is a type 3 interview, I just start failing every question on purpose cos nothing good comes out of those interviews and I avoid stress I don't need.

[@andrey_tech]

Wow, thanks for the insight!

[@manonamission2000]

Gatekeeping, B-players hiring C-players... browse any corporate org chart and patterns emerge

[@gourabsarker9552]

Sir do you earn 200k pound sterlings a year in uk? Plz reply. Thanks a lot.

[@IffyEdem]

My buddy interviewed with door dash. They were late to the interview. Not my friend. The hiring manager. My buddy stayed in the Interview waiting for 15 minutes.

[@rmo9808]

I interviewed for a place a month ago they are just getting back to me now...to setup another interview.

[@sadBoiDev]

Had a interview with snap for iOS. At Leas Uber asked you to code something in iOS, snap was only hard lvl leet code questions 😢

[@andrey_tech]

Wow interesting! Same thing at Meta actually..

[@frustratedalien666]

If an interviewer is rude to me that is the best sign I can get that the place isn't a good fit for me. It is one thing to argue about architecture and totally another thing to try to talk down to someone who can't fight back due to being in an interview.

[@andrey_tech]

Makes sense

[@michaellema8852]

What do you recommend for preparing iOS System Design questions?

[@andrey_tech]

Check out my videos on iOS System Design, I have many of them Also, take a look at this repo - github.com/onmyway133/awesome-ios-architecture

[@darkpassenger9155]

Please make more videos, they are good

[@andrey_tech]

Thanks. Will do! Taking a break for a few month

[@SCBiscuit13]

I'm kind of tired of the interviewers being rude and being polite to them.

[@mrwillis5339]

Some advice. Doing coding tests to learn data structures and algorithms is almost exclusively beneficial only if that is what the job requires? Why would you put yourself through so much? It is degrading and at the end of it, maybe work for a company with all manner of issues including using $32 billion of debt over 14 years to finally be profitable? What was the pay?

[@TechnoForbes]

Did you used swift for algorithm? or any other programming language Thanks

[@andrey_tech]

Yes, Swift

[@xtu373]

I hate solving leetcode style quastion, However I'm good at building things like an app or backend APIS etc... What advice would you give me is it possible to join Meta without leetcode questions?

[@andrey_tech]

Unfortunately, for FAANG companies, LeetCode questions are mandatory. At Google, they claim that their internal data demonstrates a strong correlation between a solid performance on algorithmic interviews and subsequent job success

[@andrey_tech]

But I agree with you, sometimes leetcode questions are frustrating 😄

[@xtu373]

​@@andrey_tech from where did you learn obj-c and objc c++?

[@user-pn8dq6vt4s]

This is like an electrical engineer hating circuit diagrams. You might be in the wrong career.

[@spencerwilson-softwaredeve6384]

@@user-pn8dq6vt4s The only reason people do leetcode is because its required to get a job. My guess is 10% of developers like doing leetcode for fun, the other 90% are normal human beings.

[@faykguru]

incredible that they don't permit the hiring manager to make their own decisions; it's difficult enough to build a great development team without such constraints.

[@ashwin4911]

Such a coincidence I interviewed for the same position Staff Software Engineer, Wallet (Amsterdam) 2 months ago and also didn't get an offer. The overall feedback was mixed but the interview was extremely difficult.

[@andrey_tech]

Interesting! Good luck with your future endeavors +)

[@mforce2]

And yet with all this tough interviews and all that the software that comes out still sucks big time. How is that ? I have the Amazon TV Cube and about 1 out of 10 Alexa gets stuck when I tell her to sing a song ... Now if I wanted to get a job at Amazon they'd probably fail me big time and yet ... When I hear about some famous software company I'm like , thanks , I'll pass , the interviews are all hard and full of algos and crap. Why do I need algos ? In my entire software career I've never had to implement one algo really. Even if I would pass what would it be in it for me ? Salaries are not great ( at least in the EU ), expectations are high ... Also there's that stock options for most of them which I don't like ... I will be stuck or lose money if I want to leave

[@EditioCastigata]

I'm staff-level and do a lot of algorithms, data structures. For frontend and device QA we've other people.

[@mforce2]

@@EditioCastigata To each his own. I've never done 1 algo as a programmer nor was there ever any need to. All the algos that I needed were already done.

[@_K_W]

These people act like they are hiring you to work in a one person office and the fate of the company rest in your hands. If they see the need for your skill and have the ability to grow you internally then make the decision or have the balls to hear it from the deciding panel why you didn't make it.

[@tongobong1]

The main lesson to learn is this: hard interview means a lot of people are competing for the job.

[@patrickwitter4437]

What is your linkedIn?

[@itsworkinprogress]

Just a feedback from my side: You could have avoided the negative feedback regarding the architecture, if you would have explained in the beginning why you had chosen this approach. Larger solutions require different, more complex (and more cost intensive) approaches than smaller solutions. You design the architecture for the needs of the solution and for bonus points you could e.g. explain which components (e.g. a load balancer) you included or left out, due to which reasons, after discussing it with the customer.

[@shantanushekharsjunerft9783]

Just curious, aren’t you concerned that your current employer may find out that you are interviewing?

[@andrey_tech]

Thanks for the comment. I've already left Meta

[@jovictor3007]

Yeah if you fail the contact list ,it looks bad.very bad that is like the first project along with the menu app in all swift books.

[@guitaripod]

Thanks

[@OroborOSX11]

I absolutely refuse to interview for these mega companies. I’ve been doing iOS for 15 years now, and I know that 80% of the junk they want to interview me on is just CS trivia and junk that has literally never once been relevant in over a decade of Silicon Valley tech startup iOS engineering.

[@andrey_tech]

Totally makes sense. Thanks for sharing

[@wphanoo]

You should refuse any intereview that requires that sort of tests. That's literally free work for them, and disrespect for you. Do yourself a favour devs, don't bite into that sort of thing.

[@tongobong1]

BEWARE: The harder the interview the smaller is a chance of getting the job. I decline the invitation to interviews that are hard.

[@davorama]

When I hear someone saying "I am super excited" in any work related context I immediately lower my expectations.

[@andrey_tech]

= )

[@flowtalks2548]

Assuming the things you are telling us are true, the "better" candidate ("best fit" who "won") will probably soon regret joining Uber. Arrogance or rude behaviour during the interview process is a BIG 🚩RED FLAG. There is no excuse for this and guess what: you have right to stop the whole thing immediately (and - maybe ask for contact to their supervisors to explain why had you decided to jump off the "interview" train). If recruiter is "playing the games" with you, there is always a potential strategy of asking direct question: "why are you misbehaving?", "what is wrong with you?" The fact you were given feedback by an intern (after DAYS of being in the interview process) is a lack of respect. Fun fact: this whole Uber thing is not even profitable! So ... is it worth to work under additional (potential) pressure?

[@abdulmueed2844]

i would have never gone for this interview process after finding out that process is this long. I specifically hate live coding challenges bec they are crackabl but also are disrespecting and mostly lazy effort from hiring team

[@xtu373]

Why you left Meta? That's the company i want to work for. What are pros and crons working at Meta for Software devs?

[@andrey_tech]

Oh, it's a long story... I think I'll make a video about it later.

[@xtu373]

@@andrey_tech Maybe you can tell in short here

[@andrey_tech]

@@xtu373 I didn't enjoy my time at Meta for several reasons. One of them was the unreasonably stressful work environment. After spending over 2.5 years there, I decided to move on and recently joined Bloomberg.

[@xtu373]

@@andrey_tech was it because of the visa? Please make video on it

[@friction5001]

WTF just because you don't find the right way of designing a backend straight away doesn't mean you can't collaborate with your peers or spend some more time to reach it. Companies need to relax more and clearly they missed out on a good engineer.

[@darkwoodmovies]

This is the problem with a lot of these "old" big tech giants like Meta, they started before all the industry standards were developed so they have their own version for everything. It's kinda hard to move from a big company like that to a more modern company, you really have to re-learn everything on your own.

[@andrey_tech]

Absolutely true! 100%

[@xtu373]

From where did you learn obj-c and obj-c ++

[@andrey_tech]

When I started learning iOS development 10 years ago, there were no Swift yet 😄 Hence I learned Objective-C.

[@xtu373]

@@andrey_tech how you learn that books?

[@andrey_tech]

​@@xtu373 Books + Information online

[@KamiMountainMan]

Do they pay for 6 7 days of interviewing you for a position that they can hire and fire next day?

[@andrey_tech]

I wish.. haha

[@Dom-fs8om]

All those interviews and they probably knew by 2nd interview if they were going to hire you.