The irony of most of the interview prep courses out there is that they were almost all created by ex FAANG engineers who turned out to be much better at creating TH-cam videos that they were at being software engineers.
I totally agree that the interview process should not just be focused on leetcoding interviews - especially for Sr+ engineers, but from recent experience with FAANG as an engineer with 25+ yrs experience, what I found was ... screening calls .. 100% leetcode (HARD in my case) .. so if you can't pull leetcode hard Q's out of your backside (perfectly) in 25 mins you don't even get to the 'onsites', where, you get another THREE leetcode HARD interviews, followed by a System Design and a behavioral ... this was the pattern across the board. The focus, no matter what your seniority, seems to be leetcode .. which is what takes 90% of the prep time going in .... as I Sr guy I can do Sys Design all day long, because it's closer to what I actually do as a Sr engineer .. but the leetcode stuff.. well that's never been part of the dayjob and requires practice..and luck! Such a terrible and contrived way to evaluate Sr engineers IMHO
I don't know how AWS hires, but as one of the senior engineers in a FANG company, there is NO WAY you can get away with 30% coding in your studying time. Things asked of a senior engineer is still so code heavy that you will definitely fail if you only allocate 30% time and are not a coding genius by birth.
I hear you, if you can't get past a phone screen it this advice doesn't work. My point was once you get an interview loop stop over-focusing on leetcode questions.
I could not disagree more. System design and behavioral interviews are easy if you are already a good senior engineer. I have 10 YOE and I barely need to prep for these to be moderately successful in most interviews. Coding problems, on the other hand, require countless hours of study time. If you can solve "Leetcode #4 - Median of Two Sorted Arrays" optimally with no study time, you deserve a Nobel Prize (and yes, Amazon asks this in interviews).
@@ALifeEngineered You're not fooling anyone. I have a staff engineer freind at Amazon. He has told me of the horrors. Everyday, all the top management gather around a secret underground statue of bezos, they have to chant "come on jeffrey you can do it" while they sacrifice an important part of their souls. My friend had to eat his adopted child's goldfish.
This was an excellent video. I would point out that a lot of senior/principal engineers focus on coding so much because the LC game has come up while they were busy building things over a decade+ career. It's the hardest thing for them to do because it's the most removed from their actual job. LC interview questions have you draw on DSA concepts you may not have seen for two decades, while behavioral and system design questions often draw from your actual experience.
Yep Buddy after 14 years of experience I'm like ... year DS and Algos .. i'm too old for this ... (don't get me wrong .. i can figure out a solution ... but won't be as fast as I'm prepared for it)I think I will retract from my Amazon interview :/ (Senior Cloud App Architect)
You've hit the nail on the head here. Writing function-level code while talking about it was very alien to me. I had to practice that skill because I was tripping over myself on otherwise simple algorithms.
Totally agree w/ this comment. Behavioral, system designs type, and knowledge domain questions more reflect the years of experience. Leetcode style questions are a completely different skill set not reflective of the day-to-day, so they typically need more time to prep for.
On system design: "These questions are easiest to answer if you have the experience, if you don't, it will be exceedingly apparent". So all senior engineers have experience actually scaling systems to millions/billions of users? I think not.
Many senior engineers have experience scaling systems in general. Doesn’t have to be for millions, the concepts are much the same. Once you know what to look for, you know it.
@@CVFunStuff As far as I know.. the majority of scaling is things like a gateway for throttling requests based on rbac, providing smart load balancers (in triplet to avoid downtime) that can remember what server (or group of servers.. farm) a specific user (via request header details) was sent so it can continue to send that same user to the same server(s), and ability to build stateless back ends (with caching of some sort if need be) so that you can just start up another instance.. which itself should join a server group to be included in future requests once its ready by the load balancers in play. Is that not the gist of it?
@@b3owu1f That's one tech stack, sure. It can be simpler than what you described. You don't necessarily need to send the same session to the same server; most servers will round-robin all requests and session tokens can help ensure a user's session stays validated. You don't necessarily need to throttle based on RBAC either, although it's a good optimization. You don't even need stateless backends (although I personally use K8s); a single, multithreaded server instance on a powerful machine could do you well enough for a small to mid-sized project (up to hundreds of rps). It's surprising how many requests a basic setup can handle. Only when you truly get to millions or billions of rps do some of these optimizations start to matter.
Lots of good information here, thanks! I have 14 years of experience as an engineer, of which 5 as a senior, 1 as a software architect, and overall during these periods the last 2 years I've been a tech lead. My last 6 years have all been at a well known tech company too. That said, if I got a question like "Tell me about a time you strongly disagreed with your team" I probably wouldn't know what to say as I feel that in all my experience I have NEVER seriously disagreed with any of my teammates - in all the teams I've been I always had a surprisingly good rapport with my teammates and the things we did disagree on were small and inconsequential, hardly worth mentioning. However I have disagreed with engineering managers and even our head of engineering, and in some of those disagreements I was able to make a compelling case and get what I and the team wanted, whereas in other situation my opinions were acknowledged but the course of action set. I left the company recently and I've been interviewing. I found that I am very bad at interviewing, because I was often stumped by behavioural questions such as that one - where my immediate answer was "never disagreed", or I just couldn't tell them of a time I did X because I just couldn't remember specifics. To the point where somebody told me they thought I was a beginner. Cool, but if I'm such a beginner then how was it that I have all these achievements - managed to lead teams, run critical projects, deal with stakeholders and deliver things that were loved by our customers? Well it's because I wasn't prepared for these types of interview questions. Now I am prepared, I have identified a set of stories that I can tell these people, but now I feel like this is also disingenuous, because anyone can prepare and give good sounding stories during an interview, yet that doesn't mean they will actually be good at doing the job.
Oh, you can prepare good stories and you should. But a good interviewer will ask you very specific questions and it will become apparent really quick if you were a protagonist in the story or just a bystander. Imitation only brings you so far.
@@j.metzger1730 Not really, it's all about perception. Most hires are based on perception of the candidates and not their skill. Even absolutely incompetent people will get hired and given a good salary.
@@j.metzger1730 That's if the interviewer is paying attention. I've found that the best interviews have been those that felt like conversations rather than interrogations. I've had conversations about projects and systems I've worked on, and I also asked about some of the interviewer's projects and gave my thoughts on some of their issues. These discussions do go into details, but that's good because that can further clarify the extent of your expertise. At the other end, the worst interview I had was one that had the interviewer asking rapid fire questions about specific theoretical models, design patterns, and acronyms, scoring me on how many I got right and how many I got wrong, with no discussion around any of these topics. That interview stage could have been replaced by an online form.
@@El3ctr0Lun4 I agree with this because you can’t prepare for this kind of interview style. It’s whether you know it through experience and you can also see how the person come up with solution and be able to support it even go deeper to clearly see how much they know. I think this would be a good way to assess a candidate
Lovely what you said, and thank you for that. I worked at Amazon, an according to my buddy I was expected to code like him, design like him and think like him because I started in a L5 role (as him). Language was not a barrier because we both speak Spanish. In fact after one week working on a project he stopped joining any meeting because I was supposed to answer all questions (no writing documentation exist because he worked alone, in fact I must say SIM tickets were poorly documented if you try to find out why some technical decisions were done that way). I recall once my manager told me to get more info about a process and when I asked my "buddy and mentor", he says that it was not my work and I need to spend more time coding. I ended up quitting, because you could be a good technical developer (I am not consider myself the best but I do my best) but the lack of business info and the lack of support was a nightmare. In fact, in the starting training sessions when they tell you you must rely on your team in order the avoid that feeling of the impostor syndrome, well my lovely buddy made feel that way. My big advice, those companies (FAANG) like any other companies have their pros and cons (like any other job). Do not idolatry them (in my case the salary was not that high, a 10% raise in compare to my previous job, so it did not pay off the nightmare I experienced). And I am the kind of person that do not mind working extra hours as long as I am learning (in fact the project was quite interesting). Try what you think it is best for your career (and probably you realize these kind of companies are not meant for you, and you know what.... It is OK)
This is great. It's about time someone with real-world principal-level experience at FAANG disrupted the scammy coding prep resources. Wishing for a product manager to make a similar channel 🙏
Really great explanation and I just got the offer for principal. I wish I would see this video a month earlier. Thank you very much. Even now it is good to know for the future. Just want to add a little to the topic, in majority of interviews companies not smart enough to compare adequately all three aspects for desired position. They expect you should spend 100% preparation for coding, 100% preparation time for behavioral and 100% for situational parts. If you demonstrated good coding knowledge but did not solve the problem, no matter how good you are in system design or leadership you're most probably rejected. And as far as coding challenge is most difficult in terms of completing in time (not solving the problem), we still need to spend majority of time preparing for it. And in reality they may see how good I am in preparing for coding but not for coding itself. Obviously new graduates are better in preparation.
so for principal engineer in FAANG companies, did you need to prepare for coding part? i mean DS and Algos? Coz i am preparing for principal engineer roles and i am afraid, you need to be good in coding, low level design (oops) and system level design (high level design). The latter two are comparitively easier for me as they are part of my day to day job, but the coding preperaiton is very exhaustive and consumes almost 80% of my prep time. I dont want to spend 80% of my prep time on code for a principal position, but i am afraid, if i dont, then some hard DS and algo question will come my way and cause my downfall, as at this stage algo and ds seems to be my weakest link
Completely agree. There is a diminishing return for coding preparation, especially for senior positions. Get good enough and make sure you can do a good systems design and tell good behavioral stories.
@@ALifeEngineered "good enough" is particularly difficult for engineers that come through alternative paths. I don't have a CS degree, but I've been coding for 20 years, and can count on 1 hand the number of times I've had to use recursion or design algorithms from scratch (as opposed to just choosing/using a library). Yet most LeetCode/coding interview questions are these sort of "back to CS school" problems. It feels like a huge lift at this point in my career, when I'm focusing on becoming a better manager/director, but 90% of my prep for FAANG is going to be teaching myself "pure" CS, strictly for the interview.
Worked at Amazon as a senior architect ...this guy basically might have been reading from the interview ' handbook' and I mean that in a good way -- if you're not in the first or second year of your career, watch the whole video... at 1X. Maybe twice. Maybe take notes.
Generally speaking this video is spot-on, however, for FAANG, the level evaluated for the coding sections at ANY level (specially for Google) is tremendously high, hence the need (for most candidates) to over-prepare for that part alone. And just like you mention in the video, the baseline or minimal test that you need to pass in order to be considered for a position will always be an Algo & DS exercise. But overall good advice to not skip System Design and Behavioral for those of us who are more experienced. Great video!
I’m a new senior (not principal) level engineer and your advice is mind opening. I’ve been asked that same “describe a time when you disagreed….” question many times and I’ve always answered at a mid to junior level level without realizing it. I did have examples that match senior/principal levels but I never prepared for these questions.
This is what every senior engineer should watch. Web is full of Leetcode BS. Subscribed and liked. Can’t wait to watch more. Please add more videos on prepping for Principal roles.
I was skeptical looking at the title and thumbnail, but I gave your video a shot anyways. Your answer about looking from the companies perspective on hiring was something I never thought about. I always thought getting hired is difficult; but now I know, hiring is way more difficult for these companies.
Extremely helpful breakdown. Whenever I study for coding interviews, I tend to go a bit too deep and spend too much time there. I am in the middle of studying for a few interviews, and often spend hours learning about more obscure algorithms and data structures that likely wont be seen in the coding interview. For instance, I spent hours studying and building suffix arrays and LCP arrays in linear time using the DC3 algorithm, so I could use this for almost any string related question seen in the interview. I tend to just want to know the fastest way to solve every problem, regardless of if the solution is unexpected in a typical coding interview. It was a good thing I watched this today. Love the content!
I benefit a lot from those examples at the end of the video ~after 9 min. It would be a great help if you could make a whole video about how different levels of engineers would answer interview questions. This resonated the most with me and would be very helpful.
While I appreciate that this may help someone get hired at a FAANG company, do realize that every company has a culture. This video is essentially an expose on the type of culture that Amazon has. Consider that before moving forward with this type of company! Thanks for showcasing your experiences.
@@s.n.a.k.e_e.k.a.n.s You sound pretty bitter tbh. I'd rather go through the grind to get in these "egoisitic nose high places" and earn a ticket to upper class society thanks to 300% salary increase, than be you lol
People who have been in the industry for a while know that the companies applying these recruitment processes are just not worth it. They are like the pizzeria that deliver flyers across the entire city. One day you decide to go there and pizza is terrible. But they don't need to have good pizza. Because enough people go there to try. Best case scenario. You pass an interview like this and you are gonna find a toxic work culture where people constantly try to virtue signal and over expose their achievements while trying to screw anyone they may perceive as a threat. Most likely case scenario. In less that 1 year they replace you by someone who can do the same for 5% less money. Because these kind of company is ALWAYS looking for marginal benefits. That's why "it is impossible to inverview everyone properly". My advice is: Run away.
This video is really great. Not only if I want to apply for a new job as a Senior/Principal level but also to interview candidates for senior levels or mentor engineers to get to the next level.
Great advice. When I am in an interview I anticipate what the interviewer is going to ask and tell stories about it. I will often hear them say well you just answered my next question. Telling good stories keeps the interviewer engaged and sometimes even fascinated. Stories can lead to the interviewer discovering something they didn't know before and when that happens they will take a liking to you. When you can story tell you can manipulate the interview and interviewer any way you wish. The degree they allow you to do so is an indication of of your success on that occasion.
I am a senior level software engineer but I gotta admit I really struggle with leetcode type problems. I will still study more system design and behavioral questions but I feel like I need to up my game on those coding problems.
Same here. I look back on some of the work I've done and it involved designing and implementing entire complex microservice architectures on my own, training juniors, bringing new ideas to the client which were well received, improving the performance of their systems by an order of magnitude at some points and I feel this qualifies me as a senior. But give me a hard leetcode problem on a live call with a 30 min time constraint and you might as well be interviewing a golden retriever. I can't believe this is still how so many companies do their hiring process.
@@EvilTim1911 it really sucks but at least with your day to day experience in general it sounds like you are still well suited for senior level interviews. Behavioral and System Design is very important. I am a mobile developer so I still have a lot to learn about system design. At this point my performance on how I do with a coding interview is a crap shoot. For sure I can't do any DP questions though lol
About "small businesses", I worked with many startups and I never saw one of them fail because of "bad code". It was more about market fit / missions / user needs and so on. "Knowing how to code" and "knowing data structures" are two different things. Somebody has still to define what the hell "good code" is. Your good code is bad code for another engineer. In short, this video is... bad. There is no evidence whatsoever about what's said. To me, technical questions are random questions in a very large set of random question,s with an artificial context and many assumptions made on both side. It's a bit like asking to pass the driving test each time you want to change car. It requires useless grind through some interview preparation books.
I think this is true. Seems like the pandemic has spawned a lot of channels where senior engineers justify their companies' byzantine hiring practices. Trend looks fishy.
This video is so great. It explained to me in detail how I can be seen in a senior position interview. It is like an expanded version of the humorous "how programmers overprepare for job interviews" video from the Joma Tech channel.
I have never needed to balance a binary tree. I haven't done it since college. So you are saying that by this heuristic that I don't know how to code. This is why I do Leetcode. Level 1 is the hardest.
Thank you so much for the video. Still just a beginner in coding, but it really shed some light on what you might need to succeed, going down the path!
The first question is why would you want to apply for a large corporation job. Being treated like a number isn't fun. Not to mention it's much harder to make an impact and get promoted compared to a small company.
bloody good. many thanks, mata. Could you please make more about how you as principal handle different situations in your daily work: handle difficult persons (include other principals:), have visibility at senior level, manage to get the work having biggest impact etc.
I wish this was the way and I agree that this helps with small companies. Lots of enterprise companies I have seen recently for Sr. Developer jobs have been assigning hard leetcode problems and not engaging with you during the interview at all or making much eye contact.
Finding this could not have come at a better time. Thanks so much, I'll revise my strategy asap. Yes, I was focusing too much on just coding challenges.
This is probably the best description of the recruiting and interview process AND the expectations of the staff+ engineering roles. Or at least what they should be. Bravo.
I appreciate the thoughtfulness and clarity of your content. I like the perspective you take on using proxies to help make a decision to hire with very little time. I'm wondering if you have advice on proxies that candidates can employ to gauge if a potential employer is the right place for them? Awesome channel, thank you for the advice!
Thank you so much for your content. Just with this video alone I have learned plenty. Definitely following your channel since within the next 5 years I hope to be able to reach senior or (hopefully) a principal level :).
Interesting take, but considering the insane complexity of the coding questions at FAANG, especially G, I'm not sure I'm convinced. I mean, an expectation to solve 2 LC mediums in 1 hour? Jeez.
What he describes is more appropriate at other non FAANG companies. All FAANG companies, specifically Amazon, also are obsessed with code based interviews.
How to check candidate skills, SIMPLY! Do for 2 or 3 Hours pair programming with the candidate, how much it cost ? one pc , one pizza and your brain force! SO why those companies not doing this? Come on people, its time to end quick sort, data structures stupid questions, admit that you picking stuff from the air.
I have 15 years engineering experience in the industry and I failed amazon's first round leetcode test and was rejected. Funnily enough, 5 years ago I got an offer from Amazon and I rejected them. Just goes to show interviews are luck of the draw.
Amazing video. The think is the people will not see the value of these kind of advices til they had some experiencie... Thanks a lot for sharing your wisdom.
Couldnt agree more. I spent hours on leetcode doing problems that Amazon supposedly always asks which all were really hard questions. I ended up being asked completely different questions in an interview that were much simpler, but because I did not bother to go over fundamentals and rather go do all the hard leetcode problems, I failed my coding interview. Thanks a lot, leetcode.
@@FlabbyTabby hahah fuck the what? I've been building cloud native web apps with high performance websocket connections over several JS and serverside frameworks and never once had to know a leetcode question. Leetcoding is so stupid it hurts, learn the fundamentals, learn to design systems and solve problems. Thats is coding.
The issue I see is that LeetCode questions have been gamified in the past few years and that FAANG now increased the requirement to pass first level. I have tons of experience and I'm currently interviewing for Principal level positions. Given my experience, system design and leadership questions will be very natural, whereas quickly coding a DP problem is something I haven't done in many years. Focus the interview prep on your weaknesses, not your strengths.
I'm an sde 2 at Amazon and honestly, principals at Amazon are extremely smart. I've never come across a principal engineer at Amazon that I haven't admired.
How many times is balancing a binary tree in the top 50 list of skills that matter in writing a product? If the answer is almost never, why should we use it in interviews?
I have 15+ years of work experience, but couldn't figure out why my company wouldn't promote me to senior or even lead. Your video has made the reasons painfully clear. Still, I really really love coding. Maybe I should be happy just being a staff engineer. Any higher-up seems boring and pointlessly stressful (for me). I guess freelancing or me starting my own business is utterly out of the question at this point...
Interviews are broken in some many levels. Our industry is the only one that requires you to prove you know how to do the same stuff over and over... imagine if they interview Doctors this way "here is a dummy, show me how you operate it"... it doesn't matter you attended university, or have worked for company X and Y for many years. You now have to prove you can do some BST shit in record time... frustrating !
Hey Steve, I really like your videos thanks a lot for the good work! I am not an Engineer that has a dream company to work at, so I find myself in a situation where I need to find which is the right company for me, and during the interview process I am switching roles between being the interviewee and being the interviewer. Therefore, it would be really nice to see a video with tips on how to find a good company, and how asset if the engineering environment is suitable for me, if the code-base is healthy, if the coding mentality and practices overlaps with my preferences, etc. Obviously, everyone has different goals and ambitions when it comes to picking a work place, but I believe that there is a common layer that covers most Engineers (at least for Staff/Principal level). Just an idea..!
Nothing worse than finding a gem of a video like this one, smashing the subscribe button, and then seeing that the channel has four videos and hasn't posted for 8 months :(. Come back, Meta!
I've always wondered this too. I disagree a bit with this post because I've been on both sides.. and overwhelmingly those I hired (or agreed should get hired) that lasted and were good engineers I did so based on talking with them about their experience, guiding it towards questions related to what we were looking for, and their resume. I could see if someone was 8 years in and had 10 jobs.. that they likely were not a good fit. But someone with 2 or 3 jobs over 6 to 10 years.. employed 2+ years at each.. I could ascertain enough from that alone that they could code. Having a LOT of colleagues in this industry now.. most would NOT keep someone around for more than a few months or so if they could not code.
This video explains why it makes sense from companies perspective. But I’d say if it doesn’t make sense from YOUR perspective then don’t do it! Let them hire bunch of widgets.
Thanks for sharing man. I was in a final round for a junior position with an AWS principal architect interviewing me and rejected. The points you talked about in this video are really inspiring for my future interviews.
Obsoletely true. Thank you. often times not all senior engineers get a chance to scale a system to billions of users. So they have to go by preparation and not experience.
I refuse to partake in leetcode type interviews, I suggest you do to. Recently was given a reply with a test and responded saying the test acts as a blocker and if they’d drop it. They agreed to. Might not work all the time but worth a try.
One thing I have noticed at tech companies is a lot of people seem to not ask technical questions to solidify a good project structure/architecture. This is after they have been hired. But maybe this can only come from practice.
The issue is the coding questions in the first round from FAANG are the same across all levels. Senior and higher level will have a hard time solving textbook algorithm questions because we haven't touched that for a long time. E.g. we all know what heap sort is, how it works and the time complexity, but to write one with fast speed might fall short. Leetcode is definitely necessary in that sense. I don't think the textbook questions should be the questions for senior engineers but it is the fact now and have to accept it.
As an engineer who interviews, leetcode is 100% useless bullshit that recruiting departments sign up for under the guise of saving money. Every engineer and engineering manager I know hates the god damned things, but they are forced on us by recruiting. Fact is, I can get way more information out of a 15 minute design question than any number of hours of leetcode puzzles can provide.
I agree with most of the things you said but the reality of today's interview is different from what companies actually need/want. And interviewees don't have the choice but to follow whatever "proxies" companies prepared.
My opinion : These tech interviews are just a weeding thing. You are not expected to remmember everything theoretically..But that is how the world works. Just like Exams. Short Internships are the best because that gives enough time to assess applicants.
Ironically, I haven't studied for code, I know how to read and pickup the codebase and make modifications but to this day, if someone in a interview asked me to write a coding statement, i'd say uhhhh i'll usually google this but i'll give it a shot.
Forget the content, you had me sold on the background of the dope ass DJ Setup and the Whiskey Collection. The wigs confirmed my gut feeling and intuition!
![[Full Episode] The Restaurant War Thailand ศึกพ่อค้าซ่าแม่ค้าแซ่บ Episode 1 | 22 ก.ย. 67](http://i.ytimg.com/vi/BuzQ70v-UZQ/mqdefault.jpg)
The irony of most of the interview prep courses out there is that they were almost all created by ex FAANG engineers who turned out to be much better at creating TH-cam videos that they were at being software engineers.
@ScienceVideosFan Touche´
lets be honest here we still need people like them for the juniors. seniors developers don't even care which makes it hard to learn
i agree, lmao.
TechLead types?
so… you forgot to add "ex-engineers" there
I totally agree that the interview process should not just be focused on leetcoding interviews - especially for Sr+ engineers, but from recent experience with FAANG as an engineer with 25+ yrs experience, what I found was ... screening calls .. 100% leetcode (HARD in my case) .. so if you can't pull leetcode hard Q's out of your backside (perfectly) in 25 mins you don't even get to the 'onsites', where, you get another THREE leetcode HARD interviews, followed by a System Design and a behavioral ... this was the pattern across the board. The focus, no matter what your seniority, seems to be leetcode .. which is what takes 90% of the prep time going in .... as I Sr guy I can do Sys Design all day long, because it's closer to what I actually do as a Sr engineer .. but the leetcode stuff.. well that's never been part of the dayjob and requires practice..and luck! Such a terrible and contrived way to evaluate Sr engineers IMHO
I found the same sadly
100% agree
I don't know how AWS hires, but as one of the senior engineers in a FANG company, there is NO WAY you can get away with 30% coding in your studying time. Things asked of a senior engineer is still so code heavy that you will definitely fail if you only allocate 30% time and are not a coding genius by birth.
totally agree
I hear you, if you can't get past a phone screen it this advice doesn't work. My point was once you get an interview loop stop over-focusing on leetcode questions.
Video: stop doing leetcode
Me after watching the video: Guess I better go do some leetcode
Video: it costs ONE MILLION DOLLARS to hire a developer and not give him the resources it takes to succeed!!!! Me: I'm not charging enough.
Its all about leetcode to pass.
I could not disagree more. System design and behavioral interviews are easy if you are already a good senior engineer. I have 10 YOE and I barely need to prep for these to be moderately successful in most interviews. Coding problems, on the other hand, require countless hours of study time. If you can solve "Leetcode #4 - Median of Two Sorted Arrays" optimally with no study time, you deserve a Nobel Prize (and yes, Amazon asks this in interviews).
The fact that this guy keeps talking about firing every 3rd sentence is a give away about amazon culture :)
It's not that bad.
@@ALifeEngineered You're not fooling anyone. I have a staff engineer freind at Amazon. He has told me of the horrors. Everyday, all the top management gather around a secret underground statue of bezos, they have to chant "come on jeffrey you can do it" while they sacrifice an important part of their souls. My friend had to eat his adopted child's goldfish.
@@daruiraikage i atttest to this i was there
@@daruiraikage 😂😂😂😂
@@daruiraikage is this really true?
This was an excellent video. I would point out that a lot of senior/principal engineers focus on coding so much because the LC game has come up while they were busy building things over a decade+ career. It's the hardest thing for them to do because it's the most removed from their actual job. LC interview questions have you draw on DSA concepts you may not have seen for two decades, while behavioral and system design questions often draw from your actual experience.
Especially when LC is used as a gate keeping before a system design interview.
well said
Yep Buddy after 14 years of experience I'm like ... year DS and Algos .. i'm too old for this ... (don't get me wrong .. i can figure out a solution ... but won't be as fast as I'm prepared for it)I think I will retract from my Amazon interview :/ (Senior Cloud App Architect)
You've hit the nail on the head here. Writing function-level code while talking about it was very alien to me. I had to practice that skill because I was tripping over myself on otherwise simple algorithms.
Totally agree w/ this comment. Behavioral, system designs type, and knowledge domain questions more reflect the years of experience. Leetcode style questions are a completely different skill set not reflective of the day-to-day, so they typically need more time to prep for.
On system design: "These questions are easiest to answer if you have the experience, if you don't, it will be exceedingly apparent".
So all senior engineers have experience actually scaling systems to millions/billions of users? I think not.
Sys design is also total bs
Many senior engineers have experience scaling systems in general. Doesn’t have to be for millions, the concepts are much the same. Once you know what to look for, you know it.
I don't think he means the experience of scaling to billions of users. I think he means that you have experience scaling systems and understand it.
@@CVFunStuff As far as I know.. the majority of scaling is things like a gateway for throttling requests based on rbac, providing smart load balancers (in triplet to avoid downtime) that can remember what server (or group of servers.. farm) a specific user (via request header details) was sent so it can continue to send that same user to the same server(s), and ability to build stateless back ends (with caching of some sort if need be) so that you can just start up another instance.. which itself should join a server group to be included in future requests once its ready by the load balancers in play. Is that not the gist of it?
@@b3owu1f That's one tech stack, sure. It can be simpler than what you described. You don't necessarily need to send the same session to the same server; most servers will round-robin all requests and session tokens can help ensure a user's session stays validated. You don't necessarily need to throttle based on RBAC either, although it's a good optimization. You don't even need stateless backends (although I personally use K8s); a single, multithreaded server instance on a powerful machine could do you well enough for a small to mid-sized project (up to hundreds of rps). It's surprising how many requests a basic setup can handle. Only when you truly get to millions or billions of rps do some of these optimizations start to matter.
Lots of good information here, thanks! I have 14 years of experience as an engineer, of which 5 as a senior, 1 as a software architect, and overall during these periods the last 2 years I've been a tech lead. My last 6 years have all been at a well known tech company too.
That said, if I got a question like "Tell me about a time you strongly disagreed with your team" I probably wouldn't know what to say as I feel that in all my experience I have NEVER seriously disagreed with any of my teammates - in all the teams I've been I always had a surprisingly good rapport with my teammates and the things we did disagree on were small and inconsequential, hardly worth mentioning. However I have disagreed with engineering managers and even our head of engineering, and in some of those disagreements I was able to make a compelling case and get what I and the team wanted, whereas in other situation my opinions were acknowledged but the course of action set.
I left the company recently and I've been interviewing. I found that I am very bad at interviewing, because I was often stumped by behavioural questions such as that one - where my immediate answer was "never disagreed", or I just couldn't tell them of a time I did X because I just couldn't remember specifics. To the point where somebody told me they thought I was a beginner. Cool, but if I'm such a beginner then how was it that I have all these achievements - managed to lead teams, run critical projects, deal with stakeholders and deliver things that were loved by our customers?
Well it's because I wasn't prepared for these types of interview questions. Now I am prepared, I have identified a set of stories that I can tell these people, but now I feel like this is also disingenuous, because anyone can prepare and give good sounding stories during an interview, yet that doesn't mean they will actually be good at doing the job.
Well yeah, reality is that the managers and recruiters interviewing don't know shit about how the work gets done. They're just idiots.
Oh, you can prepare good stories and you should. But a good interviewer will ask you very specific questions and it will become apparent really quick if you were a protagonist in the story or just a bystander. Imitation only brings you so far.
@@j.metzger1730 Not really, it's all about perception. Most hires are based on perception of the candidates and not their skill. Even absolutely incompetent people will get hired and given a good salary.
@@j.metzger1730 That's if the interviewer is paying attention. I've found that the best interviews have been those that felt like conversations rather than interrogations.
I've had conversations about projects and systems I've worked on, and I also asked about some of the interviewer's projects and gave my thoughts on some of their issues. These discussions do go into details, but that's good because that can further clarify the extent of your expertise.
At the other end, the worst interview I had was one that had the interviewer asking rapid fire questions about specific theoretical models, design patterns, and acronyms, scoring me on how many I got right and how many I got wrong, with no discussion around any of these topics. That interview stage could have been replaced by an online form.
@@El3ctr0Lun4 I agree with this because you can’t prepare for this kind of interview style. It’s whether you know it through experience and you can also see how the person come up with solution and be able to support it even go deeper to clearly see how much they know. I think this would be a good way to assess a candidate
Lovely what you said, and thank you for that. I worked at Amazon, an according to my buddy I was expected to code like him, design like him and think like him because I started in a L5 role (as him). Language was not a barrier because we both speak Spanish. In fact after one week working on a project he stopped joining any meeting because I was supposed to answer all questions (no writing documentation exist because he worked alone, in fact I must say SIM tickets were poorly documented if you try to find out why some technical decisions were done that way). I recall once my manager told me to get more info about a process and when I asked my "buddy and mentor", he says that it was not my work and I need to spend more time coding. I ended up quitting, because you could be a good technical developer (I am not consider myself the best but I do my best) but the lack of business info and the lack of support was a nightmare. In fact, in the starting training sessions when they tell you you must rely on your team in order the avoid that feeling of the impostor syndrome, well my lovely buddy made feel that way.
My big advice, those companies (FAANG) like any other companies have their pros and cons (like any other job). Do not idolatry them (in my case the salary was not that high, a 10% raise in compare to my previous job, so it did not pay off the nightmare I experienced). And I am the kind of person that do not mind working extra hours as long as I am learning (in fact the project was quite interesting). Try what you think it is best for your career (and probably you realize these kind of companies are not meant for you, and you know what.... It is OK)
It would be great if "Senior Role" was also mentioned in the Thumbnail.
Lol then he wouldn't get as many clicks!
10:28 He gives steps for each roll
That's why he is senior
I guess it is kind of randomly asking but do anybody know of a good website to stream new series online ?
@@moisesreid283 youtube ofc
This is great. It's about time someone with real-world principal-level experience at FAANG disrupted the scammy coding prep resources. Wishing for a product manager to make a similar channel 🙏
Really great explanation and I just got the offer for principal. I wish I would see this video a month earlier. Thank you very much. Even now it is good to know for the future. Just want to add a little to the topic, in majority of interviews companies not smart enough to compare adequately all three aspects for desired position. They expect you should spend 100% preparation for coding, 100% preparation time for behavioral and 100% for situational parts. If you demonstrated good coding knowledge but did not solve the problem, no matter how good you are in system design or leadership you're most probably rejected. And as far as coding challenge is most difficult in terms of completing in time (not solving the problem), we still need to spend majority of time preparing for it. And in reality they may see how good I am in preparing for coding but not for coding itself. Obviously new graduates are better in preparation.
so for principal engineer in FAANG companies, did you need to prepare for coding part? i mean DS and Algos? Coz i am preparing for principal engineer roles and i am afraid, you need to be good in coding, low level design (oops) and system level design (high level design). The latter two are comparitively easier for me as they are part of my day to day job, but the coding preperaiton is very exhaustive and consumes almost 80% of my prep time. I dont want to spend 80% of my prep time on code for a principal position, but i am afraid, if i dont, then some hard DS and algo question will come my way and cause my downfall, as at this stage algo and ds seems to be my weakest link
Completely agree. There is a diminishing return for coding preparation, especially for senior positions. Get good enough and make sure you can do a good systems design and tell good behavioral stories.
@@ALifeEngineered "good enough" is particularly difficult for engineers that come through alternative paths. I don't have a CS degree, but I've been coding for 20 years, and can count on 1 hand the number of times I've had to use recursion or design algorithms from scratch (as opposed to just choosing/using a library). Yet most LeetCode/coding interview questions are these sort of "back to CS school" problems. It feels like a huge lift at this point in my career, when I'm focusing on becoming a better manager/director, but 90% of my prep for FAANG is going to be teaching myself "pure" CS, strictly for the interview.
it's cool to find someone who gives advice that isn't for "COMPLETE BEGINNERS". I enjoy the senior/principle mindset.
Worked at Amazon as a senior architect ...this guy basically might have been reading from the interview ' handbook' and I mean that in a good way -- if you're not in the first or second year of your career, watch the whole video... at 1X. Maybe twice. Maybe take notes.
Generally speaking this video is spot-on, however, for FAANG, the level evaluated for the coding sections at ANY level (specially for Google) is tremendously high, hence the need (for most candidates) to over-prepare for that part alone. And just like you mention in the video, the baseline or minimal test that you need to pass in order to be considered for a position will always be an Algo & DS exercise. But overall good advice to not skip System Design and Behavioral for those of us who are more experienced. Great video!
Technical interviews are always a toss of a coin. Anybody can fail anybody based on a random set of requirements.
Yeah, they're actually a blind. In reality, whether or not you're chosen is entirely based on prejudice, bias and discrimination.
Only the people who get constantly rejected say that
It's easier to blame random chance than to actually evaluate your weaknesses and learn from them
I’m a new senior (not principal) level engineer and your advice is mind opening. I’ve been asked that same “describe a time when you disagreed….” question many times and I’ve always answered at a mid to junior level level without realizing it. I did have examples that match senior/principal levels but I never prepared for these questions.
Take a look at my latest video.
This is what every senior engineer should watch. Web is full of Leetcode BS. Subscribed and liked. Can’t wait to watch more. Please add more videos on prepping for Principal roles.
FYI, Web is not a level.
Your wig game is strong 😂 Would love to see more system design videos!
I was skeptical looking at the title and thumbnail, but I gave your video a shot anyways. Your answer about looking from the companies perspective on hiring was something I never thought about. I always thought getting hired is difficult; but now I know, hiring is way more difficult for these companies.
Extremely helpful breakdown. Whenever I study for coding interviews, I tend to go a bit too deep and spend too much time there. I am in the middle of studying for a few interviews, and often spend hours learning about more obscure algorithms and data structures that likely wont be seen in the coding interview. For instance, I spent hours studying and building suffix arrays and LCP arrays in linear time using the DC3 algorithm, so I could use this for almost any string related question seen in the interview. I tend to just want to know the fastest way to solve every problem, regardless of if the solution is unexpected in a typical coding interview. It was a good thing I watched this today. Love the content!
in other words, you are the overkill warlord
WOW. Awesome. My AWS interview is in 7 days! Thank you - this video helped me a ton.
How did it go?
The story telling recommendation is gold. I’ll remember that. Thanks for the content!
Thanks for squashing the notion of leetcode..i was so anxious around it. Cant wait for more prep on senior engineers
I benefit a lot from those examples at the end of the video ~after 9 min. It would be a great help if you could make a whole video about how different levels of engineers would answer interview questions. This resonated the most with me and would be very helpful.
While I appreciate that this may help someone get hired at a FAANG company, do realize that every company has a culture. This video is essentially an expose on the type of culture that Amazon has. Consider that before moving forward with this type of company! Thanks for showcasing your experiences.
This is why people with self respect don't go to this egoistic nose high places.
@@s.n.a.k.e_e.k.a.n.s You sound pretty bitter tbh. I'd rather go through the grind to get in these "egoisitic nose high places" and earn a ticket to upper class society thanks to 300% salary increase, than be you lol
@@handsomesquidward151 You can get 200% salary increase without selling your soul.
I'm not way near the level to apply for a senior position, but it's good to know these things early on :)
People who have been in the industry for a while know that the companies applying these recruitment processes are just not worth it.
They are like the pizzeria that deliver flyers across the entire city. One day you decide to go there and pizza is terrible. But they don't need to have good pizza. Because enough people go there to try.
Best case scenario. You pass an interview like this and you are gonna find a toxic work culture where people constantly try to virtue signal and over expose their achievements while trying to screw anyone they may perceive as a threat.
Most likely case scenario. In less that 1 year they replace you by someone who can do the same for 5% less money. Because these kind of company is ALWAYS looking for marginal benefits. That's why "it is impossible to inverview everyone properly".
My advice is: Run away.
Fantastic video! Just as your other video pointed out "Now that I see it... I can't unsee it".
This video is really great. Not only if I want to apply for a new job as a Senior/Principal level but also to interview candidates for senior levels or mentor engineers to get to the next level.
Great advice. When I am in an interview I anticipate what the interviewer is going to ask and tell stories about it. I will often hear them say well you just answered my next question. Telling good stories keeps the interviewer engaged and sometimes even fascinated. Stories can lead to the interviewer discovering something they didn't know before and when that happens they will take a liking to you. When you can story tell you can manipulate the interview and interviewer any way you wish. The degree they allow you to do so is an indication of of your success on that occasion.
Someone not shilling leetcode or algoExpert?? you sir deserve a subscribe
I'm applying for senior position at amazon and I'm super happy that I watched this before preparing! Thanks!
I am a senior level software engineer but I gotta admit I really struggle with leetcode type problems. I will still study more system design and behavioral questions but I feel like I need to up my game on those coding problems.
Same here. I look back on some of the work I've done and it involved designing and implementing entire complex microservice architectures on my own, training juniors, bringing new ideas to the client which were well received, improving the performance of their systems by an order of magnitude at some points and I feel this qualifies me as a senior. But give me a hard leetcode problem on a live call with a 30 min time constraint and you might as well be interviewing a golden retriever. I can't believe this is still how so many companies do their hiring process.
@@EvilTim1911 it really sucks but at least with your day to day experience in general it sounds like you are still well suited for senior level interviews. Behavioral and System Design is very important. I am a mobile developer so I still have a lot to learn about system design. At this point my performance on how I do with a coding interview is a crap shoot. For sure I can't do any DP questions though lol
Thanks for sharing, the last section about how answer shows your seniority really makes me rethink about my answer before.
About "small businesses", I worked with many startups and I never saw one of them fail because of "bad code". It was more about market fit / missions / user needs and so on.
"Knowing how to code" and "knowing data structures" are two different things.
Somebody has still to define what the hell "good code" is. Your good code is bad code for another engineer.
In short, this video is... bad. There is no evidence whatsoever about what's said. To me, technical questions are random questions in a very large set of random question,s with an artificial context and many assumptions made on both side. It's a bit like asking to pass the driving test each time you want to change car. It requires useless grind through some interview preparation books.
I think this is true. Seems like the pandemic has spawned a lot of channels where senior engineers justify their companies' byzantine hiring practices. Trend looks fishy.
I agree tech interviews are broken. You have to prepare in very strange ways to be successful with them.
Obviously incompetent C suite is more disastrous than incompetent technical employees. Tech debt is a thing and will matter in the long run.
Respect brother. Honest and open apart from rest of youtuber crowd, who try to market their channel rather than earn it organically
This video is so great. It explained to me in detail how I can be seen in a senior position interview. It is like an expanded version of the humorous "how programmers overprepare for job interviews" video from the Joma Tech channel.
I have never needed to balance a binary tree. I haven't done it since college. So you are saying that by this heuristic that I don't know how to code. This is why I do Leetcode. Level 1 is the hardest.
Thank you so much for the video. Still just a beginner in coding, but it really shed some light on what you might need to succeed, going down the path!
The first question is why would you want to apply for a large corporation job. Being treated like a number isn't fun. Not to mention it's much harder to make an impact and get promoted compared to a small company.
bloody good. many thanks, mata. Could you please make more about how you as principal handle different situations in your daily work: handle difficult persons (include other principals:), have visibility at senior level, manage to get the work having biggest impact etc.
I wish this was the way and I agree that this helps with small companies. Lots of enterprise companies I have seen recently for Sr. Developer jobs have been assigning hard leetcode problems and not engaging with you during the interview at all or making much eye contact.
Finding this could not have come at a better time. Thanks so much, I'll revise my strategy asap.
Yes, I was focusing too much on just coding challenges.
this was really good, as a principal engineer i totally agree on your clearly described points. subscribed!
This is probably the best description of the recruiting and interview process AND the expectations of the staff+ engineering roles. Or at least what they should be. Bravo.
The best way to prepare for an interview is to get really good at your job and then learn how to tell your story.
The wig part is gold!!! The last piece of advice on the ratio of portions gives an exact idea what to do next! Big thanks!
This video is a godsend. Thanks for explaining the proper context, and how to use that context in prep.
I appreciate the thoughtfulness and clarity of your content. I like the perspective you take on using proxies to help make a decision to hire with very little time. I'm wondering if you have advice on proxies that candidates can employ to gauge if a potential employer is the right place for them? Awesome channel, thank you for the advice!
Thank you so much for your content. Just with this video alone I have learned plenty. Definitely following your channel since within the next 5 years I hope to be able to reach senior or (hopefully) a principal level :).
Interesting take, but considering the insane complexity of the coding questions at FAANG, especially G, I'm not sure I'm convinced. I mean, an expectation to solve 2 LC mediums in 1 hour? Jeez.
@gaming site either my commens are getting deleted or I'm tripping. It's a website with coding tasks, you have to google for it.
What he describes is more appropriate at other non FAANG companies. All FAANG companies, specifically Amazon, also are obsessed with code based interviews.
Thank You! This information was so helpful for me. I have a big interview for an engineer role later today. Glad I found you!
How to check candidate skills, SIMPLY! Do for 2 or 3 Hours pair programming with the candidate, how much it cost ? one pc , one pizza and your brain force! SO why those companies not doing this? Come on people, its time to end quick sort, data structures stupid questions, admit that you picking stuff from the air.
I've always thought something like this would be better.
Great stuff! I’d be interested in more system design questions and how to approach and formulate an exceptional type of answer. 👍🏽
These videos are gold! I watched all of them. Please, please stick with it.
I have 15 years engineering experience in the industry and I failed amazon's first round leetcode test and was rejected. Funnily enough, 5 years ago I got an offer from Amazon and I rejected them. Just goes to show interviews are luck of the draw.
It's economics. Right now the market is saturated with engineers so they can be ridiculous with interviews.
GREAT video! This is coming from an Engineering Director with 27 years of experience.
I am a Senior Engineer. My issue is after studying and doing Leetcode questions if I don’t keep on revising I forget them in a week.
Although I am looking for a Data analyst, I found this very helpful. Thank you!
Amazing video. The think is the people will not see the value of these kind of advices til they had some experiencie... Thanks a lot for sharing your wisdom.
Couldnt agree more. I spent hours on leetcode doing problems that Amazon supposedly always asks which all were really hard questions. I ended up being asked completely different questions in an interview that were much simpler, but because I did not bother to go over fundamentals and rather go do all the hard leetcode problems, I failed my coding interview.
Thanks a lot, leetcode.
It's not leetcode's fault, it's the company's fault for asking useless questions and not giving a crap about actually hiring skilled engineers.
@@FlabbyTabby hahah fuck the what?
I've been building cloud native web apps with high performance websocket connections over several JS and serverside frameworks and never once had to know a leetcode question.
Leetcoding is so stupid it hurts, learn the fundamentals, learn to design systems and solve problems. Thats is coding.
The issue I see is that LeetCode questions have been gamified in the past few years and that FAANG now increased the requirement to pass first level. I have tons of experience and I'm currently interviewing for Principal level positions. Given my experience, system design and leadership questions will be very natural, whereas quickly coding a DP problem is something I haven't done in many years. Focus the interview prep on your weaknesses, not your strengths.
I'm an sde 2 at Amazon and honestly, principals at Amazon are extremely smart. I've never come across a principal engineer at Amazon that I haven't admired.
simp
@@fghfdgable I'd rather simp for someone because of their competence than because of their fat distribution
How many times is balancing a binary tree in the top 50 list of skills that matter in writing a product? If the answer is almost never, why should we use it in interviews?
I have 15+ years of work experience, but couldn't figure out why my company wouldn't promote me to senior or even lead. Your video has made the reasons painfully clear. Still, I really really love coding. Maybe I should be happy just being a staff engineer. Any higher-up seems boring and pointlessly stressful (for me). I guess freelancing or me starting my own business is utterly out of the question at this point...
just find another company
I am completely in agreement with the content, this is helping me change my mindset for sr position preperation
Interviews are broken in some many levels. Our industry is the only one that requires you to prove you know how to do the same stuff over and over... imagine if they interview Doctors this way "here is a dummy, show me how you operate it"... it doesn't matter you attended university, or have worked for company X and Y for many years. You now have to prove you can do some BST shit in record time... frustrating !
Hey Steve, I really like your videos thanks a lot for the good work!
I am not an Engineer that has a dream company to work at, so I find myself in a situation where I need to find which is the right company for me, and during the interview process I am switching roles between being the interviewee and being the interviewer. Therefore, it would be really nice to see a video with tips on how to find a good company, and how asset if the engineering environment is suitable for me, if the code-base is healthy, if the coding mentality and practices overlaps with my preferences, etc. Obviously, everyone has different goals and ambitions when it comes to picking a work place, but I believe that there is a common layer that covers most Engineers (at least for Staff/Principal level). Just an idea..!
Nothing worse than finding a gem of a video like this one, smashing the subscribe button, and then seeing that the channel has four videos and hasn't posted for 8 months :(. Come back, Meta!
It's happening.
@@ALifeEngineered Thank you based Meta
I passed my tech interview today because fo this advice!!! big thanks mate - you are a hero.
The keyword is "small potato" - this has killed my 7 interviews at FB and Amazon in the last 5 years because of giving small potatoes examples.
Thanks a lot! This talk is pure gold!!! And it's available for everyone. Super detailed and knowledgeful. Thanks a lot for sharing,
Why don't they trust the experience you had from previous companies?
I've always wondered this too. I disagree a bit with this post because I've been on both sides.. and overwhelmingly those I hired (or agreed should get hired) that lasted and were good engineers I did so based on talking with them about their experience, guiding it towards questions related to what we were looking for, and their resume. I could see if someone was 8 years in and had 10 jobs.. that they likely were not a good fit. But someone with 2 or 3 jobs over 6 to 10 years.. employed 2+ years at each.. I could ascertain enough from that alone that they could code. Having a LOT of colleagues in this industry now.. most would NOT keep someone around for more than a few months or so if they could not code.
Telling a story is a good point. You may need to tell the interviewer a whole hero's journey.
So get system experience by doing system design which requires system design to get a job.
Love the leadership bit at the end. Very true. Also, nice wig selection.
Definitely would appreciate some pointers on learning system design as efficiently as possible
This video explains why it makes sense from companies perspective. But I’d say if it doesn’t make sense from YOUR perspective then don’t do it! Let them hire bunch of widgets.
Watched it over and over again. Each word is compacted with golden information. When will you have new videos? Can't wait!!!
Thanks for sharing man. I was in a final round for a junior position with an AWS principal architect interviewing me and rejected. The points you talked about in this video are really inspiring for my future interviews.
Keep on plugging away. Interviews are random, things will work out over time if you put the time in.
Destiny only favours those who works under Labour Under Correct Knowledge . She may close one door but open another.
Some companies still put Seniors through the Leetcode rigour. It's their shop, but boy do I hate having to deal with that shit.
I got discouraged and depressed after I watched your videos. But do love your contents and the way you talk
Obsoletely true. Thank you. often times not all senior engineers get a chance to scale a system to billions of users. So they have to go by preparation and not experience.
I refuse to partake in leetcode type interviews, I suggest you do to. Recently was given a reply with a test and responded saying the test acts as a blocker and if they’d drop it. They agreed to. Might not work all the time but worth a try.
Dang I really like this statement:
“You can disagree with me but you can’t say I don’t know what I’m talking about”
Level 1: Code
Level 2: Systems Design
Final Level: Leadership (Senior & Principal)
One thing I have noticed at tech companies is a lot of people seem to not ask technical questions to solidify a good project structure/architecture. This is after they have been hired. But maybe this can only come from practice.
The issue is the coding questions in the first round from FAANG are the same across all levels. Senior and higher level will have a hard time solving textbook algorithm questions because we haven't touched that for a long time. E.g. we all know what heap sort is, how it works and the time complexity, but to write one with fast speed might fall short. Leetcode is definitely necessary in that sense. I don't think the textbook questions should be the questions for senior engineers but it is the fact now and have to accept it.
As an engineer who interviews, leetcode is 100% useless bullshit that recruiting departments sign up for under the guise of saving money. Every engineer and engineering manager I know hates the god damned things, but they are forced on us by recruiting.
Fact is, I can get way more information out of a 15 minute design question than any number of hours of leetcode puzzles can provide.
It looks like FAANG designs the coding tests to purposefully fail you so that they can bring i more H1B grads from fresh stage.
Great content, really helpful tips for more senior candidates. Thanks a lot for making this video!
Hey meta, thanks for providing this awesome content and it is sorely needed in this space.
I love how the behavioral questions are meant to be hard to fake, but if you study you can get thru them :)
As a Senior Product Director, I can confirm that a lot of this advice is applicable to product, growth, design and TPM roles at higher levels.
I agree with most of the things you said but the reality of today's interview is different from what companies actually need/want. And interviewees don't have the choice but to follow whatever "proxies" companies prepared.
My opinion : These tech interviews are just a weeding thing. You are not expected to remmember everything theoretically..But that is how the world works. Just like Exams. Short Internships are the best because that gives enough time to assess applicants.
Ironically, I haven't studied for code, I know how to read and pickup the codebase and make modifications but to this day, if someone in a interview asked me to write a coding statement, i'd say uhhhh i'll usually google this but i'll give it a shot.
Forget the content, you had me sold on the background of the dope ass DJ Setup and the Whiskey Collection. The wigs confirmed my gut feeling and intuition!
Thanks for all your vids. Glad this came up in my recommended.
"Lets get meta" tht was a cool line
I'm in job search and I found this video very insightful!
Thanks, man!
First time on your channel
Very concise and clear!