You only need 150 LeetCode questions.

These are 5 simples tips I used to study leetcode effectively. These strategies helped me find a career as a software engineer at big tech companies like Amazon Microsoft and Google.
#softwareengineer #coding #google #programming #engineering #softwaredeveloper #softwaredevelopment #code #developer #faang #resume #resumetips #salary #leetcode #interview #study #studymotivation

[@Wertasile]

Thank you Alex! Your insightful Linkedin posts and now your KZbin channel provide even more insight. Looking forward to more videos!

[@smallpotato507]

very good advice. thanks Alex!

[@Android-17]

Solid advises 🌟 thank you!

[@constans74]

Your last point is the best- this is a skill and you can learn it.

[@justinhoang8078]

Hey Alex, I noticed that you are Vietnamese software engineer! That’s really motivating bro! Thanks for sharing

[@ccysp1220]

Thank you Alex!

[@devonzara]

So, 30 minutes and then move on to the next one... but if you don't know the patterns, you're unlikely to discover them on your own with other problems. I feel like you missed a few crucial steps: 1. Look up and test a solution 2. Study and understand the solution, brainstorm why this solution works and if you can think of alternate or even better solutions 3. Mark the question as "failed" (or a less harsh term if you prefer) and set a date to revisit it based on how much you struggled with it Personally, I've found these numbers work well for me: - If I solve it quickly/easily, or didn't even need to type it out... no need to revisit it - If I had previously failed this problem and this is the first time I solved it... revisit in 1 week - If I solved it but I struggled a little... revisit in 1 week - If I almost solved it but got one little thing wrong... revisit in 4 days - If I failed to solve it but had the right approach in mind... revisit in 2 days - If I failed to solve and didn't even have the right approach in mind... revisit tomorrow If the schedule gets filled up with problems to retry, it's perfectly fine to not do any new problems that day. The idea is to build understanding, not race to the finish of the Blind/Grind/NeetCode lists.

[@ceciphar]

How are you tracking this?

[@devonzara]

@@ceciphar I'm just using Notion... Created two tables on a single page; "Problem List" keeps track of the current status of each problem I've tried. Second table, "Practice Sessions", is a log of all individual attempts of each problem. After doing a problem, I update the "Practice Sessions"... I add an entry for the problem's attempt. Inside of the entry's page I include notes on things I did well and things I struggled with. Then I populate the other fields in the table like the rating for how comfortable I felt with the problem on that attempt, the current date, how long I spent trying to solve it, how long I spent looking up/studying the solution if I failed to solve it on my own, etc. Next, I update the "Problems List" table to reflect the "current" status of the problem I tried. If it was my first time trying that problem, I add a new entry for it. If I tried it before, I update the existing entry for it... copying over the comfort rating, date of my last attempt, and I add a date for when I wish revisit the problem. Overall, it takes about 3-5 minutes to log what I've done... but I feel it's a valuable tradeoff and gives you a chance to reflect on and absorb what you just worked on before moving on to the next one.

[@takeuchi5760]

​@@ceciphar you can just make the different lists on leetcode

[@takeuchi5760]

Yes this is exactly what I thought, moving on from a problem without understanding is awful advice and won't help in the long run. You should move on to looking at the solution not just skip the problem.

[@user-xc7rp5pr2l]

Thank you ❤…a lot ❤️

[@spageen]

It’s better to really understand 150 than kind of understand 300

[@mesaber86]

Study the best solutions instead of coming up with your own subpar one that waste your time. Also solving the problems isnt hard, doing it efficiently is.

[@araz911]

what's the point of leetcode if AI solves all of them in like one response

[@mesaber86]

@@araz911 are you gonna type that on your resume? AI solves everything for me so hire me? 🤔

[@araz911]

@@mesaber86 you are hired

[@mesaber86]

@@araz911 thx!

[@miyamotomusashi5170]

Book recommendations are good bro! But audio is low

[@realalexnguyen]

Glad the books are helpful! I'll definitely raise the volume on the next video

[@miyamotomusashi5170]

@@realalexnguyen could you please make a video on how to get into US based big tech companies from Asian countries.

[@ashwinnema06]

Where are you working?

[@eyesopen6110]

This reliance on puzzles is ridiculous. No need for formal education or experience. Who cares if you've actually put together a production worthy app. Puzzles are the only thing that matters...

[@ceciphar]

That’s what the resume screen is for. Talk about it during your phone screen. Yea it’s just a bunch of puzzles but it’s puzzles that demonstrates fundamental computer science topics

[@eyesopen6110]

@@ceciphar Fundamentals are for new grads/students. Does a hospital ask a seasoned surgeon first year questions? Probably not...I don't want the kid surgeon. I want the one with decades of experience.

[@balapraneeth395]

Bro i kind of need help for getting an internship as a college student. Like, what do i do??

[@astrahcat1212]

It's about the people you know, attend any events, meetups, conventions etc... focused around development, get very social and trade LInkedIns with all of the people you meet.

[@parthbhatia341]

In india this is on steroids people do bare minimum of 800 questions and even do competitive programming on top of that

[@clatttheman3550]

makes up for there terrible english

[@ravibhosle8478]

Learn to use mic, or just change it

[@realalexnguyen]

How can it be better?

[@AlejandroAndraca]

@@realalexnguyen is too low and sounds like you're talking from far away