i am in relatively senior role in tech. when i started prepping for an interview after years, i was shocked at the process they have these days. Firstly, we have to clear the data structures coding challenges. Second round is super tough technical interview where a bunch of engineers ask you left righ and center about devOps, infra setup, security and data engineering. Once i managed to clear these, the third round was supposed to be behavioural. But I met two senior engineers who took 1.5 hours of tech interview again on the projects that i worked on and on data structure and ultimately I was rejected. I was fairly confident of answering all the questions they asked (most of them). I think more than technology, it is about the culture of the organization. If the people there think you are not a good fit in the sense they dont see catching up with you over beer on Friday, they most probably will reject you. Likeability is a big factor.
The frustrating thing about this is its illustration of how broken the interview process is. Here we have an established engineer from a major tech company who had significant contributions and impact - but because he didn't spend months prepping DSA for that first interview, he "bombed." Interviewers are reading from a "cheat sheet" of expected systems design answers, what questions to ask e.g. they don't know the answers either, but expect the candidate to know literally any system in great detail. That's insane to me. We've got to figure out a way to do better.
It's not broken. It's actually pretty effective at evaluating candidates within a limited amount of time. In an ideal world, everyone would get an internship to prove themselves, but that's obviously not possible. No one should get any entitlement because of their position. Sure, I have more experience, but I should know everything that a fresh graduate does, and if I don't I think it's fair to expect me to prep.
@@EngineeringwithUtsav I don't know. It seems like your experience should count for something. They're treating you as if you're lying about it and have to prove yourself during some crazy coding test that isn't anything like day-to-day development. I don't think other professionals have to go through this.
As a hiring manager, I really can't overstate the importance of mock interviews. You can be the best candidate out there but if you are too nervous during the interview you might run into problems. Practicing this in mock interviews before really helps you to come across more natural.
I love your videos. You are so honest and straightforward in terms of sharing your experiences and thought processes. Thank you so much for taking time to help others!
Straight shooter. Says it as it is in a way that is real and palatable. These are more life lessons than IT guidance. Keep up the good work. Much appreciated.
Great Video. Currently I am doing some interview prep just to be more flexible and refresh some of the basics. I was shocked how fast I forgot details about data structures or algorithms I did not need. The theory is there, but when doing leetcode I find myself thinking "a priority queue/heap should make it easy, but how exaclty do I use it?" The same also happens with some algorithms. At least for me it interrupted the flow, I was not really able to track how long a coding problem took and just checked the API/algorithm to just finish the current problem. It gets questions done, but is not really time efficient. So I agree 100% agree, first theory then the problems.
Your contents are supremely transparent. I just love it. Hoping to watch many more videos like this. And wish you all the best in your upcoming job interviews.
I liked donne martins github collection of system design topics. It gave me an overview of topics that exist and some good examples. Once I read that I started diving deep into each topic.
I definitely fell into the "design interviews are easy" trap and I almost never spent any time preparing for them. It is intimidating to know that I probably need 3-6 months of prep for them
Very relatable video. I am a freelancer for a long time, I usually do contracts that are under a year in length. I mix my projects and switch between development and consulting, so once in every two years I do coding interviews. And I half intentionally always bomb the first one. I found out about myself some time ago that the biggest driver for me, to catch up with latest tech, practice algorithms and problem solving is failure. Positive motivation like working for a big name or big $ no longer does it for me. Or did it ever?
Nice talk Utsav! You covered almost everything. Thanks for reminding me that System Design should also be an important part of preparation. I thought I knew systems but after your video, I think I'll go back to understanding things again from thee basics.
Is it really practical to take time off so one can be a full time interviewee ? I think it is better if one applies for jobs that are already in his technical or work sphere ...
Thats how successful may be look like...even with this much of experience.... You can't stop learning... keep going and going...life is about struggle...
Utsav can please start making videos about data structures and algorithms, probably a crash course that could help us in cracking interview, something similar to your video related to interviews problems would be appreciated.
System Designs are really nightmares for freshers. But on the other hand they also help in differentiating the best candidates from the good ones. No better way to put it out there apart from your video :) Cheers! :)
What to you suggest, whether we should prepare everything and start giving interview . I know we cannot cover every aspects. or other way do 50% prep and start giving interviews and learn from mistakes and go on until cracked.
In your experience, at roughly what level of experience should I expect system design questions? If I’m applying for a SWE2 at a FAANG for example, is it worth deep diving into system design prep?
No need to see dive too much as SDE2. Understand requirements, basic QPS math, trade offs in CAP and how/when to chose one over another, known common tech around typical SD areas. That should be good enough. I think the grokking course and RUclips resources are just in par with level 2.
How can we know which comes under advance DS? , If you have any resource which has proper distribution between advance and normal DS , then please do share it.
This is by far the most relatable video. I have had a ditto experience interviewing with companies ! Need loads of resources and most importantly time where I can be highly productive to learn System Design. One of the most fun topics. Dream topic and the most challenging of them all !! Would you be willing to mentor me ? Would you be willing to take up mock interviews ?
I started doing it briefly but my calendar got swamped with requests I couldn’t keep up with. Now that I’ll be starting to work full time, I’ll likely be in the interview panel there, so I’m pretty sure it will be a conflict of interest to conduct mock interviews unfortunately
Very insightful, Utsav. I wonder if it could be possible to somehow measure or quantify a candidate preparedness level. We all agree thorough preparation is paramount to increase the chances to land the job, but how much is enough? Some people like to measure with time, like Sam from "Keep on Coding" who stated that if he was to start interviewing he would need "3 months of coding challenge practicing". Other people like Joma from "Joma Tech" like to measure by the difficulty of the problems you can solve, and others like Clément Mihailescu from "AlgoExpert" measure by quantity, or the number of problems you solve in his platform. Personally, I think all of these dimensions can't measure the level of preparedness because each candidate is different, with different learning speeds and different cognitive abilities, and the companies being targeted are also different, each evaluating candidates differently. A good hint of the candidate preparedness can be acquired in mock interview services, but even there the measurement isn't standardized and has an ample variation degree. I wonder if it could be a set of 5 or 6 scripted mock interviews with very specific topics being asked, paced, and with specific coding challenges that are representative of the major concepts asked in coding interviews in general, then a candidate can go through these "master mock interviews" and then see how it goes and compare his performance against others, and infer conclusions like "hmm, 80% of candidates that took these tests and landed a job at Google performed better than me, I am probably not ready yet, I need more preparation".
False competence is a common pitfall during tech interviews. I doubt there is a standard way to measure preparedness. I have my method that worked for me, I’ll be sharing that in the next video :)
Truly it does seem like the interview process in software jobs is very very broken. Definitely all your advice is GREAT! But, man... getting in is almost a random process. I hear all the time that people get questions that simply can not be answered unless you actually knew the question upfront. It is like a leetcode crap shoot. Truly the process seems broken. BEST of luck and hope you land a GREAT job soon! Would love some more idea of the specific questions you get asked in the process. (I am looking to get back in after a year off (covid!) as well. Wish us all luck!
Coding interviews aren't perfect, but there are also not many other objective ways to evaluate candidates in a short amount of time. It's a function of time, cost and objectivity.
@@EngineeringwithUtsav Why can't they look at what you've done in past jobs? Developers in the past didn't have to go through hours of "Spanish Inquisition" interviews, and the companies seemed to find good employees anyway.
I am an aspiring junior and went through a lot of interviews myself recently too and it's crazy how different the interviews are even tho they all were for the exact same title "junior php web developer". For example for one interview i just had 1 hour of talking and then 7 hours for designing an API. Another one was 2 hours of talking and 2 hour coding interview with a complicated algorithm. Another one was 1 hour talking and then an on-premise interview (other ones were online) where I had to solve a real world problem within 5 hours which can only really be solved in that time if u are very familiar with both the repository and visitor pattern (which i wasnt). So yea, it's really different each time and also the people were super different each time. it's really really fascinating how big the differences are between each job even when the title is exactly the same. Before all these interviews I only had experience working with laravel and so I kind of thought everything would be similar to that, but so far the interviews have shown me that I know nothing, lol :D Now I am learning a lot about design patterns and "clean code" from uncle bob and others. (I did get an actual offer for the job that wanted me to do the api design, the 2 hour coding interview told me immediately that im not good enough and the other ones haven't told me yet)
I'm curious, where would you or anyone else for that matter rate college students who just got out of college? While web development might not seem like a 'software' field because it's niche and borderline software/application development to some people, what would be a great salary or hourly range? While I want to be optimistic, the unfortunate thing is that my current situation doesn't allow me to have a salary less than 50k, which to some is a deal breaker.
It wasn’t. Those are pretty straight forward. It was about the longest increasing sequence, with a slight constraint on the differences between numbers.
@@EngineeringwithUtsav hmm, interesting, I wonder where do you need deque there like even when you need to skip because you have memoization on your side.
That was the trick. It looked like a DP problem, but it wasn’t. Don’t want to disclose the question due to NDA but I couldn’t find it on LeetCode. Cheers! :)
Find people you know. Mentors. Friends. Make sure they are used to interviewing. Watch videos to practice - I have one as an example. I may do some as an example.
In My Recent SWE Intern Interview at Hackerrank, I cleared round 1 with CTO and then the second round seems to be a system design interview like he asked me about "how can we make a thing similar to gitpod without using containers?" this should be considered as a Sys. design interview Q? btw, I am in a sophomore year of my B.Tech Degree.
This video made me think , that I'm dumb.. cause I want to be a full stack web developer ( a lot of skills to learn ) + the system design.. things getting scary and complicated
Tech interviews have become this weird, almost ritualistic, type of ordeal that they don't even make sense anymore. Hire fast based on resume and personal interviews and fire even quicker when you see that you don't have a match.
Those leetcode style questions are a real pain in the a** and impractical for the most part in the real world. Pair programming is a much better alternative.
Well informative. But you didn't mentioned that which Company's offer you have and you said yes to that Company. We all curious to know that in which company you will be joining.
in my experience interviewers are looking for a single excuse to reject you, as a candidate you have to be perfect for the duration of the interview according to a standard you don't know which is nearly impossible. Yes, the job of the interviewer is trivial in comparison with that of the candidate.
It’s actually the opposite in most cases. It’s a waste of time and resources to interview and reject candidates. Interviewers are on your side and they want you to succeed, even if it feels otherwise.
@@EngineeringwithUtsav not in my experience. May be cultural depending on country but here in most cases they're trying to find an excuse to reject you. And especially if on entering the room they find you're not a 25 year old fresh graduate with 20 years of professional experience but a 50 year old seasoned veteran.
Let me guess, your side project and some of hobbies include guitar & keyboard? We are the same man... So it means you can take some time off to learn to play rachmaninov, dream theater, or John coltrane
Everyone might be considering their " best time " for some " best buy " while tech engineers are concerned about their " best interview " for the " best pay " ....
@@EngineeringwithUtsav can you go more into this, especially since I thought levels.fyi was the closest thing to research based on role and level, but you seemed to suggest that that was not quite there.
A small hint, go for IAM Engineering, create a lab with inter-connected systems, and present a diagram and working demo of your lab, once you are done with the presentation most questions will already be answered. Diagrams and working demos go a long way instead of letting the interviewer torture you with questions. What I have found out, having a sweet and positive personality goes a long way. Smile and be positive. Most importantly remember, people often don't want competition, being too smart sometimes works against you.
i am in relatively senior role in tech. when i started prepping for an interview after years, i was shocked at the process they have these days. Firstly, we have to clear the data structures coding challenges. Second round is super tough technical interview where a bunch of engineers ask you left righ and center about devOps, infra setup, security and data engineering. Once i managed to clear these, the third round was supposed to be behavioural. But I met two senior engineers who took 1.5 hours of tech interview again on the projects that i worked on and on data structure and ultimately I was rejected. I was fairly confident of answering all the questions they asked (most of them). I think more than technology, it is about the culture of the organization. If the people there think you are not a good fit in the sense they dont see catching up with you over beer on Friday, they most probably will reject you. Likeability is a big factor.
I did developer interviews back in the 90's, and they didn't treat candidates like this, even ones fresh out of college.
i share the same feeling
The frustrating thing about this is its illustration of how broken the interview process is. Here we have an established engineer from a major tech company who had significant contributions and impact - but because he didn't spend months prepping DSA for that first interview, he "bombed." Interviewers are reading from a "cheat sheet" of expected systems design answers, what questions to ask e.g. they don't know the answers either, but expect the candidate to know literally any system in great detail. That's insane to me. We've got to figure out a way to do better.
It's not broken. It's actually pretty effective at evaluating candidates within a limited amount of time. In an ideal world, everyone would get an internship to prove themselves, but that's obviously not possible. No one should get any entitlement because of their position. Sure, I have more experience, but I should know everything that a fresh graduate does, and if I don't I think it's fair to expect me to prep.
@@EngineeringwithUtsav I don't know. It seems like your experience should count for something. They're treating you as if you're lying about it and have to prove yourself during some crazy coding test that isn't anything like day-to-day development. I don't think other professionals have to go through this.
@@davidowens9597 totally agree with you
@@davidowens9597 i agree. I am not sure starting from WHEN your experience seems like irrelevant from hiring perspective for a SDE job
Thanks for sharing your experience. Most underrated youtube channel in techie background. I am damn sure your channel going explode in few months.
Said the same things a couple of months ago.
The mentor I never had. Thanks, Utsav!
As a hiring manager, I really can't overstate the importance of mock interviews. You can be the best candidate out there but if you are too nervous during the interview you might run into problems. Practicing this in mock interviews before really helps you to come across more natural.
Are you on LinkedIn?
Would want to connect with you.
Dai, your videos are amazing quality!! I sometimes watch it just for how crisp everything is (intro, background, audio/video, presentation)
I like the honesty and real things u presented so easily.
I love your videos. You are so honest and straightforward in terms of sharing your experiences and thought processes. Thank you so much for taking time to help others!
Straight shooter. Says it as it is in a way that is real and palatable. These are more life lessons than IT guidance. Keep up the good work. Much appreciated.
This channel is highly underrated. Your content is gold!
Great Video. Currently I am doing some interview prep just to be more flexible and refresh some of the basics. I was shocked how fast I forgot details about data structures or algorithms I did not need. The theory is there, but when doing leetcode I find myself thinking "a priority queue/heap should make it easy, but how exaclty do I use it?" The same also happens with some algorithms. At least for me it interrupted the flow, I was not really able to track how long a coding problem took and just checked the API/algorithm to just finish the current problem.
It gets questions done, but is not really time efficient. So I agree 100% agree, first theory then the problems.
Your contents are supremely transparent. I just love it. Hoping to watch many more videos like this. And wish you all the best in your upcoming job interviews.
I liked donne martins github collection of system design topics. It gave me an overview of topics that exist and some good examples. Once I read that I started diving deep into each topic.
Can you give link for that 🙂
I definitely fell into the "design interviews are easy" trap and I almost never spent any time preparing for them. It is intimidating to know that I probably need 3-6 months of prep for them
hai utsav i feel good when i watch your videos and gives me the different kind of motivation.thanks a lot man
Your channel is underated my friend. Good content and quality. Keep up the good work
Always looking forward to the new video
Thank You for your videos, very informative. I wish you luck with growing your channel, it deserves more subscribers.
I'm glad I found your channel. Awesome content 🔥
You're videos are always brings a good light to our knowledge!!
Thanks Utsav for sharing your invaluable true experience
Always giving us gems. Thank you.
Awesome Content Utsav
Learn from those who have been before. Super advice for all, regardless of background. Thank you 😊🙏
Great Video, as always.
Thanks for sharing
Great Stuff! It would be great if you can start a series on Data Structure & Algorithm concepts.
Very relatable video. I am a freelancer for a long time, I usually do contracts that are under a year in length. I mix my projects and switch between development and consulting, so once in every two years I do coding interviews. And I half intentionally always bomb the first one. I found out about myself some time ago that the biggest driver for me, to catch up with latest tech, practice algorithms and problem solving is failure. Positive motivation like working for a big name or big $ no longer does it for me. Or did it ever?
Such a great channel. I am glad I came across it today. You have a new subscriber!
Nice talk Utsav! You covered almost everything. Thanks for reminding me that System Design should also be an important part of preparation. I thought I knew systems but after your video, I think I'll go back to understanding things again from thee basics.
Is it really practical to take time off so one can be a full time interviewee ? I think it is better if one applies for jobs that are already in his technical or work sphere ...
Thank you for this utsav dai.
Thats how successful may be look like...even with this much of experience.... You can't stop learning... keep going and going...life is about struggle...
Software Engineering is about struggle (but wait any good challenge is about struggle -> bigger struggle === bigger reward)
Utsav can please start making videos about data structures and algorithms, probably a crash course that could help us in cracking interview, something similar to your video related to interviews problems would be appreciated.
Would love to see this!
System Designs are really nightmares for freshers. But on the other hand they also help in differentiating the best candidates from the good ones. No better way to put it out there apart from your video :)
Cheers! :)
The much awaited video🔥💯
Thank you very much for sharing your highly valuable experience , very encouraging for me , from Kolkata City , India 🙏
Solid advice dai.
Your content is 🔥🔥
So happy to find you channel
Nice Talk man !!
BTW where are you landing up next :)
One of the best mentors ever ❤️❤️❤️
Thank you so much this was very helpful 😁
What to you suggest, whether we should prepare everything and start giving interview . I know we cannot cover every aspects. or other way do 50% prep and start giving interviews and learn from mistakes and go on until cracked.
In your experience, at roughly what level of experience should I expect system design questions? If I’m applying for a SWE2 at a FAANG for example, is it worth deep diving into system design prep?
No need to see dive too much as SDE2. Understand requirements, basic QPS math, trade offs in CAP and how/when to chose one over another, known common tech around typical SD areas. That should be good enough. I think the grokking course and RUclips resources are just in par with level 2.
@@EngineeringwithUtsav Great, thanks! Keep up the great work, I think your channel is going to blow up in no time!
I wish you make an affordable course on System Design.
Shouldn't system design interviews only be for architects or staff engineers or at startups?
Nope. Anyone that’s not fresh out of college can get them. The depth may vary by experience.
Great content, are you planning to share a system design experience and your thought process to resolve it
Just did
How can we know which comes under advance DS? , If you have any resource which has proper distribution between advance and normal DS , then please do share it.
Anything that is not taught in university.
This is by far the most relatable video. I have had a ditto experience interviewing with companies ! Need loads of resources and most importantly time where I can be highly productive to learn System Design. One of the most fun topics. Dream topic and the most challenging of them all !! Would you be willing to mentor me ? Would you be willing to take up mock interviews ?
I started doing it briefly but my calendar got swamped with requests I couldn’t keep up with. Now that I’ll be starting to work full time, I’ll likely be in the interview panel there, so I’m pretty sure it will be a conflict of interest to conduct mock interviews unfortunately
Very nice content and correct suggestions for reading materials, except the promotion :)
Thanks for the great content. Could you give us a tour of your house in your other channel ?
Very insightful, Utsav. I wonder if it could be possible to somehow measure or quantify a candidate preparedness level. We all agree thorough preparation is paramount to increase the chances to land the job, but how much is enough? Some people like to measure with time, like Sam from "Keep on Coding" who stated that if he was to start interviewing he would need "3 months of coding challenge practicing". Other people like Joma from "Joma Tech" like to measure by the difficulty of the problems you can solve, and others like Clément Mihailescu from "AlgoExpert" measure by quantity, or the number of problems you solve in his platform. Personally, I think all of these dimensions can't measure the level of preparedness because each candidate is different, with different learning speeds and different cognitive abilities, and the companies being targeted are also different, each evaluating candidates differently. A good hint of the candidate preparedness can be acquired in mock interview services, but even there the measurement isn't standardized and has an ample variation degree. I wonder if it could be a set of 5 or 6 scripted mock interviews with very specific topics being asked, paced, and with specific coding challenges that are representative of the major concepts asked in coding interviews in general, then a candidate can go through these "master mock interviews" and then see how it goes and compare his performance against others, and infer conclusions like "hmm, 80% of candidates that took these tests and landed a job at Google performed better than me, I am probably not ready yet, I need more preparation".
False competence is a common pitfall during tech interviews. I doubt there is a standard way to measure preparedness. I have my method that worked for me, I’ll be sharing that in the next video :)
@@EngineeringwithUtsav wil be waiting for that video
since Sep last I had 20 interview I am still struggling to get a role as azure devops (non developer) in toronto
Truly it does seem like the interview process in software jobs is very very broken. Definitely all your advice is GREAT! But, man... getting in is almost a random process. I hear all the time that people get questions that simply can not be answered unless you actually knew the question upfront. It is like a leetcode crap shoot. Truly the process seems broken. BEST of luck and hope you land a GREAT job soon!
Would love some more idea of the specific questions you get asked in the process. (I am looking to get back in after a year off (covid!) as well. Wish us all luck!
Coding interviews aren't perfect, but there are also not many other objective ways to evaluate candidates in a short amount of time. It's a function of time, cost and objectivity.
@@EngineeringwithUtsav Why can't they look at what you've done in past jobs? Developers in the past didn't have to go through hours of "Spanish Inquisition" interviews, and the companies seemed to find good employees anyway.
Which book would you recommend for learning algorithms? Thanks.
Start with Grokking Algorithms.
I am an aspiring junior and went through a lot of interviews myself recently too and it's crazy how different the interviews are even tho they all were for the exact same title "junior php web developer". For example for one interview i just had 1 hour of talking and then 7 hours for designing an API. Another one was 2 hours of talking and 2 hour coding interview with a complicated algorithm. Another one was 1 hour talking and then an on-premise interview (other ones were online) where I had to solve a real world problem within 5 hours which can only really be solved in that time if u are very familiar with both the repository and visitor pattern (which i wasnt). So yea, it's really different each time and also the people were super different each time. it's really really fascinating how big the differences are between each job even when the title is exactly the same. Before all these interviews I only had experience working with laravel and so I kind of thought everything would be similar to that, but so far the interviews have shown me that I know nothing, lol :D Now I am learning a lot about design patterns and "clean code" from uncle bob and others.
(I did get an actual offer for the job that wanted me to do the api design, the 2 hour coding interview told me immediately that im not good enough and the other ones haven't told me yet)
Keep at it. Interviews are also just luck sometimes. You got this!
I'm curious, where would you or anyone else for that matter rate college students who just got out of college? While web development might not seem like a 'software' field because it's niche and borderline software/application development to some people, what would be a great salary or hourly range? While I want to be optimistic, the unfortunate thing is that my current situation doesn't allow me to have a salary less than 50k, which to some is a deal breaker.
That question I guess was either LRU or LFU cache.
It wasn’t. Those are pretty straight forward. It was about the longest increasing sequence, with a slight constraint on the differences between numbers.
@@EngineeringwithUtsav hmm, interesting, I wonder where do you need deque there like even when you need to skip because you have memoization on your side.
That was the trick. It looked like a DP problem, but it wasn’t. Don’t want to disclose the question due to NDA but I couldn’t find it on LeetCode. Cheers! :)
@@EngineeringwithUtsav sure no pressure. I guess I'll pound my head for few days trying to derive the question :)
what do you categorize as advanced DS?
video on how to negotiate pls
which position do you apply for?
sde-4?
Where can we give mock interviews. Is leetcode Mock interview fine, please guide me as my placement season will start in 3-4 months.
Find people you know. Mentors. Friends. Make sure they are used to interviewing. Watch videos to practice - I have one as an example. I may do some as an example.
Pramp. Interview Cake.
Did you get any offer?
A few :)
@@EngineeringwithUtsav cool. Congrats
What's written on your right arm ? Thanks
you have 5 guitars?
In My Recent SWE Intern Interview at Hackerrank, I cleared round 1 with CTO and then the second round seems to be a system design interview like he asked me about "how can we make a thing similar to gitpod without using containers?"
this should be considered as a Sys. design interview Q? btw, I am in a sophomore year of my B.Tech Degree.
Companies can ask whatever they want to ... this seems more of a domain knowledge question than a system design
This video made me think , that I'm dumb.. cause I want to be a full stack web developer ( a lot of skills to learn ) + the system design.. things getting scary and complicated
You’re not dumb. Time effort will fix most things :)
What is system design?
Hai sir i have to know about jobs based on operating system
I think sometimes the technical interview is waste of time. Especially, They might tell you there is 2 more interviews after the Technical interview.
Tech interviews have become this weird, almost ritualistic, type of ordeal that they don't even make sense anymore. Hire fast based on resume and personal interviews and fire even quicker when you see that you don't have a match.
The result of trying to standardize and quantify hiring. It’s got it’s pros and cons for sure.
Suggestion me frameworks of java for beginners
you are amazing
Those leetcode style questions are a real pain in the a** and impractical for the most part in the real world. Pair programming is a much better alternative.
Ur vids r really cool & info at the same time ;)
Well informative. But you didn't mentioned that which Company's offer you have and you said yes to that Company. We all curious to know that in which company you will be joining.
In due time :) most likely a candidate for Instagram story instead of a RUclips video.
Thanks for sharing your experience! Just curious: what are the companies you interviewed with? :O
Any suggested resource for practising mock interviews?
Anyplace is fine as long as interviewers are not just fellow interview candidates but folks that can provide good feedback
Hope you have got an offer in your hand right now 😃👍
I do, a few :)
@@EngineeringwithUtsav Awesome 👍
in my experience interviewers are looking for a single excuse to reject you, as a candidate you have to be perfect for the duration of the interview according to a standard you don't know which is nearly impossible.
Yes, the job of the interviewer is trivial in comparison with that of the candidate.
It’s actually the opposite in most cases. It’s a waste of time and resources to interview and reject candidates. Interviewers are on your side and they want you to succeed, even if it feels otherwise.
@@EngineeringwithUtsav not in my experience. May be cultural depending on country but here in most cases they're trying to find an excuse to reject you.
And especially if on entering the room they find you're not a 25 year old fresh graduate with 20 years of professional experience but a 50 year old seasoned veteran.
tnx a lot!
Sir talk something about competitive programming..
I don’t do or enjoy competitive programming. It’s not a big thing in the US.
@@EngineeringwithUtsav :( :(
When can we expect System Design Course?
Soon :)
Good job
Hey sir which is your native place...
Let me guess, your side project and some of hobbies include guitar & keyboard?
We are the same man...
So it means you can take some time off to learn to play rachmaninov, dream theater, or John coltrane
From 13.4 to 13.13 I heard👂 some Fancy 🔥😁 word...
I like that Gayatri Mantra Tattoo on your right hand 😅
its not it. he has nothing to do with india
@@kaushikrishi01 Not India but somewhere else
@@kaushikrishi01 He is from Nepal.
@@nirajkhatiwada6696 yup 🇳🇵💪
Everyone might be considering their " best time " for some " best buy " while tech engineers are concerned about their " best interview " for the " best pay " ....
do you regret quitting?
I miss working with people, but no regrets. But then again, it also wasn’t a permanent thing.
Nice chit-chat 👍
What's your origin?
How do you know your worth tho? Because it depends on the market
Research, find what others with your experience are getting paid, understand how salary ranges work
@@EngineeringwithUtsav can you go more into this, especially since I thought levels.fyi was the closest thing to research based on role and level, but you seemed to suggest that that was not quite there.
is that Gaytri Mantra tattooed on your arm ?
I leanred????
What?! Don’t tell us which offer you accepted at the end? 😀
:)
Good that you share your experiences. However, your key problem is you are not trying to move up the technical hierarchy like lead or archirect
Lol, my key problem :) and you know that, how? Just curious 😅🤔
You didn't tell us about your favourite one's you wanna join😁
great
A small hint, go for IAM Engineering, create a lab with inter-connected systems, and present a diagram and working demo of your lab, once you are done with the presentation most questions will already be answered. Diagrams and working demos go a long way instead of letting the interviewer torture you with questions. What I have found out, having a sweet and positive personality goes a long way. Smile and be positive. Most importantly remember, people often don't want competition, being too smart sometimes works against you.
wow, today i'm early