跟讀練習: Interview Tips from a Senior Software Engineer... and a 4 year old - 通過影片學習英語口語

選擇練習模式

每種模式都會開啟全屏練習室。

171 句

如果句子過短或過長，請點選 Edit 進行調整。

Hey everybody, it's Jesse, and I'm making this video today from a bunk bed.

This is my friend Ambrose And this is Taggy!

Oh, and my robot hand.

I really love robots!

This is my son

and today I want to talk a little bit about what I did to prepare for my interviews

So the last two videos on my channel were about my Google interview specifically

and then another video just more in general of my whole experience of interviewing.

So I had several questions about what I did to prepare.

So I'm going to go over some of the websites I used

and books and resources and I'm going to let you know which ones I think were the most helpful.

So just to start out, I interviewed for front-end developer positions,

front-end engineer, software engineer positions.

And so my, it was more front-end based for me, all of my interviews, interview questions, and my preparation.

So depending on whether you're front-end, back-end, or full-stack, and what languages you use, this may be a little bit different.

But one service that I think was really valuable was called Pramp.

It's P-R-A-M-P.

I'll make sure I put links to everything I talk about in the description.

So, PRAMP is a service where you sign up and you get paired up with someone else for a time slot.

So, I think it was like an hour time slot.

In the first half hour, one of you takes the role of the interviewer and the other one is the interviewee.

And then, for the second half of the time slot, you switch places.

so it gives you not only do you have a practice question

but you also have a time limit

and you have someone else that's asking the question

that you have to explain yourself to

that was really helpful they have it broken down by different categories so you can just do front-end related stuff

data structures and algorithms.

It can just blast.

Yeah.

Whoa.

I flew it.

And I love tagging.

Because of that, it stood out as being really unique and offering something that some of the other resources didn't.

If I can go to sleep, eat when I sleep without tagging.

If you don't have any experience, like a lot of experience with actual interviews.

Shhh, okay, let's be quiet.

If you don't have experience with interviews, then I definitely recommend PRAMP.

They may have like a free tier.

I'm not sure.

I think it is a paid service, but there may be some way to get some free things.

I'll find out and put more info in the description.

So the next thing that I used that was very, very helpful was a book called Cracking the Coding Interview.

And I know I mentioned this in some of my other videos, and I mentioned it to some of you that ask me questions directly.

It's a huge book.

It has a lot of information in it.

It was written by a woman who actually interviewed a lot of people at Google.

It goes through and explains what interviewers are thinking, what they're looking for when they actually interview you.

Just being able to get into that mindset of what interviewers are actually thinking helped me so much.

It helps me.

You know, there's so many things you could talk about or focus on when you're in an interview.

So just knowing what these people want to hear is great.

Okay, Darth Vader.

Actually, I'm a boss Thomas Spiegel and my last name's Weiger.

That's right.

So, I definitely recommend that book.

And I know Tygie's last name.

Tygie's last name is Ty.

Oh, okay.

There's also a ton of practice problems and explanations of data structures and algorithms.

So, if you were going for a more general software engineer position or a back-end position, then those practice problems would help you a lot.

For me, it wasn't that helpful.

because most of my questions were specifically front-end JavaScript related.

So it was still cool to go over some of that info.

I don't have a computer science background, so a lot of it was new to me.

So I'm sure it'll be helpful to me at some point, but just wasn't so much for the interview.

So if you're going for front-end stuff, then I think it's safe to skip over a lot of those sections of that book.

But the next resource that I used, and this is probably a little bit more front-end specific, is FreeCodeCamp.

So FreeCodeCamp has some practice interview questions,

and they also have some kind of less difficult JavaScript algorithm challenges.

So I think that's a great way to refresh your JavaScript knowledge should

if you already have a job um where you're not coding that much uh all the time

you want to get in the habit of of coding um as much as you can before you interview

you can go wash it off if you want Fine!

I ate a pancake at Jesus.

I'm in the carcass house.

So, I highly recommend Free Code Camp for a variety of things,

but in this case, for sure, for your interview prep.

And another resource that I used was JavaScript Data Structures and Algorithms book.

I'll put the official title and link to that below.

So I ended up getting the e-book.

So I had that on my phone.

So I got the hard copy of the Cracking the Coding interview.

But when I was in a situation where I didn't have my hard copy, but I always had my phone on me, then I could always look at that.

So that helped me because it was JavaScript specific, which is the language that I was being tested in. So

that was, it was easier for me to understand the example problems than what I was seeing in Cracking the Coding interview.

It was just another explanation of some of those data structures and algorithms, which, like I said, ended up not helping me that much because I didn't really get questions about it.

But if you are going for something that's a more full stack position or back end position, you may get asked questions about that.

So I highly recommend that as well.

Something that is back.

You're back.

And I'd recommend that for whatever books you're using,

I think it would be a good idea to have an electronic copy of the book.

So even if you like hard copies, that's great.

If you can only find it in hard copy, that's fine.

And sometimes, especially when you're looking at code, it's a lot easier to just have a hard copy sometimes.

But having that on my phone was so useful.

You know, if I was waiting in line, waiting at the doctor's office, you know, I didn't feel like I was wasting time.

I could always look at that in practice.

100

So it just kind of always kept it in my mind.

101

And I think that's really helpful. When you're...

102

You just need to be able to always be thinking about code.

103

It just makes it so much easier when you're actually on the spot in the interview.

104

You only have a short amount of time.

105

You're probably a little bit nervous.

106

So I think it's kind of like...

107

This is the Master Sword.

108

Yeah, it's the Master Sword from Zelda.

109

Yeah.

110

I mean, not the Master Sword, but a good replica.

111

I think like like you would approach let's say a foreign

112

language spoken language with more use you're gonna be more comfortable

113

when you actually get into a conversation with somebody the same way with coding even

114

if you didn't have great resources

115

but you still coded as as often as you could okay squeaky now no we're squeaking

116

if you throw it as often as you possibly could that's gonna be more useful than

117

if you have great resources the perfect books the perfect questions

118

and only looked over them

119

you know occasionally

120

just practice

121

actually go on the interview

122

just be be honest okay you don't have to you don't

123

have to be down on yourself you don't have to tell the interview all the things you don't know

124

but on the other hand don't claim that you know things

125

that you don't because they'll be able to figure it out really easily right

126

if they say hey do you know how to make a

127

network request in javascript you say oh yeah i do it all the time I say, okay, can you do it for me?

128

You know, write it on the whiteboard.

129

Well, then you're stuck, right, if you don't really know how to do it.

130

So just be honest.

131

You could say, you know what, hey, I've done it before, but I'm a little rusty on the syntax.

132

Or, you know what, I never actually had to do that.

133

I kind of know how it's done.

134

Can I just explain it to you?

135

So something like that is way more acceptable.

136

And if you have to just say, listen, I've never heard of that before.

137

Just say it.

138

And you can even add. So.

139

I really like her.

140

Hey, can I talk now?

141

Yeah.

142

Thank you. So. If you don't know.

143

Admit that you don't know.

144

But then it would be helpful to say.

145

Listen, like if I had to do that for my job.

146

Here's where I would go to find the answer.

147

You know, so say.

148

I would I would look this up on MDN or something like that

149

And then at least you would you could give some answer even

150

if you have no idea you've at least given some answer

151

And said like here's how I would approach this this problem

152

So Think I'm gonna wrap this video up The that was my my advice.

153

Let me know what you think if it's too distracting

154

here for the video or if you can't like I want Tiggy to say something and Tiggy say something

155

I really like toys and I really like animals

156

and I really am spitty and I eat humans

157

and I really want pancakes and butter and bread and everything in the whole world.

158

I'm going to say goodbye to everybody on YouTube.

159

Would you like to say goodbye?

160

Bye.

161

Bye.

162

Bye.

163

That was Heidi.

164

Bye.

165

That was me.

166

All right.

167

And now you.

168

See you later, everybody.

169

Hopefully this helped.

170

And give me your ideas for what videos I should do next.

171

Until next time, have a great day.

下載應用

流利口語所需的一切

AI 發音評分逐句打分

音標練習掌握每個音

詞彙學習建立你的詞庫

詞彙遊戲邊玩邊學

掃碼

Download on theApp Store Get it onGoogle Play

同頻道

How to friction-max your learning with software engineer Jessica Rose [Podcast #216]

Daily ConversationUniversity StudentsWorking Adults

Inside a Hong Kong Hackathon [Full Documentary]

Daily ConversationUniversity StudentsWorking Adults

FOR YOU

本課的詞彙與口語要點

這節 B2 級別的口語課以影片“Interview Tips from a Senior Software Engineer... and a 4 year old”為素材。這段影片共有 171 個句子、1799 個單詞可供跟讀。講話部分時長為 12:55。說話人語速平穩，每分鐘約 139 個詞，很適合跟讀。 85% 的單詞屬於英語最常用的 3,000 詞，其餘的詞建議在練習前先學一下。

影片中的重點詞彙

影片中最難的 15 個單詞，附發音和釋義：

單詞	發音	釋義
algorithm 名詞	/ˈælɡəɹɪðm̩/	演算法, 演算法
interviewer 名詞	/ˈɪntɚvjuɚ/	訪問者 /訪問者
pancake 名詞	/ˈpæn.keɪk/	薄烤餅 /薄烤餅, 薄煎餅 /薄煎餅
stack 名詞	/stæk/	堆
carcass 名詞	/ˈkɑɹkəs/	屍體 /屍體, 胴體 /胴體
preposition 名詞	/ˌpɹɛpəˈzɪʃən/	介詞 /介詞, 前置詞 /前置詞
whiteboard 名詞	/ˈwaɪtbɔɹd/	白板
syntax 名詞	/ˈsɪn.tæks/	句法
refresh 動詞	/ɹɪˈfɹɛʃ/	提神
replica 名詞	/ˈɹɛplɪkə/	複製品 /複製品, 仿製品 /仿製品
distract 動詞	/dɪˈstɹækt/	分心
whoa	/woʊ/	籲
mindset 名詞	/ˈmaɪn(d)ˌsɛt/	心態 /心態, 思維模式 /思維模式
tier 名詞	/ˈtɪɚ/	層 /層, 排
wrap 動詞	/ɹæp/	包裝 /包裝, 包

影片中出現的短語動詞

單詞	釋義
end up 動詞	到達
break down 動詞	壞了 /壞了, 出故障
find out 動詞	找出, 查明
go through 動詞	通過 /通過
sign up 動詞	報名 /報名, 註冊 /註冊

值得反覆跟讀的句子

影片中簡短而完整的句子，可以直接用在日常對話裡：

Shhh, okay, let's be quiet.
For me, it wasn't that helpful.
Can I just explain it to you?
Hey, can I talk now?
Would you like to say goodbye?

影片中的語法

說話人最常用的結構，並附上影片中的原話：

結構	影片中的用法
被動語態 be + 過去分詞 — 強調發生了什麼，而不是誰做的	was called · was written · being tested
現在完成時 have/has + 過去分詞 — 過去發生但與現在仍有關聯的事	I've done · I've never heard
定語從句 who / which + 從句 — 補充說明人或事物	woman who actually · specific, which is

需要注意的發音

說話人用了 56 次縮略和弱讀形式，例如 don't, you're, I'm。請按聽到的簡短形式來說。

“sh” 和 “zh” 音: preposition /ˌpɹɛpəˈzɪʃən/, refresh /ɹɪˈfɹɛʃ/
長單詞——注意重音位置: interviewee /ˌɪn.tɚ.vjuːˈiː/, preposition /ˌpɹɛpəˈzɪʃən/, developer /dɪˈvɛləpɚ/

中文母語者容易讀錯的音：

/v/ — 不要讀成 /w/，上齒輕觸下唇: interviewer /ˈɪntɚvjuɚ/, interviewee /ˌɪn.tɚ.vjuːˈiː/, developer /dɪˈvɛləpɚ/
詞尾子音 — 要讀清楚，後面不要加母音: slot /slɑt/, pancake /ˈpæn.keɪk/, stack /stæk/, carcass /ˈkɑɹkəs/, squeak /skwiːk/
/r/ 和 /l/ 的區別: algorithm /ˈælɡəɹɪðm̩/, replica /ˈɹɛplɪkə/

如何用這段影片練習

先完整聽一遍影片，不要開口，記下不認識的單詞。
用正常速度逐句跟讀，每句重複到你的節奏與說話人一致為止。
錄下自己的聲音並與原聲對比，特別注意 algorithm, interviewer, pancake 這類單詞。

什麼是跟讀法？

跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧，最初開發用於專業口譯員的培訓，並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大：您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同，跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性，語調，節奏，連讀，聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。

影子跟讀法: 閱讀完整分步指南 →

跟讀練習: Interview Tips from a Senior Software Engineer... and a 4 year old - 通過影片學習英語口語

選擇練習模式

下載應用

同頻道

How to friction-max your learning with software engineer Jessica Rose [Podcast #216]

Inside a Hong Kong Hackathon [Full Documentary]

推薦影片

Interviewing Part 1 - What You Need To Ask In Advance

Senior Product Designer Mock Interview: App Critique of Yelp

A Day in the Life of an Amazon Software Engineer

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

Data Science Interview Prep: 3 Key Resources You Need to Know

Mastering iOS Development: Mock Interview with Ramiro Neto

Claude Code: The Advanced Guide (99% of Devs Skip These Features)

🔥HR Interview Questions and Answers (2025) | Top HR Interview Questions for Freshers | Intellipaat

3.3k

pv content

Interview Practice

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

本課的詞彙與口語要點

影片中的重點詞彙

影片中出現的短語動詞

值得反覆跟讀的句子

影片中的語法

需要注意的發音

如何用這段影片練習

什麼是跟讀法？