Episode Transcript
Transcripts are displayed as originally observed. Some content, including advertisements may have changed.
Use Ctrl + F to search
0:01
Bring me honey If
0:04
you don' see the twins . Have
0:08
fun , I
0:13
have another加-on . Make
0:17
friends , bringunna
0:22
. Why is your dressии' ? It
0:24
doesn' take too much work To
0:28
find this . Hello
0:32
Texas listeners , and welcome
0:34
to another Feisty Friday where
0:37
I go through kind of more job-related
0:40
social media and
0:42
discuss some of the advice that
0:44
I find . Today we're going to be going
0:46
through some LinkedIn posts . I'm not
0:48
going to include who they're from . I
0:50
ultimately don't want to like start
0:52
any fights or anything like that . I'm
0:55
just here to give advice from my perspective
0:57
as a software engineer who did successfully
0:59
break into industry . So first post
1:01
I want to talk about is somebody
1:04
saying engineers who are currently looking
1:06
for work or interviewing start
1:08
studying for the coding interviews now with late
1:10
code . So yes and
1:12
no . If you're applying places and
1:15
you're not having much luck , late
1:17
code isn't going to help you get
1:19
a job . So I
1:21
would say make sure that
1:23
you're prioritizing your
1:25
resume , being on point first , but
1:28
from there , starting with
1:30
a problem here or there and spreading
1:32
out . Learning and reviewing
1:35
how to do interviews is
1:37
way better than cramming
1:39
. It is a learned skill
1:41
. It is a different skill than generally writing
1:44
normal code . Interviewing
1:46
in tech is very weird
1:48
and very different , and so it is helpful
1:50
to prepare a bit . But a
1:53
lot of people who have met and interacted
1:55
with kind of wind up getting a little
1:57
carried away with preparing
2:00
for late code , before they're even
2:02
actually have a resume
2:04
who's going to get them to an interview ? And late
2:06
code isn't going to get you to the interview , so
2:09
you want to make sure that you're
2:11
getting the interview as well
2:13
, so just make sure that you're paying attention
2:15
to that . But preparing early isn't
2:17
a bad thing . So this next
2:20
one I'm going to mention because it makes me happy , it's
2:23
basically somebody saying that
2:25
they basically
2:27
take medication for depression
2:30
and ADHD and that like
2:33
that's really important and
2:35
that so many people
2:37
are really judgmental
2:40
and stigmatizing about that within
2:42
, like the workspaces . And
2:44
I definitely can feel that I personally
2:47
have anxiety and depression
2:49
and so I'm on anti anxiety meds
2:51
, I'm on anti depressants and
2:54
the thing is like , especially as a woman in
2:57
tech , that a lot of
2:59
the guys historically have said that
3:01
women have disproportionate amounts
3:03
of anxiety within tech because we're just
3:06
not cut out for this industry , whereas that's
3:09
not the cause of
3:11
anxiety for most of us . It's
3:14
often people like that or
3:16
just the fact that we're expected
3:19
to have so much in line . There's
3:21
so much that we're just
3:23
expected to like shoulder and
3:26
I didn't come from the best background
3:28
on the face of the earth and you
3:30
know what ? I'm also in weekly therapy and
3:33
if somebody tries to
3:35
belittle me for
3:37
that , at the end of the day , like I'm doing great
3:39
in life . I've
3:42
had a lot of struggles and I'm
3:44
doing great , but I do
3:46
think that it's an important conversation because
3:48
, especially people who are coming from
3:50
backgrounds of struggling with their
3:52
mental health or struggling with their
3:54
health or having disabilities and
3:56
bringing into tech like this stigma
3:59
is so profound , because the hustle
4:01
culture is generally so profound and
4:03
the thing is like I also have a no matrices
4:06
I . There's days where
4:08
man I'm in tears due to pain
4:10
and Honestly
4:14
, I'm not going to say it makes me a better
4:16
engineer , but
4:19
at the same time , it doesn't make me a worse one
4:21
. It makes me really able
4:23
to appreciate just
4:26
how hard it is to actually
4:29
be successful at what I'm doing . I
4:31
love when people are being really honest
4:34
about coming
4:36
from a different background and
4:38
having pieces of themselves
4:41
that maybe aren't as represented , because
4:43
it's so important . Okay , so
4:45
this next one that I'm going to talk about is from
4:47
a recruiter at Google and
4:49
he says Networking is a huge part of
4:51
the job search process , but the approach
4:53
to it is completely counterintuitive to what
4:55
most of us think . Here's what a mentor
4:58
shared with me recently Networking
5:00
is about being interested more
5:02
than interesting . Networking
5:04
is a long-term relationship , not a short-term
5:06
transaction . Networking is about
5:09
how much we can give versus how much we can
5:11
get . Networking is general interest
5:13
and not superficial acknowledgement . And
5:15
hey , it's a great weekend to start . Honestly
5:18
, I cannot agree more . Especially
5:22
when going to Grace Hopper and preparing for Grace
5:25
Hopper , I had started
5:27
doing advice posts for the first time
5:29
and that was kind of the first time that I really
5:31
started to see
5:34
that there's a lot of people
5:36
who think that networking is just
5:38
focused on completely about themselves
5:40
. And I like to think of
5:42
networking as kind of building work
5:45
friends , even if you don't work for the same
5:47
companies , and
5:50
maybe someday down the road
5:52
you guys will help each other great jobs . But that shouldn't
5:55
be the focus . The focus should be what can you
5:57
learn from each other , how can you grow
5:59
from each other , especially
6:02
a friendship , and so often
6:04
networking does wind up just
6:06
being a me , me , me , me . So
6:09
I'm really glad to see , especially
6:12
somebody with a title like Recruiter
6:14
at Google , where a lot of people will listen to them
6:17
saying that that's really not
6:21
the best way to go about it
6:23
. Let's
6:26
see , we have people
6:28
kind of the
6:30
general expectation
6:32
of people looking for jobs
6:34
. The job market isn't super
6:36
easy right now , but
6:39
there's also people who are actively
6:41
saying that they have jobs at their companies
6:44
. Oh no , an
6:46
Instagram , a LinkedIn influencer
6:49
my least favorite thing so many
6:51
of them say so little with
6:53
so many words . Okay , so
6:58
this person posted a video of a
7:00
two-year-old doing math . Theoretically
7:02
two-year-old I'm doubting . That child is
7:04
two . My first job was out of daycare
7:07
, so I'm decently good at
7:09
being aware of ages . Some
7:12
two-year-olds can stretch well beyond expectations
7:14
. This two-year-old is an example with his
7:17
amazing math skills . Two-year-olds
7:19
are just beginning to learn math concepts , but
7:21
they can learn a lot in a short period of time . There's
7:24
some math skills that two-year-olds can learn . Counting
7:26
Two-year-olds can learn to count
7:28
up to 10 and some may be able to be
7:32
able to count higher . One-to-one
7:34
correspondence this is an understanding that
7:36
each number corresponds to one
7:38
object . Two-year-olds can learn to match
7:40
objects to numbers and that they can learn
7:43
to count objects accurately . Sorting
7:45
and classifying Two-year-olds can learn
7:47
to sort and classify objects by size
7:49
, color , shape and other properties . So
7:52
, basically , this person is
7:55
showing a video of a two-year-old doing
7:57
multiplication , theoretically , but
7:59
then their post has nothing
8:02
to do with it . Very classic
8:04
LinkedIn , quite frankly . To
8:06
be like , oh , look at this
8:08
two-year-old doing what's beyond expectations
8:11
and then not actually talking about it . Oh
8:14
, I have an ad for
8:16
Harvard CS50
8:19
. Love it . If
8:22
you need reinforcing , I
8:24
highly recommend getting on edX
8:26
and finding Harvard CS50
8:28
. It is just one of the best classes
8:30
. Oh , somebody's talking about what
8:32
to wear in an interview . So
8:35
here's the thing it depends on
8:37
what job you're looking for and
8:40
also the company . A lot of people
8:42
are saying , oh , dress
8:44
for the job that you want , and okay
8:46
, that's a nice theory . It's not
8:48
that simple , but that's a nice theory . If
8:51
I continue that theory , though , then
8:53
I go . Well , my dream job
8:55
is to be CEO of Google or Apple
8:57
, and just in their purchase , I wear jeans
8:59
and a t-shirt . Cool , so I can wear
9:01
jeans and a t-shirt and I'm dressing for the job I want
9:03
. And the thing is that
9:05
, in tech , dressing for interviews
9:08
is generally pretty informal . So
9:13
it isn't this dress in a suit
9:15
and tie I have found
9:17
, having interviewed for tech roles out of few
9:19
finance places , that they're generally a little
9:21
more formal , but for
9:23
the most part , most of tech jeans
9:25
and a t-shirt is perfectly acceptable for
9:27
an interview . When they say dress what you're comfortable
9:30
in , actually dress what you're in and
9:32
like Amazon , when I interviewed with
9:34
them a few years ago , they told me in one of their emails
9:37
that basically my interviewer might be in a
9:39
hoodie and jeans and so , like , if
9:41
I'm comfortable in a hoodie and jeans , wear a hoodie and jeans
9:43
, and I love that . They were really , really clear
9:45
on that . They really meant it . When they said
9:47
dress in whatever was comfortable for me . But
9:50
if you're getting ready for a tech interview , also
9:53
, if you're unsure , just ask your recruiter
9:55
. They're supposed to be there to help you . A lot of recruiters
9:58
, from what I've heard , do
10:00
get paid bonuses for the number
10:02
of their recruits who get hired , and
10:04
so , while they can't necessarily
10:07
influence the hired decision , they're
10:09
not going to give you bad advice , because it doesn't
10:11
benefit them either . And
10:13
even if they don't even if they don't get a bonus
10:16
for you getting hired , they still . There's
10:18
no , there's no reason that they would , that
10:20
they would lie . There's really no purpose to
10:22
that . So I definitely say
10:24
casual is better and then
10:27
, when in doubt , ask your recruiter . In
10:29
general , west Coast is
10:31
more casual than East Coast
10:34
. So if a company is based on the West Coast
10:36
, you can guess that their definition
10:38
of like business casual is going to
10:40
be a little different . People
10:47
don't leave bad jobs . They leave because
10:49
of bad bosses , poor management , who
10:51
don't appreciate their volume . I've
10:54
seen this a lot of places . I
10:56
do think it's generally true , but
10:58
the question is what do they then define
11:00
as a bad job ? Because
11:03
I would say a bad job , a bad
11:05
boss does make your job a bad job . Poor
11:08
management does make your job a bad job . But
11:11
I think it's like witty and fun , but
11:14
simultaneously like what are
11:16
you actually saying here , which
11:18
is honestly , unfortunately , one of my
11:20
, which
11:26
is one of my big kind of things
11:28
with a lot of people I'm linked in
11:30
is that they'll give you advice , that
11:33
what are you supposed to do
11:35
with it ? So
11:38
that is
11:41
one thing is just like
11:43
ask yourself
11:45
like how do you apply advice when
11:47
you see advice online , especially
11:50
from people who say that they're experts ? So
11:54
here's another post . I've
11:56
noticed over the last few weeks that people
11:58
I admire have two things in common . They
12:01
often one say I don't know
12:03
to listen . There's
12:05
so much to learn in our jobs and really the
12:07
world for that matter , and it takes and
12:09
it makes it hard to have an informed opinion about
12:11
absolutely everything . Being
12:13
honest and humble enough to say I
12:16
don't know , but I'd love to learn more is a phrase that
12:18
opens up the conversation for everyone . It's
12:20
amazing what happens when we learn from folks around
12:23
us with more experience , more
12:25
insight and more knowledge , and
12:27
the interesting thing is that this
12:30
can actually be a strength , not a weakness
12:32
. All of a sudden , we get to learn something new
12:34
and connect with someone because we listen to them . It's
12:36
a win-win . I'm learning to use these phrases
12:38
more and more every day . I
12:41
definitely
12:43
agree . The
12:46
wisest people I know listen all
12:48
the time and are
12:50
willing to say I don't know , and
12:53
I think that it's really important to be
12:55
humble enough to say I don't know
12:57
and to be willing to learn . Simply
13:01
saying you don't know isn't good enough
13:03
in and of itself . You do need to back
13:06
it up with being willing to learn , but
13:08
it's so powerful
13:10
to not need to be the
13:12
expert all the time , and
13:15
also a lot of the time , the people
13:17
who are the quietest when they say
13:19
things . Their words are so
13:21
meaningful . I
13:24
admire them a lot . I
13:28
definitely . Just it's
13:34
such a good skill to practice saying
13:36
less and listening more . In
13:39
general . This
13:44
one's interesting how
13:47
we got my first job in machine learning
13:49
Me . Can I switch from software
13:52
engineering to ML ? My VP no , me
13:55
, why not ? Vp not
13:57
enough ? Experience Me . I have two
13:59
years . We experienced in six months of ML
14:01
courses so I can help the ML team deploy
14:03
their models . Vp
14:05
not enough . After four months
14:08
of being told no , me . So can I
14:10
switch VP sighing
14:12
maybe a three months apprenticeship Me
14:15
deal , and the rest was history . Looking
14:17
back , I was ultimately successful because
14:19
I leveraged my uniqueness . I got the job by
14:21
bringing something new to the ML team and
14:24
solving a problem they had model deployment . I
14:26
was specific , I knew what they wanted and
14:28
why I wanted it , and I made it abundantly
14:31
clear . I never let my
14:33
intensity waiver , even when I was
14:35
feeling rejected and hopeless . I never let it show
14:37
. I made it clear that I was never going to stop trying
14:39
. So I
14:43
in general think
14:46
that this is pretty helpful . I
14:48
would say that I
14:51
think that to a certain degree , like if
14:53
you're interested in something kind
14:55
of more niche like
14:57
machine learning . It's helpful to also figure
15:00
out how your company feels about
15:02
people moving into those shops , because
15:05
every company has their own culture and
15:07
there's pros and cons
15:09
to that , and
15:13
so at this person it
15:15
sounds like they were at a company
15:18
that was pretty strong
15:21
in people staying in their lanes kind
15:23
of mentality , whereas I
15:26
work at Boeing and Boeing
15:29
does not feel that way . Boeing
15:31
is very much a come and learn kind
15:33
of mentality , and
15:39
so my manager one
15:41
day came in to a conference room
15:43
and said who wants to learn
15:45
some machine learning work ? We have a
15:47
machine learning team who needs some help and
15:50
three of us with minimal background . I
15:53
have the most background of the three of us , which isn't
15:55
much . Three
15:58
of us with minimal background said , sure , I'm willing
16:00
to learn , and so we got transferred
16:02
largely to working on machine
16:04
learning , and so
16:06
one thing that I would say is helpful
16:09
as well is if you're really passionate about
16:11
something , I
16:13
don't necessarily think that
16:15
if your company continues
16:17
to tell you no for months on end , I
16:20
consider looking elsewhere
16:22
and seeing if somebody else
16:25
will give you that opportunity , because
16:27
you have to watch out for your own career . I
16:30
definitely think that that
16:33
is true in this post that
16:35
this person did look out for their own career but
16:38
like , at what point would enough have
16:40
been enough ? Were they comfortable
16:42
staying a sweeper effort if they continue to get told no
16:44
, because the
16:46
reality is that was a non-zero
16:48
possibility . Four
16:50
months of being told no is a decently
16:53
long period of time for somebody to stick with
16:55
that , and so
16:57
my one piece of advice would
16:59
just be make sure that you're watching out for yourself
17:02
on that front . But
17:04
being persistent is super helpful . I
17:08
definitely think that leveraging
17:10
your uniqueness is super important to breaking
17:12
into especially niche roles . I
17:15
personally , in general
17:17
at this point there's a lot of
17:20
new grads in computer science
17:22
or software engineering , and so
17:25
being unique somehow is super , super
17:27
helpful . So I
17:29
, for instance , will
17:31
kind of focus in on the fact of
17:33
I am
17:36
really good at cybersecurity
17:38
and software and decently good at
17:40
machine learning at this point , and
17:42
what I won't tell companies is I
17:44
know that I'm not the best software
17:46
engineer they're going to hire . I'm also not the best
17:48
at security , and I'm surely
17:51
not the best at machine learning , but
17:53
if you need somebody with overlap
17:55
, I'm
17:58
probably one of the best people
18:00
for my price tag in
18:03
all three . And so
18:05
knowing that , knowing
18:07
what makes you unique and looking for how
18:09
you can leverage that for the company is really , really
18:11
helpful . And
18:14
, yeah , never letting your intensity waiver
18:17
. Like I said , I don't
18:19
know if I would have like stuck around
18:21
to be told you know no
18:23
, for four months , but I do think that
18:25
you do have
18:27
to have real commitment to it , like
18:30
if you say that you want something
18:32
, you're the one who has to
18:34
be the one who makes your career what it is . You
18:37
have to decide that path and then
18:39
you have to make sure that you're getting what you need
18:41
. But in general , I
18:43
do really like that . Goodness
18:48
, so many , so
18:52
many company advertisements . Yeah
18:59
, this is a . This is a good one . Basically
19:02
, this person posted about
19:05
how a job was listed as being
19:07
remote , but they
19:10
must reside
19:13
in the area of the office
19:15
and they will be required to come into office
19:17
on an as needed basis , and
19:20
basically that people
19:23
who
19:26
are searching for remote jobs . This is listed
19:28
as a remote job when in reality
19:30
, the text of the job does not qualify
19:32
as a remote job . It doesn't matter
19:34
if you can be at home most
19:36
of the time , if you need to live
19:40
close enough to come on an as needed
19:42
basis . I would qualify that as a hybrid
19:44
job and I completely agree with that
19:46
, and I also think that , like you
19:49
know , to
19:52
say that I must reside in the
19:54
area of the city that
19:56
the shop is in , like that's , how
20:02
close to that city do you want me to reside
20:04
in ? So
20:07
you know those . Those are those
20:10
are the things that I definitely can
20:12
agree with us
20:15
not the right move
20:17
. If you're a recruiter , it's better to
20:19
be upfront with people than
20:22
to kind of
20:24
make
20:27
it seem like a
20:29
job is different than what it is
20:31
. Just be honest . I'm
20:36
just gonna include a shout out Lee
20:40
McKermon McKieman . God
20:42
, I am so sorry . I'm super
20:44
dyslexic . I cannot read to save my life
20:47
Most of the time . He is one of my favorite
20:49
people on LinkedIn . He
20:51
has no idea who who I
20:53
am , but I follow him . He's
20:56
a staff software engineer at Google and he's
20:58
one of the people who just like talks
21:01
about what it's like to have
21:04
some of the experiences that he's had and I and I love it . I
21:08
he's just scrolling
21:10
through seeing some of his posts . I just I love it , um
21:12
, I love it , um
21:14
. So
21:17
, going back to what I was doing
21:19
? Um , this person posted
21:22
99% of LinkedIn profiles
21:24
. I see , don't clearly show me who you are
21:26
, where you came from , how you got there . Too much
21:28
showing off , not enough human . So
21:31
here's the thing on LinkedIn Companies
21:35
are on there . Um , I
21:37
am not going to be 100% human
21:39
when a company potentially is going
21:41
to see it when it's right One
21:44
of the things that I'm literally including in my job applications , quite
21:46
frankly , um
21:48
, that's asking for a level of vulnerability
21:51
that just , unfortunately , isn't likely going to occur , because it's
21:53
really high risk . If
21:57
it's not high risk , it at least feels high
21:59
risk , because most of us don't have insight
22:01
into what recruiting actually looks like . So
22:04
I don't know how deep
22:06
into my LinkedIn posts in comments Somebody's going if
22:08
I include my LinkedIn on my application . Um , so I
22:10
I definitely think that some people aren't being
22:13
human at all and I think
22:17
that that's important , but I just think that's important
22:19
, but
22:23
I definitely don't think that we're
22:26
all going to show who we are completely as a as a person . Um
22:32
, oof
22:36
, another one of these . Um
22:38
, beware of suspicious job offers
22:40
on LinkedIn . Um
22:43
, I recently received a message
22:45
that left me both concerned and skeptical , and
22:47
I felt the need to share it with all of you . I received
22:49
an unsolicited job offer that seemed too
22:51
good to be true . The message was well-crafted
22:53
and appeared to be from an individual claiming
22:56
to be a professional in the field of instructor design
22:58
in art collections and a fundraising
23:00
influence for reputable charity
23:02
organizations . The offer included
23:05
descriptions of a personal assistant role , flexible
23:07
hours and a seemingly generous salary . It
23:09
also mentioned receiving payments through certified bank
23:11
checks , which raised the red flag
23:14
. Let me break it down . One , the job
23:16
offer came without came out
23:18
of the blue , without any prior contact
23:20
. Two , the promise of high pay for minimal
23:22
work seemed unrealistic . Three
23:24
, the method of payment through certified bank
23:27
checks is unusual . Four , there
23:29
were noticeable grammatical errors in the message
23:31
, which is often the sign of a scam . Five
23:33
, be aware of reshipping scams . If a job
23:35
involves receiving and forwarding packages , maybe
23:38
part of a reshipping scam and you
23:40
could unknowingly become involved in illegal
23:42
activities . This kind of message
23:44
set off alarm bells and we need to be more cautious
23:47
about such offers . They could be
23:49
potential scams or phishing attempts to steal personal information
23:51
or money . Have you ever received similar
23:54
messages ? If so , please share your experience
23:56
. It's essential to maintain a vigilant and ethical
23:58
presence on LinkedIn , where many professionals
24:01
connect and build their careers , just look
24:03
out for one another and question the
24:05
ethics behind such offers . Remember
24:07
, if something seems too good to be true , it probably
24:10
is . Always verify the legitimacy
24:12
of every job offer , especially when
24:14
it arrives unexpectedly . So
24:16
, unfortunately , one
24:19
of the things that I have seen an increased
24:21
in courtesy of
24:23
the job market kind of being bad is
24:26
people creating
24:28
fake job scams . So
24:32
this one's a little bit more
24:34
obvious than a lot of the ones
24:36
that I've read about . But I've
24:39
read people , seemingly
24:42
from legit companies that
24:44
do exist in the tech space
24:46
, reach out to them , do phone
24:49
interviews , do
24:51
make it seem similar , legit
24:53
, and then basically
24:56
they realized that it was a scam when they had a
24:58
company ask them to pay for shipping for
25:00
their work laptop and
25:02
no reputable company would ever do
25:04
that . But
25:07
it's definitely important to be super , super
25:09
cautious about any
25:12
job communications that you're having , especially
25:15
on LinkedIn these days , because a lot
25:17
of people are scamming on LinkedIn
25:19
because unfortunately , when people are desperate
25:22
, they're paying less attention to , kind of
25:24
some of those red flags . So you
25:26
want to be super cautious of
25:28
anything that kind of feels off
25:30
. When in doubt , try and
25:32
reach out to a recruiter from that company that
25:34
you know is actually at that company . One
25:37
of the things on LinkedIn that you can do now
25:39
is you can actually verify
25:41
your workplace , and
25:43
I imagine that a lot of recruiters have verified
25:45
their workplaces and so you can find
25:48
a recruiter and most
25:50
would be happy to help look
25:52
up if you're actually in the interviewing pipeline
25:55
and have the ability to see that . But
25:58
definitely like if
26:01
something's too good to be true , it unfortunately
26:03
is usually not real . Let's
26:06
see . Oh
26:10
, I like this one . I've been a
26:12
data scientist for almost seven years but
26:14
I still Google pandas and NumPy functions
26:16
several times a day . Why remembering
26:18
intricate functions is helpful , but
26:20
if they were applied 0.1% of your
26:23
workflow , they're not worth retaining . Time
26:25
is better spent in understanding practical techniques
26:27
like data cleaning , feature selection
26:29
, feature engineering , modeling and evaluation
26:31
. So the takeaway don't overly
26:33
optimize your skills . Think about the big picture
26:36
of what you are aiming to achieve with
26:38
data science and invest in growing the skills
26:40
that are worth it . So very
26:43
much so . One of the things that
26:45
people don't get and
26:47
feel really insecure about is that they don't feel
26:49
like they can solve 100% of problems without
26:52
Googling them , and the thing is
26:54
that , as a software engineer , we do that
26:56
all the time and
27:00
the key is just to make sure that you know
27:02
how to break down the problems , that you
27:04
know the skills that you can't just type
27:07
into a Google search and get an answer
27:09
for , but
27:11
the actual functions
27:13
, the actual . That's
27:16
not that helpful
27:18
to have 100% . So definitely
27:21
don't stress out about
27:23
not remembering 110%
27:25
of syntax , because most of us
27:27
do not . So
27:32
I have one post that I
27:34
think captures , unfortunately , what a lot
27:36
of people feel right now within the
27:38
tech industry , and
27:40
this person writes I have never seen a job
27:43
market this difficult . I have done more interviews
27:45
than I can even count over the last several months
27:47
. I've seen posts here from
27:49
people who have been out of work for almost a
27:51
year now that were in my field . So
27:54
I know some very smart individuals
27:56
who are out of work right now and it is confusing
27:58
why they have not been picked up yet . I hope things
28:00
turn around for all of us . I don't like seeing
28:03
this many people out of work . So , first of all
28:05
, none of us like seeing this
28:07
many people out of work . It's really hard to be
28:09
on LinkedIn and see so many people who
28:11
have been laid off , who don't have
28:13
a job , things like that . That's really hard
28:15
emotionally to see and
28:18
that is nothing in comparison to all
28:20
the people actually experiencing that , and
28:22
my heart's go out to them . One thing
28:24
that I do think is really important is
28:27
to make sure that it's
28:29
easy to kind of get
28:31
caught up in just applying , applying
28:34
, applying , applying , applying because you
28:36
feel like you're doing something , you feel like you're potentially
28:39
going to make progress . But
28:41
if you're not making progress , change
28:43
tactics because clearly
28:45
, applying , applying , applying , applying isn't
28:47
working .
Podchaser is the ultimate destination for podcast data, search, and discovery. Learn More