Shadowing Practice: Cracking the Behavioral Interview for Software Developers - Learn English Speaking with Video

Creating lesson...
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.

Vocabulary and speaking notes for this lesson

This speaking lesson is built on the video “Cracking the Behavioral Interview for Software Developers”. The speaker keeps coming back to these words: answer, interview, app, technical, usually. This video has 119 sentences and 1568 words to shadow. The speech runs for 7:52. The speaker talks fast, about 199 words per minute, so expect linked and reduced sounds. 83% of the words are among the 3,000 most common in English; the rest is worth studying before you start.

Key vocabulary in this video

15 words from the video worth learning, with pronunciation and meaning:

WordPronunciationMeaning
interviewer noun/ˈɪntɚvjuɚ/One who interviews.
behavioral adjective/bɪˈheɪvjəɹəl/Of or relating to behavior.
framework noun/ˈfɹeɪm.wɜːk/A support structure comprising joined parts or conglomerated particles and intervening open spaces of similar or larger size.
deploy verb/dɪˈplɔɪ/To prepare and arrange (originally military unit or units, i.e., to array troops) for use.
internship noun/ˈɪntɜːnʃɪp/A job taken by a student in order to learn a profession or trade.
server noun/ˈsɝvɚ/A program that provides services to other programs or devices, either in the same computer or over a computer network.
passion noun/ˈpæʃən/A true desire sustained or prolonged.
demonstrate verb/ˈdɛm.ənˌstɹeɪt/To show how to use (something).
implement verb/ˈɪmpləmənt/To bring about; to put into practice; to carry out.
resolve verb/ɹɪˈzɑlv/To find a solution to (a problem).
stack noun/stæk/A large pile of hay, grain, straw, or the like, larger at the bottom than the top, sometimes covered with thatch.
gauge noun/ˈɡeɪd͡ʒ/A measure; a standard of measure; an instrument to determine dimensions, distance, or capacity; a standard
confuse verb/kənˈfjuːz/to puzzle, perplex, baffle, bewilder (somebody); to afflict by being complicated, contradictory, or otherwise difficult to understand
assign verb/əˈsaɪn/To designate or set apart (something) for some purpose.
topic noun/ˈtɑpɪk/A subject; a theme; a category or general area of interest.

Phrasal verbs you will hear

WordPronunciationMeaning
build out verbTo develop or expand (a system, structure, project, etc.).
end up verbTo bring to a conclusion.
go back verbTo return to a place or state after having been there at a previous time.
pick up verbTo lift; to grasp and raise.
set up verb/ˌsɛt ˈʌp/To make ready for use.

Sentences worth repeating

Short, complete lines from the video that you can reuse in everyday conversation:

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

Grammar in this video

The structures the speaker uses most, with the exact words from the video:

StructureIn the video
Passive voice be + past participle — the focus is on what happens, not who does itwas given · isn't set · were assigned
Present perfect have/has + past participle — a past action that still matters nowI've noticed · I've gained · i've experienced

Pronunciation to watch

The speaker uses 46 contractions and reduced forms, such as gonna, don't, I'm. Say them the short way, as you hear them.

  • The “sh” and “zh” sounds: internship /ˈɪntɜːnʃɪp/, passion /ˈpæʃən/, explanation /ˌɛkspləˈneɪʃən/, exposure /ɪkˈspəʊ.ʒə(ɹ)/, efficient /ɪˈfɪʃənt/
  • Long words — get the stress right: behavioral /bɪˈheɪvjəɹəl/, infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, explanation /ˌɛkspləˈneɪʃən/, potentially /pəˈtɛnʃ(ə)li/, communicate /kəˈmjuːnɪkeɪt/

How to practise with this video

  1. Listen to the whole video once without speaking and note the words you do not know.
  2. Start at 0.75× speed, shadow it sentence by sentence, then go back to normal speed once it feels easy.
  3. Record yourself and compare with the original, paying attention to words like interviewer, behavioral, framework.

What is the Shadowing Technique?

Shadowing is a science-backed language learning technique originally developed for professional interpreter training and popularized by polyglot Dr. Alexander Arguelles. The method is simple but powerful: you listen to native English audio and immediately repeat it out loud — like a shadow following the speaker with just a 1–2 second delay. Unlike passive listening or grammar drills, shadowing forces your brain and mouth muscles to simultaneously process and reproduce real speech patterns. Research shows it significantly improves pronunciation accuracy, intonation, rhythm, connected speech, listening comprehension, and speaking fluency — making it one of the most effective methods for IELTS Speaking preparation and real-world English communication.

Shadowing technique: read the full step-by-step guide →