Pratique du Shadowing: I ask this question to every Backend Engineer I interview - Apprendre l'anglais à l'oral avec la vidéo
Création de la leçon...
1
What's going on guys?
2
My name is Hussain and I thought I'm gonna make a little bit of a lighter weight video for you guys today.
3
Taking a break from the pre-search of back-end engineering, right?
4
Those can exhaust your mind when you watch these videos and keep learning and learning and learning.
5
So I thought I'd talk to you about my interviewing techniques.
6
And by no means, it's not perfect.
7
And I don't think there is a perfect interview question that you need to memorize to get any job you want.
8
Those might be shortcuts where you learn certain thing and you know what the interviewer will ask.
9
And based on that, you can guess or answer and memorize these things.
10
But I don't think this is a good strategy in general.
11
But that being said, my approach is instead of asking,
12
oh, solve Dicestra algorithm or do a quick sort algorithm,
13
which can be easily memorized if you think about it, right?
14
and as a result, if you ask these kind of questions
15
and the candidate just memorized them and happened to guys read or take these courses, right?
16
These algorithm courses and come to an interview and nail the interview.
17
Yeah, how do you know they are good?
18
They might have been able to solve these algorithms, but it doesn't prove that they have the capability to think on themselves.
19
They have the abilities to have analytical thinking.
20
So that's the question I ask.
21
I'm going to tell you in a minute, but it's a very open-winded question.
22
And I tailor this question specifically to the back end,
23
but I tweak it a little bit based on how the interview is going.
24
And the reason I make it
25
so open-minded is the candidate will not be able to kind of give one answer and this is the right answer.
26
Because guess what?
27
That question doesn't have an answer.
28
It just has like multiple thousands of answers.
29
And as a result, you can just gauge your interviewee.
30
You can gauge your candidate skills.
31
You can gauge how much they know.
32
You can gauge how willing are they to be pragmatic on their solutions.
33
All right.
34
So three minutes and we didn't ask that question.
35
The question is as the following.
36
given an
37
architectural system there is a database
38
and there is a back end web application right the database
39
could be postgres sql server could be mysql anything you want there is a database there is a web server
40
that is consuming this database right at the backend could be node.js could be django java anything you prefer
41
and there's in front of that there is a reverse proxy
42
that does load balancing this thing and i don't specify details
43
if you notice i just say very high level details right
44
and then this reverse proxy could be nginx of hl proxy could be caddy i just give them examples right
45
and then finally there is this application
46
right this the client application could be a desktop application could be a web browser
47
and the reason i don't say one thing is just to confuse them even more
48
because there there are just
49
if you pick a web versus desktop the branch first of
50
all the candidate will go to the branch they are most comfortable
51
which is something i want to know second thing is they
52
if they go to the web that's not wrong it's just
53
i would i want to know where they're going after that right it's just fascinating to have a discussion.
54
So this is the stack, right?
55
And I told them, I told the candidates, hey, you're responsible for the whole stack.
56
I don't like the word full stack engineer,
57
just because I don't think there is someone who can be adept in the whole stack.
58
Yeah, you can know about the whole thing,
59
but to be very well a master on certain thing, you have to pick one thing and dive deep into it.
60
There's nothing wrong with being a full stack engineer.
61
I'm just saying you will be a generalist at best, right?
62
That's my idea, right?
63
But yeah, so you're responsible for the whole stack.
64
And now I just say, here's what happened.
65
Here's the problem.
66
My user has this application all the way here, and they're clicking on a button, right?
67
And this button, the moment they click on this button,
68
the application freezes for 60 seconds, exactly 60 seconds.
69
And then the response comes back and a table is displayed with the results.
70
So this button is responsible to display the results.
71
So I say this is the question.
72
Where where where what do you do to identify the performance problem in the whole stack
73
and I just let them run with it obviously there is no right
74
or wrong answer the problem right could be in the front-end
75
application could be in the reverse proxy there's the reverse proxy could be choking on something
76
that the web server could be processing this stuff
77
and it could be that the database could be just a slow database query
78
that doesn't have indexes or could be we're retrieving too much information
79
or could be we're doing something any anything in this stack right
80
and and based on
81
that it is fascinating for the past 16 years from of
82
my career the different answers i get on these questions
83
and based on that i i have a gut feeling to okay let's hire this guy
84
or gal it's just a gut feeling at the end of the day because
85
oh all right you you will notice that
86
if someone is is really interesting databases they will spend
87
so much time here all their time
88
so okay i might do this i might do this i
89
might go do database tuning i might i might actually uh enable uh database tracing
90
and see how the squares look like i i'm gonna see they've spent a lot of time and
91
if they're they're really passionate about front-end engineering you will see most of their time spent on the front end
92
and this is okay i'm gonna look at div top uh div tops div tools
93
and i do all
94
that stuff i'm gonna check all these networking i'm gonna check the javascript stack i'm gonna check the event loop
95
and see if i'm doing something wrong and and
96
and sometimes they say stuff i don't even know like uh i'm gonna check react components
97
which i don't i don't know anything about right so so yeah it's just it's so
98
and as they took through the stack i see their eyes light up in certain areas
99
and this is where i know this guy
100
or gal is really passionate about this area right
101
because they're spending a lot of time just discussing this stuff right
102
and if they gloss over this thing doesn't mean they are bad it's just they're not interested
103
and that's absolutely fine right
104
so some people spend a lot of time in the reverse proxy
105
and my god i met one gal she was
106
so good she broke down she spent almost like 25 minutes talking about the reverse proxy
107
and how she can optimize it i was baffled she was
108
so good yeah she ended up accepting another offer though
109
but uh yeah
110
so that's that's fascinating all this stuff is fascinating to me
111
that's what's the question i ask guys in an interview again
112
it doesn't give you it doesn't give you any it gives you some indication
113
but i don't think there is a question
114
that you can ask that's the gal i want
115
or that's the guy i want i don't think they exist there's there is no way way to find
116
if this person fits your job you can ask them technical
117
question all all you want it's like oh what is
118
and sometimes i do that's like
119
if they they uh sometimes i like to make the candidate uncomfortable a little bit like
120
if they spend a lot of time in their front end i know they don't know much about backing
121
so i ask them very very stupid questions
122
that i know they're not gonna answer
123
but i just want them to feel a little bit at
124
ease right it's just it's just an asshole move from me
125
and it's like okay what what what is uh talk to
126
me about repeatable read isolation level for example in databases and
127
when we're going to use it obviously this is a little bit of a very technical question
128
and specifically to the relational databases right but i like to ask this question
129
but they if they didn't answer that does not mean they don't get the job
130
or they are bad not at all right and most engineers that interview for a long time understand this thing
131
there's there's no way it's always a gamble
132
if we hire someone it's always about how you feel gut feeling
133
and gary v actually says that sometimes says okay i
134
if i look at someone he's even at the extreme end it's like he look at someone
135
and say okay you're hired because he quickly fires someone
136
if it doesn't if they they don't perform he doesn't have a problem with
137
that right so this is his approach so he hire hire hire her and he doesn't have a problem with firing.
138
So he doesn't have a problem with hiring.
139
He doesn't have a problem.
140
It's like he chose a trial based on his gut feeling, right?
141
And yeah, so that's the idea of the interview.
142
I hope it gives you some sort of idea.
143
If you're interviewing for a job, just be yourself.
144
And if you're truly to yourself, you're enjoying engineering, there is a job out there for you that just fits you and just be kind,
145
be nice, be down to earth.
146
And if you know something, if you don't know something, just say, I don't know.
147
That's absolutely fine.
148
It doesn't mean anything, right?
149
If the interviewee, if the interviewer asking you difficult questions just for the sake of they showing their skills,
150
then I don't think that's a good interviewer either.
151
So it's a balance.
152
I don't know.
153
So I don't think there is a way to pass an interview, right?
154
A sure thing way to pass an interview.
155
Yeah, you can memorize all the algorithms you want, but I never ask any algorithm question in my job or even my previous job for that matter.
156
But yeah, guys, that's a quick video today.
157
I hope you have a wonderful Wednesday.
158
Today's Wednesday.
159
And I'm going to see you in the next one.
160
I had to head back to work it's around 6 in the morning
161
just thought I'm gonna make a video for you guys I'll see you in the next one
162
you guys stay awesome, goodbye
Why practice speaking with this video?
Practicing your spoken English using video content like this one can significantly enhance your fluency and comprehension. Engaging with authentic materials allows you to hear natural speech patterns and contextual language use, making it easier for learners to pick up real-life conversation skills. By participating in a technique known as shadow speech, where you mimic the speaker’s pace and intonation, you improve not only your speaking abilities but also your listening comprehension. This method is particularly beneficial for IELTS speaking practice, as it helps refine your ability to respond spontaneously and clearly in high-pressure situations.
Grammar & Expressions in Context
Throughout the video, the speaker employs several key grammatical structures and expressions that are valuable for English learners. Here are a few noteworthy examples:
- Present progressive tense: The use of "are learning" demonstrates actions that are currently happening. This tense is crucial for discussing ongoing practices, such as “I am practicing my speaking skills.”
- Conditional phrases: Phrases like "if you notice" indicate hypothetical scenarios, which can help learners understand how to express conditions and choices, e.g., “If you want to improve, practice often.”
- Question formation: The speaker frequently uses open-ended questions, such as "How do you know they are good?" This structure encourages learners to formulate their responses more dynamically, an essential skill for IELTS speaking practice.
- Modal verbs: Expressing ability, necessity, or possibility with modals like "can" and "might," allows learners to articulate potential outcomes and suggestions effectively, helping them become more versatile speakers.
Common Pronunciation Traps
When engaging with this video, learners may encounter various pronunciation challenges. Here are a few tricky words and phrases to pay attention to:
- "Dijkstra": This algorithm name can be difficult to pronounce for non-native speakers; focus on the 'D' sound at the beginning.
- "Postgres": The pronunciation can vary, so listening carefully to how it's articulated in context will help solidify your understanding.
- "Analytical": Make sure to emphasize the 'lyt' part to avoid mushing the syllables together.
- Technical terms: Words related to backend engineering, such as "database" and "server," require clear enunciation to ensure clarity in both conversations and explanations.
By incorporating the techniques discussed in this video and utilizing a shadowspeaks approach to enhance your practice, you'll be well on your way to achieving greater confidence and proficiency in your spoken English skills.
Qu'est-ce que la technique du Shadowing ?
Le Shadowing est une technique d'apprentissage des langues fondée sur la science, développée à l'origine pour la formation des interprètes professionnels. Le principe est simple mais puissant : vous écoutez de l'anglais natif et le répétez immédiatement à voix haute — comme une ombre suivant le locuteur avec un décalage de 1 à 2 secondes. Les recherches montrent une amélioration significative de la précision de la prononciation, de l'intonation, du rythme, des liaisons, de la compréhension orale et de la fluidité.