跟读练习: Cracking the Behavioral Interview for Software Developers - 通过视频学习英语口语

what's up guys today we're gonna be doing something a little different

but I feel like it's gonna be super helpful a lot of engineers can crush it on the technical interview

but when it comes to the behavioral part that's where a lot of people struggle

and I know candidates who did great on the technical interview

but they got a rejection

because they failed on the behavioral part they weren't able to demonstrate

that they had proficient communication skills or how well they handle certain situations

and that's what the behavioral interview gauge is for

because you can be a technical genius but

if you can't convey what you're trying to say it's going to be hard to work on a team

and I'll be the first to admit it I'm not great at just thinking of examples right on the spot

so usually how I prepare for an interview

and how well I do on it usually have a direct correlation

so before going into an interview where I know I'll be ask situational questions I'll usually brainstorm

and think of about eight to ten examples from my career that can be used to answer different styles of questions.

Anything from conflict management to a time where I made a good technical suggestion

because a lot of times you can mold your situations to what the question is asking

and what I've noticed is that the best answers usually have a story behind it.

Obviously you don't want to add too much fluff to your answer

or diverge away too far from what the question is asking

but if you can kind of paint a picture of the solution to your interviewer

that usually leads to better results

so in this video I'm gonna give myself a few prompts

and answer them as

if this were a real interview before we get into the video make sure you guys hit the like button

so I know you guys like this kind of video

and let me know in the comments if you'd like to see more

so the first question is gonna be tell me about yourself this is the question

that most behavioral interviews start with now it's important to mention that even though these are behavioral interviews,

they will still have some technical aspects to them.

So let's take a look at how I answered this question.

Hey, my name is Sam.

I'm a software engineer and I enjoy solving complex problems.

I have experience as a full stack web app developer

and I enjoy working with all layers of the stack and I enjoy building out user -friendly efficient websites.

My passion for web app development started

when I was doing my internship at AWS

and I was given a solo project to work on for the entirety of the internship

and this really gave me full ownership over everything from the design decisions to the actual coding of it

and I was also able to gain a lot of experience and exposure to different AWS cloud computing tools.

After my internship I decided that this is what I wanted to do as a career

and since then I've gained about three years of experience building

out dozens of different applications at my current company i'm helping

out with the modernization of our existing infrastructure this includes building

out new microservices as well as updating existing ones the technologies i've experienced with include dotnet for building out apis

and our server side code sql with mysql oracle and sql server as well as experience with different various javascript frameworks,

including Vue .js and Angular.

So I believe my experience and my passion would make me a great asset for your company.

So in my answer, I tried to keep it short and sweet.

I didn't get into my whole life story, even though it is a tell me about yourself.

Keep it relevant.

Don't start talking about your dog or something.

You guys think I'm joking, but I've actually heard people say that when I've been in group interviews.

And I would say a sweet spot for this question would be a minute and a half, maybe two minutes.

Again, that isn't set in stone.

These are kind of like more like guidelines, right?

Have you ever seen Pirates of the Caribbean, right?

These aren't rules.

They're more like guidelines.

All right, the next question is going to be, tell me about a time you had to persuade someone at work.

What did you do?

Let's take a look at my response.

At my previous company, our team supported 20 to 30 different web applications.

And there was really no uniformity in terms of what front -end JavaScript framework we could or should use.

So what ended up happening is we would have some apps written in Angular, some apps written in React, some written in Vue, it was kind of all over the place.

And the problem with this was, say you were assigned to write a feature in a certain app and you didn't really know that framework, you would have to at least spend time getting a basic

understanding of it before you can even start to implement that feature.

So this potentially increased the development time by a lot.

So my proposal was to just have all our apps be written in Vue .js

because it's something that I had experience with.

I thought it was fairly easy to pick up.

It's a lightweight app and it's pretty easy to inject into existing applications.

So what I did was I created a little mini demo presentation

and I set up a meeting between my team and my manager

and just demonstrated the pros and cons of using that framework.

So the result of that was my manager was on board

and we decided to use Vue .js for all our new development.

Again, that was about a minute and a half to answer it and it was told like a story.

I explained what the problem was and what I did to resolve

that problem and showed how I made a lasting positive impact to the company.

All right, the last question we're going to look at is tell me about a time you failed at work

and what did you learn from it?

So this one time I was assigned the task of implementing a new feature into one of our applications.

And we used Git as our source control, so as I was working on this feature, I was continuously pushing to our master branch, which isn't good practice

because you always want to keep your master branch deployable as well as in sync with what's in production.

Also, if we deployed this app with this feature being partially done, it would break the application.

But this was an app that barely ever got updated, so I figured I'd be all right

but of course we had an emergency bug fix

that had to be made and I was like we actually can't deploy it

because the app is gonna break luckily with source control you are able to go back

and we were able to add

that change to where I started working on the future

but in the future I learned that in order to you know

if I wasn't making any changes first create a branch off of master

and deploy to that branch and then when you're finally done with the future then merge the changes back into master.

Now a potential issue to this answer is that it assumes that the interviewer knows how Git works.

Most likely you're gonna be doing one of these interviews with another dev

so I mean they probably know how Git works but it's possible

that they don't but I think a really important thing to answering these questions is

100

that you don't want to confuse your interviewer by going too into the weeds with a particular technology

101

that they might not know.

102

So just gauge who you're interviewing with it's it's very easy to get very technical about something

103

and totally lose your interviewer and that's not good

104

because it means you weren't able to clearly communicate a technical topic

105

which is important when you're working with other devs on a team all right

106

so the takeaways from this video are keep your answers about

107

one to three minutes long the best answers usually tell a story usually there's a problem

108

or a situation and you talk about an action

109

that you took to help resolve that situation

110

and finally don't confuse your interviewer a lot of times your answers might include a very complex technical subject

111

that your interviewer isn't going to understand in a two -minute explanation

112

so just be aware of that and and even simplify your answer

113

if you need to all right guys thank you guys for watching the video

114

if you guys would like me to do another one of these uh definitely let me know

115

and if you have a specific question

116

that you want me to answer in one of these videos let me know in the comments

117

and i'll try to include it if if i end up doing another one

118

so i will see you guys in the next one.

119

And as always, keep on coding.

✨ 推荐视频

405 句

Former Amazon Recruiter Explains the Perfect "Tell me about Yourself" Answer (2026)

Business EnglishInterview EnglishUniversity Students

22 句

I'm an ex-Google interviewer. You're doing LeetCode wrong.

Business EnglishInterview EnglishUniversity Students

79 句

How AI Is Ruining Job Interviews

Business EnglishInterview EnglishUniversity Students

8 句

Google product manager behavioral interview (Top 5 questions)

Business EnglishInterview EnglishUniversity Students

281 句

How to succeed in your JOB INTERVIEW: Situational Questions

Business EnglishInterview EnglishUniversity Students

214 句

Phlebotomy Job Interview Questions and Answers! Get hired!

Business EnglishInterview EnglishUniversity Students

173 句

15 Common Health and Safety Interview Questions and Answers - Safety Training

Business EnglishInterview EnglishUniversity Students

193 句

SOC Analyst: Top Interview Questions & Answers (2025)

Business EnglishInterview EnglishUniversity Students

本课的词汇与口语要点

这节口语课以视频“Cracking the Behavioral Interview for Software Developers”为素材。视频中反复出现的词有：answer, interview, app, technical, usually。这段视频共有 119 个句子、1568 个单词可供跟读。讲话部分时长为 7:52。说话人语速较快，每分钟约 199 个词，会出现较多连读和弱读。 83% 的单词属于英语最常用的 3,000 词，其余的词建议在练习前先学一下。

视频中的重点词汇

视频中 15 个值得学习的单词，附发音和释义：

单词	发音	释义
interviewer 名词	/ˈɪntɚvjuɚ/	訪問者 /访问者
framework 名词	/ˈfɹeɪm.wɜːk/	骨架, 框架
deploy 动词	/dɪˈplɔɪ/	部署
internship 名词	/ˈɪntɜːnʃɪp/	實習 /实习
server 名词	/ˈsɝvɚ/	服務器 /服务器, 伺服器
passion 名词	/ˈpæʃən/	激情, 熱情 /热情
demonstrate 动词	/ˈdɛm.ənˌstɹeɪt/	论证
implement 动词	/ˈɪmpləmənt/	實施 /实施, 執行 /执行
resolve 动词	/ɹɪˈzɑlv/	解決 /解决
stack 名词	/stæk/	堆
gauge 名词	/ˈɡeɪd͡ʒ/	標準尺寸 /标准尺寸, 標準規格 /标准规格
confuse 动词	/kənˈfjuːz/	讓……困惑 /让……困惑
assign 动词	/əˈsaɪn/	分配, 分派
topic 名词	/ˈtɑpɪk/	主題 /主题, 話題 /话题
proposal 名词	/pɹəˈpoʊzəl/	提議 /提议, 建議 /建议

视频中出现的短语动词

单词	释义
end up 动词	到达
go back 动词	回去, 返回
pick up 动词	拾取, 撿 /捡

值得反复跟读的句子

视频中简短而完整的句子，可以直接用在日常对话里：

Don't start talking about your dog or something.
What did you do?
Let's take a look at my response.

视频中的语法

说话人最常用的结构，并附上视频中的原话：

结构	视频中的用法
被动语态 be + 过去分词 — 强调发生了什么，而不是谁做的	was given · isn't set · were assigned
现在完成时 have/has + 过去分词 — 过去发生但与现在仍有关联的事	I've noticed · I've gained · i've experienced

需要注意的发音

说话人用了 46 次缩略和弱读形式，例如 gonna, don't, I'm。请按听到的简短形式来说。

“sh” 和 “zh” 音: internship /ˈɪntɜːnʃɪp/, passion /ˈpæʃən/, explanation /ˌɛkspləˈneɪʃən/, exposure /ɪkˈspəʊ.ʒə(ɹ)/, efficient /ɪˈfɪʃənt/
长单词——注意重音位置: behavioral /bɪˈheɪvjəɹəl/, infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, explanation /ˌɛkspləˈneɪʃən/, potentially /pəˈtɛnʃ(ə)li/, communicate /kəˈmjuːnɪkeɪt/

中文母语者容易读错的音：

/v/ — 不要读成 /w/，上齿轻触下唇: interviewer /ˈɪntɚvjuɚ/, behavioral /bɪˈheɪvjəɹəl/, server /ˈsɝvɚ/, resolve /ɹɪˈzɑlv/, solve /sɒlv/
词尾辅音 — 要读清楚，后面不要加元音: framework /ˈfɹeɪm.wɜːk/, internship /ˈɪntɜːnʃɪp/, demonstrate /ˈdɛm.ənˌstɹeɪt/, implement /ˈɪmpləmənt/, resolve /ɹɪˈzɑlv/
/r/ 和 /l/ 的区别: behavioral /bɪˈheɪvjəɹəl/, resolve /ɹɪˈzɑlv/, proposal /pɹəˈpoʊzəl/, partially /ˈpɑɹʃəli/, correlation /ˌkɔɹ.əˈleɪ.ʃən/

如何用这段视频练习

先完整听一遍视频，不要开口，记下不认识的单词。
先用 0.75 倍速逐句跟读，熟练之后再回到正常速度。
录下自己的声音并与原声对比，特别注意 interviewer, framework, deploy 这类单词。

什么是跟读法？

跟读法 (Shadowing) 是一种有科学依据的语言学习技巧，最初开发用于专业口译员的培训，并由多语言者Alexander Arguelles博士普及。这个方法简单而强大：您在听英语母语原声的同时立即大声重复——就像是一个延迟1-2秒紧跟说话者的影子。与被动听力或语法练习不同，跟读法强迫您的大脑和口腔肌肉同时处理并模仿真实的讲话模式。研究表明它能显着提高发音准确性，语调，节奏，连读，听力理解和口语流利度——使其成为雅思口语备考和真实英语交流最有效的方法之一。

影子跟读法: 阅读完整分步指南 →

跟读练习: Cracking the Behavioral Interview for Software Developers - 通过视频学习英语口语

Answering behavioral interview questions is shockingly uncomplicated

How To Land Your First Junior Dev Role

SOFTWARE ENGINEER Interview Questions & TOP SCORING ANSWERS!

Ace every UX/UI design interview like THIS

Former Amazon Recruiter Explains the Perfect "Tell me about Yourself" Answer (2026)

I'm an ex-Google interviewer. You're doing LeetCode wrong.

How AI Is Ruining Job Interviews

Google product manager behavioral interview (Top 5 questions)

How to succeed in your JOB INTERVIEW: Situational Questions

Phlebotomy Job Interview Questions and Answers! Get hired!

15 Common Health and Safety Interview Questions and Answers - Safety Training

SOC Analyst: Top Interview Questions & Answers (2025)

本课的词汇与口语要点

视频中的重点词汇

视频中出现的短语动词

值得反复跟读的句子

视频中的语法

需要注意的发音

如何用这段视频练习

什么是跟读法？