The BEST android courses in the world: codingwithmitch.com/ 4 things you should NOT DO in a software engineering interview. Social: / mitch_tabian / codingwithmitch . .
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.
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
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)
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?
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
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.
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.
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!
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.
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
@@codingwithmitch Nice! Also recently I heard you say in another video I think. That you won't hire someone who doesn't write unit tests. Do you mean UI or viewmodel/repo tests. I still find it hard writing tests on Android, there's never any clear guidance, there are so many variants and things are constantly changing. And the tests I do write sometimes I feel are obvious and not doing anything important. Any tips/resources you can suggest for this?
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
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.
