Luyện nói tiếng Anh bằng Shadowing qua video: The Skills You’ll Need to be a Senior Software Developer

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.

229 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.

Welcome to today's video.

Chào mừng các bạn đến với video ngày hôm nay.

In this video we're going to go over the skills that it takes to be a senior software developer.

Trong video này, chúng ta sẽ cùng tìm hiểu những kỹ năng cần có để trở thành một lập trình viên phần mềm cấp cao.

We will be covering what those skills are, how to present those skills in an interview,

Chúng ta sẽ cùng tìm hiểu những kỹ năng đó là gì, cách trình bày những kỹ năng đó trong buổi phỏng vấn.

and also what steps to take to move into a senior role.

Welcome to the Life at Miro channel.

Let's get started.

Hi, my name is Alyssa and I'm our technical sourcer for engineering.

Hi, my name is Elliot Monofy and I am a senior engineering manager in Enterprise.

So some of the things that I look for in an interview, basically we have about 30 minutes,

so I have to get through kind of a lot of content really quickly.

So some of the things that I'm checking for because I'm not so much deeply technical in the way that Elliot is,

is communication skills and style.

Are you clear?

Are you structured?

Do I understand kind of the journey that you're taking me on?

I know that this is really important for you too.

How do you assess like communication when you're when you're speaking with candidates?

Yeah, for communication generally we do behavioral style interviews and so

when you're doing a behavioral style interview you want the interviewee to be telling

you taking you on a journey telling you a story about the time

that they worked on a project or a time

that they dealt with the situation right and

so being able to coherently form that story

so I understand what happened how they were part of

that story where they fit into the puzzle is very important in understanding what their role is what skills they have.

What their scope is.

Exactly.

And so if there's not a fully formed story there,

it's very hard to really get what they're trying to tell you and where they were doing something, or their manager was doing it,

or somebody else on the team because they're not being very clear.

And so communication ends up being the number one thing that we're looking for in these calls.

People will say, we did, whereas it helps to be more clear when you say, I drove or I led.

I did this thing that way I have a very clear idea of what it is

that you did rather than like kind of what the team did overall.

And with that you can also mention which parts your manager did

which parts other members of the team did because you can't do everything right?

Exactly.

Especially as a senior engineer many times you'll be taking the requirements from a you know PM

or somebody else on the team and you'll be breaking those down so that other engineers, less senior engineers will pick up that work.

And if you're not doing that work, that's okay to mention, right?

You may be instead focused on things like designing the architecture of the system or some other aspects or communicating with stakeholders,

working cross -functionally.

There's so many other aspects to being a senior engineer that go way past what the other engineer's roles are.

Are there any, because you're doing the recruiter screen, right?

And I feel like in the recruiter screen you're obviously looking for clear signs

that this person hasn't made it to that senior role just yet right

so that we so that you know they they don't you know end up

that we know that it's a fit from the start right what are the signs for you

that are clear

that this person is not ready yet for a senior role well we already kind of touched on communication style

but I would say kind of the scope of the overall work

so are you what I'm looking for for senior basically is

have you implemented basically from the beginning the overall plan you need to execute the initiative

so meeting with as you said meeting with stakeholders breaking down

those requirements also after the the initiative is done are you still maintaining it

and and if you don't have those things then

that makes me think maybe not quite a senior right now

but definitely we can get there

and then generally after your call with them we go into those uh more technical interviews right

and in these technical interviews we start assessing uh especially in the system design interview

we start assessing more of the the technical skills

that we see from the candidate right their ability to adapt

to new technologies uh to do research on those technologies understand what is out there

and how they can use them to build a system that has multiple services with lots of different communication between the services,

know when which pieces of design best fit and where to make the greatest trade -offs to make resilient

systems that can have millions of customers, which Miro does.

Something I always talk about in my initial screening with candidates is just how important the system design is for Miro.

Here you touched on it, it is kind of breaking down the requirements.

How are you.. considering what some of the trade -offs are and maybe,

for example, if one of the interviewers doesn't ask you or asks you something that you may not know the answer to,

still making a decision and still sticking with it, even though right now it may not be the best thing.

Yeah, I think the big thing there, right, is that even if you don't, if you've never, let's say,

worked with every piece of technology, not everybody can.

Yeah.

But when you get that list of technical

and non -technical requirements from the interviewers in

that system design to be able to understand what it is

that are the goals and that come from those requirements and understand that, hey, when I'm picking out a cache, when I'm picking out a database,

I may not know all the options that are out there.

I may default to one that I've used before.

But if I know that the one I've used before doesn't meet the requirements, then to even say that in the interview,

hey, I would go do research for on these things.

I'm looking for a cash that is best for x y

and z and it should i don't care about that other thing

and so that you you show that you can go out there

and investigate because nobody has all the answers all the time right

and there's also some maturity there to not just throw out hey i'm gonna use this buzzword here exactly

because we'll find it out and then you won't do

so well that doesn't show the maturity of a senior engineer

and then generally after that round right we get into the the um the behavioral rounds, right?

We have two of those and that's where we start to get a little bit,

it's a little bit more of a mix of soft skills and technical, right?

And those will be a little bit more project focused interviews, though we do sprinkle in some other questions, right?

And I think the biggest item for us here on the seniority, and I think you've heard

this from us a lot feedback for the candidates is the ability to pull from a large resource of examples.

Exactly.

And having clear, personalized examples, that really, I mean, you said this in the beginning,

it really helps to wrap your head around what it is that the person did.

This also shows that this person is thinking and storytelling in a structured way.

100

Because one of the problems

101

we see is a lot of times people will use the same example multiple times in one interview or over separate interviews,

102

even though the question is widely different.

103

They just adapt an answer as much as they can.

104

And this usually shows that they just don't have the experience that we're looking for from them.

105

They have maybe one really good example and they're just trying to use that again, which is fine right and experience would come with time

106

and it comes with with working and

107

and getting to run into really challenging things

108

and each one of those comes with learnings

109

and i think learnings is the next thing i want to talk about here

110

and i think is really key for a strong engineer is

111

that strong engineers also they learn from both their successes

112

and their failures yes um and so i feel that when you're doing the interviews,

113

being able to call out areas in which you succeeded

114

or failed and what you learned from those

115

and how you have taken those learnings back into your work is really key to being a senior engineer.

116

I think this is also like a clear marker of a senior.

117

Of course you failed, but how do you kind of implement the failure

118

and take it to like turn it into a positive basically.

119

Another thing I am always looking for when I'm speaking with a senior

120

and something that's like a clear indicator to me is feedback.

121

How do you give, how do you receive feedback, how do you ingest it?

122

When you're working on a team it's really important that you're like actively soliciting feedback.

123

Okay how can I improve on this?

124

What can I do?

125

Does this work?

126

Does this not work?

127

And that is what a lot of our teams do at Miro, we find feedback really important.

128

Feedback is kind of one part of a greater ability for people to not only learn themselves,

129

but also help other people learn and grow, whether that's part of mentoring or part of even,

130

I think this falls into the same place as feedback,

131

but being able to, let's say two people are challenging each other on a single solution

132

or path forward technically or even non -technically

133

and sometimes you may find yourself convincing others

134

but sometimes you also may find yourself being convinced right and

135

and someone who's senior can cannot be stubborn

136

and can be like hey look that person's right we should go with

137

that one and or even you know the term that

138

that we use all the time disagree and commit right yeah

139

because someone who's truly senior doesn't always hold their ideas as part of themselves.

140

A lot of what is the most important.

141

in addition to the technical skills are the soft skills

142

because you need to be able to like fit on the team

143

and work in a way that basically you're not the blocker.

144

I would actually say

145

that soft skills are usually the biggest hurdle for an engineer to take to get from the normal

146

software engineer role to a senior engineer because the technical chops are something they've been working on for years.

147

But at that point, they haven't been thinking about leading other people, working across teams, working across functions, their communication skills.

148

And usually that's the one that's lacking, right?

149

And so it actually is quite challenging for them to learn those skills.

150

But I do think it is possible.

151

And I think that's the kind of the next area I wanted us to talk about

152

which is kind of how do you what are the steps

153

that an engineer can take to move into that

154

that senior role at Miro we have a pretty well -defined rubric for doing

155

that we call it the career matrix it has a set of eight individual competencies

156

and one what we call a core competency

157

and generally the the idea of this is it gives the

158

engineers something to build their IDP off of their individual development plan.

159

Generally what you would want to do as an engineer whether you're at Miro

160

or outside of Miro is you speak with other more senior engineers on your team, you speak with your manager,

161

you receive as much feedback into these development areas as to where you believe you're strong

162

and where you happen to be weak, right?

163

And we can't expect everyone to be perfected everything

164

but generally you want to hit as many of these competencies as possible yeah and so

165

when you find your your weaknesses you find

166

you create a plan as to how you want to develop in those areas yeah

167

and um the career matrix for us is a like a clear defined structure everyone has access to it

168

and so you can kind of see like what level you are at now

169

and what you can do to take yourself to the next level

170

and as much as it is on your manager and business need and stuff like that,

171

it's really on you and what are you going to do to get there?

172

And I think the best part about it is that by clearly defining it,

173

at least within Miro, we have a baseline of what it means to be senior, right?

174

There's not as much of this, you know, everyone being at different levels,

175

it's pretty calibrated across the organization is this is what we believe a senior is, these are the things that they contribute to the company,

176

these are the skills that they have, which is really great and it also makes it very easy for non -engineers to go in

177

and see what it is that you need.

178

Exactly and I know

179

that you recruiters have been using it quite a lot to understand what it is we're looking for in these roles.

180

Yeah another thing I wanted to mention and this goes kind of hand -in -hand with the matrix is impact.

181

As a senior basically the work that you're doing needs to be visible

182

and it needs to have an impact on not only your team but on customer business metrics.

183

Yeah, no, I agree with you.

184

I would say that all of the little individual competencies that we talk about are just a way to hone your skills.

185

But when someone truly becomes senior, generally here at Miro, we believe it's somebody who can take a pretty complex project,

186

break it down for potentially up to five engineers within their team to pick it up and deliver successfully at Miro.

187

And additionally, that project should have a pretty strong impact at the company, right?

188

It should be moving some of our objectives and actually making a difference.

189

And like you said, this generally brings visibility back at

190

that senior engineer because most people will know that they're the one who helped drive this project to completion, right?

191

Yeah.

192

And something I touched on earlier is not only driving the project to completion

193

but maintaining it afterwards because it's easy or I don't want to say easy

194

but anyone can kind of get a project across the line

195

but then what do you do with it after it's done how do you kind of keep it up

196

and continue to make an impact in

197

that area as you are getting more senior I did mention this a little bit at the top

198

but how do you communicate with non -technical stakeholders and

199

that is something that I'm also looking for I'm not the most technical person, but I need to be able to understand,

200

okay, what did you do?

201

How do you break it down so that someone like me can clearly understand

202

and digest what your impact has been on the org?

203

For you, what is one of the clear markers that somebody can communicate with someone non -technical?

204

Generally, if their manager doesn't have to step in.

205

No, I'm kidding around there a little bit.

206

But generally, for some of the really complex projects that we have, especially within the enterprise stream, which is the stream that I'm working in,

207

a lot of times

208

you may have to get involved with other teams like even the legal team at the company

209

or the security team or some of these other teams

210

that may not be as as technical or you're speaking to the you know

211

CPO or COO or some other role at the company and

212

when you're speaking to people in these roles they don't understand the technical implications of the things

213

that you're mentioning right yeah and And we would prefer for a senior engineer,

214

and we expect for a senior engineer to not have to pull anyone else into that conversation, including their manager.

215

They should be able to hold that conversation pretty easily on their own

216

and break down those very technical challenges into something that's digestible and the other person can understand.

217

So the final topic that we were hoping to speak with you today is picking between the individual contributor track,

218

which is more like a senior software engineer, or the management track, which is an engineering manager.

219

Once you reach this fork in the road, especially here at Miro, you have to start understanding which skills you're looking to hone.

220

As a senior engineer, you need to continue focusing on those technical skills

221

and start asking your manager for larger and more complex projects

222

that are potentially going to have an even larger impact on the organization as a whole.

223

If you instead try to speak to your manager about going into the management role,

224

this is where you need to start honing your kind of project management skills, your people management skills, delivery,

225

some of the other skills that maybe you haven't been focusing on over the previous years in your career.

226

If you want to hear more about this, we actually have another video that we'll be posting, and this will dive deeper into this topic.

227

We covered quite a lot of content today.

228

Are there any skills that we missed?

229

If so, please comment below.

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 ý

129 câu

How to Become a Great Software Developer — Best Advice from Top-Notch Engineers

Business EnglishInterview EnglishUniversity Students

51 câu

Configure Your Coding Agent for Salesforce Development with Salesforce Skills and Salesforce DX MCP

Business EnglishUniversity StudentsWorking Adults

14 câu

2025 DevOps, SRE, Cloud Engineer Interview Questions: Ace Your Interview with This Guide

Business EnglishInterview EnglishUniversity Students

315 câu

how AI broke the SWE Career Ladder

Business EnglishInterview EnglishUniversity Students

210 câu

What Software Architecture Should Look Like • Dave Farley • GOTO 2022

Business EnglishUniversity StudentsWorking Adults

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 “The Skills You’ll Need to be a Senior Software Developer”. Những từ được nhắc lại nhiều nhất trong bài: senior, engineer, skills, technical, interview. Video này có 153 câu và 2924 từ để luyện shadowing. Phần lời nói dài 17:18. Người nói nói với tốc độ tự nhiên, khoảng 169 từ mỗi phút, gần với hội thoại hằng ngày. 89% số từ nằm trong 3.000 từ tiếng Anh thông dụng nhất, nên từ vựng dễ theo. 45 trong 153 câu là câu hỏi, nên bài này hợp để luyện ngữ điệu câu hỏi và cách trả lời ngắ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
feedback danh từ	/ˈfiːdˌbæk/	sự phản hồi
requirement danh từ	/ɹɪˈkwaɪɹmənt/	yêu cầu
topic danh từ	/ˈtɑpɪk/	chủ đề
enterprise danh từ	/ˈɛntəˌpɹaɪz/	xí nghiệp
convince động từ	/kənˈvɪns/	thuyết phục
implement động từ	/ˈɪmpləmənt/	thực hiện, chấp hành
recruit động từ	/ɹɪˈkɹut/	tuyển dụng
cache danh từ	/kæʃ/	bộ nhớ đệm, vùng nhớ đệm
afterwards trạng từ	/ˈæf.tɚ.wɚdz/	sau này, sau đó
architecture danh từ	/ˈɑː.kɪˌtɛk.t͡ʃə/	kiến trúc
resource danh từ	/ɹɪˈzɔːs/	tài nguyên
visible tính từ	/ˈvɪzɪb(ə)l/	nhìn thấy được, khả kiến
objective danh từ	/ɒbˈd͡ʒɛk.tɪv/	mục tiêu, mục đích
contribute động từ	/kənˈtɹɪb.jut/	đóng góp
database danh từ	/ˈdeɪtəˌbeɪs/	cơ sở dữ liệu, CSDL

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

Từ	Nghĩa
break down động từ	hỏng, hỏng hóc
go out động từ	ra, chết
pick up động từ	nhặt, lượm

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:

Do I understand the journey that you're taking me on?
Because you're doing the recruiter screen, right?
How do you receive feedback?
How do you ingest it?
Are there any skills that we missed?

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	they've been working · haven't been thinking · have been using
Mệnh đề quan hệ who / which + mệnh đề — thêm thông tin về người hoặc vật	again, which is · have, which is · somebody who can
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	hasn't made · have you implemented · you've heard

Phát âm cần chú ý

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

Âm “sh” và “zh”: potentially /pəˈtɛnʃ(ə)li/, initiative /ɪˈnɪʃ.ə.tɪv/, completion /kəmˈpliː.ʃən/, cache /kæʃ/, implication /ˌɪmpləˈkeɪʃən/
Từ dài — đặt trọng âm cho đúng: communicate /kəˈmjuːnɪkeɪt/, behavioral /bɪˈheɪvjəɹəl/, potentially /pəˈtɛnʃ(ə)li/, initiative /ɪˈnɪʃ.ə.tɪv/, technically /ˈtɛk.nɪˌkəl.i/

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: requirement /ɹɪˈkwaɪɹmənt/, matrix /ˈmeɪ.tɹɪks/, aspect /ˈæspɛkt/, convince /kənˈvɪns/, implement /ˈɪmpləmənt/
Âm /tʃ/, /dʒ/ và /ʒ/ — tiếng Việt không có, đừng đọc thành “ch” hay “gi”: architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, objective /ɒbˈd͡ʒɛk.tɪv/, chop /t͡ʃɑp/, digest /daɪˈd͡ʒɛst/, digestible /daɪˈdʒɛstəbəɫ/
Âm /æ/ — mở miệng rộng hơn âm “e”: feedback /ˈfiːdˌbæk/, aspect /ˈæspɛkt/, adapt /əˈdæpt/, cache /kæʃ/, afterwards /ˈæf.tɚ.wɚdz/

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ư feedback, requirement, topic.

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: The Skills You’ll Need to be a Senior Software Developer

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

Tải Ứng Dụng

How to Become a Great Software Developer — Best Advice from Top-Notch Engineers

Configure Your Coding Agent for Salesforce Development with Salesforce Skills and Salesforce DX MCP

How demand for workforce skills will change with automation: A minute with MGI

My Senior UX Design Interview Experience | tips, questions, prep, & more!

[C1] Learn Soft Skills for Workplace Success | Business English Practice

The Technical, Business and UX Skills Every Product Manager Needs

Top 1% Career Strategy: How to Get Hired in the AI Era

I Wrapped an API Into a Real SaaS (full build / step-by-step)

Mastering iOS Development: Mock Interview with Ramiro Neto

2025 DevOps, SRE, Cloud Engineer Interview Questions: Ace Your Interview with This Guide

how AI broke the SWE Career Ladder

What Software Architecture Should Look Like • Dave Farley • GOTO 2022

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

Từ vựng quan trọng trong video

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

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

Ngữ pháp trong video

Phát âm cần chú ý

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

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