Shadowing Practice: Ace every UX/UI design interview like THIS - Learn English Speaking with Video
Bir pratik modu seçin
Her mod tam ekran bir pratik odası açar.
218 cümleler
Cümleler çok kısa veya çok uzun ise, ayarlamak için Düzenle'ye tıklayın.
1
Come on in.
2
Hi sir, really excited to be here.
3
So nice to meet you.
4
Uh-huh.
5
We're just looking over your CV.
6
Angst, huh?
7
What kind of surname is that?
8
Yeah, I know.
9
Awful.
10
Yeah.
11
So, Angst, what qualifies you to be our product designer?
12
Yeah, sure.
13
I've been doing UX UI design for the last five years at a range of different companies, startups, scale-ups, even bigger corporations.
14
Sure, sure.
15
Why don't you go ahead and design something for me?
16
Uh, sorry, what?
17
Yeah, design something for me right now.
18
Draw a watering can for us.
19
Uh, sir, all due respect, product design doesn't really work like that.
20
No?
21
Okay, why don't you go ahead and tell me how it works then?
22
Well, as your product designer, my responsibility is to make sure your product takes your users needs into consideration.
23
So I'll conduct extensive usability testing, user research, A-B testing, observe users in their natural environment.
24
One watering can coming up.
25
Product design interviews.
26
They can be scary, and each one can feel completely different compared to the last one that you did.
27
But design interviews don't actually have to be that intimidating.
28
If you're new to the channel, welcome.
29
My name's Leander, and I've been a product designer based in London for the last five years.
30
Over the course of my career, I've done hundreds of interviews.
31
And I can tell you from personal experience that after a while, all product design interviews start to feel very similar.
32
The key to nailing product design interviews is building a foundational understanding in all of the different potential interview stages
33
that you might run into in any given product design interview.
34
And that's exactly what we're going to talk about today.
35
All of the different potential interview stages you might run into as a product designer and how to nail each one.
36
Let's jump in.
37
So typically the first stage is the recruiter screen.
38
This is a relatively informal conversation between you and the recruiter, sometimes the hiring manager, that lasts about 30 minutes
39
and gives them an opportunity to tell you more about the role and for you to ask questions about it.
40
Typically this is not a conversation that focuses on your in-depth experience, but it is a chance for the recruiter to ask some baseline questions to make sure
41
that you actually are a good fit for the role.
42
Some of the questions you might run into during this stage are tell me a bit about yourself.
43
What have you been up to?
44
What are your salary expectations?
45
Do you need visa sponsorship?
46
And maybe, why are you looking for a new role?
47
So when answering the question about your experience and what you've been up to, make this interesting.
48
Actually try to tell a story.
49
Don't just list off your experiences one by one because that's really boring and the recruiter's probably going to fall asleep.
50
And I really like to touch on why I became a product designer in the first place.
51
Switched from project management to design, which allowed me to be more creative, made me feel more connected to the company and the people.
52
And then I also like to talk about why I chose to work at the places
53
that I've worked at previously as a product designer.
54
I really like to work at companies where I feel like the people generally want to be there.
55
Small startups, really fast-paced, high-performance environments.
56
That makes me feel really energetic.
57
It motivates me to go to work.
58
And this is a good opportunity for me to explain this to the recruiter
59
and for the recruiter to understand what drives me
60
and also for the recruiter to feel like I actually care about my job and I want to be there.
61
Now, when talking about why you're looking for a new role, no matter what your circumstances are, I don't care if you got fired.
62
I don't care if you just really want a new job or if you're bored of your current job, always answer this by talking about why you want to work for this specific company that you're talking to.
63
Talk about why this company is exactly the thing that you're looking for, why this team is the right fit, and that is going to make a much better impression on the recruiter.
64
These chats always zip by and it's a really good opportunity for you to ask questions about the company, too, and to genuinely find out if this is a place that you would like to work at.
65
Now once you pass the recruiter screen, stage two of the interview process is usually going to be a portfolio review.
66
This is the technical round of the interview and it's likely going to be with the hiring manager, maybe an engineer, a product manager.
67
A few people from the team will definitely be sitting in on this one.
68
In my experience this round usually consists of two segments.
69
One is always the portfolio review itself
70
and then the other is usually more of a a formal style interview where you're asked questions about your process, how you collaborate, and we can talk about some of those questions now that you might run into.
71
Things like, how do you collaborate with engineers?
72
What's been the most disappointing outcome of one of your designs?
73
Name a time you've disagreed with somebody over a design decision and how you overcame that.
74
How do you deal with negative feedback?
75
It helps a lot to prepare answers to questions like this in advance, and there are plenty of lists on the internet about the questions that you might get asked.
76
I'll definitely include one below in the description, so be sure to have a look at that.
77
Let's just go over a few examples of some good answers to some of these questions
78
and some bad answers to some of these questions.
79
For the question, how do you collaborate with engineers?
80
A bad answer here is any that doesn't indicate that you involve your engineers throughout the entire design process, which is something you definitely should do.
81
And conversely, a good answer is something like, I like to involve my engineers as early in the design process as possible.
82
That gives me an opportunity to talk about any technical challenges we might run into, share my design vision, any ideas, collaborate with the engineers because they might have some good solutions in mind as well.
83
And it just makes it a lot easier then for us to move forward
84
and ensure that we are heading in the same direction and
85
that we don't encounter any difficulties or technical constraints down the line once I've already done all my design work.
86
Let's look at one more.
87
The question, what's been the most disappointing outcome of one of your designs?
88
Now a bad answer here is any that indicates that you didn't actually learn anything from your failure.
89
That's what this question is really asking.
90
It's do you learn something from failure or do you kind of just take it on the chin and move forward?
91
So a good answer here is talking about an experience that was disappointing and talking about what you learned from that experience.
92
And bonus is if you can share a future situation
93
that you found yourself in and you used those learnings to prevent another bad outcome.
94
Now, the other part of this interview stage is the actual portfolio review.
95
Now, I've done an entire video on how I would approach this.
96
You can watch that right here if you haven't seen it already.
97
But the TLDR here is that I would make a presentation.
98
So I'd actually make a slide deck of one
99
or two of my case studies that I can present during this stage of the interview.
100
A couple of tips for this stage.
101
Be prepared for pushback.
102
That's really the point of these interviews.
103
Somebody is going to want to poke holes in your process, and they're going to want to find out why you did the things that you did.
104
They weren't there, remember?
105
And so they don't have all the context.
106
And some of your decisions might not seem as obvious to them as they were to you.
107
Just be ready to answer some tough questions and just justify why you did what you did.
108
It's okay to push back on pushback.
109
That's exactly what these people are looking for.
110
They want to know that you were justified in making the decisions that you made.
111
Now, the third potential stage that you might run into is my least favorite one.
112
And you can ask any designer and they'll probably agree with me here.
113
But that is the design challenge.
114
Now, you're not always going to run into this stage.
115
Some companies just don't do these.
116
And I think they probably don't do them because they know most designers hate doing them.
117
But the design challenge can be one of two things.
118
So it's either going to be a take-home challenge or it's going to be a whiteboarding exercise.
119
We'll talk about the take-home challenge first.
120
This is pretty straightforward.
121
The company is going to give you some kind of prompt, some kind of assignment.
122
It's usually kind of related to what they do, and you're going to have somewhere around a week to complete it.
123
I'm just going to give you a hint.
124
You're going to spend way more time on this than you should.
125
And that's why take-home challenges are probably the most annoying.
126
Even though companies will tell you, oh, we don't want you to spend more than four hours, you're just going to spend more because you want to do your best
127
and you know you're stacked up against other designers and everyone's going to do the same thing.
128
The good news about take-home challenges is
129
that you really can take your time with them and you can use all the resources at your disposal.
130
That includes the internet, your friends, maybe a mentor, and you can refine this as many times as you want to.
131
So you can do a first draft, you can get it reviewed by somebody, you can iterate on that.
132
And so it's really an opportunity for you to do the best possible piece of work that you can.
133
Companies usually give take-home assignments when they want a fully fledged high fidelity solution.
134
So they want to see the UX, but they also want to see the UI.
135
Use resources like Mobbin.
136
I did a whole video on how to copy good UI design.
137
You can watch that here if you haven't seen it already.
138
And just make sure that your solution is justified, that you explain your process, and that it looks really, really good.
139
Now the other kind of design challenge is the whiteboarding exercise
140
and this one is a little bit more subtle
141
and it's really going to depend on the company
142
that you're interviewing at how this is done sometimes it's done
143
in fig jam online sometimes it's done in the office on an actual whiteboard
144
and the point of doing a whiteboarding exercise is twofold the
145
company a wants to see how you collaborate with others
146
because other people will be in the room
147
and you'll have a chance to ask them questions
148
and involve them during the process which you should do
149
and the other reason they do this is they want to see how you solve problems on the fly
150
so they want to see your process for how you approach solving a problem and finding a solution.
151
You can Google UX whiteboarding challenge and you're going to find a ton of resources on how to approach these.
152
Just a couple of tips when it comes to whiteboarding exercises.
153
The first one is don't immediately jump into solutionizing.
154
The team is going to give you some kind of problem to solve.
155
If you jump straight into solutionizing, that's a big red flag for a product designer.
156
The team want you to write down the problem statement and then they want you to gather context.
157
They want you to understand the problem as deeply as you possibly can, ask a ton of questions, gather all of that context, and then they want you to start forming some kind of solution,
158
knowing all of those things that you now know.
159
This is where the other part comes in. Be collaborative.
160
Involve the other people in the room.
161
I said it before, it's a really good opportunity for you to already be collaborative with potential future team.
162
And that leads me to the third tip, which is think out loud.
163
If you're just standing up at a whiteboard and you're silent, no one is going to know what's going on.
164
They're not going to understand your process at all.
165
Talk about everything that you're doing, everything that's going through your head, why you're making certain decisions.
166
The more you talk, the better.
167
And then Tip number four, don't be afraid if they poke holes in your approach.
168
Kind of like the case studies where they ask you a lot of questions and they want you to justify your decisions.
169
There's usually more than one right answer to solving design problems.
170
So don't freak out if they disagree with one of your approaches
171
or they ask you a bunch of prodding questions about why you're doing the things you're doing.
172
Just stay calm, justify your choices, and also take on some feedback from other people in the room if they're giving it to you.
173
That's gold.
174
Now, if you made it to the fourth round, congratulations.
175
You've done very well.
176
You are in typically the final stages of the product design interview process.
177
Now, this is usually an in-person round, and it's typically some kind of panel format where you'll maybe one by one
178
or all together meet a bunch of different people from different teams and to spread across the company.
179
Let me just jump ahead real quick and explain how companies make decisions about hiring people just generally.
180
After the company has interviewed all the candidates in the pool, they'll usually have meetings where they'll stack up all the candidates and rate all of their pros and cons.
181
And that's how they'll make a final decision about who they hire for the job.
182
If there are a few candidates that have gone through the final round, this process is almost never black and white.
183
And there are very small things that might put one or the other candidate just over the line.
184
And that is why it is
185
so important during this final round to let your personality shine through as much as you possibly can.
186
Do your research about who you're going to be talking to.
187
You're almost certainly going to know who that is before the day of the interview.
188
So go on their LinkedIn profiles, see if they've done any talks, see if they've made any videos.
189
Anything that you can use is fuel that you can then bring to the table during these interviews.
190
And you can ask them questions about it.
191
They're going to love that you did some research on them.
192
And it's just going to make for much, much richer dialogue between you and the interviewer.
193
Like I said before, this round is usually more of a culture fit round.
194
So you're not going to be asked any crazy technical questions anymore.
195
That round was already done, but you'll likely face a bunch of different star questions and star questions are any questions that are formatted.
196
Like tell me about a time where you dot, dot, dot.
197
So you can look up star question prompts on the internet.
198
I'll post a couple in the description below just so you have those, but just prepare for as many of them as you possibly can.
199
You can't really go wrong.
200
And even if you're not asked them, they'll still give you some ammo for bringing up different things during the interview process.
201
The last tip I'll give here is to ask as many questions as you possibly can.
202
And don't be afraid to ask tough questions, especially if you're interviewing for a smaller company like a tech startup.
203
Ask questions like, what are some challenges the company is facing right now?
204
What's the toughest obstacle for the company to overcome in the next six months?
205
Talk to me about something the team isn't doing right now that you wish they were doing.
206
This is also a chance for you to interview them a little bit.
207
And you want to make sure that they've thought about these things
208
and that they actually like and care about the place that they're working at.
209
And that's really it.
210
If you've made it this far, congratulations.
211
I hope you get the job.
212
Let me know how it goes.
213
And also let me know if you want me to do a deep dive on any of the topics that we covered, any of the interview stages that we went over during this video, or if it would be helpful for me to give some answers
214
that maybe I would give to some of the questions
215
that we covered and other questions that we didn't cover in this video.
216
Happy to do a video on those, but let me know if it would be helpful in the comments below.
217
As always, guys, best of luck with this and see you very soon.
218
Thank you.
Uygulamayı İndir
Akıcı konuşmak için ihtiyacınız olan her şey
AI TelaffuzHer cümleyi puanla
IPA AlıştırmasıHer sesi ustalaştır
Kelime BilgisiKelime bankanızı oluşturun
Kelime OyunuOynarken öğrenin
FOR YOU
Video Öner
B21
102 cümleler
The UX/Product Design Interview Process Explained (2023) - how I landed multiple FAANG offers
Interview EnglishWorking Adults
B2408 cümleler
Describe Your Work Experience in English. Job Interviews & Networking | Business English
Interview EnglishWorking Adults
B21
199 cümleler
The Essential UX Interview Questions (And How To Answer Them!)
Interview EnglishUniversity StudentsWorking Adults
B21
113 cümleler
Google Interview Tips That Actually Get You Hired
Interview EnglishWorking Adults
B22
75 cümleler
The unfair way I got good at Leetcode
Interview EnglishUniversity StudentsWorking Adults
B22
405 cümleler
Netflix product manager mock interview and tips (with ex-Netflix Lead PM)
Interview EnglishWorking Adults
B26
102 cümleler
How to Ace an Entry Level Interview | Mock Job Interviews | Indeed Career Tips
Business EnglishInterview EnglishUniversity Students
B21
79 cümleler
How AI Is Ruining Job Interviews
Interview EnglishWorking Adults
B21
283 cümleler
My UX Design Case Study Presentation that Got Me Hired | Case Study Walkthrough
Interview EnglishWorking Adults
B21
245 cümleler
QA Automation Interview Questions and Answers
Interview EnglishWorking Adults
B22
328 cümleler
Senior Product Designer Mock Interview: App Critique of Yelp
Business EnglishInterview EnglishUniversity Students
B2370 cümleler
Improve English Speaking Skills | Meeting a girl | Shadowing Practice with a Simple Conversation 💬
Interview EnglishWorking Adults
Bu dersin kelimeleri ve konuşma notları
Bu B2 seviyesindeki konuşma dersi “Ace every UX/UI design interview like THIS” videosuna dayanıyor. En çok tekrarlanan kelimeler: design, interview, product, stage, process. Bu videoda gölgeleme çalışması için 218 cümle ve 2962 kelime var. Konuşma bölümü 12:30 sürüyor. Konuşmacı hızlı konuşuyor, dakikada yaklaşık 237 kelime; bu yüzden birbirine bağlanan ve zayıflayan sesler duyacaksınız. Kelimelerin %88’i İngilizcede en sık kullanılan 3.000 kelime arasında, bu yüzden kelime dağarcığını takip etmek kolay.
Bu videodaki önemli kelimeler
Videodaki en ileri düzey 15 kelime, telaffuzu ve anlamıyla:
| Kelime | Telaffuz | Anlam |
|---|---|---|
| collaborate fiil | /kəˈlæb.ə.ɹeɪt/ | birlikte çalışmak |
| justify fiil | /ˈd͡ʒʌstɪfaɪ/ | haklı göstermek |
| disappoint fiil | /ˌdɪsəˈpɔɪnt/ | düş kırıklığına uğratmak |
| portfolio isim | /pɔːtˈfəʊ.liˌəʊ/ | portföy, cilbent |
| whiteboard isim | /ˈwaɪtbɔɹd/ | beyaz tahta |
| poke fiil | /poʊk/ | dürtmek |
| bore fiil | /boɹ/ | burgulamak |
| stack isim | /stæk/ | yığın |
| constraint isim | /kənˈstɹeɪnt/ | kısıtlama, sınırlama |
| intimidate fiil | /ɪnˈtɪmɪdeɪt/ | sindirmek, yıldırmak |
| surname isim | /ˈsɝˌneɪm/ | soyadı, soyad |
| twofold sıfat | /ˈtuːfəʊld/ | çifte |
| interviewer isim | /ˈɪntɚvjuɚ/ | röportajcı |
| circumstance isim | /ˈsɝ.kəmˌstæns/ | durum, hâl |
| sponsorship isim | sponsorluk |
Duyacağınız deyimsel fiiller
| Kelime | Telaffuz | Anlam |
|---|---|---|
| find out fiil | anlamak, ortaya çıkarmak | |
| look up fiil | /ˌlʊk ˈʌp/ | yukarı bakmak |
Tekrar etmeye değer cümleler
Videodan, günlük konuşmada yeniden kullanabileceğiniz kısa ve tam cümleler:
- Why don't you go ahead and design something for me?
- What have you been up to?
- What are your salary expectations?
- Do you need visa sponsorship?
- Things like, how do you collaborate with engineers?
Bu videodaki dil bilgisi
Konuşmacının en çok kullandığı yapılar, videodaki sözcüklerin aynısıyla:
| Yapı | Videoda |
|---|---|
| Present perfect have/has + fiilin üçüncü hâli — geçmişte olan ama şimdi de önemli olan bir eylem | I've been · I've done · have you been |
| Edilgen yapı be + fiilin üçüncü hâli — kimin yaptığı değil, ne olduğu önemli | were justified · is justified · be asked |
| İlgi cümlecikleri who / which + cümle — bir kişi ya da şey hakkında ek bilgi | process, which is · tip, which is |
Dikkat edilecek telaffuzlar
Konuşmacı you're, don't, I've gibi kısaltılmış biçimleri 83 kez kullanıyor. Bunları duyduğunuz gibi kısa söyleyin.
- “sh” ve “zh” sesleri: foundational /faʊnˈdeɪ.ʃə.nəl/, expectation /ˌɛk.spɛkˈteɪ.ʃən/, shine /ʃaɪn/
- Uzun kelimeler — vurguyu doğru yere koyun: collaborate /kəˈlæb.ə.ɹeɪt/, portfolio /pɔːtˈfəʊ.liˌəʊ/, collaborative /kəˈlæb.ə.ɹə.tɪv/, foundational /faʊnˈdeɪ.ʃə.nəl/, intimidate /ɪnˈtɪmɪdeɪt/
Bu videoyla nasıl çalışılır
- Videonun tamamını konuşmadan bir kez dinleyin ve bilmediğiniz kelimeleri not edin.
- 0,75× hızla başlayın, cümle cümle tekrar edin ve kolaylaşınca normal hıza dönün.
- Kendinizi kaydedin ve orijinaliyle karşılaştırın; collaborate, justify, disappoint gibi kelimelere özellikle dikkat edin.
Gölgeleme Tekniği Nedir?
Gölgeleme, başlangıçta profesyonel tercüman eğitimi için geliştirilen ve çok dilli Dr. Alexander Arguelles tarafından popüler hale getirilen, bilim destekli bir dil öğrenme tekniğidir. Yöntem basit ama güçlüdür: ana dili İngilizce olan bir sesi dinler ve hemen yüksek sesle tekrar edersiniz — konuşmacıyı 1-2 saniye gecikmeyle takip eden bir gölge gibi. Pasif dinleme veya dilbilgisi alıştırmalarının aksine, gölgeleme beyninizi ve ağız kaslarınızı gerçek konuşma kalıplarını eşzamanlı olarak işlemeye ve yeniden üretmeye zorlar. Araştırmalar, telaffuz doğruluğu, tonlama, ritim, bağlı konuşma, dinleme anlama ve konuşma akıcılığını önemli ölçüde geliştirdiğini göstermektedir — bu da onu IELTS Konuşma hazırlığı ve gerçek dünya İngilizce iletişimi için en etkili yöntemlerden biri yapar.