I just realised that coding artifacts and non-coding artifacts don't really make much sense in this context... I think what I meant was elements that are directly related to coding implementation, and elements that aren't. But that's kinda wordy so hopefully you still get the point I was trying to make :)
hello , i noticed that you read of a script and as a result you look at the camera at random there is a software that concentrates your eyes strait to the camera tha tou can use.
Perfect video tbh, everyone talks about these tech interviews like the implementations are the easiest things ever... they're not; so this is def super helpful.
I wish each interview could give 5 mins in the beginning just for the interviewee to think about the problem, brain storm, and gather methods. It is kind of ridiculous to ask interviewees to talk, code, and solve at the same time. Then the whole coding interview becomes if you have seen the question before.
I like this coding interview framework. We often don't communicate our process, or rush to solve the question without asking clarifying questions, constraints, etc. It can save a lot of time for the interviewee and the interviewer to follow a step-by-step, structured approach.
Hi Andrew, Thank you for sharing this info. A lot of your sharing echoes my practice as I transitioned from a Mechanical Engineering PhD-level engineer to a senior SDE. Honestly, I learned a lot of CS skills when problem comes. Thus, those non-coding artifacts are actually like complementary portion to my coding artifacts. Of course, I keep practicing leetcode and Data Structure and Algorithm regularly just to keep myself sharp in skill. It is like a life-long practice. Thank you,
1) Clarify requirements 2) Brute force solution 2.5) Code brute force solution 3) Optimal solution 4) Code optimal solution 5) Testing and analysis Constantly communicate as much as possible and ask clarifying questions
@madster01 Rejected. 😂 It's totally on me, though! Spent half the time on the problem dumbfounded that Python's dict keys don't return as integers even if you insert them as integers. Perfectly demostrated to the interviewer my inexperience in the language. 😁 Chatted with the interviewer afterwards for 10 minutes discussing my performance. He told me my communication was excellent and I should totally keep working on my coding skills to nail the job next time.
@@imaginaryvenus5What do you mean integer keys don’t return as integers? I tried this code and got an integer returned. # Give dictionary an integer key hash = {1: None} print(type(list(hash.keys())[0])) #
hello! i really hope that you see this after 3 years what should I do on the questions part if the task seems very easy, I'm confident about my complexity answers, the implementation as well and really want to start coding right away? should I still ask questions & clarify use cases? I don't think I'm a perfect coder but the task I got was marked 'Easy' on Leetcode as well I see that this part is graded separately from the code but won't I seem too dumb if I suddenly try to clarify everything for a simple task?
What is he saying? "If we use some type of..." and I don't understand the next word he says (at 8:42 in the video). (And the video has no subtitles available.) ... UPDATE: HE'S SAYING "CACHING" **facepalm**
This is so stupid - spending your time to master leetcode skill when ChatGPT can answer those on that spot just to impress some dumb-ass interviewer. It's like learning the trick you will only show once. Screw that
That is so true lol. Something I always feel dumb about interview where we need to know so much algorithms. Those people that passed the interview when on the job position can just have the AI do 90% of their work. And then they just need to be there to modify it to make it the way they want.
Also I heard that, during interview they would ask u some question out of the coding circle. Like how does a package work or something, which I got 0 knowledge 😅
I just realised that coding artifacts and non-coding artifacts don't really make much sense in this context... I think what I meant was elements that are directly related to coding implementation, and elements that aren't. But that's kinda wordy so hopefully you still get the point I was trying to make :)
hello , i noticed that you read of a script and as a result you look at the camera at random
there is a software that concentrates your eyes strait to the camera tha tou can use.
it was perfectly understandable what you meant. it's a great video thank you very much for sharing
Perfect video tbh, everyone talks about these tech interviews like the implementations are the easiest things ever... they're not; so this is def super helpful.
Wow I'm sorry for the people outside the 14k people who watched this video. This was spectacularly practical and useful, thank you so much!
REally?
I wish each interview could give 5 mins in the beginning just for the interviewee to think about the problem, brain storm, and gather methods. It is kind of ridiculous to ask interviewees to talk, code, and solve at the same time. Then the whole coding interview becomes if you have seen the question before.
I feel you, it sucks :/
Who says you can't do this? You can spend 5 minutes doing this just think out loud.
Thissssssss!!!!!!!!!!!!!!!!!
I've seen a bunch of these style videos over the last two years... this is definitely one of the best by far!
I like this coding interview framework. We often don't communicate our process, or rush to solve the question without asking clarifying questions, constraints, etc. It can save a lot of time for the interviewee and the interviewer to follow a step-by-step, structured approach.
Hi Andrew, Thank you for sharing this info. A lot of your sharing echoes my practice as I transitioned from a Mechanical Engineering PhD-level engineer to a senior SDE. Honestly, I learned a lot of CS skills when problem comes. Thus, those non-coding artifacts are actually like complementary portion to my coding artifacts. Of course, I keep practicing leetcode and Data Structure and Algorithm regularly just to keep myself sharp in skill. It is like a life-long practice. Thank you,
RIP to everyone that has to do "interviews" that are just online coding challenges with no interviewer
1) Clarify requirements
2) Brute force solution
2.5) Code brute force solution
3) Optimal solution
4) Code optimal solution
5) Testing and analysis
Constantly communicate as much as possible and ask clarifying questions
Much Needed. Thanks for putting this all together. Great Work.
Watching this 15 minutes before an interview. I only have a week of experience with leetcode style problems. Expecting total failure 😆 Wish me luck!
Hey, how did it go?
@madster01 Rejected. 😂
It's totally on me, though! Spent half the time on the problem dumbfounded that Python's dict keys don't return as integers even if you insert them as integers. Perfectly demostrated to the interviewer my inexperience in the language. 😁
Chatted with the interviewer afterwards for 10 minutes discussing my performance. He told me my communication was excellent and I should totally keep working on my coding skills to nail the job next time.
@@imaginaryvenus5What do you mean integer keys don’t return as integers? I tried this code and got an integer returned.
# Give dictionary an integer key
hash = {1: None}
print(type(list(hash.keys())[0]))
#
@@imaginaryvenus5it’s all a learning experience. I’m sure you’ll mail your next one don’t give up !
@@imaginaryvenus5 was it on-site whiteboard style on online using a web service to write/run the code btw?
Fantastic advice. Thank you!
Hey, this video is so good. Please keep making videos
I'm now at least a bit more motivated to do this thanks!
What if you have never seen the problem before? And are stuck?
Why music?
Amazing work! nice job with the example, lot of things to think about if you are a good engineer!
Great video!
hello! i really hope that you see this after 3 years
what should I do on the questions part if the task seems very easy, I'm confident about my complexity answers, the implementation as well and really want to start coding right away? should I still ask questions & clarify use cases? I don't think I'm a perfect coder but the task I got was marked 'Easy' on Leetcode as well
I see that this part is graded separately from the code but won't I seem too dumb if I suddenly try to clarify everything for a simple task?
Great video! Could I get the song you used for the outro?
Bro, use Shazam
What is he saying? "If we use some type of..." and I don't understand the next word he says (at 8:42 in the video). (And the video has no subtitles available.) ... UPDATE: HE'S SAYING "CACHING" **facepalm**
Thanks bro for sharing
No worries !
back to leetcode for me it is because I still don't understand the technical jargons XD
Dude lower your tone i can’t listen the music
thank you!
tHANK YOU SO MUCH
thanks
Overall, speak more and leave a good impact on the interviewer
kaneki?
Are you Taiwanese? You speak very fluently and pronounce very well. How did you achieve it?
thankk youu
Annoying music
I suck at all things that aren't free because I'm a cheapskate. 😂
This is so stupid - spending your time to master leetcode skill when ChatGPT can answer those on that spot just to impress some dumb-ass interviewer. It's like learning the trick you will only show once. Screw that
That is so true lol. Something I always feel dumb about interview where we need to know so much algorithms. Those people that passed the interview when on the job position can just have the AI do 90% of their work. And then they just need to be there to modify it to make it the way they want.
Also I heard that, during interview they would ask u some question out of the coding circle. Like how does a package work or something, which I got 0 knowledge 😅
Great video!