Prática de Shadowing: how AI broke the SWE Career Ladder - Aprenda a falar inglês com vídeo

Escolha um modo de prática

Cada modo abre uma sala de prática em tela cheia.

315 frases

Se as frases estiverem muito curtas ou longas, clique em Edit para ajustá-las.

So AI did two opposite things to the junior level, which is number one, in the short term, there are a lot less jobs for juniors.

We have unemployment for serious computer grads at 6 % for the first time in years.

That also has to do with the economics, but on the flip side, it also empowered the juniors a lot more.

So back in the days, if you'd be a junior, you really needed a lot of handholding.

And pretty much any questions had to be answered by a senior engineer

that had to mentor you usually those people never had the time

because they're just churning out features and doing bugs

and you'd be left at your own devices with whatever documentation

companies had usually not a lot nowadays they give you a

code base you can just query it with the llm

and the llm not only answers questions

but it can also guide you to bring a feature to an end

and even do it for you

so all of a sudden juniors can actually deliver features kind

of end -to -end almost features two questions pop into my mind.

Number one, if juniors can deliver end -to -end, or almost can deliver end -to -end, what does this mean for mid -level and senior developers?

And secondly, if juniors with AI can deliver end -to -end, then why aren't there any job openings and it's so hard to find a junior position in the first place?

Yeah, so because juniors are also delivering end -to -end features, the frequency of everything that we shipped changed a lot.

We are shipping a lot more code.

So a lot of the work at the senior level, we'll see it's around building the software factory, building the systems that can sustain all this as a junior they can deliver features

but do they understand the long -term consequences of choosing one strategy for our css

or for our components of our backend rather than the other

probably not they can know it at a theoretical level

but they never had that production experience when things actually break

so yes they can deliver a lot more but you need seniors to enable the platform on which they deliver.

So that's number one.

And about the employment question, the problem is the junior label,

the way the industry recruiters and hiring managers look at juniors is still as someone that needs handholding.

And given the immense pressure it's on the budget right now, because a lot of companies are buying tokens, they're spending on AI and tokens and so on,

they really want someone that just can come into the codebase

and deliver end -to -end just because the economics around it

so what happens is they don't want to bet on someone it's also

because there's so much change they don't really know where to go

so they want the senior people to kind of tell them

they are not ready to absorb junior work all this is to say is

that if you're a junior you have to brand yourself as a software engineer take any work you can

if you can freelance if you can work for free

if you can do volunteering so You can add work experience to your resume

and work with AI and then go to companies and show them how you can deliver end -to -end.

Never market yourself as a junior and don't mention side projects or anything that makes you look junior.

People talk about their portfolio and side projects.

Those are, they scream junior.

You rather show them something that's real.

So if I understood correctly, if I'm a junior engineer right now, I should think of myself as a senior engineer from, let's say, five years ago.

Because with AI, even as a junior, you're way closer

and way more able to deliver almost end -to -end like a senior a few years ago

and companies are still stuck in this old mindset where they

are actually looking for what the senior engineer was a few years ago right

so you are solving two problems in one shot exactly now

moving on to the mid -level bugdon how do i go from junior to mid -level

and what does mid -level means these days with ai

so obviously mid -level engineers also got a lot of benefits from ai

and so back in the days you define mid -level as someone

that can own a feature now they can own a whole application

so if you're a front -end engineer you could probably work across the whole surface of the application

and even make more global decisions and

if you're a back -end engineer it's pretty much the same what changed is

that as a front -end engineer now because

when you're mid -level you're working a lot of times in implementation building the feature now

that will be more or less instantaneous

so you have the chance to go into architecture you'll have the chance to go into the CICD pipeline

if you're a front end you can even touch a bit the back end and

if you're a back end engineer you can get closer to

either the DevOps side of things go deeper in the database just

because your time freed up so not only you do feature delivery

but all of the sudden you can care about architecture a bit of system design

and entry and delivery

when it comes to observability metrics CICD granting uptime all those

things used to be owned by the senior in the team

but now it kind of democratizes in a way one question

that comes to my mind Bogdan is now

that everybody's kind of moving up

and doing more the juniors are doing more the mid -levels

are doing more I guess the seniors are also doing more

a lot of people are worried about conflicting responsibilities you know

if I'm doing more

and you are doing more at some point we are going

to have a conflict we're going to have a collision right yes

if you assume a static mindset where we're building the whole thing

and now you can also do what i used to do then cool

but what happens with ai is that a lot of things

that were not possible are now possible people

that were building young native apps are building now native apps with swift

and ios so the surface

that any of us has to own became much bigger the

expectations on a junior level are not the ones we used

to have the expectations for a normal software engineer are not the ones who have the speed at

which you need to make decisions in terms of the quality of the code it's much higher

and you need to make a lot of decisions without necessarily

knowing what the code is you need to somehow infer what

this decision will mean for the code base not only that

but what we are seeing is that the focus now it's on token efficiency

so until i think mid of this year it was all

about okay let's adopt the i edit everywhere spend as many tokens as you can token max

but now companies realize hey it takes time to build valuable stuff it takes time for us to monetize this

but our cost increased now we spend on the people

and on ai so what they are doing is okay let's talk to our senior engineers

and see how do we spend our tokens how do we

design the code base how do we design a token efficient code base

100

and we call that a zero token architecture

101

so things definitely change we are not building the same software we used to build three years ago

102

if you're looking at the software from three years ago your typical crowd application

103

that would take a lot of manual work to get to

104

production then yes you'd feel like oh my god i'm being displaced

105

but the reality is yes you are being pushed up

106

but there's a lot of space up where you can grow talking about this intuition about technical decisions

107

and making technical decisions i guess

108

that leads us to the senior engineer senior full stack seems

109

like we have there how does the senior engineer level changes with ai

110

so one of the biggest difference between all those levels is

111

that with ai they could all build the same feature

112

but the way you can tell if someone needs to see

113

or not it's by the quality they get in their first

114

version what we are seeing is a lot of applications are

115

just releasing slop there's a lot of production box there's a lot of incidents

116

because people don't think too much about what they're doing they don't think about the consequences

117

or they don't have the experience to own the surface they they have

118

so we are passing this debt to the consumer we are passing the box to the user

119

and you can see big applications are breaking and

120

so the difference today is not any more the speed back in the days you were a senior

121

if you could deliver faster

122

and the reason why you could as a senior engineer own end -to -end features is

123

because you are reasonably faster across all the stack whereas the mid -level let's take them ages

124

so now the difference is quality

125

whereas a senior could get the same feature live they would spend less tokens

126

and there will be less production defects there will be less bugs basically the other difference is

127

that the senior can understand the software factory we are building not only the feature

128

that comes out

129

but also how should we set up our agent md our

130

skills what models should we use how to make the system more stable

131

so they talk more about the not only the car

132

but the factory

133

that produces the car now a lot of people are talking

134

about software factories i saw other people comparing it with the kitchen

135

because software it's a design process we are not churning out the same car all the time

136

so this whole comparison with the factory is not direct people are trying to build a structure

137

but the software needs to be a lot more mobile anyways all this is to say

138

that see the senior full stack engineer would probably be the person

139

that delivers across the stack with ai with the highest quality in the least amount of iterations

140

and i would say they don't only deliver software

141

but they make the system

142

that delivers software the teams the ai the code base the harness

143

that the models are working around them better right

144

and that's a totally new dimension for senior engineer one thing

145

i want to touch upon it's we see a lot of front -end engineers

146

which are also lost they feel like the market has been displaced

147

and that's why you have this full stack word there bogdan

148

so why full stack

149

so with ai all of us are required to move towards the full stack a bit more

150

so either you're in the back end

151

or in the front end companies they want speed they know what the models can do

152

and you will be required to work across a full stack

153

now this does not mean you have to get into database optimization but

154

if you look at front -end engineer positions in the US

155

in the last three months we scrapped around 10 ,000 of them

156

and 60 % were mentioning REST APIs

157

and Node .js as a core skill those are front end positions

158

so front end is not anymore adjust the client application you also care about the data layer

159

so my advice to everybody in the front end is look

160

at your front end skills make sure they are solid and

161

if they are your best way to increase your chances in

162

today's market it's add full stack skills to your skill set Bogdan, what about the next level?

163

I think at senior level, it's where people split between individual contributor and engineering manager.

164

And I know at least engineering managers have been highly impacted by AI.

165

Yes.

166

So when it comes to the senior full stack engineer, this is what we call career level because it's where you could stay for the rest of your career.

167

Now, the thing that changed with the senior level is that back in the days, you used to be very attached to your tech stack.

168

So you'd be a senior full stack engineer that knows react

169

and typescript nowadays it's easier for you to extrapolate that to

170

other programming languages or even other platforms so

171

when we talk about full stack it's not anymore about your typical stack somebody

172

that can really think about the high level the fundamentals of software engineering

173

and they can apply

174

that to even a different platform like i don't know you

175

could do embedding engineering you could build a mobile app

176

so this is the most stable level it's also the hardest to get to

177

because you need to be able to move very fast from sql optimization to CSS patterns.

178

So your fundamentals have to be really strong

179

and you need to have this ability to transverse your knowledge from one point to the other.

180

Now moving up you could choose to either go on the management track or go to the CTO level.

181

What we've seen in the last couple of years is that the management track also became more thin.

182

A lot of companies fired a lot of engineer managers and a lot of tech leads.

183

A lot of the clarification and alignment can be done with the central LLM.

184

Other companies have this central LLM that you can ask things about the company strategy.

185

So a lot of the management work, it's also being replaced.

186

But again, when it comes to hiring people, making sure the culture is okay, you probably have a lot more conflict now, as you mentioned, between different people because they all overlap.

187

It's very hard to set boundaries for responsibility if there's a live bug who did this.

188

And so I do think you will need very good engineering managers

189

and head of engineering

190

but again the the sector is changing a lot of those big companies have been letting people go

191

and what amazon and a lot of other companies did is

192

that they force their engineering management to become hands -on

193

which is closer to the senior full stack goal

194

or the lead developer so all in all this is to say

195

that the engineering manager also needs to become a bit more full stack

196

and i would add bogdan now that everyone is building and building

197

and shipping i i feel like alignment of the product alignment

198

of the team alignment of the code base it's something

199

that someone has to do a lot more intensely than they used to do a few years ago

200

because you just have a lot more stuff

201

and it's easy for teams probably to go in different directions

202

to be like let me build this let me explain everybody has a an experimentation mindset right now

203

and i think they forget about the vision right

204

and probably an engineering manager role is to align

205

that tangle vision just more intensely like before

206

because there's more stuff being built align the product managers behind it

207

and align the management behind it so

208

if i would be an engine manager right now in the

209

market i would specifically talk about my my ability to steer teams in the right direction

210

when they're building and shipping so much exactly

211

so it's easier than ever to just go into 100 different directions

212

and you'll see products

213

that are not cohesive at all in terms of how they behave i'm not only talking about css

214

but also like the interaction patterns how screens look like

215

and what happens to the back end it will all look different

216

and the one thing that i want to mentioned with AI is that it made easier to build new software companies.

217

Now, it's going to take some time, but you do see a lot of AI founding engineers, a lot of positions where they require someone that's pretty much at the senior level

218

and has a bit of understanding of the product, and they're building things from ground up.

219

So what happened is big tech is getting a bit displaced, and a lot of the new positions, and it's very relevant to your senior full -stack engineer, will be in traditional industries, where you go into finance or healthcare,

220

and you are working almost directly with stakeholders and AI to build something from scratch.

221

Awesome.

222

Then what about the individual contributor path beyond senior?

223

We had, you could become a freelancing contract to stay at the senior level.

224

Like you said, you could become a lead developer and lead teams, but technically.

225

And then there was a principal staff engineer path.

226

Exactly.

227

So the freelance contracting is pretty much the same dynamics as a senior.

228

The only difference is you can usually charge more, but you have less stability.

229

Lead developer is pretty much where engineering managers are being forced.

230

And the principal staff, this one is weird because those are the people that are actually focusing on actually the AI work.

231

So this means kind of building harnesses, doing a lot of context engineering at company level,

232

and doing a lot of choosing which models we use, optimizing our tokens.

233

So there's a lot of work to be done there.

234

And also there's a lot of pressure on all these downstream services.

235

People are releasing daily now.

236

We used to release every two weeks.

237

And so there's a lot of things that are breaking under the hood, and the principal engineers are the ones responsible to get the company there.

238

One of the good examples I can give is we had this new model that is JEV, which is basically about adding static.

239

the safety to LLM generations, to LLM decision -making, and that's where engineers, principal engineers come in and are like, okay, should we use a reasoning model?

240

Can we use a decision -making model?

241

Can we use a local model?

242

Can we run an open source model?

243

And all those kinds of things that are not, you don't need to be a machine learning engineer for this, it's traditional engineering, and that's where they would work.

244

Whereas back in the days, they would be like, oh, should we split this microservice or not, which is now the kind of work that even seniors can grasp.

245

Now, I feel like we went very fast around the freelance contracting.

246

That's a whole world by itself, because now with AI, companies feel very capable and there's a lot less freelance work going around in the first place.

247

And the work that's left for the folks watching us, the expectations are crazy because people are like, hey, I'm paying you a thousand bucks a day.

248

Then just can you just use AI and ship it?

249

So if you want to go into freelancing right now, number one, you're getting into a much more unstable market.

250

And number two, you have to be a master of managing expectations because what AI did,

251

it's totally distorted expectations over employees in the first place.

252

But I can't even imagine the pressure freelancers are under right now.

253

If you want Bogdan Knight to do a video specifically about the freelance dynamics with AI coding, then just let us know in the comments.

254

Now, moving on to the last ladder, Bogdan's CTO, very interesting for people who have high aspirations in the audience.

255

How did the CTO job change with AI?

256

so i think cto was one of the most stable just

257

because a lot of the skills at the cto level are

258

dealing with very incomplete information it's a lot about hiring

259

and yes you can ask how to do those things

260

but it will be a recipe for disaster you still need

261

experience what we see a lot is this position called founding engineer which is kind of a cto founding engineer

262

And you see a lot of small companies, people that were doing HR or sales, that all of a sudden, they see the opportunity to build their own software.

263

And they need a founding engineer, which is someone that kind of does product management and development.

264

And I think there's a lot of opportunities there too.

265

Now, you need to make sure that you have very sound fundamentals.

266

So you deliver with quality because you are the last person.

267

Something breaks, they'll come to you.

268

And you need the product skills.

269

So it's a combination between product management, moving fast with AI, and traditional full -stack engineering.

270

So I think that's a new one.

271

And it's pretty much the same about the, what we call the forward deploy engineer, which is the equivalent of a founding engineer,

272

but in a established company where you get in and you're doing a lot of consultancy around the product.

273

And then once the solution is defined, then you can execute on it with AI.

274

The million dollar question now, in the past, seniority being the difference between a junior and mid -level senior, what was all about technical ability, right?

275

But I feel like AI changed that.

276

And my question is, what makes us CMEA now?

277

And what is the thing that developers who want to level up should focus on?

278

What's the criteria there?

279

So if I were to summarize it in one word, it would be quality.

280

And so quantity is not a differentiator anymore.

281

Just like blog posts and social media posts, everything can be done in seconds with AI.

282

But the quality will be very poor.

283

And the problem with quality is that you'll get

284

that feedback after you deploy that to production and you have less users or more bugs.

285

And what we will see is that is the people that can reasonable software quality is the people that ask themselves, okay, we're having all these bugs.

286

Is it because the architecture has to be changed?

287

Is it because we need to use something different in the way we do our state management

288

or do we have to change our database?

289

And so that kind of questions and having that wisdom only comes from experience.

290

The problem I see with AI and cloud codes is

291

that they can definitely do great work if you are able to ask them to do great work.

292

And the only way for you to do that is if you understand software engineering, you understand how computers work, you understand HTTP, you understand HTTPS, and you really can reason about those things.

293

Now, you won't have to write as much code by hand as you used to, but the decision, the quality of your decision -making matters more than ever.

294

So yeah, somebody can come in as a junior and talk about how they can ship a lot of features, but nobody will care because everybody, even a product manager can ship a feature on the code base right now.

295

So it has nothing to do anymore with engineering.

296

And that's something I want to underline because people say, hey, you know, everybody can answer these questions.

297

You know, you just give them access to cloud code.

298

And we heard stories of developers and companies where everything is being done by AI.

299

Everything has been, the whole business logic has been fed into models

300

that tickets are being written by AI and they are being implemented by AI.

301

And it's all kind of this virtual dimension where nobody really knows what, they're just following what the LLM says.

302

And what people have to be aware of is that, yes, everybody can find an answer if they have access to cloud code, but what if they don't?

303

So the question is, how can you reason and what can you do without AI first?

304

Because everyone has access to these models.

305

They are a commodity.

306

The one thing I would close with is that everybody can buy a camera and everybody can buy a phone, but that doesn't make your photographer.

307

With that being said, folks, if you are trying to understand where you're at in the software engineering ladder, are you a mid -level, junior, senior, then check the link in the comments.

308

There is a free Tangle assessment that's very much focused on fundamentals.

309

It's about 10 minutes and it will give you a full overview of what your Tangle gaps.

310

Also, if you're looking to get hired in the next 90 days, check the link in the comments.

311

We have a specific program for that and

312

if you're looking to become an AI native senior full stack engineer

313

and work with Bogdan and I personally to help you do

314

that check the link in comments and see if you're a fit with

315

that being said Bogdan thank you so much and we will see you folks in the next one

Baixar aplicativo

Tudo o que você precisa para falar fluentemente

Pronúncia com IANota em cada frase

Prática de IPADomine cada som

VocabulárioMonte seu banco de palavras

Jogo de vocabulárioAprenda brincando

Escaneie o QR

Download on theApp Store Get it onGoogle Play

Mesmo canal

Backend Interview Questions (Junior & Mid)

Interview EnglishUniversity StudentsWorking Adults

FullStack Interview Questions (Junior & Mid)

Business EnglishInterview EnglishUniversity Students

React Interview Questions Senior Level (React Fiber, Reconciliation, Virtual DOM)

Daily ConversationUniversity StudentsWorking Adults

Senior Frontend Developer Interview Questions

Business EnglishInterview EnglishWorking Adults

FOR YOU

Vídeo recomendado

129 frases

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

Business EnglishInterview EnglishUniversity Students

130 frases

How AI Is Killing The Value Of A College Degree

Business EnglishInterview EnglishUniversity Students

263 frases

Anthropic's CCA Exam as a Field-Guide for Agentic Engineering — Frank Coyle, UC Berkeley

Business EnglishInterview EnglishUniversity Students

229 frases

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

Este vídeo tem 315 frases e 4251 palavras para praticar shadowing. A fala dura 20:33. O falante fala rápido, cerca de 207 palavras por minuto, então espere sons ligados e reduzidos. 87% 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
stack substantivo	/stæk/	pilha
token substantivo	/ˈtoʊkən/	símbolo, sinal
developer substantivo	/dɪˈvɛləpɚ/	desenvolvedor, desenvolvedora
expectation substantivo	/ˌɛk.spɛkˈteɪ.ʃən/	espera, expectação
architecture substantivo	/ˈɑː.kɪˌtɛk.t͡ʃə/	arquitetura
hire verbo	/ˈhaɪɹ/	contratar, alugar
fundamental adjetivo	/ˌfʌn.dəˈmɛn.təl/	fundamental
bug substantivo	/bʌɡ/	hemíptero
alignment substantivo	/əˈlaɪn.mənt/	alinhamento
stable substantivo	/ˈsteɪ.bəl/	estábulo, cavalariça
cloud substantivo	/ˈklaʊ̯d/	nuvem, nimbo
whereas	/(h)wɛɹˈæz/	enquanto, ao passo que
sudden adjetivo	/ˈsʌd.ən/	repentino, súbito
database substantivo	/ˈdeɪtəˌbeɪs/	banco de dados, base de dados
folk substantivo	/foʊk/	povo

Phrasal verbs que você vai ouvir

Palavra	Pronúncia	Significado
come out verbo	/ˌkʌm ˈaʊt/	sair, partir
set up verbo	/ˌsɛt ˈʌp/	preparar

Gramática neste vídeo

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

Estrutura	No vídeo
“Used to” used to + verbo — um hábito ou estado do passado que não é mais verdade	used to be · used to do · used to build
Voz passiva be + particípio passado — o foco está no que acontece, não em quem faz	be answered · be left · be owned
Orações relativas who / which + oração — informação extra sobre uma pessoa ou coisa	level, which is · ones who have · JEV, which is
Present perfect have/has + particípio passado — uma ação passada que ainda importa agora	has been displaced · have been · we've seen

Pronúncia para ficar de olho

O falante usa 54 contrações e formas reduzidas, como you're, don't, they're. Diga-as na forma curta, do jeito que você ouve.

Os sons de “th”: thin /ˈθɪn/, theoretical /ˌθi.əˈɹɛt.ɪ.kəl/
Os sons de “sh” e “zh”: expectation /ˌɛk.spɛkˈteɪ.ʃən/, dimension /daɪˈmɛn.ʃən/, optimization /ˌɑptəmaɪˈzeɪʃən/, efficient /ɪˈfɪʃənt/, efficiency /ɪˈfɪʃ.ən.si/
Palavras longas — acerte a sílaba tônica: developer /dɪˈvɛləpɚ/, expectation /ˌɛk.spɛkˈteɪ.ʃən/, architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, fundamental /ˌfʌn.dəˈmɛn.təl/, economics /ˌiːkəˈnɒmɪks/

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 stack, token, developer.

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: how AI broke the SWE Career Ladder - Aprenda a falar inglês com vídeo

Escolha um modo de prática

Baixar aplicativo

Backend Interview Questions (Junior & Mid)

FullStack Interview Questions (Junior & Mid)

React Interview Questions Senior Level (React Fiber, Reconciliation, Virtual DOM)

Senior Frontend Developer Interview Questions

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

How AI Is Killing The Value Of A College Degree

Anthropic's CCA Exam as a Field-Guide for Agentic Engineering — Frank Coyle, UC Berkeley

The Skills You’ll Need to be a Senior Software Developer

How Great Software Engineers Are Moving Faster Than Ever

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

How AI is Changing Data Scientist's Workflow

The Art Of Winning In Tech

AI & Education: Generative AI & the Future of Critical Thinking

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

The AI Take Over Has Completely Backfired (Here's the Proof)

A Return to Code

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

Vocabulário principal deste vídeo

Phrasal verbs que você vai ouvir

Gramática neste vídeo

Pronúncia para ficar de olho

Como praticar com este vídeo

O que é a Técnica de Shadowing?