Good to see you back with best learning stuff for me 🙌 Like that point "accept you are stuck and looking for solutions rather than pretending I know everything" Personally I think those people annoy
Great video, good tips! That's indeed a pretty cool shirt. During an interview I try to do the thing that you suggested which is to make them see that I'm a cool, chill guy (at least I hope I am) who is fun to be around. I make it work both ways, if the interviewer seems like somebody I would not want to be around every day, then that is a big discouraging factor for me as well.
Yeah. I like your shirt 😅. I totally agree about the 4th point. I used to be a perfectionist and tried to make things as optimized as possible from the beginning of the development process, sometimes I even ended up frustrated because in my quest to optimize everything I would change the logic several times. It can also waste your time, because sometimes during the dev process we realize things should be done differently, thus losing all your work. First you should make everything simple (Make an MVP)
That’s true most of the time our job is not about skill but about being able to communicate and work along with the team. I knew one guy who won a lot of programming contests he was the best in terms of skill though it was hard to work with him cause he was too arrogant and and he was too obsessed with deeper levels of abstractions rather than get the job done in balanced way, a lot of over engineering
Great hints. I like these human sides of the programming experience. I hope to know more about the standard practices in the work process but then I want to know what a programmer does in a typical day, work challenges, and the best part of being a programmer (more than the pay). Or shall I say Coder? What's the difference anyway?
I hate exam-driven interviews. Generates a weird feeling where there is no trust. Prefer a real work scenario for a couple of hours or days. Thanks for the video.
Any tips for trying Android Development interviews? Trying to transition to another company but it feels like there’s so many different types of interviews. It’s either study DSA or know the latest libraries.
If you're applying to a company that does DS and algo questions then sadly grinding leet code is probably what you have to do. Some companies do take home projects instead - like square. So apply to square 😉
My tip for take home projects would be to take the time to make sure every single thing in the project is as good as you can make it to be. If you are not sure about something or you don't have time to implement something well and it is not mandatory, then it's better to skip that feature. Chances are your code will be nitpicked to oblivion. If they don't like your code, then chances are that you won't even get an interview where you could explain your reasons. It happened to me where I wanted to add lots of things to the project to show that I know and use them because they will be good conversation starters (naive me) but they were not 100% perfect (due to time constraints), so they declined me without a chance to explain them.
@@codingwithmitch Thanks! Another thing I learned is to try to specify the scope of the take home project with them if it is too broad initially. Something you deem unnecessary for a project like this could be a must-have for them. For example one time all they said was "show the content of a dummy api in a list" and all the recommended dummy apis and the one I used only sent a few items (8-20) with a simple call so I didn't implement paging which they heavily criticized.
Hey mitch thank you for these tips can you make a video on how to prepare for Data Structures and Algorithms and how to communicate and behave in interviews apart from this video's tips.
Can we have a Video "solving LeetCode problems", Most companies have this kind of filter in their technical interview, but sometimes I get stuck on how should I start, how to analyze the algorithm, how to know what data structure we need. , etc Thanks!
Other advices are legit 👍. Really agree. But still: any mind games during interview is a huge red flag. Why? Because they want to know, how you behave in a conflict, but a single case is not reliable source. You could be nervous (you probably are), frustrated and so on. Technical interview should be technical.
Well I was more thinking something like: "hey, why didn't you choose path B?" Not really trying to confuse you necessarily. More like just trying to get more info about your thought process.
Don't forget to prepare for the sliding window or dynamic programming test before this interview 😅 If you can't pass that test which hasn't been used since jesus christ you're clearly useless for an android position
I got in an interview, I'm stuck and try to ask interviewer for hint and what they would do; instead of helping me they said something like they not here to help me. I passed and don't accept their offer XD
Do you like my shirt?
Don't forget to leave a comment .
Yes...How can i get one ?
I like your shirt. Where I can get it?
Xaxaxaxaxaxaxa
I don't know where you can get one. My wife got it for me and she can't remember where.
I've got a Firemonkey Shirt (Delphi)
Hey Mitch! Great to see ya again!
Good to see you back with best learning stuff for me 🙌
Like that point "accept you are stuck and looking for solutions rather than pretending I know everything"
Personally I think those people annoy
Great video, good tips! That's indeed a pretty cool shirt. During an interview I try to do the thing that you suggested which is to make them see that I'm a cool, chill guy (at least I hope I am) who is fun to be around. I make it work both ways, if the interviewer seems like somebody I would not want to be around every day, then that is a big discouraging factor for me as well.
Yeah. I like your shirt 😅. I totally agree about the 4th point. I used to be a perfectionist and tried to make things as optimized as possible from the beginning of the development process, sometimes I even ended up frustrated because in my quest to optimize everything I would change the logic several times. It can also waste your time, because sometimes during the dev process we realize things should be done differently, thus losing all your work. First you should make everything simple (Make an MVP)
I've had a lot of developer interivews and this is very good advice.
the pull up the documentation advice is golden. thank you!
Great video! You put into words some of the strategies I didn't even know I used in interviews!
Please do more videos in the future, I miss your videos on RUclips!
Glad that I've found your channel men!
That’s true most of the time our job is not about skill but about being able to communicate and work along with the team. I knew one guy who won a lot of programming contests he was the best in terms of skill though it was hard to work with him cause he was too arrogant and and he was too obsessed with deeper levels of abstractions rather than get the job done in balanced way, a lot of over engineering
Arrogant people are the worst to work with
Mich I love this video and I miss your videos :D I know you have less time now but at least keep the VBLOGS! :D
Great advice. That shirt is stupendous
Nice video Mitch, I like the new format. Keep it up!
PS the pineapple shirt is always a winner 👌
Expecting more like these Mitch ❤️
This is awesome advice. Considering I just bombed a phone interview lol
love this kind videos of you, please share more videos about interviews
Mitch your eye color is cool 😂
Great hints. I like these human sides of the programming experience. I hope to know more about the standard practices in the work process but then I want to know what a programmer does in a typical day, work challenges, and the best part of being a programmer (more than the pay). Or shall I say Coder? What's the difference anyway?
Good ideas. I'll maybe make some videos on that
Thanks a lot for this video, Pretty cool shirt 🤩and yeah i love this kind of videos please do more 🙏
I hate exam-driven interviews. Generates a weird feeling where there is no trust. Prefer a real work scenario for a couple of hours or days. Thanks for the video.
Ya I'm a fan of the take home project
Long time no see 🎉
Where are you from Mitch? it's so wonderful to listen to you.
British Columbia
I love the tips! Thanks!
Any tips for trying Android Development interviews? Trying to transition to another company but it feels like there’s so many different types of interviews. It’s either study DSA or know the latest libraries.
If you're applying to a company that does DS and algo questions then sadly grinding leet code is probably what you have to do.
Some companies do take home projects instead - like square. So apply to square 😉
My tip for take home projects would be to take the time to make sure every single thing in the project is as good as you can make it to be. If you are not sure about something or you don't have time to implement something well and it is not mandatory, then it's better to skip that feature. Chances are your code will be nitpicked to oblivion. If they don't like your code, then chances are that you won't even get an interview where you could explain your reasons. It happened to me where I wanted to add lots of things to the project to show that I know and use them because they will be good conversation starters (naive me) but they were not 100% perfect (due to time constraints), so they declined me without a chance to explain them.
@@BapeRuLLZ ya that's a good point. Don't add things you aren't 100% confident in. They're going to tear it apart.
@@codingwithmitch Thanks! Another thing I learned is to try to specify the scope of the take home project with them if it is too broad initially. Something you deem unnecessary for a project like this could be a must-have for them. For example one time all they said was "show the content of a dummy api in a list" and all the recommended dummy apis and the one I used only sent a few items (8-20) with a simple call so I didn't implement paging which they heavily criticized.
Hey mitch thank you for these tips can you make a video on how to prepare for Data Structures and Algorithms and how to communicate and behave in interviews apart from this video's tips.
I feel like there's not much more to it other than solving the actual problem if we're talking about DS and algos
Thansk for the great video ♥ cool shirt btw 😄
"Hey mitch here is your engagement"
Feels kinda nostalgic to say 😁
👅
Mitch is back!
👋
very informative video Mitch, thanks alot.
Good video Mitch,
Super helpful. thank you. beautiful shirt😉
Can we have a Video "solving LeetCode problems", Most companies have this kind of filter in their technical interview, but sometimes I get stuck on how should I start, how to analyze the algorithm, how to know what data structure we need. , etc
Thanks!
Thank you, mitch
the first thing i said was "wow nice shirt! " :D
Imagine being that guy who was in the interview with you watching this video lmao
I was thinking that lol but he prob wouldn't know
@@codingwithmitch eh, even if he does, lesson learned for him I guess. You didn't name the person so it's totally okay.
Nice shirt, Mitch :)
Great video!
Hi make more video about interviews questions... Thank you
Shirt is really cool ;)
When square took your interview, do they ask DSA question or just android dev questions with assignment?
Take home android project
Like your shirt 😂, thanks for the video it was very informative
Mitch, that's really a nice Shirt 😉
If someone suggest worse way to confuse you - that's a big flag. For me it's no go, I would not work with such people.
Other advices are legit 👍. Really agree. But still: any mind games during interview is a huge red flag. Why? Because they want to know, how you behave in a conflict, but a single case is not reliable source. You could be nervous (you probably are), frustrated and so on.
Technical interview should be technical.
Well I was more thinking something like: "hey, why didn't you choose path B?" Not really trying to confuse you necessarily. More like just trying to get more info about your thought process.
@@codingwithmitch of course how you ask makes difference, agree
Mitch I love your shirt.
Don't forget to prepare for the sliding window or dynamic programming test before this interview 😅 If you can't pass that test which hasn't been used since jesus christ you're clearly useless for an android position
Are you talking about navigation drawer? Did they ask you to make one in your interview?
@@s-w No, sliding window is a technique to reduce time complexity in DS&A tests
@@s-w that right there is sarcasm 🙂
Greatest super shirt i've ever seen...
Super duper
Awesome 👌
I got in an interview, I'm stuck and try to ask interviewer for hint and what they would do; instead of helping me they said something like they not here to help me. I passed and don't accept their offer XD
Ya sounds like not a great place to work lol
this really helped! thank you
🔥
Ty
mitch, ı love your shirt it is pretty cool
it's been ages
Like you shirt ❤️
Ok you say anything i can comment.
So, I would comment Please Mitch add discount on your course in this inflation))
This weekend when I launch the new course I'll do a discount code
Nice talk.. I like your shirt... Lol 🤣
It is indeed a good shirt 👌❤
Can you help me?
Hi, nice shirt :)
word