シャドーイング練習: Cracking the Behavioral Interview for Software Developers - 動画で英語スピーキングを学ぶ
レッスンを作成中...
1
what's up guys today we're gonna be doing something a little different
2
but I feel like it's gonna be super helpful a lot of engineers can crush it on the technical interview
3
but when it comes to the behavioral part that's where a lot of people struggle
4
and I know candidates who did great on the technical interview
5
but they got a rejection
6
because they failed on the behavioral part they weren't able to demonstrate
7
that they had proficient communication skills or how well they handle certain situations
8
and that's what the behavioral interview gauge is for
9
because you can be a technical genius but
10
if you can't convey what you're trying to say it's going to be hard to work on a team
11
and I'll be the first to admit it I'm not great at just thinking of examples right on the spot
12
so usually how I prepare for an interview
13
and how well I do on it usually have a direct correlation
14
so before going into an interview where I know I'll be ask situational questions I'll usually brainstorm
15
and think of about eight to ten examples from my career that can be used to answer different styles of questions.
16
Anything from conflict management to a time where I made a good technical suggestion
17
because a lot of times you can mold your situations to what the question is asking
18
and what I've noticed is that the best answers usually have a story behind it.
19
Obviously you don't want to add too much fluff to your answer
20
or diverge away too far from what the question is asking
21
but if you can kind of paint a picture of the solution to your interviewer
22
that usually leads to better results
23
so in this video I'm gonna give myself a few prompts
24
and answer them as
25
if this were a real interview before we get into the video make sure you guys hit the like button
26
so I know you guys like this kind of video
27
and let me know in the comments if you'd like to see more
28
so the first question is gonna be tell me about yourself this is the question
29
that most behavioral interviews start with now it's important to mention that even though these are behavioral interviews,
30
they will still have some technical aspects to them.
31
So let's take a look at how I answered this question.
32
Hey, my name is Sam.
33
I'm a software engineer and I enjoy solving complex problems.
34
I have experience as a full stack web app developer
35
and I enjoy working with all layers of the stack and I enjoy building out user -friendly efficient websites.
36
My passion for web app development started
37
when I was doing my internship at AWS
38
and I was given a solo project to work on for the entirety of the internship
39
and this really gave me full ownership over everything from the design decisions to the actual coding of it
40
and I was also able to gain a lot of experience and exposure to different AWS cloud computing tools.
41
After my internship I decided that this is what I wanted to do as a career
42
and since then I've gained about three years of experience building
43
out dozens of different applications at my current company i'm helping
44
out with the modernization of our existing infrastructure this includes building
45
out new microservices as well as updating existing ones the technologies i've experienced with include dotnet for building out apis
46
and our server side code sql with mysql oracle and sql server as well as experience with different various javascript frameworks,
47
including Vue .js and Angular.
48
So I believe my experience and my passion would make me a great asset for your company.
49
So in my answer, I tried to keep it short and sweet.
50
I didn't get into my whole life story, even though it is a tell me about yourself.
51
Keep it relevant.
52
Don't start talking about your dog or something.
53
You guys think I'm joking, but I've actually heard people say that when I've been in group interviews.
54
And I would say a sweet spot for this question would be a minute and a half, maybe two minutes.
55
Again, that isn't set in stone.
56
These are kind of like more like guidelines, right?
57
Have you ever seen Pirates of the Caribbean, right?
58
These aren't rules.
59
They're more like guidelines.
60
All right, the next question is going to be, tell me about a time you had to persuade someone at work.
61
What did you do?
62
Let's take a look at my response.
63
At my previous company, our team supported 20 to 30 different web applications.
64
And there was really no uniformity in terms of what front -end JavaScript framework we could or should use.
65
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.
66
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
67
understanding of it before you can even start to implement that feature.
68
So this potentially increased the development time by a lot.
69
So my proposal was to just have all our apps be written in Vue .js
70
because it's something that I had experience with.
71
I thought it was fairly easy to pick up.
72
It's a lightweight app and it's pretty easy to inject into existing applications.
73
So what I did was I created a little mini demo presentation
74
and I set up a meeting between my team and my manager
75
and just demonstrated the pros and cons of using that framework.
76
So the result of that was my manager was on board
77
and we decided to use Vue .js for all our new development.
78
Again, that was about a minute and a half to answer it and it was told like a story.
79
I explained what the problem was and what I did to resolve
80
that problem and showed how I made a lasting positive impact to the company.
81
All right, the last question we're going to look at is tell me about a time you failed at work
82
and what did you learn from it?
83
So this one time I was assigned the task of implementing a new feature into one of our applications.
84
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
85
because you always want to keep your master branch deployable as well as in sync with what's in production.
86
Also, if we deployed this app with this feature being partially done, it would break the application.
87
But this was an app that barely ever got updated, so I figured I'd be all right
88
but of course we had an emergency bug fix
89
that had to be made and I was like we actually can't deploy it
90
because the app is gonna break luckily with source control you are able to go back
91
and we were able to add
92
that change to where I started working on the future
93
but in the future I learned that in order to you know
94
if I wasn't making any changes first create a branch off of master
95
and deploy to that branch and then when you're finally done with the future then merge the changes back into master.
96
Now a potential issue to this answer is that it assumes that the interviewer knows how Git works.
97
Most likely you're gonna be doing one of these interviews with another dev
98
so I mean they probably know how Git works but it's possible
99
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.
✨ おすすめ動画
B21
405 文
Answering behavioral interview questions is shockingly uncomplicated
Business EnglishInterview EnglishUniversity Students
B22
12 文
Self introduction BAIRES DEV study
Business EnglishInterview EnglishUniversity Students
B23
63 文
How To Land Your First Junior Dev Role
Business EnglishInterview EnglishUniversity Students
B21
202 文
SOFTWARE ENGINEER Interview Questions & TOP SCORING ANSWERS!
Business EnglishInterview EnglishUniversity Students
B2218 文
Ace every UX/UI design interview like THIS
Business EnglishInterview EnglishUniversity Students
B22
125 文
Former Amazon Recruiter Explains the Perfect "Tell me about Yourself" Answer (2026)
Business EnglishInterview EnglishUniversity Students
B21
22 文
I'm an ex-Google interviewer. You're doing LeetCode wrong.
Business EnglishInterview EnglishUniversity Students
B21
79 文
How AI Is Ruining Job Interviews
Business EnglishInterview EnglishUniversity Students
B22
8 文
Google product manager behavioral interview (Top 5 questions)
Business EnglishInterview EnglishUniversity Students
B22
281 文
How to succeed in your JOB INTERVIEW: Situational Questions
Business EnglishInterview EnglishUniversity Students
B22
214 文
Phlebotomy Job Interview Questions and Answers! Get hired!
Business EnglishInterview EnglishUniversity Students
B2173 文
15 Common Health and Safety Interview Questions and Answers - Safety Training
Business EnglishInterview EnglishUniversity Students
このレッスンの語彙とスピーキングのポイント
このスピーキングレッスンは、動画「Cracking the Behavioral Interview for Software Developers」を教材にしています。 繰り返し出てくる語は次のとおりです：answer, interview, app, technical, usually。 この動画には、シャドーイング用の文が119文、単語が1568語あります。 音声の長さは7:52です。 話す速さは速く、1分あたり約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/ | 激情 |
| implement 動詞 | /ˈɪmpləmənt/ | 実行する, 実現する |
| resolve 動詞 | /ɹɪˈzɑlv/ | 解く, 分解する |
| stack 名詞 | /stæk/ | 塚 |
| confuse 動詞 | /kənˈfjuːz/ | 混乱させる |
| assign 動詞 | /əˈsaɪn/ | 割り当てる |
| topic 名詞 | /ˈtɑpɪk/ | 話題, テーマ |
| proposal 名詞 | /pɹəˈpoʊzəl/ | 提案, 求婚 |
| cloud 名詞 | /ˈklaʊ̯d/ | 雲, 雲霞 |
| infrastructure 名詞 | /ˈɪnfɹəˌstɹʌkt͡ʃə/ | インフラストラクチャ, インフラ |
動画に出てくる句動詞
| 単語 | 意味 |
|---|---|
| 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 |
注意したい発音
話し手はgonna, don't, I'mなど、短縮形や弱形を46回使っています。聞こえたとおりの短い形で発音しましょう。
- 「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/
日本語話者が苦手な音：
- /r/ と /l/ の区別 — /l/ は舌先を歯茎につけ、/r/ はどこにもつけない: behavioral /bɪˈheɪvjəɹəl/, resolve /ɹɪˈzɑlv/, proposal /pɹəˈpoʊzəl/, partially /ˈpɑɹʃəli/, correlation /ˌkɔɹ.əˈleɪ.ʃən/
- /v/ — /b/ にならないように、上の歯を下唇に当てる: interviewer /ˈɪntɚvjuɚ/, behavioral /bɪˈheɪvjəɹəl/, server /ˈsɝvɚ/, resolve /ɹɪˈzɑlv/, solve /sɒlv/
- /f/ — 「フ」ではなく、上の歯と下唇で出す: framework /ˈfɹeɪm.wɜːk/, confuse /kənˈfjuːz/, infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, helpful /ˈhɛlp.fl̩/, efficient /ɪˈfɪʃənt/
この動画での練習方法
- まず声を出さずに動画を最後まで聞き、知らない単語をメモします。
- まず0.75倍速で一文ずつシャドーイングし、慣れてきたら通常の速度に戻します。
- 自分の声を録音して元の音声と比べます。interviewer, framework, deployなどの単語に特に注意しましょう。
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。