Shadowing Practice: The unfair way I got good at Leetcode - Learn English Speaking with Video

Creating lesson...
1
Lead code is hard, not only because it's hard to be good enough to solve questions, to land a job at high paying companies,
2
but also because it's hard to know how and exactly where to start when there is so much information available.
3
When I just got started, I couldn't even solve an easy question well enough to pass an interview.
4
But I had no choice, so I invested lots of time, I made lots of mistakes, but also learned a lot.
5
reached out to me on LinkedIn to pass their interviews and receive offers, I realized that back then I wasn't bad.
6
I was just getting started.
7
Especially in the beginning, you should put more time into learning solutions rather than solving questions,
8
so that you start developing intuition within that topic more quickly and then solve questions faster.
9
So for example, if I'm now starting to learn binary trees, instead of just choosing a list and then trying to solve question by question,
10
I would make two lists of easy and medium tree questions, starting with the common ones, and then I would separate each list again into two.
11
and instead of trying to solve the question, I will go to the solution and learn the common solution well.
12
After doing that, for all of the questions in that list, I will go to the second list and I will start practicing.
13
When I land on a question that I could not come up with an answer for, it can be a one -off or an outlier,
14
but when just starting, it usually means that it's a new pattern I was not exposed to, and I will learn that solution and move forward rather than wasting
15
But give it a try and see
16
if it also helps you get better at lead code much more efficiently which is what matters
17
Solving a question during an interview, at least for me, feels more like acting on a stage
18
and the scene is that you solve a question rather than actually solving a question.
19
The reason is, is that you don't get to have even 5 minutes to think quietly and sketch some ideas.
20
You need to entertain the interviewer.
21
Well, not entertain per se, but you need to keep them engaged.
22
Share your thought process and walk them through what you're doing.
23
Your attention is split, which makes it really difficult to think.
24
When I'm asked in the first few minutes, I either know what the answer is that thanks to something I've solved
25
that is at least similar or don't and in
26
that case I just try to get away with asking the interviewer to have time to think
27
and throw some ideas as they come until I land on something
28
that might lead to a solution
29
and usually Interviews will also nudge you towards the right direction
30
when you voice it So once you have practiced for long enough
31
so that you're able to solve medium level questions if you stop there need to practice on websites like Pramp,
32
and start solving these questions when your attention is more split, compared to when you solve questions on your own, and get good at solving technical questions in an interview style.
33
Although, over time, the more you interview, you will naturally get better at this.
34
you It's not about quantity alone nor quality alone.
35
You need both.
36
Quality means that you follow a roadmap
37
that exposes you to the most common questions and topics to practice so that you have a sound starting point.
38
This way you can slowly work your way to expand the spectrum of questions that you can intuitively recognize.
39
for the types of questions that you will see during the interviews.
40
For example, I've never been given a question on dynamic programming, whether I interviewed at FANG, a popular startup or a mid -tier paying company.
41
But I've been given a lot of questions on arrays similar to the common ones but somewhere on trees, backtracking and priority cues.
42
Something additional I've noticed during the 15 + interviews I've done is
43
that the more the question you're asked is higher into this pyramid, the more similar it is to common questions in that topic.
44
So when I was asked the question on trees, it was virtually identical to a common tree question I've thoroughly solved before
45
which helped me to easily solve the question during the interview.
46
On the other hand, when the question was seen before.
47
Even though it was solved using the same pattern from common questions from before, it required more adjustments
48
which is why sometimes being asked about less common topics can make things easier for you
49
when you had practiced several such questions.
50
Make sure that you're not solving questions for the sake of solving questions.
51
I know it sounds strange but
52
when I practiced initially I got caught up with all the community trying to learn the best
53
or fastest solution and so on but I was wasting lots of time.
54
When you interview, the solution you need is the solution that gets you to pass the interview.
55
You do it consistently and that's how you land offers.
56
This rarely means having the shortest solution or an exotic one
57
than a reasonable common solution that is usually suggested to that question.
58
When you're interviewing, there will be specific posts and lists, sometimes even for smaller companies, so research and practice these questions that others have posted.
59
I've seen more than once a question I was asked
60
which was identical to a question someone else posted on a website like Litcode or Glassdoor.
61
With some companies, you will have a round with the hiring manager.
62
That will sometimes be technical but often will also include some of the high -level related does.
63
When you know you have a round with the hiring manager, do your due diligence about the company and their engineering work,
64
think about their challenges and things that they had to overcome and weave that in the conversation.
65
Each time I had a round with the hiring manager, I could see how doing this at some point made me vibe with the hiring manager
66
and I could see how so long I don't do awfully on the technical questions, I will have the offer.
67
Finally, get good.
68
It took me well over a year of practicing each day
69
with no exceptions to get to a point where I interview pretty well and can pass interviews.
70
When you start, it's a marathon.
71
You will most likely also need to practice for a very long time, at least if you're like me, but afterwards, it will be more like a sprint where thanks to all of that practice,
72
you can recall and can quickly get in an interviewing shape when you need to.
73
With that said, thank you so much for watching and I hope to see you in the next one.
74
Bye.
75
you

Context & Background

In the video titled "The unfair way I got good at Leetcode," the speaker shares their personal journey in tackling the challenges of coding interviews, particularly with Leetcode. They express the difficulties of mastering coding problems amidst a sea of available resources and share insights on effective study practices and interview strategies. Learning English pronunciation and communication skills are essential elements of this journey, as articulating thought processes clearly is crucial during technical interviews.

Top 5 Phrases for Daily Communication

  • "Can I take a moment to think?" - A polite way to request some time to gather your thoughts before answering.
  • "Let me walk you through my thought process." - This phrase showcases your ability to communicate clearly and engage the interviewer.
  • "I want to make sure I've considered all possible solutions." - Demonstrating thoroughness and critical thinking can leave a positive impression.
  • "This problem reminds me of...” - Use this to connect new problems to previously solved ones, highlighting your experience.
  • "Could you provide more context?" - Asking for clarification can ensure you fully understand the question before attempting a solution.

Step-by-step Shadowing Guide

To effectively utilize the shadowing technique while watching the video, follow this structured approach to enhance your English pronunciation and speaking fluency:

  1. Watch and Listen: Start by watching the video without any pauses. Pay attention to how the speaker articulates their thoughts, especially when discussing complex ideas.
  2. Repeat Aloud: Play the video again, but this time, pause frequently to repeat phrases and sentences. Focus on mimicking the speaker's pronunciation and intonation.
  3. Analyze Key Phrases: Identify the phrases listed above and practice them in different contexts. Incorporate them into your own spoken responses during conversation.
  4. Record Yourself: Use a recording device to capture your repetition of the phrases. Listen back to identify areas for improvement in your pronunciation.
  5. Integrate Practice: Engage in IELTS speaking practice with a partner using similar technical scenarios. This will help you apply the phrases in a conversational setting and boost your confidence.

By embracing the shadowspeaks approach, you can significantly improve both your technical speaking abilities and your overall English skills, making you better prepared for interviews and daily communication.

What is the Shadowing Technique?

Shadowing is a science-backed language learning technique originally developed for professional interpreter training and popularized by polyglot Dr. Alexander Arguelles. The method is simple but powerful: you listen to native English audio and immediately repeat it out loud — like a shadow following the speaker with just a 1–2 second delay. Unlike passive listening or grammar drills, shadowing forces your brain and mouth muscles to simultaneously process and reproduce real speech patterns. Research shows it significantly improves pronunciation accuracy, intonation, rhythm, connected speech, listening comprehension, and speaking fluency — making it one of the most effective methods for IELTS Speaking preparation and real-world English communication.

Shadowing technique: read the full step-by-step guide →