Full Transcript

·YouTLDR

矽谷大神來了|Part2

18:14ZHTranscribed Jul 14, 2026
0:37

next question this is something i do

0:39

want to ask personally okay so right now

0:41

i'm a senior level software engineer so

0:44

how do i become like a staff engineer or

0:46

you know what what distinguishes an

0:48

engineer from senior level to say you

0:50

know staff or principal level very very

0:52

hard question in there because the whole

0:54

thing is that i can tell you that i

0:55

don't see any standard definition out

0:58

there that says that well this is the

1:00

definition of a junior intermediate

1:03

senior staff like principal architect

1:05

like yadda yadda like i don't see it

1:07

anywhere but i guess like the years of

1:10

experience of the projects that you

1:11

worked on before kind of contribute to

1:13

that

1:14

so it does but at the same time how do

1:17

you measure this yeah because you can

1:19

have someone that works three years over

1:23

at a startup and like basically just

1:25

figure out everything themselves like on

1:28

a very technical level being able to do

1:31

machine learning architecture

1:32

infrastructure building a scalable dom

1:34

system

1:35

right and you can have someone who has

1:37

been staying at um some ecosystem no

1:39

offense and lego system

1:42

i may get in a lot of trouble for this

1:45

and work 10 years on a very specialized

1:48

project that has no idea how to do

1:50

database yeah yeah right in that case

1:53

who is um who is closer to a senior

1:55

engineer who is closer to a principal

1:57

engineer so when you're talking about

1:59

like senior level engineers um like like

2:02

you're on a certain level how do you

2:04

want to grow and get to the next thing

2:07

you have to understand what the next

2:08

thing is first at least have an idea of

2:12

what you want the next thing to be is it

2:13

that you foresee yourself to be a

2:16

evangelist

2:18

to go into the company and teach people

2:21

and build tools and teach people how to

2:23

use tools to become better and like more

2:26

efficient in that job is it that you

2:28

want to be able to lead teams

2:31

to actually show them and be able to

2:32

take on bigger and bigger projects is it

2:35

that you want to have more time spending

2:39

on specialization which i just said

2:41

about the microsystem again no offense

2:44

to get into like something that is like

2:46

very specific that requires a lot more

2:49

time to do

2:50

that's where your growth paths are going

2:52

to be and in different companies they

2:55

can all be called principal engineers

2:58

so the question is back to you is what

3:00

do you want

3:02

for your next step let's see right so so

3:06

think about that like if you're saying

3:07

that hey

3:08

i want to learn how to take on bigger

3:10

and bigger projects and my answer would

3:12

be that you should know that at some

3:14

point of time you're going to run out of

3:17

your like your physical tighten speed

3:19

it's not going to be able to do bigger

3:21

and bigger project at some some point of

3:23

time you will have to subcontract it out

3:26

to to delegate this stuff

3:28

in that case the first thing that you

3:30

should learn is how do i actually get a

3:32

team how do i actually start organizing

3:34

people so that in the group of us we can

3:37

actually build something

3:39

right yeah and i would say that like if

3:41

you're going to do that doing work

3:43

talking with your boss and actually

3:45

getting the opportunity to take on

3:47

bigger projects

3:49

while bringing on other people sometimes

3:51

easiest bring on interns yeah right

3:55

bring on interns bring on juniors at the

3:57

same time you learn how to teach you

3:59

learn how to manage you need learn how

4:00

to lead then you start growing and

4:03

getting bigger and bigger in terms of

4:04

science and getting enough feedback from

4:06

both management your peers and also the

4:10

people that are working on the that's

4:12

how i actually start off i see you know

4:14

majority of the time i will tell you

4:15

that like once i get to a certain level

4:18

a lot of times the feedback is directly

4:20

from people that i manage yeah right so

4:23

that makes sense yeah so would you say

4:25

like as usually progress is it the

4:27

coding skill or the hard skill itself is

4:30

not so important anymore focus should be

4:32

more on you know people skill and how

4:34

you manage projects and how you build

4:37

the team if you're talking about

4:39

proportion a lot of times that's true

4:42

but that's the answer of my previous

4:43

question goes it really depends on how

4:46

you want to grow

4:47

i'm still seeing like some really really

4:50

brilliant engineers you want me to lead

4:52

a team no i'm not going to do it i don't

4:55

want to like um i want to focus on

4:58

building and designing good systems and

5:01

like and they just end up being very

5:03

good at it they would still be able to

5:06

figure out how to define the work

5:10

but they would be paired up with project

5:12

managers that actually helped manage the

5:15

people

5:16

they would be the one that actually say

5:18

that this is the wrong map this is why

5:20

foresee and their expertise comes in

5:23

picking a very nebulous problem and

5:26

breaking it down

5:28

and that's their specialty and they're

5:30

still okay with that

5:32

right it doesn't mean that the more

5:33

experienced you are the the more you

5:36

have to have to um teach or like to to

5:40

manage and what not it would be great if

5:41

you do like it's awesome like that like

5:44

our society and our industry needs it

5:47

but if you want to you can focus on

5:50

doing something you specialize in stuff

5:53

like getting a phd like this doesn't

5:54

mean that you have to do like i'm i'm

5:57

specific you can choose whatever topic

5:58

you want i see ics so it's not really

6:01

just a singular path it's a lot of

6:03

things when you get to that level you

6:04

can specialize it depends on what you

6:06

want exactly at the end of the day is a

6:08

free market like nowadays i walk to

6:10

companies i don't try to get them to

6:13

like identify me as one thing or another

6:15

i present to them

6:17

what i know what i have what i can help

6:20

them with

6:21

and they decide if they want to buy it

6:23

or not i see right like my own products

6:26

the most important thing is like knowing

6:29

yourself on what you want to become and

6:32

trying to market that and see if there's

6:34

any like buyers

6:40

yes

6:46

sir

8:25

what do you care the most other than you

8:26

know the technical respect assuming the

8:28

person is you know technically strong

8:31

enough for the team it's a gripe that we

8:33

have like in um in software engineering

8:35

especially software engineering

8:37

interviews

8:38

a lot of companies that i go with like

8:40

um i go to even

8:42

you know some experience from that like

8:44

it's uh go in an interview and people

8:47

just keep throwing new technical

8:49

questions like um algorithmic questions

8:51

right given an array this size and this

8:54

stuff like figure it out and all that

8:55

stuff a smart person of a certain

8:58

experience would be able to find the

9:00

patterns and answer you those

9:03

but in work when you when you choose a

9:05

partner

9:06

right um for for starting a business

9:09

yeah or when you're building your team

9:11

what do you want them to be or someone i

9:13

can work with

9:14

something you can work with what does

9:16

that mean when someone i can trust

9:18

someone i can you know learn from

9:21

someone who is you know

9:22

genuine and smart understand yeah that's

9:25

something that i look forward in general

9:26

that is the most important thing right

9:28

someone that you can trust

9:30

right someone that you can learn from

9:32

right

9:33

the whole thing is that how do you

9:34

actually get that well first you need to

9:37

make sure that they're good at

9:38

communication if they suck at it it's

9:40

going to be a hell of a ride right like

9:43

if they can clearly articulate what they

9:46

are thinking and convey the idea to you

9:49

and back and forth right that's why i'm

9:51

looking for it

9:52

right like so so a lot of times like i

9:55

still use um these technical questions

9:58

and and like algorithms make questions

10:00

now things that are going to get harder

10:03

is going to be the next thing how do you

10:05

think that you can work with this person

10:08

that means that personality has to be

10:10

there yeah right i'm not just saying

10:12

that a boring personality or not like

10:14

i'm talking about like hey if we're

10:16

going to have a an argument are you

10:19

going to stand on your ground

10:21

when you're right and also being able to

10:23

listen when there is a discussion going

10:26

on or are you going to say that no i'm

10:28

right uh i don't care about any of you

10:30

guys like yada yada or are you going to

10:33

be backing down everything is kind of

10:35

like yes i'm junior i will listen to

10:37

everything you say happening right like

10:39

are you able to get a good conversation

10:42

a good sparring session happening right

10:45

so now for me interview is relatively

10:48

dynamic i'm trying to see if i can

10:50

actually poke them a little bit

10:53

and see how they respond

10:55

right see if they are going to be

10:56

dismissive seeing if they are actually

10:59

like listening

11:00

and actually understanding the

11:02

information and then regurgitating or

11:05

like disagreeing with the ideas

11:07

seeing how

11:08

much they are going to be willing to

11:10

actually do the feedback

11:12

so that's part of that yeah first thing

11:14

is about reliability um and that is

11:17

going to be extremely hard yeah how do

11:19

you know someone is going to be reliable

11:22

yeah when you're interviewing without

11:23

yeah you only spend like 30 minutes with

11:25

the person it's really hard exactly yeah

11:27

right yeah but generally there are

11:29

things that you have to you can rely on

11:32

some of the things actually is your

11:34

intuition

11:36

one of the strongest things that um

11:38

we

11:39

have to rely on is understanding our

11:41

intuition a lot of times what i have

11:43

seen is that people who are who have

11:46

great attention to detail

11:48

also hold great responsibility as

11:50

themselves i see is this a type of

11:52

person that you feel like that they see

11:55

a problem and they will own the problem

11:57

holy exactly

12:00

seeing that and like trying to do that a

12:02

lot has to come with pps experience as

12:05

well so when we talk about like hey tell

12:08

me about your like um your history about

12:10

like your previous work and whatnot get

12:12

into what situation talk about what

12:15

happened how did they handle it why did

12:17

they step up why did they not step up

12:19

what is the reaction what is their

12:21

feeling about a situation or the

12:24

situation that they're talking about and

12:26

from that you just clean more and more

12:28

of their personality

12:30

i believe that technology technical

12:33

capabilities i can train

12:35

right give me a smart person and i can

12:38

train them within x amount of months

12:41

and they will become capable

12:44

give me a lazy person and i will spend

12:46

more time working on the person then

12:48

i'll be doing work

12:50

a non-motivated person or

12:53

someone who actually let's just say not

12:55

a good personality match with me

12:58

it's not going to work out

13:00

because it's so much harder to actually

13:02

adjust personality yeah then it is two

13:06

are just technical capabilities

13:09

i see

13:10

right

13:11

you know a lot of my audience right in

13:14

asia right asian traditions like you're

13:16

growing up parents teachers to be humble

13:18

right

13:19

and it's very different over here let's

13:21

say you come here and then you start a

13:23

new career in

13:24

the u.s north america or silicon valley

13:26

right how do you kind of like balance

13:28

out and what advice would you give

13:30

people growing up in asia there is a

13:33

difference between knowing what you know

13:36

and being good at what you do and

13:38

bragging about it there is a fine line

13:40

about it yeah usually i cross that line

13:42

my apologies on that um the humility in

13:46

it

13:47

happens the easiest when you are genuine

13:50

if you are able to be more transparent

13:54

then people will understand you

13:56

let people understand you and when you

13:59

do that you get a lot more leeway i try

14:02

to communicate my intentions

14:04

and if they align or if they understand

14:07

it then people usually appreciate it

14:10

and that like alleviates a lot of

14:13

problems about like humility or or like

14:16

i'm i'm trying to be too like saying too

14:18

many stories well i still do that

14:21

that's a problem with canada no no no

14:24

i guess folks

14:25

but like

14:26

yeah i don't know if i answer your

14:28

questions it does yeah okay

14:30

when senai we met back in the days um he

14:32

was the mentor to help build the team i

14:34

was at and i was very fortunate um you

14:36

know to have said and found it very

14:39

helpful to have a mentor at earlier

14:40

stage of my career how would you help a

14:42

team to be more productive and you know

14:45

just generally make people happy and

14:46

motivated i don't know like in my

14:49

opinion i corrupted him

14:53

yes

14:56

the most important factor in a workplace

15:00

that makes people happy is empowerment

15:02

people being listened to and people

15:04

feeling that they are being trusted to

15:06

work on something that sense of

15:08

empowerment actually gives a lot of

15:11

satisfaction to people ownership is in

15:14

there but a lot of companies a lot of

15:17

teams they do this they say that here

15:19

you own this

15:21

right yeah but you should do it this way

15:23

this way this way oh don't do it like

15:25

this do it like this this this right

15:27

just telling people like exactly you own

15:30

this but no you don't really own this

15:32

right ownership

15:34

without um empowerment

15:37

it's just responsibility ownership is

15:39

actually both responsibility and

15:41

empowerment

15:42

right usually i tell my boss that if i

15:45

own a team i have the power to choose

15:47

who is in my team i have the power to

15:49

discipline

15:51

people in my team

15:52

i have the power to actually enable

15:55

people in my team and if i cannot do

15:57

that

15:58

then it's just responsibility blaming i

16:00

don't want to be a scapegoat i don't

16:02

want to set myself up and buy extension

16:05

setting the team that i built to be in

16:08

failure

16:09

so they have to understand what that

16:12

ownership empowerment responsibility

16:15

model is

16:16

generally is that and second part of it

16:19

is about having an open conversation

16:22

being able to be free with your thoughts

16:24

to feel comfortable

16:26

that you can actually say whatever you

16:29

want to say

16:31

if you disagree with something you are

16:33

going to be able to say it out if you

16:35

want something to be changed you can

16:37

raise it up

16:38

you eliminate the fear of like offending

16:42

someone and good ideas come out and

16:45

collaboration comes out

16:47

and

16:48

camaraderie comes out

16:50

those are the two things that i believe

16:52

are important i don't think that we can

16:54

actually utilize one methodology and

16:58

push it to everyone

17:01

i think that is the wrong thing like

17:03

standardization like doesn't what

17:04

doesn't work

17:06

if you're paying dollars for a good team

17:10

then you need to utilize those things by

17:13

recognizing how the niches

17:17

and different quirks each person has and

17:20

how to actually gear them and help them

17:22

to be successful while challenging them

17:24

to be growing i believe that when people

17:27

are happy at their work and they feel

17:29

like that they are growing they don't

17:31

feel like that they want to leave unless

17:34

you're grossly underpaying them right

17:36

but if they feel like that they are

17:38

happy they enjoy the people that they

17:40

are working with they are being

17:42

challenged at all times that they are

17:44

growing at all times they know that this

17:46

is the place for them oh cool um thank

17:48

you steve for joining us today and

17:51

i'm sure um this will give people pretty

17:53

good guidance and you know something to

17:54

think about right yeah yeah and i guess

17:56

i learned a lot today um if you find

17:58

this video helpful please give it a like

18:00

and subscribe and

18:02

uh if you have other questions that you

18:04

want to ask um just you know leave a

18:06

comment down below

18:08

and yeah um

18:09

i'll see you next time then

18:11

bye

More transcripts

Explore other videos transcribed with YouTLDR.

Get the TLDR of any YouTube video

Transcribe, summarize, and repurpose videos in 125+ languages — free, no signup required.

Try YouTLDR Free