►
From YouTube: AMA - Being a Senior Support Engineer APAC/EMEA 2023
Description
Ask me anything session with Senior Support Engineers.
https://gitlab.com/gitlab-com/support/support-team-meta/-/issues/4954
A
Hello,
everybody,
my
name
is
Armin
I'm,
facilitating
the
ask
me
anything
meeting
of
being
becoming
a
senior
today,
that's
the
third
session
that
will
be
recorded
this
year.
A
So,
as
you
can
see,
we've
got
loads
of
support
Engineers
on
the
call.
Maybe
we
could
do
a
very
brief
introduction
of
everybody.
If
we
go
around
the
zoom
call
list
Charles.
If
you
want
to
introduce
yourself
quickly,
please
sure.
B
My
name's
Sean
I'm,
based
in
South,
Africa
and
I,
am
a
what
do
they
call
it
standard
support,
engineer
I,
don't
think!
That's
the
robin
intermediate
intermediate
yeah,
your
support,
engineer,
yeah
so
I'm
just
here
to
to
learn
more
and
listen
to
what
people
have
and
I
ask
a
few
questions.
I
guess!
Thank
you.
Philip.
D
E
Chris,
hey
yeah,
I'm
Chris,
based
in
the
UK
I've,
been
here
actually
a
year
today,
as
a
support
engineer
so
looking
to
see
what
the
challenges
and
opportunities
becoming
a
senior
sport
engineer
presents.
A
Thanks
Chris
Ronald.
F
G
Hi
I'm
a
Matt
I've,
been
in
gitlab
for
two
years
and
five
months
and
I've
been
a
senior
for
the
past
a
yeah
eight
months.
H
Hi
I'm
Daniel
Janice,
also
senior
support
engineer
at
git,
lab
I've
been
around
for
about
two
years,
something
more
and
a
senior
engineer,
also
for
eight
months.
Thanks
for
reminding
me,
asthma
thanks.
I
E
K
J
Yourself
quickly,
please
hi
everybody
I'm
Chris.
Well,
what
information
are
you
looking
for?
I
mean.
J
A
Same
for
me,
I'm
definitely
trying
to
actually
learn
what
what
to
do
and
how
to
how
to
progress.
So,
thank
you.
Chris,
hey.
K
K
And
I've
been
here
for
like
almost
three
years
senior
since
a
couple
of
months
now.
L
Hi,
everyone
I
just
realized
I
think
I'm,
the
only
one
from
Apex,
because
it's
a
bit
late
for
us,
but
yeah
I'm
Emily
I've,
been
here
a
little
bit
over
two
years
going
three
years,
I'm
a
support
engineer.
A
Fantastic,
thank
you.
Everyone
right
without
further
Ado,
let's
dive
into
the
question
pool
so
I
think
you
all
have
the
document
open,
but
I'll
verbalize
the
questions
and
then,
if
any
senior
support
Engineers
want
to
answer
them.
Please
go
ahead.
A
So
the
first
question
was
how
often
do
or
I
guess
in
this
case,
did
you
update
your
promotion
doc?
Do
you
keep
track
of
your
wins?
And
how
do
you
do
that?
That's
definitely
a
question
I'm
interested
in
because
that's
one
of
my
problems,
I'm
struggling
with
to
actually
keep
track
of
my
work.
K
And
I
think
so:
I
was
exactly
in
your
place.
I
had
a
lot
of
problems
of
keeping
track.
My
of
my
work
I'm
definitely
Master
procrastinator
in
this
case.
So
in
my
case
it
was
like
I
started,
creating
promotion,
Doc
and
abandoned
it
for
a
long
time,
then
I
was
like
it's
about
time
to
just
submit
something
so
I
spent
a
week
collecting
everything
I
did
within
last
couple
of
months.
Every
now
and
then
I
was
taking
a
screenshot
of
something
in
slack.
K
That
was
interesting
and
that
was
it
and
then
issues
merge,
requests
tickets.
These
are
the
things
that
are
still
there.
It's
just
hectic
when
you
need
to
do
it
in
a
quick
tile,
so
definitely
not
recommending
my
way,
but
my
ADHD
makes
me
work
on
deadlines.
So
probably
that's
why
I
did
it
this
way?
I'm
not
recommended
for
myself,
people.
A
K
A
That's
that's
definitely
helpful
insight
because,
as
I
said,
I'm
I'm
procrastinating,
there
definitely.
F
F
You
have
some
description
or
anything
to
that
and
when
you
go
back
like
Lucas
did,
I
did
the
same
thing
and
it
took
me
a
week
multiple
times
in
order
to
get
everything
you
know
sorted
out
and
if
you
have
it
in
a
giant
dock,
you
already
have
the
links
available
and
you
only
have
to
pick
out.
Okay,
this
one
is
more
interesting
than
that
one
and
that's
it
thanks.
H
H
Like
to
add
is
that
for
the
ones
that
are
not
aware
of
it,
the
the
promotion
doc,
the
final
one
you
submit
should
be
promoted,
has
changed
quite
a
lot
since
a
few
years
ago.
So
before
you
would
indeed
paste
a
lot
of
stuff
in
a
big
document
of
all
the
things
you've
did
how
and
people
that
would
read
it
would
have
to
go
through
them
to
actually
understand
what
were
those
and
know
specifically
what
they
were
are,
but
now
it's
more
descriptive.
H
H
I
just
try
to
remember
the
most
important
highlights.
I
had
and
I
refer
back
to
a
document,
but
was
not
so
much
about
having
this
long
list
of
effects
as
it
was
before.
So
that
would
be
my
what
worked
for
me.
You
know
just
having
reminders
of
the
highlights,
so
I
could
write
them
back
in
a
nice
way.
A
Great
Daniel,
thank
you
great
inside
maybe
one
more.
G
I
I
just
like
to
add
that
there
is
a
template.
Now
that
is
named
track
your
work
and
it
was
not
there
before
it's
there
now
and
even
though
I'm
not
I
was
not
using
it.
When
I
did
my
promotion
Doc
and
it
was
I,
I
I
filled
a
different
promotion.
G
Doc
and
I
had
to
change
it
three
days
before
so
putting
it,
because
the
form
changed,
but
I
mean
for
now
I
use
this
template,
or
this
doc
track
my
work,
and
you
will
find
it
helpful
for
like
the
animal
evaluation
as
well
as
filling
in
the
promotion
dock,
so
yeah
it's
a
good
way
to
keep
track
of
whatever
you
do
with
your
time.
A
H
K
Yeah,
a
quite
important
thing
like
from,
like
the
philosophical
perspective,
not
really
practical
you're,
when
you're
tracking
your
work,
don't
treat
it
as
a
promotion
doc,
it's
just
a
draft,
it's
a
collection
of
stuff
and
to
get
anything
to
your
promotion
dog.
Look
at
the
senior
support,
engineer
description,
all
of
the
things
that
are
that
senior
is
supposed
to
be
doing
and
based
on
that
pick
from
the
list,
what
actually
matches
the
best.
K
So
your
best
work
that
is
actually
like
more
senior
than
your
regular
daily
job,
sometimes
the
things
that
I
was
like.
Oh
this
was
awesome.
It
was
so
difficult,
it
was
difficult,
but
it
was
my
like
normal
thing
for
a
support
engineer.
There
was
nothing
senior
in
this,
so
that
might
be
important
but
definitely
put
a
lot
of
stuff.
It's
better
to
have
more
than
less
because
then
you
have
as
a
result,
you
have
something
to
choose
from.
A
I
I
So
it's
I
found
it
often
more
useful
because
sometimes
you
remember
some
keywords
from
specific
issues
or
tickets
or
something
that's
why
you
can't
do
tickets
of
course,
but
sometimes
it's
not
so
easy
to
just
filter
through
all
of
the
Mrs
or
something
based
on
the
metadata,
but
by
keyword
as
possible.
With
this.
So
that's
quite
helpful.
Hopefully.
A
Superb
great,
thank
you,
Katrin.
Okay,
let's
move
on
to
question
two.
So
what
do
you
think
is
the
biggest
difference
between
a
support
engineer
and
a
senior
support
engineer.
C
Mark
I
guess
I
can
start.
The
main
thing,
at
least
for
me,
is
confidence
and
actually
knowing
how
to
push
the
issue
forward.
Usually,
even
if
it's
just
a
thing
you've
never
seen
in
your
life,
it
might
not
be
the
only
time
this
issue
has
occurred.
C
So
usually
you
just
check
the
tickets
check
with
other
Engineers
check
the
documentation
check
with
the
developers
check
everything
you
can
to
actually
just
keep
the
ticket
moving
forward
would
be
my
recommendation,
but
in
terms
of
like
stuff,
that's
considered
a
a
senior
level
issue
or
an
intermediate
level
issue:
I
I
guess
that
line
is
very
blurred.
Each
of
us
has
specific
types
of
things
that
we
are
very
good
at
versus,
not
so
much
so
something
that
might
be
trivial
for
me
might
be
something
that's
very
difficult
for
someone
else
and
the
same
for
me.
J
Senior
engineer
here,
which
is
probably
a
bit
of
an
odd
twist
for
this,
but
in
in
this,
is
a
the
reason
I
want
to
raise.
This
point
is
because
I've
Been
Told
many
times
that
I
gotta
get
the
show
on
the
road
and
do
this
thing
because
I'm
already
performing
like
a
senior,
it
was
the
phrase
that
was
used
performing
performing
at
a
senior
level.
So
I've
explored
this
topic
with
my
manager
kind
of
a
lot,
and
you
know
what
does
that
mean?
J
What
does
that
mean
and
the
picture
that
I've
formed?
J
Is
that
what
it
means
is
you
take
more
of
an
interest
in
your
colleagues
work
and
you
take
more
of
a
leadership
position
in
the
team,
so
you
I,
I
I,
don't
want
to
want
to
reduce
it
down
to
less,
but
I
might
in
this
statement,
but
but
it
it
to
me
to
me,
it
comes
down
to
to
guiding
helping
training,
learning
and
sort
of
paying
more
attention
to
what
needs
to
become
a
part
of
our
knowledge
space.
So
expanding
like
our
our
Nets.
J
A
Sorry,
just
just
to
add
to
this
I've
watched
the
other
two
recordings
of
this
session
that
happened
across
the
globe,
and
that
was
one
of
the
takeaways
from
the
other
two
sessions
as
well.
But
I
will
let
the
senior
support
Engineers
answer
here
that
that
are
on
the
call,
so
I.
F
I
think
Chris
is
pretty
spot-on.
Yeah
in
terms
of
you
know
it's
as
a
support
engineer.
You
look
at
more
of
a
ticket
level
in
your
senior.
You
look
a
little
more
higher.
You
know
it's
no
longer
the
actual
problem
of
ticket
or
you
see.
Multiple
of
these
you
know.
Are
people
getting
stuck
on
specific
topics.
Are
you
you're
overview
goes
a
little
bit
higher
and
see
you
know
what
else
is
going
on.
F
If
you
go
on
set,
it's
even
higher,
you
know
that's
the
difference
in
kind
of
the
levels
it
doesn't
mean
that
we
no
longer
do
tickets
or
anything
like
that.
That's
not
the
difference
here.
H
And
I
would
like
to
to
make
a
bridge
actually
between
what
Philip
said
and
what
Chris
explained,
because
there
is
a
connection.
I
believe
Philip
focused
a
lot
on
the
fact
that
Sinners
are
also
becoming
more
confident
and
better
at
the
normal
support,
engineer,
job
and
I
think
that
leads
to
freeing
up
time
to
look
on
a
higher
level.
H
Like
Chris
said
you
know,
so
we
still
do
ticket
work,
but
you
got
so
comfortable
with
it
that
you
can
keep
that
level
and
still
have
time
over
to
free
your
mind,
to
take
the
theme
to
The,
Next
Level
some
way
and
that's
a
bit
The
Challenge
I,
believe
of
becoming
a
senior,
because
you
are
then
challenged
to
see
how
you
can
do
that.
How
can
you
contribute
to
the
team-
and
there
is
no
time
template
for
that?
There
is
no
someone
saying
hey.
H
Maybe
someone
can
help,
but
in
the
end
the
job
is
up
to
you
to
see
how
you
can
bring
your
skills
or
how?
What
can
you
share
with
the
team
to
improve
it,
make
it
better
and
so
yeah?
For
me,
that's
something
I've
been
keeping
my
mind
very
busy
lately
and
I
believe
everyone
that
becomes
senior
should
start
thinking
in
that
way
as
well.
A
Fantastic,
thank
you,
everybody
yeah.
Would
anybody
like
to
add
something
in
addition
to
that.
K
Yeah
I
might
quickly
add
that,
basically,
when
you
get
promoted,
nothing
really
changes
that
much
because
you
are
promoted
because
you
are
acting
as
a
senior,
not
because
you
are
expected
to
act
as
a
senior
right
after
changing
your
title.
So
that's
the
one
thing
like
nothing,
really
changes
significantly
or
drastically.
In
that
very
moment,
you
just
continue
to
grow
and,
while
continuing
to
grow,
you
can
smoothly
move
to
the
third
question,
probably.
A
J
No
no
already,
you
did
really
well
seguing
me
to
a
very
important
La
caveat
to
the
whole
thing
actually,
which
is
important
to
mention.
This
is
where
I'm
pulling
short
at
the
moment,
this
I'm
I'm
still
for
some
reason,
I'm
slow,
not
for
some
reason.
J
I
know
why
it's
it's
just
that
my
old
Noggin
works
but
I'm
I'm
slow
to
adopt
git
lab
the
a
dog
fooding
gitlab
in
may
still
in
many
of
my
own
processes,
which
I
think
is,
is
why
I've
never
felt
ready
to
to
file
for
my
promotion
is
that
I
feel
like
I
still
I
still
need
to
close
that
Gap,
because
it
is
very
important
that
you
have
a
body
of
work.
J
You
can
reference
on
gitlab.com
Mrs,
talk
updates,
you
know,
comments,
just
activity,
and
so
so
the
change
who
cash
points
out
that
the
change
doesn't
occur.
The
day
you
get
promoted,
it
has
to
occur
as
you
work
towards
getting
promoted
and
what
I'm
still
working
on
is
disclosing
that
last
Gap
it's
becoming
more
proficient
and
efficient
that
using
GitHub
in
my
own
processes,
you
know
yeah.
A
J
A
Okay,
yeah,
no,
absolutely
yeah
you're
right,
we're
drifting
off
here.
Okay,
let's
move
on
to
question
three.
Thank
you
everybody.
So
question
number
three
is:
are
you
working
towards
staff,
support,
engineer
or
anything
else,
as
in
promotion,
Direction,.
D
F
From
the
moment,
I
became
senior
I
said
to
my
manager
great
now,
I'm
going
for
manager
position
because,
for
me,
senior
was
just
a
step
in
between
my
perspective,
has
slightly
changed,
because
managers
currently
aren't
being
hired,
but
there's
also
more
complicated
things
attached
to
it.
So
actually
recently
shifted
my
focus
to
staff.
A
Okay,
that
that
makes
sense
to
me,
on
the
other
hand,
for
me
personally
manager
is
a
completely
different
job,
though.
A
Slipping
away,
you're,
stepping
away
from
the
technical
side
too
much
in
my
opinion,
that's
why
I've
never
actually
pursued
that
that
direction,
even
in
previous
roads.
F
Interestingly
enough,
if
you
look
at
staff,
Cynthia
is
our
only
sport
engineer
right
now.
She
does
almost
no
technical
stuff.
I
literally
talked
with
her
two
weeks
ago
about
this
subject
and
she's
doing
almost
no
tickets
anymore.
No
technical
things
he's
mainly
focused
on
processing,
so
see
almost
doing
the
same
thing
as
a
manager.
No,
at
that
same
level,
yeah.
F
Sorry
Drew
was
the
sport
engineer
or
staff
sport
engineer
before
will
at
Cynthia,
who
also
moved
to
a
different
department,
who
was
mostly
soft
skills
same
as
Cynthia.
A
K
You
I
can
add
that
I
personally
decided
that
maybe
one
day
I
will
go
for
a
manager
position.
It
will
be
somewhere
when
I
grow
up,
which
might
be
later,
but
so
far
I
enjoy
technical
stuff.
So
much
that
the
only
thing
I'm
thinking
about
is
stuff
like
I
could
also
try
to
move
for
engineering
or
something
like
that.
But
yeah
basically
I
decide
it's
not
my
way.
So
I
am
not
yet
working
towards
stuff
in
the
means
of
creating
a
promo
doc
or
something
like
that.
K
I'm,
more
learning,
other
things
like
less
technical
but,
as
Ronald
said,
more
soft
skills,
but
still
within
the
technical
realm,
which
is,
for
example,
I
became
geostable
counterpart
to
as
my
path
towards
senior
and
I'm
getting
involved,
with
a
lot
of
things
that
are
happening
there,
just
to
build
that
bridge
between
support
and
Engineering
for
a
Geo
and
I'm
trying
to
basically
make
some
difference,
make
some
waves
to
get
notice.
K
G
K
Manager
says
squeaky
wheel
gets
all
the
grease
which
is
kind
of
true,
especially
in
the
remote
environment,
where
nobody
can
actually
see
you
doing
stuff
on
daily
basis,
then
talking
to
you
on
your
desk
so
that
that's
important
make
noise
tell
about
what
you're
doing
and
as
I
said
as
for
the
stuff
I'm
working
towards
it.
Nothing
else.
So
far
in
my
radar.
A
D
Yeah
I
mean
yes,
I
am
working
towards
it.
Similarly,
to
True
cash,
not
super
actively,
yet
I'm
mainly
trying
to
just
kick
start
the
promotion
document
early
on
because
for
a
senior
I,
I
wrote
it
in
about
a
week,
and
that
was
very
stressful.
So
this
time
I
would
rather
have
the
the
change
happen
with
the
promotion
document.
Instead
of
summarizing
all
the
change
in
an
instant
iteration.
A
Indeed,
iteration
yeah.
Thank
you
everybody.
Unless
somebody
else
wants
to
add
anything
to
this.
We
can
move
on
to
question
four,
so
question
four:
how
long
did
it
take
from
deciding?
Yes,
I
will
be
going
for
that
promotion
to
handling
handing
in
the
finished
promotoc.
How
long
did
it
take
that
just
jumped?
How
long
did
it
take
to
arrive
at
the
yes
decision?
A
G
G
I
started
the
promotoc
I
guess
earlier
than
when
I
actually
got
promoted.
I
guess
I
always
knew
that
I
wanted
to
go
for
a
senior
right
away,
but
it
took
me
some
time
to
to
change
my
mentality
from
where
I
came
from
to
how
gitlab
works
and
I
guess
once
I
got
that
going.
G
My
major
decided
like
it's
it's
time
to
go
ahead
and
start
filling
the
promo
as
we
go
and
for
me,
as
I,
was
saying:
I
used
a
different
template
for
the
promo
doc,
but
I
was
keeping
track
of
tickets
and
Mrs
that
I
would
want
to
relate
to
when
the
time
comes
and
I've
had
to
kind
of
deliver.
My
promo
document
two
three
days
so
and
move
to
a
different
template.
G
It
was
not
exactly
a
pleasant
experience,
but
we
got
it
done,
but
even
that
the
promoted
dock,
the
template
itself
was
different.
I
guess
having
a
track
of
what
you
want
to
add.
There
did
help
a
lot.
It
was
a
matter
of
reformatting
things,
because
the
new
template
was
more
about
not
not
about
the
number
of
tickets
or
Mrs
that
you
do.
G
But
more
of
how
this
aligns
or
serves
the
the
values
of
gitlab,
so
it
was
more
about
how
to
phrase
it
to
to
fit
in
this
format,
but
yeah,
it's
stressful,
it's,
but
it's
still
a
will.
Yeah.
B
A
J
F
You
yeah
I
interviewed
a
lot
of
you,
but
basically.
A
F
When
I
joined,
I
was
already
operating
at
the
senior
level,
so
I
got
this
question.
I
was
like
did
something
change?
No
because
for
me,
I've
always
worked
on
that
level.
The
only
difference
was
I
was
working
on
this
house
where
I'm
living
in
right
now
with
a
pro
contractor,
which
required
an
enormous
amount
of
time.
So
when
Tom
said
to
me,
he's
like
you're
working
in
Promenade
first
thing,
I
said
like
no
I'll
finish
the
house
first,
before
focusing
on
something
else.
Next
to
it.
Well,
the
house
took
like
a
year
longer
than
planned.
F
So
all
the
time
I
was
just
throwing
stuff
into
my
promo
dog,
never
really
looking
at
it
and
then
basically
sorted
out
switched
to
different
templates
like
20
times
at
some
point,
get
really
frustrated
about
it
and
then
basically
the
decision
was
made
within
gitlab
to
if
you
start
working,
you
don't
have
to
change
your
program
in
terms
of
layout.
They
just
have
to
accept
this.
This
is
the
one
there
that
you
use
when
you
started.
This
should
stay
the
same.
F
E
I
think
that's
a
challenge
for
me.
It's
it's
understanding.
What
makes
you
senior
in
terms
of
stuff,
I
I,
know
stuff.
I
should
know
for
me,
I
think
I
should
know
everything
and
I
I
can't
make
that
distinction
between
senior
and
not
senior
I.
F
E
A
K
F
D
G
Yes,
yeah
I'd
like
to
second
that
definitely
and
I'd
like
to
share
confession
that
I
think
I
felt
the
worst
when
I
was
actually
going
through
the
the
promotion
phase,
because
my
poster
syndrome
was
kicking
hard.
I
was
feeling
like
I
might
actually
effort,
I
mean
it's
happening,
but
do
I
deserve
it
and
I
kept
feeling
that
a
little
bit
after
until
I
guess
when
it
was
actually
announced
and
I
found
lots
of
nice
comments
from
everyone
and
then
like
maybe
I'm,
not
that
bad.
G
You
know
but
yeah,
it's
normal
I,
guess
to
feel
that
we
get
it
from
time
to
time.
But
as
Manu
was
saying,
I
guess
I
started
to
feel
a
bit
better
about
it
about
everything.
Even
before
going
for
the
promotion
making
peace
with
that
I
will
not
know
everything,
and
it's
just
fine.
A
Thank
you,
everybody.
That's
that's
really
comforting
to
actually
understand
that
that
other
people
have
gone
through
or
have
gone
through
the
same
emotions
as
well.
No,
it's
definitely
good
good
to
hear.
A
Okay,
let's
move
on
to
question
five
I
think
we're
not
doing
that
great
in
time,
but
we
don't
have
to
go
through
all
these
questions
so
question
five
for
the
seniors
that
have
have
been
here
a
while.
How
do
you
feel
your
role
has
changed
with
the
rollout
of
the
sgg.
L
A
So
I
would
imagine
some
of
the
seniors
here
on
the
call
actually
didn't
work
as
seniors
before
the
Sgt,
so
maybe
the
people
that
actually
did
work
previously
before
the
sdgs
were
rolled
out
as
a
senior
could
maybe
pick
this
up.
First.
F
A
So
I
guess
that
plays
into
what
what
was
said
earlier,
that
as
a
senior
support
engineer,
you
you're
looking
for
the
bigger
picture
for
the
overview.
What
kind
of
tickets
are
coming
in?
Where
are
people
struggling
that
kind
of
stuff
yeah,
so
that
would
that
would
make
sense
yeah?
So
you
actually
just
because
your
main
view
is
the
Sgt
view.
Yeah
yeah,
you
joined.
You
were
senior
before
that
as
well.
I
think.
I
Yeah
pretty
similar,
however,
it's
relatively
easy
to
get
around
this
by
regularly
checking
the
other
groups,
but
it's
one
more
step,
so
yeah
I,
don't
also
do
this.
Often,
what
I
have
instead
is
a
zendesk
filter
for
some
specific
organizations
which
I
know,
for
example,
send
in
tickets
regularly.
F
A
Yeah
that
makes
sense
yeah.
Would
anybody
else
like
to
comment
on
that.
A
Okay,
then,
let's
move
on
to
question
number
six:
how
do
you
feel
your
ticket
works
specifically
has
changed
after
becoming
a
senior?
Is
it
more
or
less,
faster
or
slower,
I
think
to
an
extent
we
answered
that
already,
but
if
anybody
would
like
to
share
any
more
insights
or
information
on
that.
G
Well,
for
me,
I
guess
it's
more
I'm
trying
to
take
more
tickets
to
take
a
part
of
like
the
the
the
share
of
the
the
complex
tickets
in
the
Q
and
I
feel
like
responsible
for
that
and
I'm
still
trying
to
find
a
balance
between
my
ticket
work
and
and
other
stuff
I'm
still
trying
to
find
my
feed
in
there.
But
I
wouldn't
say
it.
It
is
less
at
all.
For
me,
it
has
been
more.
C
C
C
You
could
pick
up
a
lot
of
easier
tickets,
but
I
do
see
some
people
that
they're,
just
even
though
they
have
like
five
or
six
tickets.
Each
of
those
is
like
months
old
and
they're
trying
to
resolve
it.
So
we
can't
really
measure
them
like
being
equal
like
doing
a
password
reset
ticket
versus
troubleshooting.
C
A
specific
database
issue
is
not
really
equivalent
in
terms
of
like
the
ticket
work
itself
as
long
as
you're,
confident
in
what
you're
doing
as
long
as
you
want
to
keep
pushing
the
ticket
forward,
you're
always
free
to
take
it
like,
for
example,
I've
literally
taken
a
ticket.
I
know
nothing
about
yesterday
for
the
sake
for
the
purpose
of
like
learning
and
pushing
it
forward.
If
I,
if
I
get
stuck,
I
can
just
ask
for
help
and
that's
a
good
thing.
H
And
that's
again
what
Manu
said
right
being
comfortable
with
what
you
don't
know
that
makes
the
biggest
difference
going
for
it
and
and
to
answer
the
question
myself:
I,
don't
think
it
changed.
That
was
definitely
a
place.
I
was
already
I
felt.
I
was
already
senior
at
is
just
picking
these
tickets.
I
had
no
clue
about
and
taking
them
to
a
resolution.
I
didn't
change
the
amount
as
I
was
doing
before
it's
just
like
I
said
before
that
the
capacity
increases
as
you
become
better
at
them.
A
Thank
you
thanks
everybody.
Okay,
let's
move
on
to
question
seven,
how
do
you
feel
about
the
promotion
process
here
at
gitlab?
Can
you
compare
it
with
any
prior
experiences
from
previous
roads
or
anything?
Is
it
I
mean
it
seems
to
be
relatively
straightforward
in
my
limited
knowledge,
but
any
experiences
there.
F
I
explained
it
in
the
previous
one
as
well
one
of
my
previous
companies,
the
decision,
if
you
were
promoted,
was
based
on
the
number
of
years.
You
were
working
for
the
company
so
when
I
joined
there
were
two
seniors
in
that
company
who
were
basically
Juniors
because
they
were
fresh
out
of
school
when
they
started
I
had
a
ton
more
experience
than
them,
and
it
makes
it
really
difficult
to
really
see
them
as
a
senior
because
they
couldn't
help
anyone
else,
because
they're
basically
didn't
know
how
to
solve
problems
a
gitlab.
F
F
K
So
twice,
I
had
to
talk
to
his
manager
to
move
my
manager
because
they
were
like
good
friends
and
they
were
going
through
on
motorbikes
together
so
like
when
we
had
a
team
event,
so
we
went
for
a
beer
and
I
had
to
say
like
hey
Robin,
can
you
just
move
my
promotion
because
I'm
like
doing
all
that
stuff
and
I
want
to
be
promoted?
That's
how
it
happened
like
no
documents,
no,
nothing!
They
just
knew
what
I'm
doing,
because
I
was
pretty
invoked
about
it
here
document
you
have
like
some
near
guidelines.
K
What
the
senior
means
it
wasn't
the
case
in
any
of
my
previous
jobs,
so
so
yeah
a
much
different
on
one
hand,
it's
much
easier
if
you
are
like
very
structured
person
that
can
follow
processes
or
people
like
me
that
have
difficulties
doing,
but
it's
it's
difficult
as
hell,
but
it
works.
C
That
that
goes
to
show
that
get
lab
is
a
mature
company.
Like
we've,
the
the
company
itself
existed
for
many
years
at
this
point
and
I'm
guessing
that
they've
tried
one
way
another
like
iterated
on
the
process,
because
the
current
one
I'm
liking
it
like
I,
like
that
all
I
gotta
do
is
just
document
it
give
it
to
my
manager
and
then
just
follow
the
process.
C
In
both
cases,
the
promotion
is
different,
like
in
the
first
one
it's
based
on
how
they
see
you
and
the
second
one
pretty
much
the
same,
although
there
might
be
some
other
person
that
just
needs
to
vouch
in
terms
of
like
what
you
know,
what
you
don't
know
if
you
deserve
the
promotion,
get
that
being
a
mature
company
and
everything
we
have
a
lot
of
people.
There
is
no
way
to
like
know
everyone
and
know
what
they're
doing
so,
having
having
everything
documented
and
following
a
simple
process:
I'm
I'm,
loving
that
approach.
A
Thank
you
thanks,
Philip
and
Lucas
for
sharing
those
insights.
That's
very
very
true
my
experience
from
previous
previous
roles
as
well.
It's
it
seems
to
be
a
much
more
structured,
formal
approach
here,
you're,
absolutely
right
yeah,
so
we
haven't
got
much
time
left.
One
question
I
would
like
to
ask
is
question
number
nine.
Has
the
promotion
changed?
How
you
view
yourself
so.
F
D
D
They
will
now
see
Senior,
and
that
does
make
a
difference,
but
because
you
yourself,
as
you
said,
Ronald,
don't
really
notice
it
that
way,
because
you
have
already
gone
through
the
change
through
a
much
longer
time,
if
you're
not
really
aware
of
that
much
and
I'm
I,
don't
remember
the
conversation
with
whom
I
had
that
exactly.
But
someone
told
me
that
and-
and
it
made
me
think-
oh
yes
you're
right,
so
someone
who
doesn't
really
know
me
and
will
look
at
okay.
Who
is
this?
What
what
does
he
do
was
his
job
title?
D
They
will
now
have
a
different
first
impression
of
me,
and
that
is
something
to
be
aware
of.
There
is
some
weight
behind
that.
A
Yeah
I
was
I
was
thinking
that
so,
for
example,
if
you,
if
you
jump
on
a
zoom
call
with
a
customer,
and
your
title
is
obviously
there
on
display,
would
you
say
the
expectations
from
your
counterpart
from
the
customer
are
different,
because
because
of
the
title,
or
is
that
just
an
emotional
pressure
that
you
put
on
yourself,
I
I
personally,
would
feel
similar
to
you
manual,
where
you
think
yeah
okay,
there
is,
there
is
something
else
there.
A
customer
probably
has
because
of
that
has
higher
expectations.
A
F
Never
experienced
it
in
a
call
myself
that,
because
my
job
titles
senior
I've
noticed
in
tickets,
when
a
complicated
ticket
comes
in
and
customer
gets
frustrated
at
the
moment
you
reply
like
hey,
you
know,
senior
sport
engineer,
they
go.
Oh
okay.
F
H
Yeah
I
I,
on
the
other
hand,
do
not
care
or
haven't
noticed
any
difference
externally
towards
the
title
or
myself,
but
personally
internally,
like
I,
said
before
I
do
notice.
I
expect
more
from
myself
in
the
sense
of
I
feel
there's
a
pitfall
to
remain
working
as
a
intermediate
in
the
way
that
oh,
just
open
the
queue
or
just
to
handle
my
tickets
and
work
the
whole
day
like
this,
but
I
notice.
Now
there
is
an
internal
voice
inside
me,
saying
that
I
should
be
doing
something
on
a
higher
level.
No
pushing
keep
my
mind.
H
Thinking
on
what
can
be
done.
Like
I
said
how
can
what
can
be
done
on
a
strategical
level?
What
can
be
done
to
take
the
team
to
the
other
level
and
get
out
of
this
comfort
zone
that
I
already
achieved
that
these
working
tickets?
So
it's
a
personal
internal
expectation
that
came
with
it?
In
my
case,
foreign.
K
That's
very
personal,
and
it
will
depend
from
person
to
person
really,
and
everyone
will
feel
it
differently.
I
personally
have
noticed
any
change
for
myself,
because
I
always
expect
from
myself
more
than
I
do
right.
Now,
it's
kind
of
my
way
of
being
me,
I
I,
always
expect
a
little
bit
more
to
push
myself
towards
something
better
higher
quality
and
stuff
on
that,
but,
as
I
said
it's
personal
and
to
everyone
will
probably
feel
it
differently.
A
Fantastic
responses.
Thank
you,
everybody
for
those
insights.
We
have
time
for
one
more
question.
Maybe
question
number
10.
What
do
you
think
is
more
important
for
a
senior
technical
skills
or
soft
skills.
H
G
H
G
To
help
others
and
to
be
mindful
of
how
everyone
worked
differently
or
handle
stuff
differently,
so
you
need
to
understand
that
to
be
able
to
help
them.
K
Yeah
yeah
I
I
would
say
you
may
be
a
senior
that
is
very
balanced.
You
may
be
a
senior
that
is
super
technical.
You
may
be
senior,
that
is
super
soft
skills
oriented
and
if
your
strength
is
one
of
those
follow
it
and
I
think
we
have
seniors
that
are
more
technical.
K
We
have
seniors
that
are
more
soft
skills
and
it
it
doesn't
really
matter
it's
just
you
do
something
that
is,
that
is
more
than
expected
from
intermediate
fee,
like
I
I,
don't
feel
like
there
is
a
strict
required
one
that
you
have
to
be
one
or
the
other
or
both
equally
strong.
K
You
have
to
have
a
bit
of
both
to
work
in
customer
support
right,
so
you
have
to
have
soft
skills
because
otherwise
customers
probably
hate
you
or
want
to
understand
you
or
something
like
that.
So
we
already
have
that
we
all
already
have
enough
I
think,
and
so
it
is
the
way
you
choose
more
technical,
operational.
A
You're
right
Lucas-
absolutely
we
wouldn't
be
in
this
job
if
we
wouldn't
have
a
bit
of
both
you're
right,
yeah,
absolutely
yeah,
so
Ronald
you
posted
you're,
happy
to
extend
the
call
if
anybody
needs
to
drop.
Apologies
for
actually
not
managing
the
time
better,
but
I
thought
the
discussion
was
great.
That's
about
I
didn't
want
to
really
interrupt
it.
Doing.
A
I'm
happy
to
overrun,
if
you.
A
And
have
time,
but
if
you
need
to
go
then
that's
absolutely
fine
as
well.
Thank
you.
Everybody
for
your
attendance.
K
A
Question
number:
eight,
exactly
yeah,
so
if
you
could
change
anything,
I
I
noticed
this
question
actually
was
a
lot
of
people
struggled
in
the
previous
sessions
to
answer
that,
but
let's
give
it
a
go
anyway.
If
you
would
it
could
change
one
thing
about
being
a
senior?
What
would
it
be.
A
G
A
H
H
But
I
do
believe
that
there
is
a
tendency
of
calling
out
on
seniors
for
dealing
with
more
urgent
matters
right
and
it's
I
think
it's
normal
to
be
expected
and
I
don't
know
if
others
also
feel
the
same,
that
that
changed
for
them
as
they
become
seniors
or
not
at
all.
K
You
know,
I
I
have
a
feeling
that
I
am
being
called
out
to
things
that
are
within
my
area
of
expertise,
regardless
of
my
own,
so
I
I
was
doing
Geo
and
when
there
was
something
Geo.
K
F
A
Could
it
could
it
be
based
on
the
experience
that
the
management
team
has
with
your
work
Daniels,
or
maybe
it's
not
because
you're
a
senior
but
because
you
have
previously
dealt
with
hot
tickets
in
a
way
and
the
technical
skills
that
that
basically
show
the
manager?
Well,
you
are
a
person
that
could
handle
this
ticket
better
than.
H
Interrupt
but
it's
not
about
ticket
work
like
it's.
What
I
said
about
becoming
a
senior
and
acting
on
a
strategical
level
right,
so
in
a
way,
it's
up
for
each
senior
engineer
to
make
out
what
that
would
be,
how
their
influence
would
be,
but
I
do
feel
like
there's.
H
Also
a
tendency
and
and
managers
should
be
doing
that
figuring
themselves
out
how
to
take
the
team
to
the
other
level
right,
so
sometimes
they
have
ideas
of
their
own
and
and
they
suggest
a
maybe
the
seniors
could
do
this
or
could
do
that
and
that's
totally
okay,
you
know
and
in
a
very
soft
way,
there's
no
demands.
There's
no
hard
definitions
of
this
is
what
you're
gonna
do,
which
is
great
about
git
lab
in
general
right.
I
Yeah
I
would
like
to
agree
with
all
of
what
was
being
said,
so
the
the
senior
name
tag
solidifies
the
expectation
a
little
bit,
but
it's
also
a
Capstone
about
the
fact
that
you
have
already
proven
that
you
can
fulfill
this
expectation
earlier
in
the
promotion
process.
Right
I
mean
what
Lucas
said
will
and
Greece.
I
What's
the
saying
there
that
that
already
happened
before
right
and,
for
example,
giving
the
people
who
call
upon
you
for
Urgent
or
escalated
tickets,
for
example
a
good
impression
of
your
responses
and
the
fact
that
you
are
responding
well
and
can
handle
the
situation
is
a
large
part
of
the
promotion
process
as
well,
and
but
I
wanted
to
add
one
item
about
strategic
things
that
wasn't
discussed
before
strategic
can,
of
course,
also
mean
specifically
large
customers,
for
example,
so
I
know,
but
yeah
I
mean
there
are
some
customers,
of
course,
who
are
quite
large
and
therefore
strategic
and
seniors
can
be
expected
to
be
asked
more
about
these,
for
example,
in
the
focus
groups
or
in
escalation.
K
I
just
linked
one
issue,
just
because
you
mentioned
should
then
he
didn't
expect
it
I.
Don't.
K
They
are
just
like
not
very
well
communicated,
but
the
issue
that
I
linked
is
basically
very
non-hidden
expectation
or
trying
to
Define
expectations
for
senior
role
in
case
of,
for
example,
account
escalations
right
so
like
I,
don't
think
they
are
hidden.
I
think
they
are
just
not
well
defined
yet
they're,
just
some
videos
right
now,
yep.
F
Funny
story:
when
I
joined
about
a
month
in
my
manager
asked
if
I
could
jump
on
a
call
with
a
customer
pretty
large
one
at
the
time
and
I
was
like.
So
what
do
you
want
me
to
do?
You
know
want
me
to
solve
the
problem.
I'd
be
working
here
from
what
that's
not
gonna,
or
do
you
want
me
to
be
present
and
he
basically
said
just
be
there:
I
wasn't
able
to
help
them
in
any
way.
F
I
got
a
lot
of
technical
support
or
technical
people
on
the
call
from
gitlab
that
were
helping
now
I'm
four
years
later
same
thing
happens.
You
know,
customers
getting
annoyed,
I
get
pinged
either
in
DM
or
or
you
know,
on
a
thread
when
it's
going
on
hey
this
is
happening.
Can
you
do
something
and
like
for
me
the
test,
never
changed
and
I
don't
mind
personally,.
A
Yeah,
it's
it's
often
just
to
share
presence
Ronald.
Isn't
it
yeah
right,
actually
just
getting
expectations?
Yeah,
fantastic!
Thank
you,
everybody
right,
so
we
are
10
minutes
over
time.
Do
you
want
to
continue
with
the
further
questions,
or
should
we
call
it.
F
E
L
I
L
F
A
Has
to
fit
your
life
balance
unless
you
pointed
out,
you
were
in
the
middle
of
actually
your
building
Works
going
on
everything
has
to
you
know.
Sometimes
that
has
to
take
precedence
over
over
any
promotion
aspiration.
So
yeah
I
absolutely
agree
with
everybody
here,
I
think
it
has
to
fit
each
individual
person.
E
G
Yeah
I
was
just
gonna,
I,
traded
on
that
and
say
like
it's
one
of
the
best
things
that
we
have
in
gitlab
and
it's
not
in
other
work
environments,
the
pressure
of
moving
forward
and
how
you
be
feeling
or
how
your
marriages
would
make.
G
You
feel
if
you
said
that
you're
not
ready
for
it
or
you
don't
want
it,
and
it's
one
thing
that
I
love
about
here:
that
there
is
no
this
kind
of
pressure
from
managers
and
even
like
there
is
no
peer
pressure
that
you
should
have
everyone
excels
in
their
own
way
and
you
should
enjoy
it
as
you
want.
There
is
nothing
that
should
make.
You
feel
bad
about
not
wanting
to
go
forward
with
any
other
title.
K
I
can
only
tell
that
I
wasn't
pushed
towards
a
senior
I
was
definitely
actively
encouraged
by
my
manager,
but
he
never
made
me
feel
as
if
I
have
to
do
something
as
if
there
was
any
expectation
or
Consequences
of
not
pursuing.
That
I
had
to
specifically
ask
my
manager
to
push
me
more
because,
as
I
said,
my
ADHD
brain
works
on
deadlines.
I
asked
him
to
give
me
a
deadline
to
do
my
promo
doc.
K
He
did
and
he
was
like
pushing
me
much
more
often
because
I
asked
him
to
and
that's
the
only
way
I
was
able
to
finish
my
promo
Doc
and
to
get
promoted
because
I
was
like
postponing
it
so
already
like
once
or
twice
submitting
the
talk,
because
it
wasn't
even
near
to
be
ready,
so
yeah.
There
is
definitely
no
expectation,
but
if
you
want
someone
make
you
feel
like
there
is
even
ask
them,
they
will
probably
try
their
best
to
do
it.
So.
K
Totally
up
to
you
and
if
you
feel
the
comfort
of
being
staying
on
a
contributed
level
for
longer
I
I
personally,
don't
see
any
thing
that
could
that's
that's
being
wrong
about
it.
Totally
fine.
A
Fantastic,
thank
you.
Everybody
great
session,
really
loved
all
your
ideas
and
opinions
and
insights
into
the
whole
process
with
that
we're
way
over
time.
Now,
unfortunately,
so,
apologies
again,
but
thank
you
very
much
and
have
a
great
rest
of
your
day.
Thank.