►
From YouTube: Interview with GitLab Support Engineer Brie Carranza
Description
Brie shares her journey beginning as an Information Technology Major from Slippery Rock University of Pennsylvania and then attending graduate school at Carnegie Mellon University studying Computer and Information Systems Security / Information Assurance. Currently she is a Support Engineer at GitLab.
A
I
am
good,
I
am
good,
thank
you
for
asking
thank
you
for
participating
in
this
quick
interview
for
the
morehouse
college
students.
What
I
wanted
to
do
is
just
have
a
very
informal
sort
of
interview
between
you
and
myself
and
we'll
just
talk
a
little
bit
about
your
history
and
background.
Does
that
work
for
you.
A
B
Sure
so
I
first
heard
about
software
development
when
I
was
a
little
kid
and
my
dad
gave
me
a
laptop
with
linux
on
it,
and
so
that
sort
of
introduced
me
to
open
source
software
which
led
me
to
how
that
software
is
created,
and
that
was
very
cool.
I,
it
was
really
just
seeding
to
user
bin
and
a
lesson
to
see
what
programs
are
there
and
figuring
out
where
it
came
from
and
how
it's
supposed
to
work
and
stuff
like
that.
A
B
Sure
so,
as
a
teenager,
what
I
thought
was
fun
was
hanging
out
on
launchpad
and
responding
responding
to
issues
were
possible,
but
the
first
thing
I
really
did
that
was
software.
Developmenty
was
doing
translations
for
issues
that
forced
me
to
learn
about
bazaar
and
version
control
and
how
someone
on
the
internet
with
an
idea
actually
makes
an
idea
like
go
through
a
system,
and
then
that
idea
is
converted
into
something
that
appears
in
the
software.
B
So
internships
are
one
of
my
favorite
things
to
talk
about.
I
started
doing
internships
when
I
was
16
as
soon
as
I
legally
could
work,
and
I
did
that
all
through
high
school
and
all
through
college,
and
it
is
one
of
the
best
decisions
I
ever
made.
It
taught
me
a
lot
about
technology
and
software
development,
but
also
about
the
workplace
and
what
it
means
to
be
an
adult.
B
It
taught
me
about
compassion
and
empathy
and
things
that
we
don't
really
always
talk
about
in
a
lecture
but
are
really
super
important
in
the
workplace.
So
the
first
internship
that
I
had
I
was
started
out
doing
network
engineering
and
worked
my
way
up
from
physically
pulling
cables
to
eventually
being
able
to
type
things
and
change
things,
so
that
was
exciting.
B
Sure
so
my
internship
was
so
cool.
I
worked
in
the
blue
room,
which
was
just
this
lab
and
I
had
replicas
of
all
of
our
production
equipment
in
the
lab
that
I
could
just
play
with.
So
what
I
was
responsible.
One
of
the
projects
I
did
was
set
up
a
freebsd
machine
with
a
bunch
of
physical
nics,
because
that
was
the
way
you
had
to
do
things
at
the
time
and
I
modified
the
pipes
and
queues
within
the
machine
to
replicate
our
global
network.
B
I
I
want
to
replicate
that
within
this
one
room,
so
that
was
the
first
big
project
that
I
did
for
my
internship
and
another
thing
I
did
was:
we
saw
a
thing
called
squid
web
proxy,
and
so
I
worked
on
a
plan
for
how
we
would
implement
that
in
production
and
test
it
and
we
implemented
it,
and
it
did
caching
for
people
which
spat
up
their
internet
connection
sufficiently
that
they
reached
out
to
it
saying:
did
we
get
a
bandwidth
upgrade?
I
was
like.
No,
the
caching
is
just
working
really
well.
B
B
B
B
B
We
would
get
a
notification
that
a
specific
mail
server
had
70
000
messages
in
the
outbound
mail
queue.
An
alert
is
raised
and
my
job
was
to
figure
out
why
there
were
so
many
messages
in
the
outbound
mail
queue,
and
that
was
really
what
sparked
my
interest
in
cyber
security,
because
a
lot
of
what
I
was
doing,
that
role
was
basically
incident
response
someone's
done
something
that
they
shouldn't
have
done.
Please
find
it
and
stop
it.
So
it
was
a
lot
of
that
kind
of
thing.
I
learned
about
web
shelves.
B
A
B
Sure
so
I
had
the
great
fortune
to
after
my
time
at
the
web
hosting
company
work
at
carnegie
mellon
university,
where
they
have
a
tuition
remission
program,
so
it
was
kind
of
a
new
brand,
I'm
a
very
school
oriented
kind
of
a
person.
So
it's
like
hey.
I
work
here
and
I
can
take
classes
here
and
not
have
to
pay.
This
is
super
exciting,
so
I'm
definitely
gonna
do
that.
B
I,
it
was
important
to
me
to
make
sure
that
I
could
excel
in
my
coursework
and
excel
in
my
professional
work
and
not
have
the
two
interacting
with
one
another
so
did
take
it
slow
at
first
to
make
sure
I
could
make
it
all
work.
It
was
really
interesting,
though
I
had
a
cyber
security
role
and
I
was
learning
cyber
security,
so
I
got
to
sort
of
apply
what
I
was
learning
in
real
life
and
have
this
feedback
loop.
That
was
awesome.
B
A
B
So
after
grad
school,
I
realized
that
I
wanted
to
be
solving
different
kinds
of
problems.
I
you
know
was
hearing
so
much
about
devops
and
using
gitlab
personally
and
just
finding
it
very,
very
fun
and
wanting
to
do
more.
I
started
reading
about
git
lab
as
a
company,
and
it
just
felt
like
a
good
fit
for
me.
So
now
that
I'm
here
at
gitlab,
I
get
to
apply
what
I
learned
in
grad
school
about
cyber
security.
So
people
will
write
in
about
hey,
there's
a
post
about
this
vulnerability
in
gitlab.
B
A
B
Sure
so
I'm
a
support
engineer
at
gitlab.
That
means
that
the
primary
thing
I
do
is
look
at
requests
from
people
who
are
using
gitlab
and
help
them
configure
gitlab
to
work
in
the
way
they
want
it
to
work
or
troubleshoot
any
problems
that
may
exist
in
their
existing
gitlab
environment
to
get
it
back
into
good
working
order.
B
Gitlab
may
not
do
today
exactly
what
the
customer
wants
it
to
do
for
their
specific
use
case,
but
I
have
the
power
to
say:
okay
with
the
way
gitlab
was
implemented
today.
No,
but
let
me
help
you
put
together
a
feature
proposal:
that's
well-formed
and
guide
the
direction
of
the
product
to
help
meet
your
needs
and
that,
I
think,
is
very
exciting
to
me.
I
I
know
what
I
loved
about
git
lab
as
a
developer
and
so
to
be
able
to
for
a
living
help.
People
find
that
enthusiasm
about
gitlab,
very
fun.
B
B
B
A
So
what
do
you
think
made
you
attractive
to
gitlab,
because
you've
been
here
recently
right
about
six
months,
so
take
us
back
right
to
prior
to
you
going
to
the
interview
process
right,
so
you
recognize
like
all
right.
Gitlab
is
this
particular
company
that
you
know
is
doing
some
really
cool
things
in
the
devops
space?
What
do
you
think
may
gitlab
say:
brie
she's
really
doing
some
cool
things
right
here.
We
want
to
make
her
a
part
of
our
team.
What
had
you
picked
up?
What
were
you
working
on?
B
So
I
think
that
one
of
the
primary
things
was
a
solid
command
of
linux
systems,
administration
and
systems.
Engineering.
That's
a
thing
like
that.
I
mentioned
I've
been
doing
for
a
couple
decades
and
I
take
for
granted,
but
it's
not
something
that
everyone
has.
So
I
think
that
that
was
a
big
thing
that
helped.
I
also
had
experience
with
different
kinds
of
file
systems,
and
that
teaches
you
just
a
different
way
of
thinking
that
turns
out
to
be
super
useful
and
we
have
people
we
have
customers
who
are
using
nfs.
B
A
B
So
a
lot
of
different
things
right
if
I
had
to
boil
it
down,
let's
see
I'm
much
stronger
at
like
reading
ruby.
Ruby
was
not
a
programming
language.
I
was
familiar
with
when
I
came
to
gitlab,
I'm
more
of
a
python
and
a
go-lane
kind
of
a
person
so
much
better
at
reading
ruby
than
I
was
when
I
started
so
that's
exciting,
definitely
stronger
with
git.
I
was
I
thought
I
was
pretty
good
with
git
when
I
started
and
much
better
now,
so
that's
exciting
kubernetes.
B
When
I
started
a
gitlab,
I
knew
that
kubernetes
was
something
that
I
needed
to
learn
more
about
and
there's
enough
requests
about
it
that
I've
learned
so
much
about
kubernetes.
In
my
time
here
I
sort
of
thinking
back
to
the
question
that
you
asked
before
I
have
experience
with
cluster
administration,
not
kubernetes,
but
clusters
in
general,
so
learning
kubernetes
I've
been
helped
by
having
the
linux
background
and
by
having
like
exposure
to
clusters.
B
So
my
time
at
gitlab
has
helped
me
with
picking
up
kubernetes
and
that's
exciting,
I'm
also
much
stronger
with
interacting
with
apis
http
verbs
jq.
I
love
jq.
It's
a
lot
of
fun
and
I
had
a
fairly
simple
jq
workflow.
When
I
started
at
gitlab,
I
have
a
whole
list
of
jq,
snippets
and
stuff
like
that.
Now
it's
very
exciting.
A
B
Right,
I
would
tell
the
20
year
old
me
to
be
patient
things
take
time.
I
would
also
tell
her
to
be
courageous.
I
think
that
you
it's
important
to
learn
the
things
that
you
can
affect
and
things
you
can
affect.
If
it's
something
you
can
do
something
about,
be
bold
and
be
courageous
when
it
gets
to
the
point
where
it's
on
someone
else
learn
patience.