シャドーイング練習: Crush Your Next Job Interview in English - 動画で英語スピーキングを学ぶ

練習モードを選ぶ

各モードは全画面の練習ルームで開きます。

524 文

文が短すぎたり長すぎる場合は、Editをタップして調整してください。

Hey, what's up?

Stephanie, the English coach here from EnglishFullTime .com.

Today, I have my brother

Eric with me.

We are going to do a conversation in English at normal, regular, everyday speed for you to practice your listening skills.

And we're also going to talk about something really interesting because he recently conducted some interviews with some guys from India.

And as soon as he started telling me this story a while back, I was like, wait, save this.

I want you to share it on my YouTube channel.

So he actually hasn't even told me the full story yet.

So anyways, we're not going to slow down, try to keep up.

This is full immersion.

Okay.

So with that said, go ahead and introduce yourself.

Hi, everyone.

I'm Eric.

I am a IT and cybersecurity specialist.

So I help companies get their internal IT and cybersecurity operations up to speed.

Wow, you shortened to that.

I did.

We don't need to elaborate further.

We practiced and he actually had this really long detailed, like my eyes were glazing over.

And I was like, I think we lost everybody.

Let's try again.

It's like, you did good, Eric.

You did good.

IT and cybersecurity is what I do.

You want to know more?

That's another conversation, I suppose.

Yeah, he's smart.

There we go.

Enough said.

No, okay.

So let's back up a little bit let's talk about your job, your position right now, because I remember when you first got into this,

you were like a guy who was doing tickets.

Yeah, I was a SOC analyst, a Security Operations Center analyst.

So, you know, like a complaint would come in, right?

A complaint, sometimes a complaint.

We call them tickets.

Yeah, well, every ticket you told me about was like a complaint.

Oh, because those were the interesting story ones, but most of what I did was very rudimentary.

Okay, so like customer support?

It was specifically security.

So most of the tickets we were getting were either people submitting, hey, I think this email is suspicious.

Can you look into it for me?

Or it was one of our tools sending it like, hey, this alert triggered and you might want to look into,

you know, X, Y, and Z on the network.

And we would conduct our investigations and documentation.

Okay, so before you were a lowly ticket boy.

I think the name of the position was like IT security professional level one.

Okay.

Lowly ticket boy.

Okay.

What I mean is entry level.

What I'm trying to do is make a comparison.

You're not there anymore.

Yeah, I understand.

Okay.

So now you are a CISO something or other.

A chief information security officer, which means that I'm in charge of the entire security program at the companies that I work for.

Yeah.

So now you have people under you and those are the ticket boys.

I'm just kidding.

I should stop calling them that.

I'm just kidding.

Okay.

I'm just kidding.

Okay.

So now you have other people.

Maybe I should make this a little more professional.

What do you think?

It's fine with me.

I'll have you know that I have girls on my team too.

Okay.

No, I know.

I know.

Okay.

So anyways, anyways.

So now you have people working under you.

You have a whole team.

You are actually doing the security for multiple companies.

So recently you did some interviews and now tell me about that because you came to me and you're like,

oh my gosh, Steph, you will not believe this.

Like these people were using AI.

Their interviews were terrible.

So what happened?

Yes.

It got to a point where one person is not enough to build a cybersecurity program at a company.

You get to a company large enough.

For small companies, you can do it with one person, but once you're at like 300 or 400,

500 people, you need a team to be doing this.

You either need to get a team outside or you need to build an in -house team.

So I got the approval and the budget to build an in -house team.

And so then I set out looking for what I needed.

So I needed somebody for compliance.

I needed a security operations lead.

I needed a couple of people to do the IT operations because we do both IT and security operations on my team.

And so after I got the approval in the budget, I needed to design the interviews, first of all, for what I was looking for,

design the job descriptions, the interview format, and then go out and conduct the interviews.

100

So I wrote the job descriptions based on our company's needs.

101

So for compliance, we needed somebody that could lead us through different compliance certifications like SOC 2, ISO 27001.

102

Those are just security frameworks that are used for compliance benchmarks for companies when they want to be compliant.

103

So basically, whoever applied for the job needed to have knowledge of those things and be able to do those things.

104

Right.

105

But I wasn't just looking for knowledge of those things because knowledge of the specific frameworks,

106

as those are called, you could learn it in a couple of weeks.

107

And so I knew this going into the interviews.

108

And this is my own personal philosophy on work, is that the technicals can actually be learned relatively quickly any particular tool or coding language,

109

once you know how to code, right?

110

And now everyone codes with AI, but you know, back in the day when we used to code in languages by hand.

111

Two years ago.

112

In the stone ages, basically.

113

Translating from one language to another language was not that difficult.

114

Not that much of it.

115

So once you learn one language, going from one language to another language, similar to learning languages the way that you do,

116

you know, once you know Spanish, Yeah.

117

Any language in the Spanish family, the romance languages like Italian, French.

118

Yeah.

119

Learning your first language or not your first, but your second language, I would say, is the hardest.

120

And then after that, you're like, oh, now I know how to learn languages and it gets easier.

121

Yeah, exactly.

122

So we have the same sort of thing in in IT.

123

So I had to design these interviews in such a way that captured not just the technicals, but judgment.

124

And that's kind of a tricky thing to do.

125

Like, how do you interview someone to see what judgment calls they would make and what decisions they would make, their problem -solving abilities?

126

Exactly.

127

Yeah.

128

So in what I do, nothing is scripted, much like this interview.

129

So wait, say that again.

130

Nothing I do is scripted.

131

On the interviews? In my job.

132

So every day, it's a different set of challenges and problems that arise that,

133

like, I don't have playbooks for everything that comes across my desk.

134

And I have to be able to react on the fly

135

and make judgment calls on very nuanced decisions where I have incomplete information.

136

And there's also sometimes there's personalities to navigate as well.

137

And so I have to, with incomplete information and using my own judgment and experience, make calls.

138

Sometimes these calls affect the whole company, you know, the way that we have to make these decisions.

139

And it's important that when I make those calls, I have the right framework.

140

I'm deciding for the right framework.

141

So, when I'm conducting these interviews,

142

I'm also looking for somebody that can also think with incomplete information and work through like,

143

hey, what do I know?

144

What do I not know?

145

How can I find out what I don't know?

146

What missing pieces do I need to put in place before I can make a decision

147

and have that decision be effective and I can defend that position?

148

Yeah, and without needing you for every last thing.

149

And without needing me for every last thing.

150

That's important as well.

151

I'm trying to be able to delegate to these people.

152

These are not just entry -level positions.

153

These are leaders.

154

These are like deputies

155

that I need on my team to be able to take

156

care of certain aspects of the security program without my direct oversight on everything that they're doing.

157

Yeah.

158

So I designed the interviews using AI and using these as prompts

159

and the focus and the core philosophy of the interview was demonstrated competence

160

and critical decision -making and technical understanding as a secondary.

161

So kind of taking it for granted, here's what it would look like in practicality.

162

So for example, for the compliance interview, I would just assume they were familiar with the frameworks,

163

but I don't want them to talk about what are the elements of the framework.

164

I want them to tell me what did you do when you needed to implement this framework?

165

And then there was an engineer that was giving you a hard time.

166

That was kind of the question that I asked, because that just assumes that they know what the framework is,

167

but I want to see what it looked like in action.

168

And I was also aware at this time, I know that people were using AI in interviews,

169

and I wanted to construct my interview in such a way to catch cheaters.

170

So this was actually intentional on my part.

171

All of the questions were framed that you needed to respond with a personal narrative.

172

I was asking the person, what did you do in this situation?

173

Or what would you do in this hypothetical situation?

174

Tell me how you implemented this, right?

175

All of the questions were - So, I mean, to me, like that actually seems like very,

176

like every interview should be framed like this because it's not a test.

177

It's not like in high school or college when they're just testing, do you know this information?

178

The test is you have this information, you've had this information how did you work with it?

179

How did you implement it?

180

How did you problem solve with it?

181

Because that speaks to your actual ability.

182

And when we're on the job, it's not just about knowing something.

183

It's about how do you use that information to get a job done and get it done well.

184

You would be surprised at some of the interviews that I've gone through.

185

Wait, like other people interviewing you?

186

Other people interviewing me.

187

Not interviews that I conducted, yeah.

188

I've interviewed for a lot of positions and some very large organizations as well,

189

where the interviews were asking me a question a technical question right

190

that was a simple google search away like

191

if i wanted to i could have had another screen just googled the answer and reported directly the answer.

192

And like, my philosophy on interviews is a little bit different than that.

193

Yeah.

194

Right.

195

I don't want to ask you something that you can just Google and you will get the right answer.

196

Right.

197

Anyone can do that.

198

And that's not demonstrated competence.

199

That's demonstrating, you know, how to use Google and anyone can do that these days.

200

You know, we have a very tech savvy workforce.

201

So for me, it was important.

202

It's not just the ability to just go and find information.

203

But how do you apply that information in very real scenarios that you will find yourself in on the job?

204

Yeah.

205

So tell me about like, how were you able to detect that some people were using AI

206

and they weren't really speaking from their own experience or they didn't have deep answers?

207

How did you detect that?

208

It was actually really easy.

209

And I was surprised at how how effective this was

210

because all of the questions were constructed as answer from personal narrative well first of all

211

there's the eyes the eyes let me tell you about the eyes okay

212

when you when you're doing a video interview kind of kind of like this and

213

you see somebody's eyes going over the top and going like a typewriter

214

They're just ding, ding.

215

You can see that they are reading the answer, first of all.

216

That was my first visual cue.

217

A dead giveaway.

218

Like, I understand if they're not making eye contact because the camera is at a weird place and laptop's right.

219

But this was a visual.

220

I could see their eyes moving in a reading pattern across the top.

221

And it was so obvious to me and distracting in the interview.

222

Because you're trying to connect.

223

You need eye contact.

224

You're trying to connect.

225

I was trying to make eye contact to look at them

226

and get a feel for what they were like as a person.

227

And I was, you know, the eyes were avoiding me the whole time.

228

They were just reading.

229

Eric's over there like.

230

Yeah, I was trying to make eye contact.

231

I could not do it.

232

And then I figured out, oh, they're reading.

233

And the other dead giveaway was everybody knows how AI answers these things.

234

I have a thing now where I can tell almost what AI is being used when I see posts on LinkedIn, right?

235

Every other post these days is just a straight clod output or a chat GPT output.

236

And I can tell the difference between the AIs because I use them on the regular.

237

So I know when there's just raw output being spat out by a prompt versus genuine human thought going into it.

238

It's called AI Slop.

239

And yes, it is a dead giveaway that you didn't do your own thinking.

240

You had AI do your thinking for you.

241

And people lose respect when they see that because it's just like, no, we want to hear your thoughts.

242

So just a tip here, what I do if I ever need AI for help with anything is I'll write my own idea

243

and then I'll check it with AI and be like, hey, don't take out my voice.

244

Make sure my voice stays intact.

245

I want this to sound like me, not like polished ai yeah we're like m dashes

246

that are all over the place

247

and i had to tell my ai at one point

248

i'm like nobody writes with m dashes what are you doing like do you see this out in the wild

249

so you can add skills to your ai to have it check i think there's one called like humanizer

250

or something like that and that can check your you know your output

251

and stuff like that but it is true we're in a new era everyone is using ai

252

and now for my viewers and subscribers it's like oh ai is great

253

because now finally i can present my english as being correct

254

and clear but the thing that everyone needs to be aware of is

255

that not only will it be correct and clear

256

but it will erase your voice like before you even finish developing your voice in english it's already erasing it

257

so just be really careful of that

258

and don't allow it to erase your voice especially

259

because what sounds good and clear to you to us sounds like oh my gosh that's ai like that is totally AI.

260

Did they even think that through or did they just have a prompt think for them?

261

And you don't want that reputation of being somebody that doesn't do their own thinking because, well, I mean, I hope you don't.

262

I don't.

263

I mean, you also have to think like, what is an interview, right?

264

Exactly.

265

An interview is I am the person who needs a job filled

266

and there's a specific skill set and ability to make certain decisions.

267

And in the interview, I need to be able to evaluate that you are capable of filling this role for me, right?

268

Anybody can go and read a prompt from AI.

269

But like when you are in that hot seat, when you are in that position,

270

especially leadership positions, when you're in that position and you need to make a judgment call,

271

I have to be able to see that you can be trusted with that judgment call.

272

And this notwithstanding, the fact

273

that somebody is using AI in a deceptive manner in an interview is already a red flag for judgment calls

274

because it demonstrates a lack of integrity.

275

And so that already, like when I saw that, I was like, ooh, like.

276

If you're going to not be honest with me about who you are, because that's really what using AI to replace your voice is,

277

is you're not answering those questions.

278

The AI is answering those questions.

279

And when you're doing so in a deceptive manner,

280

so in an interview where somebody is asking you a question and you're answering from the AI, that's deception.

281

And that doesn't bode well for the interview.

282

Yeah.

283

And I think for me personally, if I were to do any kind of interview with anything,

284

I honestly think AI would slow me down because my brain, my brain thinks faster than AI.

285

Like the amount of time, you know, and I trust my own words more and the way I can articulate thoughts.

286

I trust my own voice

287

and my own way of expressing way more than I would trust AI to express things for me.

288

Like, no, thank you.

289

Whenever I have AI do a project for me, like I'm constantly having to correct it.

290

I'm constantly having to be like, no, it's not like that, or stop saying like that.

291

And some people just take that raw output, and they go, okay, this is it.

292

And it's like, oof, no, you know,

293

so what I would encourage everyone to do is get to a level where you can trust your voice and express yourself.

294

Because at the end of the day, the person interviewing you, first of all,

295

they want you to be the one they don't want to interview 20 people, it's exhausting to have to interview so many people.

296

So they can get the right person on the first interview, like that's amazing.

297

So they want you to be that person.

298

And I know that sometimes, especially if English is not your native language, you can feel like, oh, but like, I'm not good enough or whatever.

299

But I feel like having an accent or messing up your grammar or whatever it is, mispronouncing a few words is okay,

300

if you can still demonstrate that that raw knowledge and experience is there.

301

Wouldn't you agree?

302

Like, oh, absolutely.

303

Yeah, like we can work through an accent, we can work through mispronunciations or grammar.

304

But what we can't work through is you don't even have the experience or the understanding.

305

And the problem is, what if you do have the experience and the understanding,

306

but you're selling yourself short by using AI and making it look like you don't know what you're talking about?

307

Because you're just reading an answer rather than saying like, well, I went through this and this is what happened.

308

And that was the key, was the answering was in the third person really no what

309

because the ai answers as an ai it doesn't answer as a

310

so you would it can't answer with a personal narrative

311

because the ai doesn't have any personal narrative so how would

312

that how would that work give me an example oh

313

so again that same question like tell me

314

when you needed a control to be implemented and there was an engineer

315

or a business leader that was giving you a hard time how did you work through

316

that relationship and so the answer comes through When there is a disagreement between an engineer and the compliance professional,

317

it is important that everybody's voices are heard.

318

Leadership should be involved.

319

Right.

320

Like so vanilla.

321

Oh, my gosh.

322

It's a vanilla answer.

323

It's like it's the right answer, but it's not you're not telling me a story about something that happened to you.

324

Yeah.

325

And everybody should have a story like that.

326

That's not a hard story.

327

If you've done the job.

328

Yeah.

329

That's not a hard story to come up with.

330

Oh, let me tell you one time, you know, this and

331

and the thing too is with on the interview

332

you're able to build rapport yeah you can tell stories you can talk about it's fun some of the drama

333

that happened in your last and like why it drove you crazy

334

and how what you had to navigate you're showing

335

that you're human yeah and it's so weird a lot of people i think

336

when they think of interviews they go into this like box where they're like i have to wear a tie

337

and i have to speak a certain way and

338

and they become less and less human

339

and it's like okay the more human you are actually the more

340

you can connect with people in an interview the better chance you have of getting a second interview

341

or getting the job

342

because at the end of the day people are working with people we're not working with robots

343

and even doing the job yeah

344

and even doing the job working with people is one of the things we're looking for

345

so that because the interview is step one

346

if you get hired they have to work with you every day

347

and it's true that's what happens yeah like

348

so you have to present who you really are and telling stories

349

and sharing personal experience is an excellent way to connect

350

so it's actually really sad that people are basically losing opportunities

351

because they're using ai and the ironic thing is they think they're doing the right thing

352

or the best thing yeah and it's like no

353

and yeah to to be fair not everybody conducts interviews this way this was something

354

that i developed because of my own philosophy on this

355

and my own bad experiences with the interviews where i was asked really technical questions

356

that like could have been googled

357

and i was like what what are we doing yeah like why it had no points to me to do

358

that like anybody can do that but you're you're absolutely right

359

that the we're working with people and

360

so starting on step one in the interview process demonstrating

361

that you are a relatable person is something

362

that i was actively looking for

363

and i wanted to see actually in fact the people that did well in the interviews they

364

We didn't have necessarily perfect answers to the questions what they

365

had were real answers to the questions like not ai

366

i actually what they they would tell me i actually went through something like this

367

and i had this one guy

368

that was really difficult to work with i had a control

369

that was really difficult to implement

370

and i just had to you know i involved leadership we had multiple meetings

371

and to try to understand his point of view so

372

that we work together i'm like that's a great story

373

because that's something that happens everywhere where you have to work with other people

374

and negotiate with them in order to get something done.

375

And it's messy.

376

The way that it happens is messy.

377

And so when I ask these questions, I'm not expecting like a, the word that comes to mind is sterile, right?

378

It's like a doctor's office.

379

Everything is absolutely clean and devoid of microscopic life bacteria.

380

Devoid of life, right?

381

Which is interesting because that's what a lot of people think they need to achieve in an interview.

382

And it's like, actually, no, you don't have to be perfect.

383

You have to be human and you have to show that you have experience and that you know what you're talking about.

384

And life is messy.

385

Relationships can be messy.

386

Work environments can be messy.

387

And we have to navigate that.

388

And everybody knows.

389

And so when you also have to think when you're doing an interview, you're interviewing someone higher up, they have very likely been in your position,

390

so they know exactly what it's like.

391

And so by talking about your real experiences, they're going to be like, yep, been there, done that.

392

I can relate.

393

Yeah, I know what it's like, you know, so.

394

When we were lovely ticket boys.

395

Ticket girls and boys.

396

Ticket girls and boys.

397

Okay, so I think you told me, speaking of ticket girls, I think you told me there was a woman actually

398

that did very well in the interview yes

399

so talk to us about her what did she do she answered everything with personal narrative

400

and again the answers weren't polished necessarily but she also asked clarifying questions

401

and this was this was like as soon as she asked a couple of clarifying questions

402

i was like like this is what you're looking for in these jobs

403

because when you ask somebody a question and they immediately jump to an answer they're like, oh, I know, do this.

404

You're almost always wrong.

405

Because the questions that we deal with in security and IT, it's not a single variable that you're solving for.

406

It is sometimes 10, 20 different variables in play at once.

407

And if you jump to an answer without solving for all those variables, you're going to get the wrong answer.

408

So somebody who asks clarifying questions

409

And it's like, hey, when you say this, is this already in place?

410

Do we have this tool available to us?

411

Is this document or policy already enforced or does it yet need to be created?

412

She was asking questions like this was my compliance interview.

413

And I knew exactly what she was asking these questions.

414

But these are exactly the questions you need to ask before you answer the question.

415

And then when she would answer the question, she would answer the question correctly based on the frameworks

416

that were assumed

417

and also with the correct logical decision making after establishing

418

we have this in place we don't have this in place

419

we have this in place we have we don't have this in place

420

she was able to order what needed to happen first what needed to happen next

421

and it was just like a dream come true in the interview

422

that somebody who thinks that's that's what you want as a leader is you want somebody

423

that can get a problem and solve it themselves.

424

Yeah.

425

So this is called critical thinking.

426

And actually asking clarifying questions is a hallmark of somebody who is a critical thinker.

427

And when we're not critical thinking, right, we're not doing that, or we should be, it's like you get a question

428

and you just answer it without thinking about other possible solutions and what could possibly affect this.

429

And I think one of the problems is that people think that there's this expectation that to show intelligence,

430

you have to be able to answer immediately.

431

And that's actually not a hallmark of intelligence a hallmark of

432

intelligence is well hang on hold on let's back up let's analyze

433

this from this angle let's talk about this well what

434

if this other thing were to happen that is critical thinking

435

so you're analyzing all the different possibilities

436

and what things are going to affect other things

437

and this is how we have to think right

438

and this is what leadership is going to be looking for they are looking for critical thinkers so

439

when you're in an interview it is not bad to ask questions in fact

440

it's as he just said it's really good

441

and i also want to confirm because I have a friend

442

and mentor who is a CTO what does

443

that stand for chief technology officer okay yeah

444

so he's a CTO he's been a CTO for I don't know how many decades

445

and he said the same thing because he also conducts interviews

446

and sometimes we talk and he rants about oh the interviews

447

and what hell like why don't people know how to do this

448

and that's one of the things he's like when I ask a question Thank you.

449

ask me a question.

450

Let's talk about it.

451

Let's dive into it.

452

Let's solve it together.

453

I'm trying to see how you think.

454

I'm not just testing what you know.

455

Because on the job, you're going to have problems and you're going to have to solve them together.

456

And you're going to have to talk about possible solutions.

457

You're going to have to dissect things.

458

You have to think critically.

459

And so the perfect place to show your critical thinking skills is in the interview.

460

So show up with questions to ask them.

461

Clarify when they say something and you're not sure.

462

Don't just invent something to try to appear intelligent.

463

Your intelligence will show through by how you talk about the situation.

464

All right.

465

Couldn't have said it better myself.

466

That's absolutely true.

467

Everything you said.

468

Yeah.

469

Okay, cool.

470

I feel like we could talk forever about this, but we all already gave some good insight here and we talked really fast.

471

So that's good.

472

This is this is a regular speed conversation did it feel fast to you at all

473

i think this is our normal talk this is our normal talk yeah

474

we both had a lot a little bit of coffee earlier

475

so you know there's a little bit of that going on yeah

476

so what we need to know from you guys in the comments one did you still understand me

477

because i get a lot of comments on my videos saying like why do i understand you

478

so well and i don't understand other people

479

so i want to know do you still understand me

480

when i speak at this rate

481

and what do you think of eric he's cool huh do you want him to come back for more conversations.

482

Let us know.

483

Tell us something you learned in the comments.

484

What else?

485

Don't use AI in your interviews.

486

Don't use AI.

487

Okay.

488

Please.

489

Like the video.

490

If you learned something, subscribe to the channel.

491

What else would we say?

492

You're in good hands.

493

She's great.

494

Oh, thank you.

495

Thank you.

496

You know what I will say?

497

I will say that when I hear you speak, and I've known this about you, I do have a way of speaking that is,

498

I would say, simpler compared to you.

499

So I don't know, I'd have to analyze it more.

500

I'm not sure if it's your sentence structure.

501

You tend to use more higher level words than I do.

502

I use a lot of technical jargon.

503

Well, technical jargon related to your work, but also when you're not even talking about your work, you're just expressing yourself in general.

504

Like, I just noticed this about you.

505

You tend to use more like higher level words, you know, there's probably a word for that.

506

And I'm just saying higher level, but I'm sure there's a better word.

507

But like, this is something also about my speech.

508

I think I just like communicating at this level because I feel like it comes naturally to me.

509

I'm not as smart as he is.

510

I'm just kidding.

511

It has nothing to do with intelligence.

512

It's a learned behavior because I speak to engineers and business leaders all day, every day.

513

And there's just certain things that we talk about and certain language that we use that vernacular just becomes normal.

514

But I will say you used to be like this even when you were in high school, even when you were in college.

515

I like big words.

516

Yeah, so it could just be that.

517

It could just be like you like big words and you like using them.

518

I like big words and I cannot lie.

519

Let us know in the comments if you know what he's referencing.

520

Anyways, yeah, so this is Eric.

521

He's awesome.

522

And thank you for watching our video.

523

Bye, everyone.

524

Bye.

アプリをダウンロード

流暢に話すために必要なすべて

AI発音採点文ごとに採点

IPA練習すべての音をマスター

単語学習自分の単語帳を作る

単語ゲーム遊びながら覚える

QRをスキャン

Download on theApp Store Get it onGoogle Play

同じチャンネル

FOR YOU

このレッスンの語彙とスピーキングのポイント

このスピーキングレッスンは、動画「Crush Your Next Job Interview in English」を教材にしています。この動画には、シャドーイング用の文が524文、単語が5398語あります。音声の長さは28:27です。話す速さは速く、1分あたり約190語です。音のつながりや弱く発音される音が多くなります。単語の87%は英語の頻出3,000語に含まれるため、語彙は分かりやすいです。

この動画の重要語彙

動画に出てくる覚えておきたい単語15語を、発音と意味つきで紹介します。

単語	発音	意味
framework 名詞	/ˈfɹeɪm.wɜːk/	骨組み
solve 動詞	/sɒlv/	解決する
judgment 名詞	/ˈd͡ʒʌd͡ʒ.mənt/	判決, 裁き
compliance 名詞	/kəmˈplaɪ.əns/	順守
output 名詞	/ˈaʊtpʊt/	出力
narrative 名詞	/ˈnæɹ.ə.tɪv/	物語
implement 動詞	/ˈɪmpləmənt/	実行する, 実現する
messy 形容詞	/ˈmɛsi/	乱雑な, きたない
connect 動詞	/kəˈnɛkt/	繋げる
complaint 名詞	/kəmˈpleɪnt/	不平, 不満
variable 形容詞	[ˈvæɹ.i.ə.bl̩]	可変, 変えられる
incomplete 形容詞	/ɪn.kəmˈpliːt/	不完全, 未完
analyze 動詞	/ˈæn.əˌlaɪz/	分析する
erase 動詞	/ɪˈɹeɪs/	消す, 消去する
script 名詞	/skɹɪpt/	文書, 文章

動画に出てくる句動詞

単語	発音	意味
find out 動詞		見出す, 調べる
go ahead 動詞	/ˌɡoʊ əˈhɛd/	どうぞお先に
go out 動詞		出る
slow down 動詞		遅らせる
take out 動詞		取り出す

繰り返し練習したい文

動画に出てくる短く完結した文です。日常会話でそのまま使えます。

You want to know more?
Can you look into it for me?
What do I not know?
How can I find out what I don't know?
How did you implement it?

この動画の文法

話し手がよく使っている文型を、動画の実際の表現とともに紹介します。

文型	動画での表現
「used to」 used to + 動詞 — 今はもう違う過去の習慣や状態	used to code · used to be
受動態 be + 過去分詞 — 誰がするかより、何が起きるかに焦点を当てる	are used · are called · be learned
関係詞節 who / which + 節 — 人や物について情報を加える	guy who was · officer, which means · somebody that could
現在完了形 have/has + 過去分詞 — 過去の出来事が今も関係している	hasn't even told · you've had · I've gone

注意したい発音

話し手はyou're, don't, I'mなど、短縮形や弱形を128回使っています。聞こえたとおりの短い形で発音しましょう。

「th」の音: hypothetical /ˌhaɪpəˈθɛtɪkəl/, thinker /ˈθɪŋ.kɚ/, notwithstanding /ˌnɑtwɪθˈstændɪŋ/
「sh」と「zh」の音: gosh /ɡɑːʃ/, polish /ˈpɑ.lɪʃ/, dash /ˈdæʃ/, reputation /ˌɹɛpjʊˈteɪʃən/, establish /ɪˈstæb.lɪʃ/
長い単語（アクセントの位置に注意）: necessarily /ˌnɛs.əˈsɛɹ.ə.li/, naturally /ˈnæt͡ʃ.(ə.)ɹə.li/, reputation /ˌɹɛpjʊˈteɪʃən/, intelligent /ɪnˈtɛlɪd͡ʒənt/, integrity /ɪnˈtɛɡɹəti/

日本語話者が苦手な音：

/r/ と /l/ の区別 — /l/ は舌先を歯茎につけ、/r/ はどこにもつけない: clarify /ˈklæɹ.ɪ.faɪ/, variable [ˈvæɹ.i.ə.bl̩], necessarily /ˌnɛs.əˈsɛɹ.ə.li/, naturally /ˈnæt͡ʃ.(ə.)ɹə.li/, relate /ɹɪˈleɪt/
/v/ — /b/ にならないように、上の歯を下唇に当てる: solve /sɒlv/, narrative /ˈnæɹ.ə.tɪv/, variable [ˈvæɹ.i.ə.bl̩], navigate /ˈnæv.ɪ.ɡeɪt/, vanilla /vəˈnɪl.ə/
/f/ — 「フ」ではなく、上の歯と下唇で出す: framework /ˈfɹeɪm.wɜːk/, clarify /ˈklæɹ.ɪ.faɪ/, defend /dɪˈfɪnd/, format /ˈfɔːɹ.mæt/, confirm /kənˈfɝm/

この動画での練習方法

まず声を出さずに動画を最後まで聞き、知らない単語をメモします。
まず0.75倍速で一文ずつシャドーイングし、慣れてきたら通常の速度に戻します。
自分の声を録音して元の音声と比べます。framework, solve, judgmentなどの単語に特に注意しましょう。

シャドーイングとは？英語上達に効果的な理由

シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。

シャドーイングのやり方: ステップ別の完全ガイドを読む →

シャドーイング練習: Crush Your Next Job Interview in English - 動画で英語スピーキングを学ぶ

練習モードを選ぶ

アプリをダウンロード

同じチャンネル

Practice Speaking & Reading Out Loud With This English Shadowing Exercise

Will reading out loud improve your pronunciation & speaking skills?

How To Change Your Accent (Part 2: My Advice For YOU)

5 Minute English Practice Strategy for Real Fluency

an honest conversation about sounding like a native

How To Change Your Accent (Part 1: My Story)

Episode 1: Fluent Pronunciation Training

Fast Speech | How To Sound Like A Native English Speaker

Practice Speaking & Reading Out Loud with This English Shadowing Exercise

What Fluency Feels Like

おすすめ動画

Improve English Speaking Skills | Meeting a girl | Shadowing Practice with a Simple Conversation 💬

Every Cybersecurity Interview Question and Answer in 35 minutes

Cracking the Behavioral Interview for Software Developers

Odd job interviews. | 6 Minute English.

50+ Phrases For Job Interviews in English

english interview p1

Phone Interview with a Recruiter

A Day in the Life of an Amazon Software Engineer

How to explain a project you workede on in 30 Minutes | Business English Learning

How to Pass Call Center Interview in 1 Day (Even No English, No Experience)

Mock Interview Preparation: Common Questions with Feedback!

The Pursuit Of Happiness - Job interview - Inspirational Movie Scenes Ep. 6

このレッスンの語彙とスピーキングのポイント

この動画の重要語彙

動画に出てくる句動詞

繰り返し練習したい文

この動画の文法

注意したい発音

この動画での練習方法

シャドーイングとは？英語上達に効果的な理由