Pratica di Shadowing: ex-Google Senior Engineer: How to Get Hired So Fast It Feels Illegal - Impara a parlare inglese con i video

Scegli una modalità di pratica

Ogni modalità apre una sala di pratica a schermo intero.

614 frasi

Se le frasi sono troppo corte o troppo lunghe, clicca su Edit per modificarle.

Software engineering companies have cut more than 100 ,000 jobs, but at the exact same time, job postings hit a three -year high.

Both of these statistics are true, and if you don't understand how, you are wasting your time.

This is Maddie, Senior Software Engineer ex -Google, interviewed at OpenAI, Meta, Databricks, and Netflix.

And in this video, she's going to walk you through every single step of getting hired in 2026.

The market, the resume, the projects, the skills, the interviews, and eventually the offer.

Let's get started.

So Maddie, everybody watching this has seen the layoff headlines.

We've got Oracle layoffs, meta layoffs, Amazon layoffs, hundreds of thousands of total firings, job cuts, and layoffs so far in 2026.

And because of that, most people think tech is dying.

You're a senior engineer inside big tech, and you've actually gone through the data.

So what's the truth?

Is big tech actually dying?

That's a good question, and that's something I myself have asked myself over and over again.

The short answer, no, big tech is not dying software engineering is not dying, but the role itself is evolving very, very fast.

So like I mentioned, there's a lot of layoffs, but on the other hand, companies like Google,

OpenAI, Anthropic are hiring more and more engineers to build the AI

that other people are saying are going to take over all of the software engineering jobs.

So I like to say the market didn't actually shrink, it split.

So what that means is there's now kind of like a bimodal distribution of jobs.

the old way was basically

if you were a junior engineer

you would get in you'd spend some time getting acquainted with

the code base you'd submit some rudimentary fixes some bugs some small projects

and you build your way up nowadays with ai with you know clod

or open ai chat gpt can understand a code base for you people no longer have

that grace so what that means is instead now juniors are expected to use ai to onboard

and to start producing code faster and faster and to more of a level compared to senior or sophomore engineers.

I will say that even though when I was interviewing, people didn't as much ask system design questions for juniors,

now more than ever, it is important, if you can, to study your system design fundamentals even as a junior

because you can tell AI to write code for you and AI will write code for you.

But if you don't understand how the code will fit in the big picture of your system, you could end up with just jarbled,

unmaintainable, incorrect code that just happens to work with the specific use case that you prompted your AI with.

So another thing I'm going to say is that I believe

that AI is being used as kind of like a scapegoat for job cuts.

So a lot of companies, like this has happened in cycles in the past, a lot of companies go through phases where they think,

oh, we should cut costs and we can do this by, you know, moving headcount from high cost of living areas like

New York and the Bay Area and moving them overseas use.

And especially with AI, they're like, oh, we can replace engineers with AI.

However, there are multiple instances of this not working the way that people intended.

So for example, I don't know if you've heard of like AWS Kiro.

Yeah, so what happened was there was an internal agent within Amazon.

And what it did was it actually caused like a pretty big production outage in I think December of last year.

And it basically triggered a whole set of protocols where now you need to have more human loop.

This is an example of a big company trying to use AI to replace a software engineering role, but it ended up much worse for them.

So I think that, yes, a lot of tasks are getting automated.

And yes, like as a junior, you're expected to perform faster and faster, but fundamentally the job itself is here to stay.

Like as we have more AI generated code, more AI in our day -to -day, we also need engineers who understand AI,

who can, you know, run evals, who can build the infrastructure for the AI.

So it's definitely like a two -way story.

It's not just is tech big tech dead or not nice

so one question i have as well maddie is

that kind of back to those statistics we talked about earlier i mean layoffs just keep happening everybody knows

that it's like you know oracle amazon meta etc

but then the number of jobs is actually going up right

so both layoffs and job postings are increasing

so do you have any idea how this is happening

because i would expect okay if there are layoffs happening

that means there are too many roles companies are just hiring less in general

but it seems like both are simultaneously happening that's a great question

i will say there are a lot of engineers

that uh i think they call it boomerang like they in the past

it was by choice they would like leave one company to go to a different company

and then come back for more pay and more comp nowadays i think software

companies are realizing sometimes

if they lay off uh you know a bunch of engineers they're actually going to need the same knowledge

that some of those laid off engineers had

so they're going to rehire them

so that's actually some of the discrepancy

it's um some of the engineers like talented engineers who got

laid off through no fault of their own their original company realizes hey like we actually need

you this is actually critical it's happened in many companies out there

so that explains some of it and also um because it is kind of employer's market.

I think employers have a little bit more leeway when it comes to, oh, like this is who we're going to keep,

this is who we're going to get rid of.

So because of that, they are able to get, quote, like the best software engineers because they are able to use like other engineers

that got laid out by other companies and use those to fill the headcount

and then release engineers from roles that are deemed like less important for the company.

So unfortunately, that is the case.

Like you can, through no fault of your own,

lose your job and your company will have no problem right now replacing you because of the state of the job market.

A lot of tech companies model the behavior after other big tech companies.

So as soon as one tech company does this, and even if there's backlash, more and more companies realize,

oh, this is a viable option that we can do because there's precedent now.

Interesting.

So it sounds like a lot of the time these companies will do massive layoffs and then realize they overlaid off.

Similar to overhiring, they overfired.

And they essentially rehire a of people

i'm still confused about like why do they still keep doing rounds of layoffs is

that just normal like the way it works is they over they hire a bunch

and they just like try a bunch of projects

and then just do layoffs with ones that don't work is

that kind of like the normal cycle

or essentially what i'm asking is are layoffs here to stay

or will there be a point where they tend to slow down

and stop essentially i think

that they are here to stay for at least the next few years

because there's also precedent and specifically nowadays it's in 2026

so you know how in 2022 and 2021 and 22

when everyone is telling everyone to get into self -engineering right

100

now there's like a big surplus of people who are new grads

101

or a year or two into like non -seniors who want jobs

102

and because of that you know supply

103

and demand the companies can then realize oh we have like

104

so many people want jobs we can afford to pick

105

and choose however i think this is a cycle thing we've seen this in the past once it becomes clear

106

that software engineering is not just like the career to go into

107

if you want to make money then people will no longer go just

108

because they want to get rich right they'll you'll get there's less people into the field

109

but people who are genuinely more passionate about the field

110

and as a result i do think that will decrease the supply

111

and then therefore like that will therefore shift the market more toward the employee

112

so i think it's going to be similar to what it is for at least a couple of years.

113

But I personally am optimistic that after a while, we'll reach a more steady equilibrium.

114

Nice.

115

It's kind of like how

116

Warren Buffett says, when people are hyping up a stock, you should sell because it's overvalued.

117

And when people are freaking out because they think an industry is dying, that's the time to actually invest.

118

It feels like software engineering is in that second category where

119

everybody and their mother are talking about how it's the worst field ever.

120

Don't get into software engineering quit your degree go burn your degree get a job at chipotle

121

but in actuality maybe

122

if you actually double down still try to recruit build your

123

profile get better at engineering in two to four years you'll be ahead of a lot of people at

124

that point exactly okay so we just talked about how software engineering as a whole isn't dead

125

and there are jobs that definitely exist

126

but the real question is what kind of jobs are those

127

and how do they differ compared to three to four years ago

128

and who are the kind of people profiles backgrounds who actually get those jobs today

129

so i think a big difference between a software engineering now

130

and even like three four years ago was

131

that it was totally fine to be a generalist three four years ago

132

you could find good job without any specialization however i believe

133

that that era is now dead with ai being able to do a lot of generalist roles

134

and be able to take um be able to generate a lot of code that's general,

135

it is more and more important to be an expert and to go into specific niches.

136

And I'm not saying that everyone has to be an AI engineer per se.

137

I'm just saying that you need to know how to like go deep into like, I don't know, like Docker,

138

React or something like that and use AI effectively.

139

I think a lot of engineers, even me up until like pretty recently, to be honest, like I would just like be,

140

I would just prompt like randomly, just like type in words and see what comes out

141

but more and more so prompt engineering is a more valuable skill as time goes on

142

and even as the models get more powerful

143

and more powerful um you can still get really bad results

144

if you just prompt randomly versus if you are good about how you prompt

145

and for example if you tell claude

146

or tell chat gbt this is like the general design

147

i want this these are the these are the um like this is the stack otherwise

148

you'll always have like what like super base

149

or you'll have like the the the react like whatever the ai spits out for you

150

so you just mentioned how the era of the generalist is dead

151

and gone and long live the specialist in software engineering

152

so i'm curious to dive more into that what are those specialist niches

153

that people can go into especially if they're a computer science student

154

or a new grad with just zero to three years of experience at the junior level.

155

I would say that it's important to explore and figure out what you are good at, what you want.

156

So, for example, I have friends who are in, like, cybersecurity, databases, front -end, too.

157

Like, there's, like, my friends who are really good at React, and I think, maybe it's a hot take.

158

Like, I personally don't think front -end is going to die entirely.

159

Like, to be honest, like, I have prompted AI to do front -end, and when I don't, if I'm not careful,

160

it looks very, you know, like, AI purple haze.

161

So I think there's still some time before AI can generate a front -end that doesn't look very AI -generated, in my opinion.

162

So yeah, things like that, especially security.

163

I feel like every other week you hear stories of someone who vibe -coded an app

164

and lost thousands of people's personal data.

165

That happens a lot.

166

So knowing the fundamentals is more and more important as time goes on.

167

And finally, I think infra is really important.

168

Like, even if, you know, you have great models, you'll always need infrastructure to run those models on.

169

So I don't think that role is anywhere near getting extinct.

170

So how does one actually specialize in some of these niches at an early stage?

171

Because I don't think these universities are adapting very quickly.

172

People still do a general computer science degree with data structures, algorithms, maybe like a databases course and be like user interfaces course.

173

But how does one actually pick a niche and specialize in it early on?

174

That's a great question.

175

I would say building your own projects

176

and even it's like a really small project something

177

that i don't think i was very good at

178

when i was in university was i would just you know build only for my internships

179

or for uh my classes

180

and i would maybe build for like you know really small projects for hackathon

181

but i never really dug deep so if i were to go back

182

and redo things like i definitely would try to pick more than a toy project

183

and i think especially now with ai it's much easier to prototype something

184

so i would say pick a project

185

that does have to do with the field

186

that you're trying to specialize in and just like build something and then just like,

187

you know, ask your AI the questions to understand actually the code is writing.

188

Don't just like prompt and just like forget about it until it like messes up like months later.

189

On that note, let's talk about projects.

190

You made a video about four resume projects that got you into Google,

191

but it's 2026 and AI can generate a slot project in seconds and every recruiter knows it.

192

So what kind of projects today make recruiters drop scrolling?

193

That's a great question.

194

I'm going to fully echo that the projects

195

that i personally made with my you know organic code with

196

my own hands would probably not definitely would not raise would not meet the bar today the type of projects

197

that would get you noticed are not toy projects not to do's

198

they're not like oh i follow tutorial they're projects

199

that would solve like a part like a legitimate problem in your life

200

and it'd be and something that is a plus you don't have to it's like

201

if you build in a way even you don't have

202

that many users it is scalable to many users because

203

that shows the recruiter that you understand things besides like how do I make it work for one user?

204

You can understand like oh

205

if I want to make

206

it for like a thousand like this is how I can like shard a database it's like xyz.

207

I also think that nowadays projects that utilize AI are also in more high demand.

208

So for example if you can like build a second brain

209

or if you can build like your own MCP server for a particular use case

210

or if you're building a rag system those are very useful projects

211

that will not only teach you a lot be very useful in your day -to -day,

212

but also will show a recruiter that you know what you're talking about.

213

I totally agree with that point.

214

What I often tell people to do is forget projects in your bedroom and almost make like a mini micro startup.

215

Find a real world problem, something that either you struggle with or friends and family struggle with and actually aim to solve that through software, right?

216

I mean, that's the point of coding in the first place.

217

It's like solving real world problems.

218

And it's a lot more impressive to a recruiter or hiring manager when you've launched your project, you've launched your app, You have actual users,

219

even better paying users, people who are getting real value and you're able to scale it to them.

220

So that's what I'd recommend.

221

Don't just build a calculator in your bedroom.

222

Anybody can do that in half a second, right?

223

Focus on building real world projects to solve real problems.

224

But on that note, how useful are projects nowadays?

225

Like if you're talking to someone who's a computer science student or an early career engineer, would you even recommend projects?

226

Or should they focus more on other things like maybe internships, hackathons, research, etc.? I don't think those are mutually exclusive.

227

I think having maybe I would say quality over quantity.

228

So don't just like spin up 30 projects.

229

Definitely, if you have like one or two that you want to focus on, actually productionize, focus on that.

230

I will say some of the projects that I've heard of have come from hackathons.

231

So hackathons are a great way to not just learn yourself.

232

It's also to find a team.

233

And if you find a team and you build a project

234

that you're really excited and you want to build it to something real outside the hackathon, that's even better.

235

I would say internships are still important if you can get internships.

236

But I know currently there aren't as many companies, like as many roles open for internships.

237

So like if you don't get an internship, totally fine to build your own thing to see what you can do.

238

Kind of like you mentioned, like being like a mini startup mode.

239

But if you can do an internship, I would still highly recommend that because I think that having internships on your resume.

240

really, really helps future companies want to hire you.

241

On that point about hackathons, I 100 % agree.

242

I think hackathons by their nature are competitive.

243

A calculator app isn't going to cut it.

244

You're forced to build a project that's resume worthy in a hackathon setting

245

because otherwise you wouldn't even place or do well at all in the hackathon.

246

Another benefit of hackathons is it's done in a team setting, like you said.

247

So you can get three or four people together, build those connections, and then build a project that's actually way better in

248

that team than you could do on your own in a 24 -hour, very short window.

249

So all in all, hackathons, 100 % worth it.

250

I would highly recommend.

251

Actually, I'll ask you, did you do any hackathons in college that you ended up building connections from or any projects from?

252

Yeah, I did a couple.

253

So I went to MIT.

254

We had this hackathon called HackMIT.

255

It's very, I think it's very popular, like a lot of people go.

256

So I was able to meet friends from other schools as well and like form connections.

257

I'm still friends with them for this very day.

258

And also an example of how hackathons can help you find

259

um really cool people to connect with i recently went to an opus 4 .8 hackathon that's hosted by

260

anthropic in san francisco

261

and one of the winners was a group of two guys um

262

they didn't know each other before the hackathon they met one of them actually from mit

263

which is why i ended up talking to him

264

and like they built a really cool project like it was

265

like basically being able to um build like a you you could take a photo

266

and then a 2d photo

267

and then you'd use like ai to generate like a 3D model of it

268

and then you could place it into like a virtual world

269

and you could world build it and I thought that was really impressive.

270

So that's an example of a project that was really impressive

271

that was made possible only

272

because this hack fund brought two people who did not know each other from Oxford Science of the US together.

273

Listen up, if you're struggling to land an amazing software engineering full -time job

274

or internship or if you submitted dozens of applications

275

and you feel like nothing is working or if you failed multiple online assessments and interviews,

276

or you just feel like you don't understand the process to land a great offer in the market of today,

277

I actually run a school for people like you called the Software Engineering Accelerator.

278

Now, over the past year, we've helped dozens of people in incredible jobs at internships at companies like Google, Amazon, Microsoft, Tesla, Salesforce, Adobe,

279

LinkedIn, Capital One, MongoDB, JP Morgan, and the list goes on.

280

And the best part about our program is that we actually guarantee the outcome.

281

If you don't get the full -time job or internship you want, you don't pay.

282

So if you'd like to work directly with me

283

and my team of FANG recruiters and engineers to land an incredible job in tech guaranteed,

284

click the top link in the description and submit an application to join us.

285

Cool, so we just talked about projects.

286

Let's talk about learning, courses, and books.

287

Most people are completely overwhelmed with random Udemy courses, leak code, some random AI tutorial,

288

a system design playlist, but no idea what actually matters or what order anything goes in.

289

So let's go from zero to hired.

290

What are the few best courses and books that people should actually pay attention to?

291

The first thing I say is it doesn't matter as much, especially in the AI era, what language you use when coding.

292

So pick the one that is most comfortable for you in the interviews.

293

I personally use Python.

294

I have friends who use like Java, JavaScript.

295

Some use C++.

296

I'm not going to comment on that, but if it works for them, it works for them.

297

They got good offers, so they know what they're doing.

298

Second, I would say fundamentals still matter.

299

Like I know right now, most companies are focusing on AI assist interviews.

300

So lead code, the type of data destruction algorithms problems are probably going to like decrease a lot

301

and maybe maybe just stop in the next couple years

302

but as of right now

303

when we're recording this video a lot of companies still ask those

304

so for better for worse so for

305

that i would highly recommend cracking the coding interview

306

and rereading um clrs which is like the standard textbook

307

that teaches all the fundamentals for data destruction algorithms i will also say

308

that even if you don't use recursion or balance a binary tree every day in your job,

309

knowing the fundamentals is still useful

310

and you don't want to be in a position where you

311

need to have your AI explain every single thing to you

312

while you're trying to debug an issue because that's just bad for you and bad for the company.

313

I feel like maybe everybody knows about this, but I think NeetCode genuinely the best resources online

314

if you want a video format for learning data structures

315

and algorithms rather than the book format but

316

if you can somehow get yourself to read a book I think you'll also probably learn more

317

that way so that's what I used I ended up using need code stuff back in the day

318

and then next I would say system design especially

319

if you are going for a more senior role is more

320

and more important as someone who came from big tech even

321

if you use system design in your company sometimes

322

if you are work for a big enough company the stack

323

that you use might not be standard so definitely recommend refreshing

324

and like constantly learning what is new

325

and what is widely used in the fields so for

326

that i recommend personally um i really like hello interview

327

so i think they have they have a bunch of youtube videos

328

i think they have a page here as well

329

i personally didn't pay for it like i use their free youtube videos the reason why i like them is

330

because they basically give you mock interviews for very like standard

331

system design questions like for example oh like design like youtube feed

332

or design facebook but what is really good is that they not only tell you what is passing, They also tell you what isn't passing,

333

like what are common mistakes that candidates make.

334

They also tell you this is passing for a mid -level candidate.

335

This is passing for a senior, for staff.

336

So it's really a great way for you to calibrate yourself.

337

And it gives you not just the right answer, but why that answer is the right answer.

338

Do you think system design is a non -negotiable for early career engineers today?

339

I would say to do well in the job, it is non -negotiable.

340

So because of that, I would say if you have time, definitely learn system design.

341

I personally didn't learn system design formally until I was interviewing to get the role I have now.

342

So that, I think, took a lot of time

343

because I was going from very little

344

because I joined my previous company without any system design experience because I was joining as a new grad.

345

So if you have time, would recommend system design.

346

It makes you not only a better interviewee, it also makes you a better engineer.

347

And finally, as we all know, AI is getting more and more important regardless of what part of engineering you're in.

348

So I personally really like one of my friends, Her name is Chip Huynh.

349

She has a book called AI Engineering, which is really, really comprehensive.

350

And I would say if you're going to just read one AI book in 2026, read that book.

351

It takes you through all the fundamentals.

352

And she goes through a lot of concepts.

353

She talks about like RAG, about agents, about MCP, about beddings.

354

And it's very, very digestible in a format that you can understand even

355

if you don't have a strong or any ML or AI experience.

356

Okay, so we've just gone through the learning layer.

357

Let's talk about the application layer.

358

Most people spam thousands of applications and never hear back.

359

But you've gotten interviews at OpenAI, Netflix, Databricks, and Google.

360

So where do most people go wrong?

361

I would say most people go wrong because they just like,

362

like you said, submit thousands of applications without thinking about if the role is a good fit,

363

without like, without reaching out to the company, without getting a referral.

364

So unfortunately, because there are so many candidates right now that want job, if you don't have like a previous connection,

365

like for example, if you didn't get a referral to the company, the chances of you getting an interview

366

and a callback are much, much lower i will also say i personally got some interviews

367

because a recruiter saw my profile on linkedin

368

and then like reached out being like oh i think this would be a good fit for you so

369

if it is possible for you to put yourself out

370

there more on linkedin that'll make it more likely for recruiters to organically reach out to you by

371

that i mean you could you know talk you could link your projects

372

you could put like specific keywords like for example

373

if you built a rag system for your company you can put rag you built mcp you could put mcp

374

that just like makes it more likely if a recruiter is searching like candidates

375

and a keyword for a job

376

that you will be one of the people considered yeah on the referral note

377

i think a lot of people hear that advice

378

and then they'll get one referral to google

379

and then they won't get an interview

380

and then they'll throw their hands up in there and be like

381

but i'm on but maddie it just didn't work like referrals don't work

382

but in reality just

383

because you get a referral it just increases your probability of getting an interview

384

it doesn't guarantee anything you know what i mean and in fact,

385

I've worked with a student who got a Microsoft referral and then within an hour or two got rejected.

386

And then they messaged me, yo, what the hell am I got rejected?

387

It didn't work.

388

And I was like, bro, you didn't get ghosted.

389

That means they actually looked at your application within a few hours and rejected you, which is a huge win.

390

Like that's way better than being ghosted.

391

So all it is is a referral just creates a different pool that they hire from.

392

You're not guaranteed to get anything, but it just increases your odds from a cold application.

393

So I would highly to recommend referrals.

394

Yeah.

395

And like you mentioned, it doesn't guarantee anything.

396

And I think especially when it comes to larger companies, like there will be many hundreds of people who have referrals.

397

So just scale wise, the recruiter will not give everyone an interview.

398

I will say if you are able to, you can also focus on smaller companies,

399

especially if you can get like a referral from a smaller company

400

that will really greatly increase the chance

401

that your application will be taking more seriously because they will not get like the hundreds, thousands of referrals that people get when applying to Google.

402

They'll get like more curated ones and they know

403

that they can trust their own referrals a little bit more than if it was just like a toss up.

404

100%.

405

I think the power of a referral scales the smaller the company, right?

406

Like for example, startup referrals matter immensely.

407

Most startups, the CEO or founder or whatever reviews basically every single referral, especially at the early stage,

408

just because it's so valuable for them to get hiring right.

409

And I personally know multiple startups of recruiting where like the

410

referral just goes straight to the to the hiring person like every single one gets reviewed

411

you might not get interviewed but at least you'll get reviewed

412

so going for smaller companies definitely makes sense yeah

413

and like it like like you mentioned it's like much better to know immediately

414

you're not a favorite rather than just like wait like i've there are many companies

415

that have ghosted me and other people

416

and it just like i would much rather just get like

417

a no immediately rather than like oh will they won't they for months another objection i often get

418

when it comes to referrals with the people

419

i work with is they often say come on i'm just

420

too nervous to ask for it i don't want to bother someone why would they refer me

421

so how do you get over the fear of rejection

422

when it comes to asking for referrals that's a great question

423

i'll say i myself am not really good at getting over

424

that fear i'm still super self -conscious like obviously i've not job interviewed for many like quite a

425

while but when i was interviewing to get to the job i currently have i felt

426

so self -conscious what kind of helped was thinking that

427

that oh it's not just good for me to get a referral a lot of companies if your person gets hired

428

you'll get a bonus

429

so i personally have gotten some bonuses from people i referred to at google

430

when i was there

431

so it's like a benefit it's mutualistic like it's not just good for the interview

432

it's not just good for the candidates also good for the fur

433

that's one thing also um it's kind of cliche

434

it's like they don't it's like you you miss 100 the shots

435

you don't take they don't have to say yes like obviously

436

if you're not a good fit they might not refer you and that's totally fine.

437

It's like, I feel like I was afraid of like, oh, like what if I'm like pressuring my friend to refer me?

438

But I think like, again, if they don't think you're a good fit, they don't have to refer you.

439

And like, I wouldn't take it.

440

I don't think anyone should take it badly if you are refused a referral.

441

So honestly, just putting, being more comfortable with putting yourself out there is a good trait for many, many different use cases, not just the referrals,

442

but for the referral in particular, I think it's just something, it's like getting over the initial fear is really, really powerful.

443

Okay, we've talked about applications and getting more interviews through networking, but you've actually been on both sides of the table.

444

You've interviewed at these big tech companies, and you've also interviewed people trying to get jobs at these tech companies.

445

And right now, interviews are crazy.

446

I mean, people are cheating using AI, left and right, and companies are redesigning their whole interview process.

447

So could you actually break down what do early career interviews look like in 2026, and how does someone navigate that minefield?

448

This is in flux because interviews are rapidly evolving

449

but as of right

450

now most companies will still start with your standard like phone

451

screen where they ask a candidate like oh like you know

452

why do you want for to work for xyz um are

453

you okay like you know logistics with the compensation the relocation

454

etc as of now they'll give you a legal style interview

455

so it's like your standard like data destruction algorithms challenge

456

i think some companies give multiple it depends on the company

457

and like especially startups i think do more of their own thing i noticed after

458

that usually you'll get especially if you're a senior you'll get on -site

459

which is like a more back -to -back hours of interviews.

460

So oftentimes companies will give you a system design round.

461

So for example like oh can you implement like a notification system?

462

Especially if the company is smaller you'll often get to talk directly to the hiring manager

463

that wants to fill the position so they can kind of judge if you're a good fit.

464

Some companies will have a round where they want you to basically explain a project that you built previously.

465

That's just like a way for them to gauge if you know how to like explain challenges that you face, drop like system design infrastructure diagrams,

466

any challenges and things like that.

467

And then finally, a lot of companies are starting to incorporate those like AI assisted interviews.

468

So I personally have not done any because when I was interviewing back in the day, a year and a half ago,

469

most companies weren't doing this.

470

But nowadays, a lot of companies will have a problem

471

that you're supposed to solve and they let you use your AI coding agent.

472

And then they'll they might ask you questions about how you're using that agent.

473

They might like kind of quiz you on that.

474

Recognizing that you haven't done one of these interviews nowadays, of course, but what do you feel like the best resources

475

or techniques are to prepare for those new kinds of interviews, right?

476

Everybody knows about Classic, LeetCode, DSA, etc. But what about those new AI enabled interviews?

477

That's a good question.

478

So my friends who have taken the interviews generally say like

479

a lot of it's just using AI naturally in your day to day workflow

480

and just finding ways that will make you faster and optimized.

481

Also, I know, for example, Anthropic has guides on prompting so they have found those useful as well

482

and those are free so I think those are good resources to help you optimize how you prompt.

483

Do you have any AI cheating stories where you were interviewing a candidate and you realized they were cheating?

484

Yes maybe it'll be different ones you know AI is condoned in the interviews

485

but I have given a couple of like standard data instruction algorithm questions

486

and it's maybe the people who cheat well I don't notice

487

but the people that I have noticed have been like super super obvious

488

so for example like I had a person who like was typing

489

and then at some point they like yawned

490

and it like it kept on typing i was like what like literally like they reached back they reached back

491

and went like went like this i was like are you seeing

492

this um another time i had a candidate had glasses

493

and there's a reflection in myself and i was like okay like you know

494

that kind of stuff there's been just my friends have also experienced like things

495

there's like someone who was reading like almost verbatim so for example

496

when I asked

497

when they asked a question there's like oh that's a great question the answer to this is blah blah

498

that would happen and I've noticed my friends have said

499

that sometimes the way to catch

500

if it's not super obvious is like you start asking a question

501

that is just wrong like a question doesn't really have good answer

502

and if the person is cheating with AI they're gonna the AI is gonna attempt to answer it

503

if the person's a real person they're gonna be like wait

504

that makes no sense

505

and like ask to clarify yeah I feel like the people I've talked to it ends up being pretty obvious

506

when someone's cheating with AI and I think another tell is like the imports like

507

if you do all your imports at once

508

and then start coding it's like what nobody actually does

509

that you know what i mean

510

so there's like some i feel like niche like micro tells for most people um

511

when it comes to revealing cheating but that's really funny for sure all right

512

so we've gone through projects courses learning the market resume applications and interviews let's talk about the offer.

513

So if you finally got a job offer, can a junior with essentially no leverage negotiate in this job market?

514

And two, how do you not get fired or laid off in this new economy?

515

That's a great question.

516

The first question, I would say if you're able to do all your interviews all at once, so you have competing offers,

517

that's like the best leverage you can get if you don't have prior experience, if you're not currently in a company.

518

A lot of companies will match, depending, especially if it's a competitor, like a good, if it's like a serious competitor to them they'll match

519

or even do more than your other offers

520

if you can show them proof

521

that you did get this other offer you can also use resources online

522

that give you information on what the companies are actually paying other people

523

so the top of my head blind is kind of toxic

524

but blind does have salary information

525

so sometimes people will post being like hey like i have this offer is this good

526

or bad and people will say it also levels .fi

527

if it's a bigger company you can anonymously submit your pay to levels at fi

528

and they check like i'm pretty sure they verify the pay stub they just don't obviously post the pay stub

529

so that's like a verifiable way that you can kind of see the range

530

that your your company is paying other people so

531

if they're offering you less you can counter

532

that makes sense all those seem like very good strategies to negotiate

533

but do juniors have leverage at all like have you heard of juniors entry -level people still negotiating

534

or is that something that just doesn't happen anymore nowadays i think

535

that if the company itself sometimes gives different stock options

536

that there's still possibility like i've heard juniors doing

537

that however i know a lot of companies like for the base pay

538

when it comes to juniors they don't negotiate at all

539

and that's just kind of company policy i think

540

this is also another place where the smaller the company the more negotiation power

541

so for for big tech at this point

542

and maybe i'm wrong about this

543

but a lot of these like entry -level roles are pretty

544

standardized especially internships like you can't really negotiate on an internship

545

but i guess the more advanced you get

546

and also the smaller the company like there's more power

547

there in terms of negotiation exactly there's no like definitive way to avoid layoffs

548

or avoid like getting pushed out unfortunately

549

but i think there's a couple things you can do to increase your chances of surviving

550

so one of them especially if you're a junior like definitely make sure

551

that your manager or your management chain is very much aware of what you've accomplished for example

552

if you like document all your wins that's like really good

553

because then your manager has like proof that you can list your prs

554

and you can like write your you put add your docs on there your manager

555

then has like a very easily accessible way for them to

556

check on your progress something else is to be honest like companies nowadays

557

i would say are a little bit more risk averse

558

and a little bit more they like to prioritize orgs

559

that make money i've noticed a lot of companies like this so if you want an org that probably won't get downsized,

560

perhaps it's the one in your company that's like ads or like that makes money or is doing like frontier AI stuff.

561

So again, there's no definitive way to not get laid off.

562

But those are two things you can do to help decrease your chances, in my opinion. For sure.

563

I feel like the best strategy to not get laid off is just accepting you might get laid off

564

and just keep up your resume and your AV skills so that even if you do get laid off,

565

you can find a new offer pretty quickly.

566

I think especially with layoffs

567

and like large scale big tech layoffs like i've spoken to

568

multiple people who went through the meta layoff a few months ago

569

i'm sure you know people as well went through

570

that it was almost like there's there was essentially no way to predict who was head

571

and i'd be really curious to talk to someone who actually decided who got laid off

572

because it feels like almost like voodoo like you have no clue who got laid off

573

there were people who felt like there were better engineers than others who were laid off

574

and other ones who were spared so you kind of have no idea

575

when it comes to this stuff all

576

you can just keep your profile your resume your applications your networking your interview skills up

577

so you can find a new job faster all right

578

so we've gone through the entire process end to end for how to survive

579

and get hired in the 2026 job market

580

i guess final point maddie what's your one piece of advice

581

to someone who's an early career engineer zero to three years of experience who's struggling to get a job today

582

i would say do not be afraid of rejection um even me as someone

583

you know who's like a classically okay like where's me like i went to mit

584

i intern at Microsoft Amazon Morgan Stanley worked at Google

585

I get a lot of rejections like over the years I used to be

586

so afraid of getting rejected I wouldn't apply

587

because I was like oh like I don't want to get like rejected

588

because that seems final but first everyone gets rejected like even the people

589

that you most admire they've gotten rejected from hundreds of places

590

like they just obviously won't put on their resume on their LinkedIn

591

that they got rejected right it only takes one offer

592

and then after you get the offer then it will help you move on

593

and on so I think that for me fear failure was something

594

that i'm still struggling with at this point

595

but definitely was really detrimental to my career when i was younger

596

and that's something

597

if i could go back i would be like i don't

598

i don't care i should have applied before i thought

599

i was ready i should have applied like you know i should apply to the companies

600

that i i thought i had no chance of getting into

601

and i will say that a lot of my A lot of my friends are doing very well now.

602

They did that.

603

They were not afraid to apply to all the really nice companies.

604

They were not afraid to apply before they studied data instruction algorithms.

605

And some of them did get in.

606

So even if there are requirements, those requirements aren't strict requirements.

607

Maddie, people want to connect with you further.

608

Where should they go?

609

You can find me on YouTube at Maddie Zhang.

610

And you can also find me on Instagram at Madeline .M .Zang.

611

Thank you.

612

Awesome.

613

Maddie, thanks for doing this.

614

Thank you for having me.

Scarica l'app

Tutto ciò che serve per parlare fluentemente

Pronuncia con IAVoto per ogni frase

Pratica IPAPadroneggia ogni suono

VocabolarioCostruisci il tuo lessico

Gioco di vocabolarioImpara giocando

Scansiona QR

Download on theApp Store Get it onGoogle Play

FOR YOU

Video consigliato

365 frasi

Vocabolario e note di pronuncia per questa lezione

Questa lezione di conversazione si basa sul video “ex-Google Senior Engineer: How to Get Hired So Fast It Feels Illegal”. Questo video contiene 613 frasi e 7731 parole da ripetere con lo shadowing. Il parlato dura 35:17. Chi parla va veloce, circa 219 parole al minuto: aspettati suoni legati e ridotti. Il 84% delle parole rientra nelle 3.000 più comuni dell’inglese; conviene studiare le altre prima di iniziare.

Vocaboli chiave di questo video

15 parole del video che vale la pena imparare, con pronuncia e significato:

Parola	Pronuncia	Significato
hire verbo	/ˈhaɪɹ/	assoldare, noleggiare
internship sostantivo	/ˈɪntɜːnʃɪp/	stage, tirocinio
nowadays avverbio	/ˈnaʊ.ə.deɪz/	oggidì, oggigiorno
resume verbo	/ˈɹɛz.ə.meɪ/	riprendere, continuare
recruit verbo	/ɹɪˈkɹut/	arruolare, reclutare
prompt verbo	/pɹɑmpt/	incitare, guidare
cheat verbo	/ˈt͡ʃiːt/	fregare, imbrogliare
algorithm sostantivo	/ˈælɡəɹɪðm̩/	algoritmo
fundamental aggettivo	/ˌfʌn.dəˈmɛn.təl/	fondamentale
generate verbo	/ˈd͡ʒɛn.ə.ɹeɪt/	generare
startup sostantivo	/ˈstɑɹtˌʌp/	avvio, inizio
guarantee sostantivo	/ˌɡæɹ.ənˈtiː/	garanzia
essentially avverbio	/ɪˈsɛnʃəli/	in essenza
solve verbo	/sɒlv/	risolvere
submit verbo	/səbˈmɪt/	sottomettersi

I phrasal verb che sentirai

Parola	Significato
lay off verbo	licenziare
go through verbo	attraversare
end up verbo	andare a finire, finire
get over verbo	superare, vincere
go back verbo	tornare
double down verbo	rincarare la dose
figure out verbo	scoprire, rendersi conto
go up verbo	salire

Frasi da ripetere

Frasi brevi e complete del video che puoi riutilizzare nella conversazione di tutti i giorni:

On that note, let's talk about projects.
Don't just build a calculator in your bedroom.
I don't think those are mutually exclusive.
I'm still friends with them for this very day.
Let's talk about learning, courses, and books.

La grammatica di questo video

Le strutture che chi parla usa di più, con le parole esatte del video:

Struttura	Nel video
Frasi condizionali if + frase, will/would + verbo — una condizione e il suo risultato	if you have time, would recommend · if you're a senior you'll get · if the company is smaller you'll often
Present perfect have/has + participio passato — un’azione passata che conta ancora adesso	have cut · has seen · you've actually gone
Forma passiva be + participio passato — conta ciò che accade, non chi lo fa	are expected · being used · are deemed
Frasi relative who / which + frase — un’informazione in più su una persona o una cosa	people who are · friends who are · someone who vibe

Pronuncia a cui fare attenzione

Chi parla usa 184 contrazioni e forme ridotte, come don't, you're, I'm. Pronunciale nella forma breve, così come le senti.

I suoni “th”: algorithm /ˈælɡəɹɪðm̩/, bother /ˈbɑðɚ/, worthy /ˈwɝ.ði/, hackathon /ˈhæ.kə.θɑn/, anthropic /ænˈθɹɒp.ɪk/
I suoni “sh” e “zh”: internship /ˈɪntɜːnʃɪp/, essentially /ɪˈsɛnʃəli/, negotiate /nəˈɡəʊ.ʃi.eɪt/, destruction /dɪsˈtɹʌkʃən/, specialist /ˈspɛʃəlɪst/
Parole lunghe — attenzione all’accento: fundamental /ˌfʌn.dəˈmɛn.təl/, essentially /ɪˈsɛnʃəli/, negotiate /nəˈɡəʊ.ʃi.eɪt/, infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, genuinely /ˈd͡ʒɛn.ju.ɪn.li/

I suoni difficili per chi parla italiano:

/h/ — va soffiata, non è muta: hire /ˈhaɪɹ/, comprehensive /ˌkɑm.pɹəˈhɛn.sɪv/, hackathon /ˈhæ.kə.θɑn/, headcount /ˈhɛdˌkaʊnt/
Consonante finale — senza aggiungere una vocale dopo: internship /ˈɪntɜːnʃɪp/, nowadays /ˈnaʊ.ə.deɪz/, recruit /ɹɪˈkɹut/, prompt /pɹɑmpt/, cheat /ˈt͡ʃiːt/
/æ/ — più aperta della “e”: algorithm /ˈælɡəɹɪðm̩/, guarantee /ˌɡæɹ.ənˈtiː/, format /ˈfɔːɹ.mæt/, react /ɹiːˈækt/, stack /stæk/

Come esercitarsi con questo video

Ascolta tutto il video una volta senza parlare e annota le parole che non conosci.
Inizia a velocità 0,75×, fai shadowing frase per frase e torna alla velocità normale quando diventa facile.
Registrati e confronta con l’originale, facendo attenzione a parole come hire, internship, nowadays.

Cos'è la tecnica dello Shadowing?

Shadowing è una tecnica di apprendimento delle lingue supportata da studi scientifici, originariamente sviluppata per la formazione dei traduttori professionisti e resa popolare dal poliglotta Dr. Alexander Arguelles. Il metodo è semplice ma potente: ascolti un audio in inglese di madrelingua e lo ripeti immediatamente ad alta voce — come un'ombra che segue il parlante con un ritardo di solo 1–2 secondi. A differenza dell'ascolto passivo o degli esercizi di grammatica, lo shadowing costringe il tuo cervello e i muscoli della bocca a elaborare e riprodurre simultaneamente i modelli di discorso reale. La ricerca dimostra che migliora significativamente la precisione della pronuncia, l'intonazione, il ritmo, il discorso connesso, la comprensione dell'ascolto e la fluidità del parlato — rendendolo uno dei metodi più efficaci per la preparazione alla prova di speaking dell'IELTS e per la comunicazione reale in inglese.

Tecnica dello shadowing: leggi la guida completa passo dopo passo →

Pratica di Shadowing: ex-Google Senior Engineer: How to Get Hired So Fast It Feels Illegal - Impara a parlare inglese con i video

Scegli una modalità di pratica

Scarica l'app

Top 1% Career Strategy: How to Get Hired in the AI Era

How much money Software Engineers make? 💰 ft. Maddy

Google’s AI endgame is here… everything you missed at I/O 2026

Why Companies Are Quietly Rehiring Software Engineers

How to Become a Great Software Developer — Best Advice from Top-Notch Engineers

how AI broke the SWE Career Ladder

If I Had to Become a Software Engineer Again in 2026, I’d Do This

Why AI is Legal’s New Competitive Advantage - Future of Work Podcast

Rapid Engineering With AI

P1 机器学习的应用【2024公认最好的 | 吴恩达机器学习 | 教程 | Machine Learning Specialization(超爽中英!)】

Nobody is hiring vibe coders. Sorry

How AI is Changing Data Scientist's Workflow

Vocabolario e note di pronuncia per questa lezione

Vocaboli chiave di questo video

I phrasal verb che sentirai

Frasi da ripetere

La grammatica di questo video

Pronuncia a cui fare attenzione

Come esercitarsi con questo video

Cos'è la tecnica dello Shadowing?