シャドーイング練習: The Essential UX Interview Questions (And How To Answer Them!) - 動画で英語スピーキングを学ぶ
練習モードを選ぶ
各モードは全画面の練習ルームで開きます。
199 文
文が短すぎたり長すぎる場合は、Editをタップして調整してください。
1
What are some of the most common questions
2
that come up in a UX design interview and how should you go about answering them?
3
In this video we'll break down some of the most important questions
4
that I hear all the time and equip you with the mindset and tactics to answer them successfully.
5
The tips, tactics and mindset that I'm going to share with you come from years of personal experience,
6
being interviewed for UX design roles and hiring UX designers to work with me on my teams.
7
My name is Dee and I've been involved in design leadership and worked as a UX designer for over 12 years.
8
Hopefully the tips I share with you in this video will help you in your UX interview.
9
As you're watching this video, if you have any questions about the tactics I offer, please let us know by writing a question in the comments and we'll get back to you as soon as we can.
10
Let's think first about what a UX hiring manager is really looking to ascertain from you in an interview.
11
What this person is looking to find out is what it will actually feel like to have you working in their team.
12
So as well as technical ability which is also important but not the primary goal in the interview, they want to know what will it feel like to have this person sitting next to me
13
and work with them every day.
14
Can I trust the decisions that they will make when I
15
when I give them work to do and will this person's values
16
and way of working align with what the company wants to achieve and how the company is used to working.
17
It's really important to get into the mindset of the interviewer as you prepare
18
and think about how you will answer these kinds of questions
19
because even though the interviewer will ask you questions
20
that sound quite specific
21
and even technical what they're trying to find out is how you think how you work
22
and less about the technical side and more about you who you are
23
and how you will fit into
24
that team it's important to keep this in mind as i'm detailing each of these common interview questions
25
and how you should answer them and with
26
that out of the way let's dive in to question number
27
one one of the most commonly asked questions in a ux interview what is your favorite digital product and why
28
and the important thing to note with a question like this
29
is they don't really want to know what your favorite digital product is
30
but they want to hear you articulate
31
and clearly justify why you think some things are really good in digital products
32
and why other things aren't specifically around UX design.
33
Some really common ways that this is answered
34
which could be considered the wrong way to answer this is to say something like I love Spotify
35
or I love Netflix because they have all the things that I want and I use it every day.
36
This is not an answer that's giving them any information about who you are
37
and how you justify and describe good UX and bad UX features and ideas.
38
what they're really looking for is for you to describe
39
and articulate which ux features and the way
40
that those products were designed to do things like enhance user engagement
41
and get people to keep coming back over
42
and over again to use their product
43
or how some of the features enhance discoverability of new content how i can constantly find new
44
and different types of movies or tv shows
45
or be exposed to a steady stream of new music that you wouldn't otherwise have discovered
46
So they're really wanting you to pinpoint those details and explain and justify why those design decisions were good ones.
47
They don't care so much about which products you love the most, but they want to see that you have an understanding of what it takes to make a product successful.
48
So think about some of your favorite products,
49
look at them and see which one you can craft a a good story around where you can pre-think and identify features,
50
design choices and decisions that have gone into making that product and how you can articulate those well to the interviewer.
51
So the kinds of things you should think about before going
52
into the interview room is what are some of my favorite products and think about why they keep your attention, why maybe you're willing to pay for them,
53
why is it worth it to you, why do you want to share it with friends and what are the things you like to share.
54
Thinking about these kinds of things will help you clearly
55
articulate and justify in a UX interview what the good features are of a particular product that you love.
56
On to the next question.
57
Why do you want to work here?
58
This is a common question in any type of interview
59
and the really common mistake that people make is to explain some logistical reasons why they want that job.
60
Maybe it's in an area that they want to work in or a new city that they want to move to.
61
Maybe it's paying the right amount of money or it's in a field
62
that they really want to branch out into and and become an expert at.
63
So if you're in an interview for a UX job
64
and previously you had a slightly different role you don't want to say oh
65
because I really want to get into UX design.
66
What that says to the interviewer is
67
that you're using them as a step in your own career
68
and that might be true for you but you shouldn't say that in the interview.
69
The company is wanting to pull out of you why they should hire you, what value will you bring to them,
70
how will you be an asset and help them grow their company and their team.
71
So if you give answers to this question
72
that are more about what you want rather than what you
73
can give to them then they won't really learn much about you
74
and why you would be a good fit for their team.
75
So again, pre-thinking about this kind of question is a really good idea.
76
Otherwise you might find yourself giving these first answers that aren't really what they're trying to get out of you.
77
So here's a tangible example.
78
Instead of saying something like, I really want to grow more in my qualitative user research skills, that sounds like this is what you want to get out of the company.
79
You can simply rephrase this in a way that makes it feel more like this is what I can offer to you.
80
So instead you can say in previous roles I didn't get
81
to do as much qualitative research as I would like and it's something I really feel is important.
82
I noticed that your company values qualitative user research
83
and this is something where I feel like I can bring a lot to your team.
84
So here you've actually said the same thing but in a way
85
that sounds much more like you have a passion and experience that you want to bring to this company rather than saying, I want to get this out of your company.
86
So with this kind of question, why do you want to work for this kind of company?
87
Pre-think about your answers and have two or three things ready and make sure you practice in advance.
88
You can rephrase your answers to make sure it sounds not
89
like this is what I want to get out of working for your company, but rather this is what I have to offer if I would come and join your team.
90
Can you walk me through one of the projects in your portfolio?
91
This question is aimed to understand in more detail how you work, how you made the decisions that you do and what it would be like if you joined our team.
92
So the way you shouldn't answer this question is to explain every little logistical step and detail of the project, who was working on it,
93
how many people, what happened, how long, all these little steps.
94
What they're looking for is to see where you made your decisions
95
and why and where things went a little bit off track and how you got them back on track,
96
how you worked with others and what the difficult parts were and how you overcame them.
97
They want to hear the story of you and why you would be awesome to work with.
98
There's also a hidden purpose to this question.
99
They want to see how clearly and well you communicate to them.
100
So when they ask you a question, walk us through this project or tell us this story, they don't really want to hear the full story of everything that happened.
101
They want to see how well you can distill
102
and explain just the relevant details to clearly get the message across that they want to know about.
103
So this is really also testing your ability to communicate with people.
104
So here's a real example of how I would answer that question based on a project that I recently worked on.
105
First I'll do it a bit the wrong way and then I'll show you the right way.
106
So an interviewer has just asked me walk us through this project
107
and the wrong way to answer would be to say okay well this was an information architecture project
108
and first we started with a kickoff with the team
109
and the strategy and direction came from this particular person
110
and then we did some sessions around information architecture
111
and we did this card sorting exercise and on and on and on like that.
112
So what I'm doing there that's not really the right way to answer is explaining the logistics
113
and the fundamental steps of the project, which is not what they're interviewing me for.
114
They don't want to hear all the steps of my project.
115
They want to hear about me and how I do things.
116
So the way I would answer this question well is to say, this was actually a really exciting project.
117
The goal was to create a digital platform for online learning
118
and knowledge sharing the role that I had in that project was to do the information architecture,
119
run some sessions and workshops with multiple team members across the organization,
120
distill and define that information and then come out with a clear concept for how we would move forward with that platform.
121
So here you can actually see I've covered a lot more ground
122
and explained a lot more about the project and my specific role
123
and the things that I did in actually less time than it took for me to
124
ramble through that long logistical description earlier.
125
So that's what they want to see.
126
They're testing your communication skills and they also want to hear about the work that you did, how you did it and the decisions that you made.
127
So with this particular question where they're asking you to walk through a particular project in your CV, think ahead of time which project and how you would distill
128
and define those key moments and key points that they want to hear about who you are, what you can do and how you work.
129
On to the last question, describe a challenge that you faced and how you handled it. And
130
when someone asks you a question like this in the context
131
of a UX interview they're going to be meaning what's a challenge
132
that you faced as a UX designer in the UX design process
133
or a challenge you faced in teamwork but all around UX design.
134
What they're trying to find out is how you handle difficult situations
135
and it's really good to think about this beforehand pick one
136
or two situations that you've faced that were challenging
137
which i'm sure there have been some make sure they're real
138
because it really does pay to be able to answer this honestly
139
and often even if you made a bad decision
140
or failed in the outcome that you were hoping to achieve that's totally fine
141
which is counterintuitive
142
but they're really wanting to hear things like you can admit your mistakes you can pivot
143
and change your ideas when you know you're on the wrong track.
144
You can work well with other people.
145
So even if there's been a difficulty in the team, you can acknowledge that and face that challenge and move forward together.
146
So acknowledging failure or difficulty in this particular situation is not a downside, but actually rather an upside.
147
The biggest mistake that you can make answering this kind of question is to pretend that you've never faced any big challenges, or if you did, you overcame them all with ease.
148
That is not what happens in real teams and real companies.
149
What they really want to see here is that you can acknowledge and admit when you have made a mistake
150
and especially that you can identify when a mistake has been made
151
and then you can move forward and try potential options and ways to get out of it, especially working collaboratively with other people.
152
To give you a real example, the story that I go back to when I'm asked this question in an interview is always back to the same case.
153
There was a project I worked on years ago where we really thought we were on the right track
154
and we were about to launch a new product.
155
We had done user research, we had done multiple concepting stages, been collaborative in the workplace and even built prototypes and tested them
156
and then we realized right at the last minute
157
that we had built our prototypes and done our user research on the wrong topics
158
and we were about to launch this product
159
that was supposed to solve a problem and we realized we had misdefined
160
that problem and we were solving the wrong thing
161
so this was a huge crisis in the team
162
and in the company we all felt like failures
163
and we were afraid to admit it and figure out what we should do
164
so the way that we move forward as a team was to acknowledge
165
that we'd made a mistake that would really affect the success of our launch
166
that we needed to delay hold back and reassess
167
and do some more work to almost start from scratch
168
but use what we had and reframe it in a different way
169
so when i tell this story in interviews the interviewer hears important things about me
170
and how i work that i'm humble enough to admit
171
when i'm wrong that i can take tough decisions to delay
172
and roll back when I think we're not on the right track, that I can work with others
173
and bring other people together with me to help me make those tough decisions
174
and that they could trust working with me as a designer
175
because I know that these big things still won't trip me up.
176
Really try and think back over the work that you've done, different companies or projects you've worked on,
177
even a course that you're a part of or even if you worked for a company where you weren't a UX designer.
178
So find those nuggets that the interviewer will really want to hear about.
179
Not just about the mistakes that you made but how you faced those challenges, what options and alternatives you tried and how you eventually came out the other side.
180
This is where the interviewer really gets to see if you show them what you're really like, how you really work and how you handle tricky situations.
181
Hopefully these tips, stories and recommendations help you to prepare for your next interview.
182
Job interviews can be really daunting, but hopefully knowing what's coming and how to prepare for it can help you feel confident when you walk into the room.
183
If you enjoyed this video, give it a like and subscribe to the Career Foundry channel for more UX and UI content just like this every week.
184
If you're interested in learning more about UX design, Career Foundry have a great free short course.
185
You can sign up by the link in the description below.
186
I would love to know from you in the comments which interview tip was the most valuable to you and why.
187
Thanks so much for watching and I wish you the best of luck in your upcoming UX interviews.
188
See you again soon.
189
My name is Dee and I've got long hair.
190
What they're trying to ascertain...
191
Fine, ascertain sounds so...
192
If you're interested...
193
If you're interested...
194
Slow down.
195
Have any questions about the tactics I offer?
196
You'll oftenly get asked in a UX interview.
197
Oftenly.
198
That's a word.
199
Cut that out.
アプリをダウンロード
流暢に話すために必要なすべて
AI発音採点文ごとに採点
IPA練習すべての音をマスター
単語学習自分の単語帳を作る
単語ゲーム遊びながら覚える
✨ おすすめ動画
B21
116 文
10 CRUCIAL Questions You MUST Ask Your Interviewer (as a UX/UI Designer)
Interview EnglishWorking Adults
B21
405 文
Answering behavioral interview questions is shockingly uncomplicated
Interview EnglishUniversity StudentsWorking Adults
B2182 文
🔥HR Interview Questions and Answers (2025) | Top HR Interview Questions for Freshers | Intellipaat
Business EnglishInterview EnglishUniversity Students
B29
72 文
Why Are You a Good Fit for this Role - How to Answer
American AccentBusiness EnglishInterview EnglishUniversity Students
B22
231 文
My Senior UX Design Interview Experience | tips, questions, prep, & more!
Business EnglishInterview EnglishUniversity Students
B22
141 文
QUALITY CONTROL Interview Questions & Answers! (Inspector, Manager + Assessor Interview Questions!
Business EnglishInterview EnglishUniversity Students
C17
99 文
How to Answer System Design Interview Questions (Complete Guide)
Business EnglishInterview EnglishUniversity Students
B22
195 文
The Emirates Interview Questions That Catch EVERYONE Off Guard
Business EnglishInterview EnglishUniversity Students
B25
320 文
The React Interview Questions You need to Know
Business EnglishInterview EnglishUniversity Students
C12
100 文
How to Answer Situational Questions for Product (PM) Behavioral Interview | Framework + Solution
Interview EnglishUniversity StudentsWorking Adults
B18
61 文
Top UIUX Design Interview Questions Asked in Deloitte, Accenture & Infosys
Business EnglishInterview EnglishUniversity Students
B26
67 文
How to Ace an Interview: 5 Tips from a Harvard Career Advisor
Interview EnglishUniversity StudentsWorking Adults
このレッスンの語彙とスピーキングのポイント
この動画には、シャドーイング用の文が199文、単語が2871語あります。 音声の長さは14:50です。 話す速さは速く、1分あたり約194語です。音のつながりや弱く発音される音が多くなります。 単語の89%は英語の頻出3,000語に含まれるため、語彙は分かりやすいです。
この動画の重要語彙
動画に出てくるやや難しい単語15語を、発音と意味つきで紹介します。
- interviewer /ˈɪntɚvjuɚ/ (名詞) — インタビュアー, 会見者. One who interviews.
- designer /dɪˈzaɪnɚ/ (名詞) — デザイナー, 設計士. A person who designs something, or who designs things as a profession.
- acknowledge /əkˈnɑ.lɪd͡ʒ/ (動詞) — 承認する, 認める. To admit the knowledge of; to recognize as a fact or truth; to declare one's belief in.
- tactics /ˈtæktɪks/ (名詞) — 戦術. The military science that deals with achieving the objectives set by strategy.
- justify /ˈd͡ʒʌstɪfaɪ/ (動詞) — 言い開く. To provide an acceptable explanation for.
- architecture /ˈɑː.kɪˌtɛk.t͡ʃə/ (名詞) — 建築, 建築学. The art and science of designing and managing the construction of buildings and other structures, particularly if they are well proportioned and decorated.
- hire /ˈhaɪɹ/ (動詞) — 借りる. To obtain the services of in return for fixed payment.
- mindset /ˈmaɪn(d)ˌsɛt/ (名詞) — 考え方, 心理. A way of thinking; an attitude or opinion, especially a habitual one.
- skill /skɪl/ (名詞) — 腕, 技. A capacity to do something well; a technique, an ability, usually acquired or learned, as opposed to abilities that are regarded as innate.
- solve /sɒlv/ (動詞) — 解決する. To find an answer or solution to a problem or question; to work out.
- delay /dɪˈleɪ̯/ (名詞) — 遅れ, 遅延. A period of time before an event occurs; the act of delaying; procrastination; lingering inactivity.
- difficulty /ˈdɪfɪkəlti/ (名詞) — 難しさ. The state of being difficult, or hard to do.
- overcome /ˌəʊ.vəˈkʌm/ (動詞) — 克服する, 征服する. To surmount (a physical or abstract obstacle); to prevail over, to get the better of.
- communicate /kəˈmjuːnɪkeɪt/ (動詞) — 伝える. To impart or transmit (information or knowledge) to someone; to make known, to tell.
- prototype /ˈpɹəʊtətaɪp/ (名詞) — プロトタイプ, 原型. An original form or object which is a basis for other forms or objects (particularly manufactured items), or for its generalizations and models.
動画に出てくる句動詞
- find out (動詞) — 見出す, 調べる. To discover, as by asking or investigating.
- look for (動詞) — 探す, 求める. To seek.
- come out /ˌkʌm ˈaʊt/ (動詞) — 出る. To be discovered; to be revealed.
- do in (動詞) — やる. To kill or end; to defeat.
- slow down (動詞) — 遅らせる. To decelerate.
注意したい発音
話し手はthey're, you're, I'mなど、短縮形や弱形を59回使っています。聞こえたとおりの短い形で発音しましょう。
- 「sh」と「zh」の音: passion /ˈpæʃən/, workshop /ˈwɝk.ʃɑp/, recommendation /ˌɹɛkəmɛnˈdeɪʃən/
- 長い単語（アクセントの位置に注意）: articulate /ɑːɹˈtɪk.jə.leɪt/, architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, difficulty /ˈdɪfɪkəlti/, communicate /kəˈmjuːnɪkeɪt/, successfully /səkˈsɛs.fə.li/
この動画での練習方法
- まず声を出さずに動画を最後まで聞き、知らない単語をメモします。
- まず0.75倍速で一文ずつシャドーイングし、慣れてきたら通常の速度に戻します。
- 自分の声を録音して元の音声と比べます。interviewer, designer, acknowledgeなどの単語に特に注意しましょう。
この動画の文法
話し手がよく使っている文型を、動画の実際の表現とともに紹介します。
| 文型 | 動画での表現 |
|---|---|
| 現在完了形 have/has + 過去分詞 — 過去の出来事が今も関係している | I've been involved · have discovered · have gone |
| 受動態 be + 過去分詞 — 誰がするかより、何が起きるかに焦点を当てる | being interviewed · I've been involved · is answered |
| 関係詞節 who / which + 節 — 人や物について情報を加える | ability which is · project, which is |
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。