►
From YouTube: Interview with GitLab Senior Engineering Manager
Description
Interview with GitLab Senior Engineering Manager
A
B
A
A
little
bit
here
because
there's
a
little
bit
to
unpack
here,
so
you
said
you
got
the
computer
when
you
were
like
junior
high
school
and
you
thought
you
wanted
to
go
into
the
hardware
side
of
things
initially.
First
and
what
were
you
thinking?
It
was
the
actual
build
themselves
you
want
to
do
like
the
mechanical.
A
A
B
Is
what
I
got
to
do
and
I
loved
it,
and
it
is
like
literally
my
first
love,
but
the
industry
was
starting
to
ship
those
types
of
jobs
overseas
and
there
also
there
weren't
a
lot
of
jobs
where
you
could
become
a
computer
engineer.
Most
of
the
jobs
are
going
towards
software
they're
just
way
more
job
opportunities
in
that
environment.
So
I
changed
due
to
a
lack
of
opportunities
and
I
wanted
to
be
able
to
live
anywhere
and
the
hardware
jobs
were
always
in
these
remote
places.
I
was
in
rochester
minnesota,
so
very
remote.
A
B
Okay,
so
let's
talk
about,
I
went
away
to
college,
so
I
went
to
spelman
college.
I
grew
up
in
the
bay
area.
We
didn't
know
a
lot
about
hbcus
back
in
the
day.
I
saw
this
movie
boys
in
the
hood
best
movie
ever
that's
when
I
heard
spelman.
That's
literally
how
I
heard
about
spelman,
and
I
did
some
research
on
it
and
I
was
like
I
want
to
be
there.
That's
that's
where
I
need
to
be
so.
B
I
went
to
spelman
and
I
knew
I
wanted
to
go
into
computer
engineering
and
I
majored
in
general
engineering,
expellement
and
computer
engineering
at
georgia,
tech
as
part
of
the
dual
degree
program:
okay,
while
at
spelman,
well
everyone
who's.
Listening
to
this
video
knows
that
the
experience
is
there.
I
had
a
great
experience
at
spelman
when
I
went
to
georgia
tech.
It
was
very
different.
It
was
like
work.
B
I
still
would
say
that
it
was
probably
some
of
the
hardest
work
I've
done
up
to
date,
and
but
I
learned
like
I
got
a
really
good
idea
of
what
I
wanted
to
do.
I
still
wanted
to
stick
to
computer
engineering
and
they
had
lots
of
companies
coming
on
campus.
It
would,
I
think,
dot
net
the
internet
was
all
taken
off
around
then
and
they
were
the
companies
would
come
to
campus
and
they
would
just
interview
us
by
like
the
dozens,
and
it
was
just
literally.
A
B
It
was
my
husband,
so
I
met
my
husband.
He
went
to
morehouse
while
I
was
at
spelman.
We
met
in
literally
the
first
week
on
campus
and
we
he
went
to
law
school
and
I
went
to
minnesota
and
after
I've
been
there
for
a
few
years
he
proposed
and
he
got
a
job
on
the
hill
in
dc,
and
so
I
moved
to
dc
so
that
we
could
start
our
life
and
our
family
in
dc.
B
And
when
I
got
ready
to
move
to
dc,
I
was
supposed
to
transfer
from
ibm
and
they
had
a
freeze,
a
hiring
freeze
when
I
got
to
ibm
in
maryland
and
bethesda
maryland.
So
I
was
basically
out
of
a
job
and
that's
when
I
started
looking
for
software
development
opportunities.
But
even
when
I
was
transferring
from
ibm
rochester
to
ibm
maryland,
I
couldn't
get
a
hardware
engineering
job
I
had
to
to
transition
to
software.
At
that
moment,.
A
B
So
software
development-
ironically
it
was
a
startup
company.
I
was
employee
number
24
and
I
worked
for
a
company
called
acumen
solutions
that
was
just
bought
out
by
salesforce
about
a
month
ago,
but
we
basically
were
contractors
or
consultants,
and
I
worked
at
companies
like
nextel
sprint,
different
telecommunications
companies
and
I
worked
in
every
phase
of
the
software
development
life
cycle.
So
the
first
job
you
usually
get
well
back
in
the
day
was
testing.
So
I
was
a
tester
and
I
wrote
scripts
using
loadrunner
windrunner.
B
I
don't
know
if
anybody
knows
about
that,
but
I
started
off
testing
and
then
I
moved
into
requirements
gathering
then
I
moved
into
design.
Then
I
moved
into
development,
and
so
I
basically
played
every
role
there
was
in
the
software
development
life
cycle
over
the
course
of
five
years
at
a
startup.
I
worked
like
70
hour.
Work
work
work
weeks,
so
it
was
a
lot
and
the
only
reason
I
left
that
job
is
because
we
decided
to
start
a
family
and
I
could
not
have
a
family
and
work
those
hours.
At
the
same
time.
A
B
So
there
were
two
jobs
in
between
the
next
job
was
for
a
government
contractor,
and
I
worked
there
for
about
three
to
four
years.
Maybe
and
then
I
decided
to
have
another
child
by
then
I
got
the
hang
of
it
every
time
you
go
to
a
new
job,
you
work
less
hours
and
you
get
more
money,
that's
how
it
was
working
right.
So
it
worked
the
first
time
I
I
had
less
hours
and
I
got
more
money.
So
I
was
like
I'm
gonna.
Do
this
one
more
time,
because
now
I
have
two
children.
B
So,
as
you
can
see,
my
trajectory
was
always
determined
and
defined
by
my
family
circumstances.
Right,
that's
that's
how
it
was
so
then
I
went
to
the
government
and
I
was
there
for
10
years
at
that
point
my
husband
relocated
to
atlanta,
and
so
when
we
did
that,
I
told
my
job.
I
was
like
look
I'm
relocating
and
they
said
you
can
keep
your
job.
So
I
was
like.
B
Oh,
I
can,
and
they
said
you
can
work
remotely,
and
so
I
did
that
for
a
time
and
then
I
got
to
a
point
where
they
were
saying:
you
can't
go
any
higher
this.
Is
it
you're
done
so
then
I
started
looking
for
a
job
and
it
was
the
first
time
that
I
was
looking
for
a
job,
because
I
wanted
to
look
for
a
job
right,
so
it
was
like
sky's
the
limit
and
someone
from
from
get
lab
reached
out
to
me
and
it
was
a
good
offer
I
had.
B
All
right,
so
I'm
a
senior
engineering
manager,
so
I
am
no
longer
coding.
I
manage
a
team
of
five
engineering
managers
and
they
all
have
different
features
in
the
gitlab
product,
so
my
teams
include
code
reviews,
source
code
and
that's
where
you're
creating
merge,
requests
and
you're
reviewing
code.
I
also
have
the
ecosystem
team
part
of
the
ecosystem
team
and
that's
working
with
integration.
So,
like
a
jira
integration,
I
have
the
editor
team
and
they're
responsible
for
the
web
ide
or
the
gitlab
pages,
and
I
think
that's
it.
Yes,
that's
it.
Okay,.
A
B
B
Mainly
because
I
like
requirements,
I,
like
converting
customer
requirements
into
actual
work
and
you
go
from
the
requirements
to
creating
ethics,
which
are
like
big
batches
of
work,
that
you
tie
you
associate
with
issues
and
you
iterate
on
that
issues
to
complete
that
epic,
which
is
what
touches
the
customer.
So
I
I
love
you
know
working
as
closely
to
the
customer
as
possible
and
that's
the
main
reason
why
I
kind
of
like
epics
the
most.
But
that's
not
my
that's,
not
my
team.
A
It's
good
to
know
right.
Okay,
so
you
have
you
have
this
very
you.
Have
this
extensive
work
issue
where
you've
done
a
lot
of
things,
you've
been
on
both
the
hardware
side
and
you've
been
on
the
software
side,
looking
back
at
when
you
had
your
choice
of
roles
right
or
when,
when
you
decided
I'm
going
to
look,
you
know
for
this
next
role
and
you
ended
up
at
get
lab.
What
do
you
think
made
you
attractive
to
gitlab?
Why
do
you
think
that
recruiter
reached
out
to
you.
B
I
would
definitely
have
to
say
the
fact
that
I've
worked
remote
for
a
long
time
and
I
know
how
to
manage.
In
a
remote
environment,
we
have
a
set
of
values
at
gitlab
that
I
had
to
figure
out
on
my
own,
because
I
was
the
only
one
who
was
remote
in
my
previous
organization
and
I
not
only
like
agree
with
them.
I
did
them
myself,
so
it
was
a
very
good
fit.
B
B
Well,
I
think
what
I've
learned
the
most
is
probably
more
change
management
there's
been
with
a
company
that
grows
as
fast
there's
a
lot
of
change
and
in
my
previous
companies
the
change
wasn't
as
quick
and
as
much
so.
I've
learned
how
to
navigate
change
management
as
a
skill
and
teach
others
and
mentor
others
as
well
as
I
I
believe,
I've
improved
my
time
management.
B
B
A
B
Don't
work
too
much,
I
I
had
three
jobs
coming
out
of
college
because
I
was
bored
and
what
ended
up
happening.
I
worked
at
ibm,
40
hours
a
week,
doing
my
engineering
job.
Then
I
got
time
and
a
half
to
work
in
the
factory
section,
cleaning
disk
and
then
in
the
evenings
from
like.
I
did
that
on
the
week
in
the
evenings,
from
five
to
nine,
I
worked
at
the
mayo
clinic
filing
paper,
so
it
wasn't
about
money.
It
was
like
I
was
just
like.
B
And
I
was
I
felt
like-
I
had
a
really
bad
work
life
balance
for
years
and
now
I'm
still
trying
to
unlearn
that
you
know-
and
I
have
children
that
need
me
and
that
want
time
with
their
mother
and
I'm
like
oh,
but
I'm
working
on
this.
You
know
and
some
of
those
bad
habits
kind
of
stick
with
you,
but
you
don't
have
to
kill
yourself
like.
So
I
would
really
just
enjoy
life
a
little
bit
more
and
not
sacrifice
the
balance
in
your
life.
A
B
I
would
say
so:
software
development
is
interesting
because
it
always
changes
it's
so
different
from
year
to
year.
When
there
is
something
new
to
learn,
learn
it
or
you
will
fall
behind.
Your
degree
is
as
good
as
the
year.
You
got
it
in
right,
so
this
is
a
forever
learning
occupation.
This
is
not
like
becoming
a
doctor
or
a
dentist
or
a
lawyer.
This
is
literally
you've
got
to
study
and
learn
every
year.
If
you
do
not,
someone
will
come
in
and
write
a
program
to
take
your
job.
B
It
happens
all
the
time,
because
technology,
the
purpose
of
technology,
is
to
to
make
things
easier
and
more
automated.
If
it's
automated,
then,
where
does
that
leave
you?
That
leaves
you
learning
the
next
thing,
so
you
need
to
always
be
like
ahead
of
the
trends
and
always
be
willing
to
do
the
work
that
no
one
else
wants
to
do
and
always
be
willing
to
learn
the
next
new
thing.
B
Definitely
take
advantage
of
this
course.
There
are
things
that
are
being
taught
in
this
course
that
you
can
definitely
apply
once
you
get
your
job
in
the
professional
world,
even
if
it's
not
a
git
lab,
but
also
remember,
you
are
basically
interacting
with
potential
future
team
members
right.
You
could
use
this
as
a
networking
opportunity
or
people
who
might
get
to
know
you
right.
You
write
a
reference
but
take
advantage
of
this
opportunity.
Please.