Luyện nói tiếng Anh bằng Shadowing qua video: 5 Coding Interview Tips From A Senior Engineer

Chọn chế độ luyện tập

Mỗi chế độ mở một phòng luyện tập toàn màn hình.

207 câu

Nếu các câu quá ngắn hoặc quá dài, hãy bấm Edit để chỉnh sửa.

What's up, everybody?

Travis here from Travis .media.

Today, I want to look at an article

that I think will be helpful for anyone planning their first or even fifth interview for a programming job.

I'm always fascinated in hearing what people who conduct these interviews on a regular basis expect from those interviewing

and what kind of mistakes people keep making so that you

and I can be sure not to make these same mistakes and stand out better.

So in this video, I'll give you five lessons

that you can take away from this information and better equip yourself for that next interview.

Let's get started.

So I found this really good

Medium article, which can be really rare for Medium nowadays.

And it's targeted towards senior engineers specifically.

And it's actually called, This is Why I Didn't Accept You as a Senior Software Engineer.

But I think it applies all the way down the chain to mid and even junior level engineers.

Even if this is your first interview.

Because if you're exhibiting behavior like a senior in your junior interview, it's a good thing.

So let's take a look at this article.

So here's what the author says.

I've been interviewing engineers for different companies for the last few years.

But lately I've been turning down candidates like never before.

I'm still using the same questions.

Nothing's changed The problem is

that people have no idea about what it means to be a senior engineer and these professionals are scarcer than ever

Okay, that's good.

Let's find out the skills

We need to work on to make us some of those scarce people and that leads us to lesson one General knowledge.

I call it general knowledge.

He calls it development methodologies

So let me read this development methodologies or organizational methods that are meant to make teams effective

These could be boring for us, but it's expected of you to have expertise in them.

During my years of work, I have developed a rejection of non -agile development methodologies.

And more than that, I think that Scrum is not agile enough.

Its exhaustive use ends up helping the ego of the project managers more than the programmers.

I agree, though I like Scrum, but I like this meme too.

So here's the point.

When I do an interview, I look for that capacity of criticism in developers, knowing Scrum is not enough.

But you also have to know its disadvantages and propose solutions to them.

So the lesson here is that you shouldn't be agreeing to everything.

We go into the interview and we're like, yeah, yeah, I like that.

Yeah, I like this.

But you should be forming opinions about things with reasons to back them up.

Not in a quarrelsome way, but no one really wants another developer that just does whatever he

or she is told without sometimes disagreeing or offering better or alternative solutions.

As a developer, programming is only part of the job.

Another very important part is leaning in with your expertise on the task at hand.

Maybe the feature that the project manager

or the client wants is not a good idea or will not go well with how things are currently built.

You're needed to speak up, share your concern, and offer a better alternative.

In the case of this interviewer, he's looking for someone that can offer their opinions of Scrum regardless if you like it or not.

You can actually offer your opinion about it

and not just agree to whatever he says about it in the hopes

that they give you the job because you guys are the same.

The lesson here is to read up on things.

Form opinions yourself about industry -wide tools and development methodologies and be able to speak your mind about it if asked.

The point here is not that you need to learn Scrum for this guy.

The point is that if you're asked about Scrum, you have an opinion about it.

We want to carry on a conversation with the interviewer and not just nod our heads at everything said.

And I'll close lesson one with this quote here.

I thought it was good.

General knowledge will help you form better opinions and show you're willing to learn outside your field.

General knowledge is important.

Read up, form your opinions.

Lesson two, how well do you know your language?

He labels this section software design principles.

The reason the rockstar engineer is so much more valuable than his counterparts isn't unique to programming.

The great software engineer is incredibly creative and can see conceptual patterns that others can't.

After finishing every interview, this is important.

Listen to what this guy is saying.

After finishing every interview, when writing feedback for the candidate, I swear I could copy and paste the same response every time.

And it's this.

I suggest you read more about Python design patterns.

A good resource can be this guide.

We'll get back to that guide in a minute.

It's so easy to filter candidates with design principles.

Only in really strange cases, I've found people with an answer to all of these questions.

And he goes on to say that, hey, these design patterns are challenging.

It's not always easy to apply and recall them.

But forcing yourself to do these checks while you're programming will put you a step ahead.

Why do we use length array in Python while in other language we can use array dot length?

Is there any optimization behind it? how much do you know your language

so this lesson is twofold number one learn about your language design patterns

and two know your language well that's why when i say

if you're starting out programming learn one language

and learn it well like javascript you could do everything with it

or python that's a popular one let's say that you learn python first

and you decide to go all in with it learn

it well learn its quirks find a book like one of those o'reilly books

that goes in depth with the language

and be able to discuss things like why python is using

a length function instead of a length method as this author mentions sure

this may be more catered to senior interviews

but it will help you stand out better as a junior

if you're at least familiar with the deeper parts of a language such

that you can carry on a conversation about it you don't

have to be an expert just be able to carry on

the conversation think about books like javascript the good parts a book that's old

but really helps you see what's going on under the hood and learn about the quirks of the language.

He says here, reading a book about the language you use is absolutely necessary when you're growing.

100

Any senior engineering interview will include advanced questions

101

that you will only know by reading because books always go deeper than online courses.

102

So do the online courses, learn the stuff, and then go deeper.

103

Learn the language, build projects, get familiar, learn algorithms, but also here and there,

104

read a new chapter or two that takes you a little bit deeper.

105

Next, try to learn some design patterns for that language,

106

or really design patterns in general with programming yes even as a junior as you build your apps

107

if it's python then do check out this link

108

that he provides it's a really really good resource it's at python -patterns .guide

109

and here you have a handful of principles and patterns

110

that you can learn

111

if you're using the python language as the author suggests

112

we're actually going to be working through some of these in the travis media community

113

when it reopens in january i closed it for december

114

because i'm doing a complete makeover

115

and overhaul of the community it's going to be awesome

116

when it relaunches if you want to be notified when

117

that reopens just go to travis .media slash community put your email in this form here

118

and i'll email you when it reopens and work it into your hobby projects

119

or your portfolio projects you of course don't have to memorize all of these

120

and be able to implement them all but

121

if you're at least familiar with them

122

and can implement a few that's enough to allow you into the conversation

123

and thus have an opinion which is part of lesson one

124

that we just talked about lesson three is check your attitude look at this

125

Working with a vain person is immensely difficult.

126

They make you feel bad all of the time and create bad vibes in the team.

127

In the long term, the damage that such a person can do, the company can be very expensive.

128

This has been an experience for any and every developer out there probably, working with a toxic developer.

129

Companies are looking for great humans when they're offering humongous salaries, and part of that is being a good person.

130

When doing an interview, we're not only evaluating the candidate's knowledge, but also his or her attitude.

131

In a specific process I did months ago, the company asked us specifically to look for good and honest persons more than great programmers.

132

He was told to look for good and honest people more than great, great programmers.

133

I can attest to companies doing this personally.

134

A job I had in the past as a site reliability engineer did just that.

135

The CTO landed a new contract.

136

They needed like 30 people, local people.

137

We had to go into the office, but he went on LinkedIn.

138

He found a bunch of people in my city, me being one of them.

139

He reached out, called me on the phone, told me the situation, and told me the company's philosophy,

140

which was we look for good people who can easily learn the stuff.

141

He said a lot of companies, they want the best programmers.

142

They don't care about the people themselves or their personalities.

143

They just want the best programmers.

144

This company flipped all of that and is looking for good people who love to learn, are easily teachable, and don't have attitudes.

145

So we talked.

146

Things went really well.

147

I still had the coding exam, but I got the job despite not really being qualified as an SRE.

148

I was a developer.

149

But they were looking for good people who were eager to learn and weren't toxic to be around.

150

A bad attitude or lying could imply an immediate elimination from a selection process.

151

Lying, too.

152

I always recommend the book, How to Win Friends and Influence People.

153

It's one of those books that everybody should read to have better relationships in life.

154

That happens to be a book we're just finishing up in the Travis Media community.

155

It's a good one.

156

You should read it.

157

Before we get to lesson four, quick intermission.

158

What should a junior mid -read to become a senior?

159

Here are some fantastic resources to grow as a senior developer.

160

I'll put links to these below because this article is a member -only article.

161

Some of you may not be members, but they're really good.

162

You could use AI to simulate an interview.

163

Here's some websites a programmer should visit.

164

But these community -driven roadmaps are really neat.

165

Just wanted to mention it real quick.

166

If you need a roadmap for learning some technology, let's say you want to learn JavaScript, just go down here, click JavaScript Roadmap.

167

Takes you to a site called roadmap .sh slash JavaScript.

168

And you just start from the beginning.

169

So introduction to JavaScript.

170

What is JavaScript?

171

History of JavaScript.

172

Once you're done with that, you move on to all about variables.

173

You learn about variable declarations, hoisting, and you just continue to go down the line until you know everything about the language.

174

Use this tool to go deeper with the language, as we mentioned in Lesson 2.

175

Lesson 4 is, what about my coding skills?

176

So far, we've mainly been talking about communication skills, knowledge skills, being able to carry on a technical conversation.

177

We often think we just need to know all the algorithms and they'll love us, but that isn't the case.

178

It's both, and often we tip the scales more on the technical stuff, for lack of the communication stuff.

179

But we do need the coding skills.

180

So this author recommends LeetCode.

181

I think everybody's recommending LeetCode Premium.

182

I bought LeetCode Premium some months ago.

183

It was a great decision to land my current job.

184

On your way, you'll discover interesting math, curiosities, patterns, and optimizations from other users.

185

Not an affiliate.

186

I have no incentive to tell you this.

187

That's just what he recommends.

188

Simulating an interview from a big company can also be useful to understand how they're structured.

189

Lesson five, the hard but understandable truth.

190

This is very important you simply may not be the right profile for the company

191

it's not you it's me right no seriously quit beating yourself up

192

because you sucked everyone sucks at the coding interview

193

i actually have a really old video that's a bit cringy about

194

when i really bombed an interview in the past

195

i'll put a link to it above even after reading a lot of material

196

Practicing every day and having a lot of experience you could be rejected

197

because you're just not the right profile for the company

198

So lesson five is that you may do great at the interview

199

You may be expecting to land the job and then you get the bad news

200

But you have to remember that it may just be that you weren't a good fit for that role

201

Nothing to do with your skills nothing to do with you personally

202

But that company has a profile certain profile they want to fill

203

and maybe you just weren't that the only things you can expect from yourself

204

Are resilience and persistence those are not only the skills

205

that will secure your job in the future but they also are the main skills we expect from a senior engineer.

206

If you found this video helpful, give it a thumbs up, consider subscribing to the channel, and I'll see you in the next video.

207

Thanks for watching.

Tải Ứng Dụng

Mọi thứ bạn cần để nói trôi chảy

Chấm điểm AIChấm từng câu nói

Luyện IPAThành thạo mọi âm

Từ vựngMở rộng vốn từ

Game Từ vựngHọc qua chơi

Quét QR

Download on theApp Store Get it onGoogle Play

FOR YOU

Video gợi ý

261 câu

How I use AI as a senior software engineer and 5 principles of AI explained in 10 minutes

Daily ConversationWorking Adults

43 câu

Genuine advice for a line manager

Business EnglishDaily ConversationWorking Adults

26 câu

Từ vựng và ghi chú luyện nói cho bài học này

Bài luyện nói này dựa trên video “5 Coding Interview Tips From A Senior Engineer”. Những từ được nhắc lại nhiều nhất trong bài: learn, interview, language, lesson. Video này có 207 câu và 2403 từ để luyện shadowing. Phần lời nói dài 10:42. Người nói nói nhanh, khoảng 225 từ mỗi phút, nên sẽ có nhiều chỗ nối âm và nuốt âm. 85% số từ nằm trong 3.000 từ tiếng Anh thông dụng nhất; phần còn lại nên xem trước khi luyện.

Từ vựng quan trọng trong video

15 từ đáng học trong video, kèm phiên âm và nghĩa:

Từ	Phiên âm	Nghĩa
lesson danh từ	/ˈlɛs.ən/	bài, bài học
developer danh từ	/dɪˈvɛləpɚ/	nhà phát triển
programmer danh từ	/ˈpɹoʊɡɹæmɚ/	lập trình viên
principle danh từ	/ˈpɹɪn.sɪ.pəl/	nguyên lí, nguyên tắc
helpful tính từ	/ˈhɛlp.fl̩/	hay giúp đỡ
suck động từ	/sʌk/	bú
resource danh từ	/ɹɪˈzɔːs/	tài nguyên
toxic tính từ	/ˈtɒk.sɪk/	độc
implement động từ	/ˈɪmpləmənt/	thực hiện, chấp hành
algorithm danh từ	/ˈælɡəɹɪðm̩/	thuật toán
math danh từ	/mæθ/	toán, toán học
label danh từ	/ˈleɪ.bəl/	nhãn
discover động từ	/dɪˈskʌvə/	phát hiện, phát kiến
incredibly trạng từ	/ɪŋˈkɹɛdɪbli/	khó tin nổi
salary danh từ	/ˈsæləɹi/	lương

Cụm động từ bạn sẽ nghe

Từ	Nghĩa
check out động từ	tính tiền, trả phòng

Những câu đáng luyện lại

Các câu ngắn, trọn ý trong video mà bạn có thể dùng lại khi giao tiếp hằng ngày:

I'm still using the same questions.
Lesson two, how well do you know your language?
We'll get back to that guide in a minute.

Ngữ pháp trong video

Những cấu trúc người nói dùng nhiều nhất, kèm đúng cụm từ trong video:

Cấu trúc	Trong video
Thì hiện tại hoàn thành tiếp diễn have/has been + -ing — việc bắt đầu từ trước và vẫn đang tiếp tục	I've been interviewing · I've been turning · we've mainly been talking
Mệnh đề quan hệ who / which + mệnh đề — thêm thông tin về người hoặc vật	people who conduct · article, which can · someone that can
Câu bị động be + quá khứ phân từ — nhấn vào việc xảy ra, không phải người làm	are meant · is told · are currently built
Thì hiện tại hoàn thành have/has + quá khứ phân từ — việc đã xảy ra nhưng còn liên quan đến hiện tại	have developed · I've found · has been

Phát âm cần chú ý

Người nói dùng 47 dạng rút gọn, ví dụ you're, I'll, don't. Hãy nói theo dạng ngắn đúng như bạn nghe.

Âm “th”: methodology /ˌmɛθ.əˈdɑ.lə.d͡ʒi/, algorithm /ˈælɡəɹɪðm̩/, math /mæθ/, thumb /ˈθʌm/
Âm “sh” và “zh”: optimization /ˌɑptəmaɪˈzeɪʃən/, declaration /ˌdɛk.ləˈɹeɪ.ʃən/, elimination /ɪlɪmɪˈneɪʃ(ə)n/, rejection /ɹɪˈd͡ʒɛkʃən/, organizational /ˌɔː(ɹ)ɡənɪˈzeɪʃənəl/
Từ dài — đặt trọng âm cho đúng: developer /dɪˈvɛləpɚ/, methodology /ˌmɛθ.əˈdɑ.lə.d͡ʒi/, optimization /ˌɑptəmaɪˈzeɪʃən/, incredibly /ɪŋˈkɹɛdɪbli/, portfolio /pɔːtˈfəʊ.liˌəʊ/

Những âm người Việt thường gặp khó:

Cụm phụ âm cuối — đọc đủ từng âm, đừng nuốt âm cuối: implement /ˈɪmpləmənt/, counterpart /ˈkaʊntɚˌpɑɹt/, resilience /ɹɪˈzɪl.ɪ.əns/, persistence /pəˈsɪst(ə)ns/, attest /əˈtɛst/
Âm /tʃ/, /dʒ/ và /ʒ/ — tiếng Việt không có, đừng đọc thành “ch” hay “gi”: methodology /ˌmɛθ.əˈdɑ.lə.d͡ʒi/, rejection /ɹɪˈd͡ʒɛkʃən/, disadvantage /ˌdɪsədˈvæntɪd͡ʒ/, agile /ˈæd͡ʒ.aɪl/, cringey /ˈkɹɪnd͡ʒi/
Âm /æ/ — mở miệng rộng hơn âm “e”: programmer /ˈpɹoʊɡɹæmɚ/, variable [ˈvæɹ.i.ə.bl̩], algorithm /ˈælɡəɹɪðm̩/, math /mæθ/, salary /ˈsæləɹi/

Cách luyện với video này

Nghe hết video một lần, chưa cần nói, và ghi lại những từ bạn chưa biết.
Bắt đầu ở tốc độ 0,75×, nói đuổi từng câu, rồi quay lại tốc độ bình thường khi đã quen.
Ghi âm giọng mình rồi so với bản gốc, chú ý các từ như lesson, developer, programmer.

Phương Pháp Shadowing Là Gì?

Shadowing là kỹ thuật học ngôn ngữ có cơ sở khoa học, ban đầu được phát triển cho chương trình đào tạo phiên dịch viên chuyên nghiệp và được phổ biến rộng rãi bởi nhà đa ngôn ngữ học Dr. Alexander Arguelles. Nguyên lý cốt lõi đơn giản nhưng cực kỳ hiệu quả: bạn nghe tiếng Anh của người bản xứ và lặp lại to ngay lập tức — như một "cái bóng" (shadow) đuổi theo người nói với độ trễ chỉ 1–2 giây. Khác với luyện ngữ pháp hay học từ vựng bị động, Shadowing buộc não bộ và cơ miệng phải đồng thời xử lý và tái tạo ngôn ngữ thực tế. Các nghiên cứu khoa học xác nhận phương pháp này cải thiện đáng kể phát âm, ngữ điệu, nhịp điệu, nối âm, kỹ năng nghe và độ lưu loát khi nói — đặc biệt hiệu quả cho người luyện IELTS Speaking và muốn giao tiếp tiếng Anh tự nhiên như người bản ngữ.

Phương pháp shadowing: đọc hướng dẫn từng bước đầy đủ →

Luyện nói tiếng Anh bằng Shadowing qua video: 5 Coding Interview Tips From A Senior Engineer

Chọn chế độ luyện tập

Tải Ứng Dụng

Video gợi ý

I don't like Programming

Top 25 Manufacturing Engineer Interview Questions and Answers for 2026

The Skills You’ll Need to be a Senior Software Developer

Google Interview Tips That Actually Get You Hired

Top 5 Communication Skills Lessons

How to ACTUALLY Get a DevOps Job in 2026

How To Effectively Leverage Skip Level 1 1s

5 Strategies Of A Successful Project Engineer

The Best Vibe Coders Aren't Engineers