Prática de Shadowing: My Entire Job Search Process: Software Engineer Resume & Interviews - Aprenda a falar inglês com vídeo

Hi everyone, I'm Sarah and welcome back to my channel and today we are going to be job searching.

Amazon this year alone has laid off 30,000 employees and that's terrifying.

I feel like any day I could wake up

and get like a horrible HR email and my day would be ruined and everything sucks.

So I think starting this job searching process is definitely going to help me take back this control

and feel a lot more prepared for the future.

I am just wildly unprepared and we're going to change that today.

All right, keep watching because today I'm going to show you everything.

How I update my resume, prepare for my job interviews, I'm going to show you my LeetCode Notion board that I've been using for like the last five years.

And also recently I set up an automated job board

so I can see all the job applications from a bunch of websites in one central database.

And thank you to Notion for sponsoring today's video.

Let's get into it.

All right, so I haven't updated my resume since I was applying for new grad roles.

It is like super out of date so we definitely need to do that right now.

One thing I will say is that this process will be so much easier if you keep a work summary.

I've been keeping a work summary since I started working at Amazon even as an intern

and basically what it is is everything that I've been working on every day.

Say I learned a new language or I worked on my project or the impact that I had, I just write it down.

At the end of the day, your manager isn't going to remember all this information for you.

You got to do it for yourself.

When you leave your job, this is all you have of it basically.

You can't take any of the code.

You can't take your laptop.

You just can keep track of what you've been doing.

So I'm going to show you how I've been keeping track of all my work

and how I'm going to use this to update my resume really quickly.

This is a Notion page that I've created

and I keep track of like every single week what I've been working on at Amazon.

This is like a weekly update I did.

I update with my one-on-ones, what I talk about, the tasks I worked on, things I did like that.

So this is my work summary.

I highly recommend keeping one and I'm going to update my resume now with this information.

All right so let's do a little resume review on what I can improve and what I'm already doing pretty well.

Obviously I'm using Jake's resume as my template.

It's a really wonderful one.

It's classic, it's easy to read, and it's scannable by the ATS scanner.

I start off with my experience, go into my projects, education, technical skills.

I think what's good about it is that in my bullet points I show the quantitative impact that I had.

I say 90% reduction in manual efforts or solve 40 plus bugs.

This is a good way to show recruiters like what you're actually doing.

What I definitely need to work on is my project section.

This is a really old project from 2021.

I definitely think I'm going to just replace this one.

It's good to include a full stack project

but this one's just not very interesting and I definitely have done some cooler ones since then.

I just added this new section here for my work at Amazon as a new grad.

I'm going to take this resume to the road and actually submit some job applications with it.

Alright, I made it to my favorite cafe

and I just need to switch up my environment because I'm going to start sending out some applications.

When I was applying for my very first internship, I was sending out applications every single for about a month with hearing absolutely nothing back.

And when I say nothing, I mean rejection emails.

I sent out around 80 applications total and maybe got five interviews from all of that.

At the time, I didn't know if I was just doing something wrong or it was just the market.

I actually emailed my co-op coordinator at the time asking

if I should just give up and if there's something wrong with me and he said something along the lines of, you're doing great, keep going.

The truth is, sometimes it really is just timing and luck.

Getting a job in tech right now is genuinely harder than it has ever been.

So if you're in a stretch where you're applying every single day and it feels like you're shouting into a void, I want you to know that it's really a normal experience

and it doesn't mean your applications are bad or that something is wrong with you.

You just have to keep going.

My favorite websites to use are LinkedIn, SwedeList, Simplified GitHub repo, WellFound, and YC job postings.

I used to check each of these websites individually every day, but this is just so time consuming.

So what I set up is a combined job database in Notion that updates every day using Notion Custom Agent.

It populates each job as a row in your Notion database with the application link, the date it was posted, the company name, the location, and the compensation if it's listed.

Honestly, you never know which application will be the one to get you through to the job offer, so be consistent and frequent.

I definitely have a strong love-hate relationship with LeetCode.

Actually, it's mostly hate.

I get so nervous.

It feels like an exam, but even worse because it's like you're the only person taking this exam and everything is like on you.

This is how every software company does their interview testing and it's just how it is.

So I would really recommend doing NeetCode 150.

And the way you're going to remember these problems is using a method called space repetition.

So space repetition is actually a scientifically proven way to get you to remember things.

It's a way of studying where you review information right before you're about to forget it instead of cramming all at once.

So let me give you an example.

Let's say you're learning a brand new problem.

You're doing two-sum for the very first time.

On day one, you do two-sum.

Day two, you do it again.

Then you wait a couple days.

Each time you remember it, your brain holds onto it a little bit longer.

So you keep increasing the gaps before the next time you do the problem.

I'm going to show you my LeetCode system that I've been doing with Notion.

And this is how I actually practice on my technical questions and stay on top of it, stay organized.

So I'm not just doing like random questions all the time.

This is my LeetCode database.

This is my baby.

And you can see from this question, I solved it September 17th, then September 18th, then September 19th.

And then I waited a little bit and solved it on October 12th.

That is the spaced repetition method that I used to solve it.

And now with Notion Custom Agents, I connected it to this database.

And I send myself a reminder every single day of three

to five questions using the spaced repetition method of what I should work on.

And your custom agent is so easy to set up.

You just need to send me an email reminder every morning

and I just hit send and it will create a custom agent to do this for me.

So this is the email that it sent me.

It sent me a question a day and it also updates my database with this new question that I did.

100

So when I was searching for my very first internship, I genuinely did not know that LeetCode was a thing.

101

I took a data structures and algorithms class in university and I treated it exactly the way you're not supposed to, which is to learn everything right before the final, pass the exam, and then immediately forget all of it.

102

I didn't realize it was literally what I was can be tested on in every single interview.

103

So I sent in about 80 applications, got around 5 interviews, and walked into them completely unprepared for technical questions.

104

My most embarrassing interview was with SAP.

105

They asked me to implement a stack using two cues, and I knew what a stack was, and that was basically it.

106

I sat there for 40 minutes completely blanking while the two interviewers just stared at me.

107

It was so bad.

108

One thing that helped me a lot was practicing out loud.

109

It sounds weird, but it trains you to explain your thinking in an interview

110

when someone's watching you and when your brain goes blank.

111

I also keep notes on every question I do, what the pattern was, what I got wrong, and how I could come back to it instead of moving on and forgetting.

112

So if you're early in your leak code journey and feeling completely lost, I totally get it.

113

I was the person who didn't even know what a stack was in a live interview.

114

You will get better.

115

Just do it consistently and practice your questions out loud.

116

Imagine getting to this point of the interview

117

and then you just blank on your interview stories because you didn't have any prepared.

118

In my Amazon interview, I think I talked to the person 20 minutes over my interview time

119

because I was just like so excited to talk and I like loved yapping.

120

So I think I'm actually like not too bad at the behavioral part.

121

Amazon has these 16 core values called leadership principles and there's things like bias for action,

122

ownership, customer obsession, and you need to answer your behavioral questions in a way that addresses each of these leadership principles.

123

Some quick tips are to use the STAR method to answer your questions which is situation, task, action, result.

124

This will help frame your answers in a way

125

that is very clear for them to understand and knows your impact right away.

126

So it's really important to build a story bank of like five

127

or six stories that you can just reuse for a bunch of questions.

128

For example, if someone asks you tell me about a conflict or tell me about a time you failed, you can definitely use the same story for each of those questions.

129

So let me show you my Notion behavioral template which I am also sharing down below.

130

Trust me, this notion behavioral template works and if you can answer all these questions, you're going to be set.

131

So this is my job search portfolio with my work summary, but on the bottom here, I also have the behavioral questions that you should probably answer.

132

These are popular questions that a lot of companies will ask and I've prepared answers for each of them.

133

Why do you want to work at XYZ company?

134

You need to be able to answer that.

135

Another question people have asked is have you disagreed with someone for a project and how did you go about solving this?

136

Name a time where you're working on something

137

and you had to convince them to work on a solution you might think was better.

138

Tell me about a time you made a bold and difficult decision.

139

Tell me about a time you solved the pain point for customers.

140

These are very popular questions that a lot of companies will ask.

141

My problem is all my answers for these questions are very outdated.

142

They're from an older story bank.

143

So all I'm gonna do is ask Notion to update the

144

answers in the behavioral questions table using the content that's been saved in my work summary.

145

And this will help me generate new story bank that I can use to practice my behavioral interview questions with.

146

I really like to get in front of a mirror

147

and then answer all these questions like talking to myself

148

or talking to a camera just so that I'm prepared to recite like these stories.

149

And what's cool is my custom agent can be updated on a trigger.

150

Every time I update my work summary I can add new story bank answers.

151

So I'm going to take a look at the answers it generated, polish them up, and then I'll be done my behavioral section.

152

So when I was first preparing for behavioral interviews, I really struggled because I didn't know what stories were worth telling.

153

I kept thinking, is this even impressive enough to bring up?

154

I would think of something I did at school

155

or a previous internship and immediately talk myself out of it because it felt too small or obvious.

156

But here's the thing I had to learn.

157

You are almost always more critical of yourself than anyone else's.

158

The story you think is okay probably sounds really solid to someone who's never heard it.

159

This is your time to show who you are and what you've done, nobody in that interview is going to do it for you.

160

One thing I also recommend is keeping track of all the

161

questions you were asked during interviews in a Notion doc as well.

162

Even if the interview doesn't go well, write down the questions they asked and the answers that you gave.

163

It sounds tedious but it builds up this bank of answers you can draw from over time and refine.

164

And one more thing, the questions you ask at the end of the interview actually matter a lot too.

165

I always ask something like, what does a successful intern or new hire actually look like on a team, Or what is the one thing that people on your team find most challenging?

166

And also, this is the perfect time for you to interview the company

167

and figure out if this is actually somewhere you'd like to work.

168

And now we're on to the more personal project section of the job searching process.

169

This is the final layer of the full job searching process, and it's also the most fun for me.

170

Now, when it comes to your resume, if you're not getting enough responses, it's probably because you don't have enough experience.

171

And sometimes that might be something you can't change.

172

Experience takes time, and I've only been working for two years, so it's really hard to say, like, I've worked at, like, six other companies.

173

So what you can do to jazz up your resume is to add some really cool projects.

174

Now, with AI, there is no excuse for a notes app on your resume.

175

Don't look at my resume because I have a really lame app right now, but it's about to get a lot more fun.

176

I really encourage you to use modern libraries and cool AI tools because it shows that you're young, you're current, you know what's going on, you know all the trends, and I think it should solve a problem that you have.

177

This will make it more interesting to the hiring manager

178

and also interesting to yourself so it gives you the motivation to keep working on it after a long day of work.

179

And finally, treat your project like a real product.

180

Make sure you deploy it, get some users on it, make a video about it, definitely have a really good readme because when people go click your GitHub, they can see it.

181

For me right now, I'm working on Outfit Generator.

182

I've been talking about it for a while.

183

I have a lot of videos on it, but it's super fun and it also solves my problem of having like too many clothes

184

and not knowing what to do with it.

185

I just need to deploy it and add authentication so that people can actually add their own outfits and log in.

186

Yeah, I'm really excited.

187

It's a cute app.

188

I'm really close to getting done, so I'm gonna work on that right now.

189

So before we even talk about what to build, I want to say build something that genuinely interests you.

190

Because that energy comes through in the code and the way you talk about it in an interview.

191

For inspiration, some of my favorite places to look are X, Pinterest, and design showcase sites.

192

They're always designers, engineers posting their work and it can really spark something.

193

And I also think one of the most underused sources of project ideas is hackathon winners.

194

Go look at the winning projects from recent hackathons and see what people are building under pressure with a tight deadline.

195

I actually recently judged a hackathon and it was

196

so cool to see everything that people have built

197

and I felt like it really inspired me to make something of my own.

198

And when someone asks you to walk you through your project in an interview, the answer should not just be what you built, it should be a series of decisions and trade-offs.

199

Why this database over another one?

200

Why this API design?

201

Why you structured and architecture this way?

202

And one more thing, if there's a specific company you really want to work at, I recommend looking at their engineering blog, open source repos, and build something in their domain using their tech stack.

203

It is 10.20pm, I'm exhausted.

204

I have work tomorrow which really sucks.

205

So if you're job searching right now and also working, I'm feeling for you.

206

It's a really tough time.

207

Let's get through it together.

208

It's going to be amazing at the end.

209

We're going to get our dream jobs.

210

It's a long journey and the market is not great, but we got to do what we got to do and stay positive.

211

I'm just so happy that I used Notion four years ago

212

and then now they have like updated all their stuff to the AI technologies.

213

So now I can really make my job searching process more manageable and streamline everything.

214

So thank you so much to Notion for sponsoring today's video.

215

If you want to try out your own custom agents, check out the link in my description.

216

And I've also linked there my Notion and behavioral interview templates.

217

Be sure to follow me on Instagram and check out this playlist of my day in the lives.

218

Bye!

📺 Mesmo canal

A Day in the Life of an Amazon Software Engineer

Business EnglishInterview EnglishUniversity Students

✨ Vídeo recomendado

64 frases

Vocabulário e dicas de fala para esta lição

Este vídeo tem 218 frases e 3122 palavras para praticar shadowing. A fala dura 14:24. O falante fala rápido, cerca de 217 palavras por minuto, então espere sons ligados e reduzidos. 84% das palavras estão entre as 3.000 mais comuns do inglês; vale a pena estudar o restante antes de começar.

Vocabulário principal deste vídeo

15 palavras do vídeo que vale a pena aprender, com pronúncia e significado:

Palavra	Pronúncia	Significado
notion substantivo	/ˈnoʊʃən/	noção, idéia
resume verbo	/ˈɹɛz.ə.meɪ/	retomar, continuar
behavioral adjetivo	/bɪˈheɪvjəɹəl/	comportamental
solve verbo	/sɒlv/	resolver, solucionar
database substantivo	/ˈdeɪtəˌbeɪs/	banco de dados, base de dados
custom substantivo	/ˈkʌstəm/	costume, hábito
summary substantivo	/ˈsʌm.ə.ɹi/	resumo, sumário
stack substantivo	/stæk/	pilha
template substantivo	/ˈtɛm.plɪt/	modelo, predefinição
examination substantivo	/ɪɡˌzæm.ɪˈneɪ.ʃən/	exame
internship substantivo	/ˈɪntɜːnʃɪp/	estágio
suck verbo	/sʌk/	chupar, sugar
hire verbo	/ˈhaɪɹ/	contratar, alugar
principle substantivo	/ˈpɹɪn.sɪ.pəl/	princípio
generate verbo	/ˈd͡ʒɛn.ə.ɹeɪt/	gerar

Phrasal verbs que você vai ouvir

Palavra	Pronúncia	Significado
set up verbo	/ˌsɛt ˈʌp/	preparar
check out verbo		verificar, sacar só
bring up verbo		criar
figure out verbo		descobrir, deduzir
give up verbo		render-se
lay off verbo		despedir
take back verbo		trazer de volta
try out verbo		provar, experimentar

Gramática neste vídeo

As estruturas que o falante mais usa, com as palavras exatas do vídeo:

Estrutura	No vídeo
Present perfect continuous have/has been + -ing — uma ação que começou antes e continua	I've been using · I've been keeping · I've been working
“Used to” used to + verbo — um hábito ou estado do passado que não é mais verdade	used to check · used to solve
Present perfect have/has + particípio passado — uma ação passada que ainda importa agora	has laid · haven't updated · I've created
Voz passiva be + particípio passado — o foco está no que acontece, não em quem faz	would be ruined · was posted · can be tested

Pronúncia para ficar de olho

O falante usa 79 contrações e formas reduzidas, como I'm, you're, I've. Diga-as na forma curta, do jeito que você ouve.

Os sons de “th”: algorithm /ˈælɡəɹɪðm̩/, hackathon /ˈhæ.kə.θɑn/, authentication /ɔːˌθɛntɪˈkeɪʃn̩/
Os sons de “sh” e “zh”: notion /ˈnoʊʃən/, examination /ɪɡˌzæm.ɪˈneɪ.ʃən/, internship /ˈɪntɜːnʃɪp/, inspiration /ˌɪn.spɪˈɹeɪ.ʃən/, ownership /ˈoʊnɚʃɪp/
Palavras longas — acerte a sílaba tônica: behavioral /bɪˈheɪvjəɹəl/, examination /ɪɡˌzæm.ɪˈneɪ.ʃən/, genuinely /ˈd͡ʒɛn.ju.ɪn.li/, architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, inspiration /ˌɪn.spɪˈɹeɪ.ʃən/

Como praticar com este vídeo

Ouça o vídeo inteiro uma vez sem falar e anote as palavras que você não conhece.
Comece na velocidade 0,75×, faça shadowing frase por frase e volte à velocidade normal quando ficar fácil.
Grave a sua voz e compare com o original, prestando atenção a palavras como notion, resume, behavioral.

O que é a Técnica de Shadowing?

Shadowing é uma técnica de aprendizado de idiomas com base científica, originalmente desenvolvida para o treinamento de intérpretes profissionais. O método é simples, mas poderoso: você ouve áudio em inglês nativo e repete imediatamente em voz alta — como uma sombra seguindo o falante com 1-2 segundos de atraso. Pesquisas mostram melhora significativa na precisão da pronúncia, entonação, ritmo, sons conectados, compreensão auditiva e fluência na fala.

Técnica de shadowing: leia o guia completo passo a passo →

Prática de Shadowing: My Entire Job Search Process: Software Engineer Resume & Interviews - Aprenda a falar inglês com vídeo

A Day in the Life of an Amazon Software Engineer

Walk Me Through Your Resume: How to Answer

Job Interview English 🇬🇧 | Real Conversation Practice (B1–B2 Level)

How I Would Start Cybersecurity in 2026 (If Starting From Zero)

Google Interview Tips That Actually Get You Hired

I cloned 3 apps and now make $35K/month

Emirates Cabin Crew Interview in 2026: The Secret Scoring System REVEALED

Cracking the Behavioral Interview for Software Developers

How To Land Your First Junior Dev Role

How to Write a Cover Letter That Actually Gets Read | Indeed

How AI Is Ruining Job Interviews

How to Improve English Writing Skills (Without Studying Grammar)