シャドーイング練習: A Day in the Life of an Amazon Software Engineer - 動画で英語スピーキングを学ぶ
レッスンを作成中...
1
Everyone wants to work in big tech because of the beautiful offices and the high salaries, but what is it actually like?
2
Today, I'll be taking you through a realistic day in my life working as a software engineer at Amazon.
3
I want to talk a little bit about what it's like working in big tech.
4
I just hope that this doesn't break any of my already existing code.
5
I've definitely been lingering on leaving Amazon.
6
We need some sort of distraction for everybody.
7
Anything new on YouTube?
8
I just got to the office
9
and today is actually my last day being on call before I hand it over to the next engineer
10
So let's go over everything we're gonna do today
11
So first off I have my one hour on call handover
12
meeting where I go over all the tickets I did
13
and hand over the pending items to the next engineer
14
And then I have some project work that I need to chip away at and another one hour meeting today.
15
So let's go I have this idea, I'm sorry, I'm coming with you.
16
I'm just saying.
17
So, this is cool.
18
Lately, I've been feeling pretty conflicted about work.
19
Some days, the job feels interesting.
20
I get to see my friends, get out of the house.
21
And other days, it feels really procedural and hard to feel excited about.
22
I think like most software engineers, I got into this field because I love to create things.
23
I started programming in high school and things just clicked for me when I started.
24
I found so much joy in watching my code run and solving problems.
25
These days, it's been really hard for me to feel that same excitement at work, and I wonder if that's just how work is.
26
I guess I'm not that passionate about accounting software, but it kind of seems like the people around me are not that excited about it either, so I wonder how they're dealing with it.
27
Maybe work is just going to be work sometimes.
28
Alright, so for my Ops handover meeting, I go over all the tickets that I got this week, especially the SEV2s, which are the critical errors that need immediate attention.
29
I talk about how the issue occurred and what I did to mitigate it
30
and what we can do to prevent it in the future.
31
And then I also discuss all the other tickets
32
that I wasn't able to get to so the next on-call can focus on those.
33
I just turned 25 and I feel like there's probably more out there
34
and I probably should be doing something more stimulating and exciting with my life.
35
It's also weird because I spent four years in university trying to land a software engineering role
36
and I really wanted to work in big tech.
37
I've always admired it in other people and I just always wanted to do it for myself.
38
But now that I'm here, it doesn't really feel as fun as I had envisioned in my head.
39
I've always wanted to make some sort of impact on the world
40
and I've always wanted my work to actually help someone out there.
41
But I kind of feel like working on accounting software that only internal Amazon financial accountants use isn't really for me.
42
It is really boring and sometimes boring is really draining.
43
But then I also feel guilty for complaining about this job
44
that I know so many people want to have and I was once someone really excited to have this job.
45
So I'm still really torn.
46
I wonder if there's other software engineers feeling the same way about their work or maybe it's just me.
47
Anyways, enough of my existential crisis.
48
Let's get back to work.
49
I want to talk a little bit about like what it's like working in big tech and the pros and cons.
50
My very first internship that I got was a very small company of four people.
51
We basically did consulting for a different company.
52
The office that we were in was probably the same size as the room that I'm in right now.
53
I learned a lot in that internship.
54
My project was to make a full stack web page for the clients
55
and it was an admin page so that they could change user information like emails or their username, things like that.
56
When I was done my project, I actually got feedback from the clients.
57
They found my page very useful.
58
It was kind of addicting to know
59
that something I had built was actually being used by somebody else
60
But I did feel like something was missing I really wanted to make big impact
61
and work on something big and cool
62
And I really wanted to work in big tech after this small internship
63
So that year I grinded leek code and practiced behavioral questions and then I landed my amazon internship that year Looking back.
64
I had the most fun during that internship.
65
Everyone I met was so smart and ambitious I was like
66
so inspired by everyone who was here
67
and I also learned an insane amount of information in a short time I literally didn't know what aws was
68
when I started
69
and then I ended up creating full stack applications with aws
70
services like lambda glue S3 I also learned how to write design documents
71
and the behind the scenes side of shipping software like getting changes deployed safely and watching for issues Before they go live.
72
It was really awesome and I felt like I was building something useful I felt like really fulfilled during that internship.
73
So when I returned to Amazon as a new grad, part of me kind of felt like it was gonna be similar to my internship.
74
I knew it wasn't gonna be the same, but I felt like I was gonna have a similar experience and feeling.
75
But what you don't really realize when you join big tech is that it doesn't really correlate to having big impact.
76
Most of the times, big tech companies are so big, they have
77
so many organizations within the company they each run like their
78
own mini companies my organization has about like 300 people
79
which is bigger than a lot of startups i work on
80
a very small part of amazon their financial accounting team the
81
work i do is very specific in terms of the experience
82
that i gain but i don't gain a lot of breadth
83
and because you're working on something so specific the customer is also very specific
84
and it's kind of hard to feel the impact of your work.
85
I kind of feel this way about my project.
86
I really don't know like how many people are going to be using it
87
and if I'm going to even get much feedback from it.
88
So while working in big tech is amazing, it exposes you to the most amazing engineers, technologies, and opportunities.
89
It can be also limiting in your impact and your scope
90
and hopefully this is helpful to anybody who's wondering what it's like to work in big tech
91
and maybe they were thinking about like choosing between like a small startup
92
or a big tech company there's definitely pros
93
and cons to each of them
94
but one thing i do like about working in big tech is there is a lot of amazing people
95
and i'm really happy this year
96
because i was able to make some new friends i'm going
97
to be getting lunch with one of my friends right now
98
so let's go i'm coming out out of what out to society what are you talking about Thank you.
99
Wow.
100
That actually looks really good.
101
I'll send that to your present.
102
What?
103
This is a little present.
104
Don't go with it.
105
Wait, I'm gonna go.
106
Oh my gosh.
107
Thank you.
108
Thank you i love i love this video yeah you can
109
just save it for later yeah i appreciate it bro on tiktok i've been seeing
110
so many stories of the people like my husband like had an affair
111
they're so awful and i'm like everyone i watch them i'm always like
112
hmm like men really age it i can't always do this
113
okay no no no okay i have to tell you the most insane one this girl
114
so basically i tried for batch sake initially the day i
115
did need a full loop say this might be constant ever
116
since all the layoffs started happening work has felt a bit unstable
117
and it's really hard not to think about it in the back of your mind even
118
if your team feels fine today there's always that lingering question of what
119
if i'm still pretty early in my software engineering career i've been working for one year
120
and there's so many fears around ai taking over my job, losing my job, to the layoffs, and it honestly makes things feel a lot more uncertain.
121
I've been trying really hard to not let that anxiety take over my life.
122
After work, I just want to disconnect, relax, and not think about coding, performance reviews, or the job market.
123
But at the same time, it's really scary to ignore it completely, especially knowing that I don't have much experience yet, and if I suddenly go out, I'll have to interview again.
124
So I've been trying to stay positive and just focus on what I can control, keeping my skills sharp and staying open to opportunities and remind myself that I'm still growing.
125
I want to help with my burnout by just keeping my options open so I don't feel stuck in one place.
126
Recently, I've been trying to keep my interview skills sharp on the side, but the hardest part for me isn't just solving the problems, it's remembering to practice consistently.
127
So I built this system that reminds me to practice every day using Notion.
128
Notion recently introduced custom agents, which are basically automations that run in the background of your workspace.
129
Instead of manually prompting the AI every time, you can set agents to run on schedules or triggers.
130
This video is sponsored by Notion and it's the perfect time to show you how I set up my custom agents.
131
All I did was connect my custom agent to a LeetCode database.
132
Every morning it sends me a problem from the database
133
and then it updates it so I don't get sent the same problem twice in a row.
134
I'll make a full video showing you how I use Notion for my job searching process, so stay tuned for that.
135
But in the meantime, if you want to try making your own automations with Notion's custom agents, use the link in my description.
136
And now we return to our regularly scheduled suffering.
137
I used to do.
138
It's that time of the year for my annual review, and it's a time to reflect on my year and what I learned and what I got out of it.
139
When I first joined, I asked the senior engineer how long it would take before I became a pro on the team, and they said a year.
140
So am I pro now?
141
No, I do not think I'm a pro.
142
Our team owns a lot of services, and I feel like I'm just scraping the surface of what they all do, and I'm still really confused by all this accounting jargon.
143
I think I know my own project pretty well and that's about it.
144
I'm more confident overall, but after all the layoffs and the recent talks about getting on the promotion path with my manager, everything is a bit shaky for me.
145
My friend Marlene joined Amazon a year before me
146
and she's already gone through the entire promotion process already
147
and she knows ins and outs way better than me
148
so I love talking to her
149
and seeing her progress gives me a lot of hope
150
because maybe in a year from now I'll be where she's at and if I am, I'm really happy.
151
It's nice to be able to talk to her about her process
152
and her time at Amazon because it definitely makes me feel a lot less alone
153
and that's one thing
154
that I'm very happy for in the last year at Amazon is the girlies that I got to meet.
155
Everyone has been so nice and it's actually made coming to work and getting through the boring days so much easier.
156
I think a lot of your experience at work is also what you choose to make of it.
157
It's the people that you push yourself to talk to, the mindset that you want to have, and I definitely need to remind myself that when I'm in my slumps.
158
I'm not sure how to make a joke I'm so cool
159
I'm just gonna get all the touch I'm gonna go on the flash I'm gonna be honest
160
You gotta call
161
me baby
162
I was
163
getting lunch with my friend today and
164
while I was waiting in the lobby I actually got recognized at work I think it's
165
so cool that people actually watch my videos a lot of the times I think I'm just like filming
166
and talking to like myself but something funny that I noticed is
167
that I only ever get approached when I'm with a friend never
168
when I'm just like by myself and I think it's
169
because I have an RBF when I'm by myself and then
170
when I'm with people I'm like smiling and laughing
171
so I think I come off a little bit unapproachable so
172
if you came up to me this year thanks it was really nice to meet you
173
and I hope to see more of you soon anyways let's get back to work
174
all right it's getting a bit late now
175
but i still have to head to one of my second one hour meetings of the day
176
so we have these meetings twice a week
177
and basically we share our individual learnings
178
or any design reviews with the team for example this year
179
i needed to do a migration from one build tool to another
180
so i wrote like a two-page document summarizing the problem how i was going to solve it
181
and all the different options with their pros and cons and then I booked this meeting with my team.
182
In this meeting they basically read over your document, they spend like 20 minutes reading over it, they annotate it, ask questions.
183
This method actually kind of makes sense because sometimes
184
when people are talking I can zone out and then when I zone back in I'm like completely lost.
185
So if I can just read a document at my own pace
186
and like annotate it I feel like I'm gonna absorb the information a little bit better
187
but then sometimes the document is like 15 pages long
188
and i already have no context about it
189
so these meetings like get me really really sleepy
190
and they also happen after lunch i talked to like one of my co-workers
191
and they've also said this feels like a nap to them it's
192
so hard to stay awake especially
193
when you don't really know what the context of the meeting is
194
because everyone's working on like their own thing anyways let's head to the meeting Alright,
195
I just got done chatting with the senior engineer.
196
They explained what I need to do for this project, so I started making some of the code changes they recommended and hopefully this will start adding more traffic to my project.
197
I just hope that this doesn't break any of my already existing code, but I really do think it probably will, so I'm just going to tweak this and hopefully it works.
198
I'm sorry.
199
What do you say?
200
We call it a night and get some beauty sleep.
201
You go.
202
I want to review my notes one more time.
203
In my last video, I was working on the annual reviews and writing some reviews for my peers.
204
So I finished up writing those and today I'll be working on my individual review.
205
You basically need to say which leadership principles you did well on
206
and maybe some you need to improve on and you want to share examples from the work that you did this year.
207
So this year I did something which was keep a work summary.
208
Basically I recorded all the work that I did throughout the year.
209
I noted down the operational work, any notable tickets that I saw, any project work that I did and the progress I made on it and the impact of all of that.
210
I also compiled all the design documents that I wrote throughout the year and what decisions that I had made.
211
A work summary is also very helpful for you later on
212
when you're going to promotions or when you want to update your resume for future jobs.
213
If you watched my video from last year, I also did an annual review, but I had only been working for a few months.
214
My team was really new to me.
215
I was really new to my team, so they didn't have much to say about me, and even though I've been working for almost a year and a half now, I still feel very new to all the systems.
216
I really only know about my project which is a very small part of what my team does as a whole.
217
I think my project definitely has similarities to other services but there's a lot of low-level detail that I don't know about.
218
So my goal from next year is
219
that I become a pro in all of the services so
220
that people will start coming to me about not just my project but all the other services as well.
221
So with that I'm going to start writing my individual review
222
and we'll get back to I'm still working today even though it's getting pretty late.
223
I tried to clock out around 5 because I want to have a life outside of work, but today was a special case because I'm still wrapping up my on-call shift, I also have project deadlines,
224
and the annual reviews so I want to finish it all before I head home.
225
I don't mind working later after most people have left
226
because it's actually quite peaceful
227
and I end up getting more stuff done office can get really loud during the day and it's super distracting for me.
228
I can't help but overhear other people's conversations
229
and then suddenly I'm really distracted not doing any work
230
and then if I put my headphones I'm listening to good music
231
and I'm also getting distracted so it's just nice when it's really quiet in the office.
232
If I could choose when to come into work I would come in way later
233
and stay way later because I'm pretty much a night owl and I get more work done at night.
234
I can't do anything tonight.
235
Why not?
236
Because I have a lot of planning to do.
237
I think within the first couple of months, I started to feel like this job at Amazon isn't really what I imagined for myself.
238
It's not that it's a bad job or anything.
239
It's more that I don't feel connected to the work.
240
What stands out to me the most is how small I feel inside a system that is this big.
241
At a company like Amazon, especially as a more junior engineer, I'm really not shaping the bigger picture.
242
I feel like I'm just floating around.
243
I understand that I'm junior, but I'm doing very mundane work.
244
I'm updating packages, running pipelines, fixing tests, all for just some financial accounting software.
245
A lot of the work starts to feel repetitive and honestly pretty empty and not because software engineering is boring, it's because this version of it doesn't feel right for me.
246
I've also been having this weird realization where I worked so hard to get here, now I'm here and I'm not sure I even want it.
247
I've definitely been lingering on this feeling of leaving Amazon and that's probably just the most honest part of all of this.
248
I'm still figuring it out in real time
249
but I'm seriously starting to ask myself whether staying on this path just
250
because I don't want a job search and the market is bad is actually a good enough reason.
251
And I've been watching a lot of videos of my favorite software engineers quitting their jobs
252
and it's just making me feel some type of way.
253
I think a lot of people assume that once you land a job at a company like Amazon you should be grateful, stay, and try to make it work.
254
And there is a part of me that thinks that too.
255
Maybe I should just try to tough it out and maybe I just need more time.
256
Maybe I need to work on a cooler project.
257
Maybe it's just, you know, seasonal depression.
258
But I also think there is a bit of a difference between something being challenging
259
and something just not being right for me.
260
And that's the part I'm trying to figure out.
261
My friend Marlene gets the best snacks for a snack wall.
262
These are so delicious.
263
I sleep all day, up all night, staring at the wall, feeling light,
264
dozing off to rest my eyelids.
265
So I've wrapped up most of my work today, the office has cleared out, and I'm going to be catching the train and heading home.
📺 同じチャンネル
✨ おすすめ動画
B23
62 文
Day In my Life as a Software Engineering Intern at Google
Business EnglishInterview EnglishUniversity Students
B23
406 文
How to Become the Most Successful Sales Engineer at Your Company
Business EnglishInterview EnglishUniversity Students
B2278 文
Fastest way to become an AI Engineer in 2026
Business EnglishInterview EnglishUniversity Students
B21
224 文
How Tech Salaries Work 💸, AI Chat with Google UX Lead, I'm moving?| Biz Analyst Diary
Business EnglishInterview EnglishUniversity Students
B25
159 文
16 AMAZON STAR METHOD INTERVIEW ANSWERS! (Amazon Leadership Principles Interview Questions!)
Business EnglishInterview EnglishUniversity Students
B2257 文
How I Escaped Help Desk Fast (Step-by-Step)
Business EnglishInterview EnglishUniversity Students
B22
75 文
The unfair way I got good at Leetcode
Business EnglishInterview EnglishUniversity Students
B21
102 文
The UX/Product Design Interview Process Explained (2023) - how I landed multiple FAANG offers
Business EnglishInterview EnglishUniversity Students
B15
53 文
THE Millennial Job Interview
Business EnglishInterview EnglishUniversity Students
B22
29 文
My Typical Tuesday
Business EnglishDaily ConversationUniversity Students
B21
202 文
SOFTWARE ENGINEER Interview Questions & TOP SCORING ANSWERS!
Business EnglishInterview EnglishUniversity Students
英語スピーキング練習に役立つポイント
このビデオは、ビッグテック企業で働くソフトウェアエンジニアの日常を語るもので、自然な会話のリズムやリアルな感情表現が満載です。特に、日常的な悩みを話すときの表現、ミーティングの内容を説明する際の構成、葛藤を率直に伝えるスキルを練習できます。英語で自分の考えを整理して話す能力を高めたい方に最適です。
聞き取りに注意すべき音のつながり
ネイティブスピーカーの会話では、単語がつながって発音されることが多いです。このビデオでもいくつかの例が見られます。例えば、「I've definitely been」は「アイヴ・デフィニトリー・ビン」ではなく、「アイヴデフィニトリービン」とつながって発音されています。また、「kind of」は「カインド・オブ」ではなく「カインドゥブ」と短縮される場合があります。これらの音のつながりを聞き取ることで、リアルな会話に慣れることができます。
ネイティブのように話すコツ
ネイティブスピーカーのようなリズムとストレスを身につけるには、シャドーイング（shadowing）が効果的です。このビデオのスピーカーは、葛藤や悩みを話すときにはゆっくりと、ミーティングの内容を説明するときには明確に発音しています。例えば、「I wonder if there's other software engineers feeling the same way」では、「wonder」と「same way」にストレスが置かれています。このようなストレスの置き方を真似ることで、より自然な英語を話すことができます。また、「英語の発音を良くする」ためには、繰り返し練習することが大切です。shadowing siteを利用して、自分の発音とネイティブの発音を比較しながら練習してみてください。
このビデオを使って、英語スピーキング練習をしてみましょう。リアルな会話の中から、ネイティブの発音やリズムを学び、自分の表現力を高めることができます。
この動画の文法
話し手がよく使っている文型を、動画の実際の表現とともに紹介します。
| 文型 | 動画での表現 |
|---|---|
| 現在完了進行形 have/has been + -ing — 以前に始まり今も続いている動作 | I've definitely been lingering · I've been feeling · i've been seeing |
| 現在完了形 have/has + 過去分詞 — 過去の出来事が今も関係している | I've always admired · I've always wanted · has felt |
| 関係詞節 who / which + 節 — 人や物について情報を加える | everyone who was · agents, which are · something which was |
| 受動態 be + 過去分詞 — 誰がするかより、何が起きるかに焦点を当てる | was done · is sponsored |
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。