쉐도잉 연습: 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
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
B225
14 문장
TOEFL Speaking 2026 Task 2 | Interview Practice #190 | Sample Answers
TOEFL PrepInterview 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
214 문장
Phlebotomy Job Interview Questions and Answers! Get hired!
Business EnglishInterview EnglishUniversity Students
B21
193 문장
SOC Analyst: Top Interview Questions & Answers (2025)
Business EnglishInterview EnglishUniversity Students
B26
67 문장
How to Ace an Interview: 5 Tips from a Harvard Career Advisor
Business EnglishInterview EnglishUniversity Students
C11
674 문장
FULL Data Science Mock Interview | SQL, Statistics, Business
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ɚ/ | 면접관 |
| deploy 동사 | /dɪˈplɔɪ/ | 배치하다 |
| server 명사 | /ˈsɝvɚ/ | 서버, 봉사기 |
| passion 명사 | /ˈpæʃən/ | 열정 |
| resolve 동사 | /ɹɪˈzɑlv/ | 해결하다 |
| stack 명사 | /stæk/ | 무더기 |
| confuse 동사 | /kənˈfjuːz/ | 혼란시키다 |
| topic 명사 | /ˈtɑpɪk/ | 화제, 주제 |
| proposal 명사 | /pɹəˈpoʊzəl/ | 제안, 구혼 |
| cloud 명사 | /ˈklaʊ̯d/ | 구름 |
| infrastructure 명사 | /ˈɪnfɹəˌstɹʌkt͡ʃə/ | 기반시설, 기간시설 |
| explanation 명사 | /ˌɛkspləˈneɪʃən/ | 설명 |
| exposure 명사 | /ɪkˈspəʊ.ʒə(ɹ)/ | 노출, 로출 |
| efficient 형용사 | /ɪˈfɪʃənt/ | 효율적인 |
| skill 명사 | /skɪl/ | 기술, 스킬 |
영상에 나오는 구동사
| 단어 | 뜻 |
|---|---|
| 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/
한국어 화자가 어려워하는 소리:
- /f/ — ㅍ(/p/)으로 바꾸지 말고 윗니를 아랫입술에 대기: framework /ˈfɹeɪm.wɜːk/, confuse /kənˈfjuːz/, infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, helpful /ˈhɛlp.fl̩/, efficient /ɪˈfɪʃənt/
- /v/ — ㅂ(/b/)과 구별하기: interviewer /ˈɪntɚvjuɚ/, behavioral /bɪˈheɪvjəɹəl/, server /ˈsɝvɚ/, resolve /ɹɪˈzɑlv/, solve /sɒlv/
- /z/ — ㅈ이 아니라 성대를 울리는 /s/: resolve /ɹɪˈzɑlv/, confuse /kənˈfjuːz/, proposal /pɹəˈpoʊzəl/, presentation /ˌpɹɛzn̩ˈteɪʃn̩/, modernization /ˌmɑdɚnɪˈzeɪʃn̩/
이 영상으로 연습하는 방법
- 먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
- 0.75배속으로 한 문장씩 섀도잉을 시작하고, 익숙해지면 보통 속도로 돌아갑니다.
- 자신의 목소리를 녹음해 원본과 비교하고, interviewer, deploy, server 같은 단어에 특히 주의합니다.
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.