►
From YouTube: GitLab Team Pitch Office Hours (2nd time)
Description
Team Pitch Office Hours for Meltano team
A
Some
so
this
is
the
second
edition
of
team
office
team
pitch
office
hours,
which
is
kind
of
a
meeting
where
teams
can
talk
about
teams
that
are
hiring
within
gitlab
can
talk
about
cool
stuff,
they're
working
on
what
their
plans
are
and
so
we'll
be
going
through.
Some
of
those
can
also,
if
there's
questions
people
have
about
you,
know,
transfer
process
or
how
any
of
that
works.
Maybe
at
the
end
we
can
do
like
a
Q&A.
A
If
there
are
more
specific
questions
or
you
can
always,
you
could
follow
up
with
me,
Sam
goldstein,
if
you
want
to,
if
you
want
to
talk
one-on-one
about
your
specific
situation,
Christopher
had
a
good
comment
in
the
chat.
Maybe
it'd
be
good
to
do
a
quick
round
of
introductions
since
I
think
we
got
a
pretty
small
group
here.
A
All
right,
I
got
everybody
now
on
the
array
thing
so
yeah
I'm
introduced
myself,
I'm
Sam,
Goldstein,
director
of
engineering
for
ops
I've,
been
here
at
get
lab
since
January,
so
a
couple
months
now
should
we
just
go
around
I
would
maybe
call
on
people
Michael.
Do
you
want
to
tell
us
a
little
bit
about.
B
A
D
A
A
A
F
Also
in
Portland
Oregon,
so
I'm
Craig,
I'm,
the
engineering
manager
for
the
memory
and
the
database
teams.
Most
importantly
for
this
conversation
we'll
be
talking
about
the
database
team
position,
openings
that
we
have
and
I
have
been
here
for
about
ten
months
and
I
worked
previously
with
John
at
puppet.
G
Sure
yeah
Derek
I'm
a
senior
was
this
in
your
front-end
engineer
on
the
mill
tonneau
team
I'm
very
much
focused
on
the
UI
UX
and
design
side
of
things
too
and
I'm
about
probably
six
hours
east
of
what
is
it
Sam,
Craig
and
Chung.
You
guys
are
important
time
in
Moscow
Idaho,
so
just
on
the
stealing
border
there
of
Washington.
H
H
Here
and
my
wife
was
driving
four
hours
south
and
it
was
83
degrees
down
there
right
on
the
border,
so
great
weather,
and
just
when
I
would
say
if
anybody
needs
any
additional
help
through
this
process,
don't
hesitate
to
reach
out
to
me
as
a
super
important
to
make
sure
that
I've
folks
feel
comfortable
and
movements
know.
This
is
a
tough
time
and
I
really
want
to
make
sure
that
we
make
sure
that
concerns
are
addressed
and
everything
else
that
goes
along
with
that.
J
K
I
have
to
check
because
there's
so
many
Eric's
around
here,
I'm
Eric
and
I'm,
the
product
manager
for
the
static
site,
editor
group
I'm
standing
in
for
John,
who
is
my
e/m.
We
are
I've,
been
here
for
about
two
months
and
I'm
in
Richmond
Virginia,
which
is
sunny,
but
not
as
warm
as
your
other
southern
areas.
K
L
A
I'll
say
that
sounds
like
a
really
interesting
project
where
it's
like,
because
I
understand
a
very
business
critical
in
terms
of
enterprise,
readiness
and
there's
a
lot
of
interesting
like
disaster
recovery
aspects
that
so
we'll
hear
more
about
that.
In
a
little
bit,
we've
got
Steve
and
then
Jerome
and
then
we'll
kind
of
dive
into
the
team
information,
speed,
Steven
everyone,
I'm,
Steven,
Wilson
I'm,
the
engineering.
H
A
A
Do
a
quick
run
through
kind
of
I
think
the
positions
we'll
be
focusing
on
in
this
discussion
and
then
I'll
kind
of
hand
it
go
around
and
people
can
just
talk
a
little
bit
about
their
teams
and
and
why
it's
interesting
to
the
so
yeah
the
enablement
group
that
Chun
is
in
charge
of
that's
all
about.
You
know:
delivering
gitlab
more
effectively
to
customers
and
there's
a
lot
of
interesting
stuff
going
on
in
that
space.
That's
pretty
critical,
configure
team
is,
has
a
one
position
available.
It's
looking
like
do
that.
A
The
way
these
transfers
are
working
out
so
there's
some
we'll
talk
a
little
bit
about
that
growth.
Telemetry
I
know
is
a
high
priority,
verify
CI,
there's
some
really
trying
to
staff
up
that
team
and
some
pretty
interesting
like
core
functionality,
a
static
site,
editor
very
interesting
project,
we'll
hear
about
a
lot
of
a
lot
of
interest
from
folks
in
that
and
then
there's
stuff
in
dev
with
you
know,
there's
a
bunch
of
positions,
I
think,
but
me
and
H.
A
C
C
Close
to
that
the
core
services
like
elasticsearch
post,
we
seek
oh
and
also
the
performance
and
memory
consumption
of
the
applications,
primarily
focusing
on
replication
and
disaster
recovery.
And
then
the
distribution
team
is
all
about
packaging
deployment
and
configuration.
So
managers
who
will
share
more
detail,
but
we
are
pretty
low
accord
to
the
tune
of
staff.
I
mean
low
level
details
yeah.
G
A
F
Craig
sure
yeah
some
run
in
the
database
team.
We
are
it's
a
good
mix
of
active
sorry,
not
act
Ruby
on
Rails
development
and
Postgres
sequel
development.
As
of
October
last
year,
we
only
had
one
database
maintainer,
so
there's
been
a
big
effort
and
push
to
get
more
database,
maintainer
and
kind
of
spread
the
wealth
we
are
up
to
four
or
five
as
of
today.
So
we've
gotten
more
of
the
development
community
within
gitlab
to
be
more
involved.
So
that's
been
huge.
Our
goals
coming
out
for
the
coming
quarters.
We
have
partitioning.
F
We
need
to
implement
mostly
that
will
impact
user
experience.
It
will
bring
back
data
a
lot
faster.
It
should
provide
some
performance
improvements
as
well
we're
upgrading
on
production
everywhere,
Postgres
sequel
is
going
to
be
upgraded
from
nine
point.
Six
to
eleven
point:
seven
we've
been
behind
for
a
little
while
and
we
will
be
able
to
consume
a
lot
of
the
performance
improvements
of
PostScript
sequel
in
the
later
versions.
F
And
then
the
next
big
ticket
item
is
we're
working
on
charting,
which
builds
on
top
of
partitioning
and
charting
will
help
with
our
availability
scalability
all
those
things
so
we're
less
like
a
feature
team
and
more
back
in
as
Chunn
kind
of
described,
so
got
some
important
and
exciting
things
to
be
working
on
over
the
next.
Several
milestones
it
for
me
looks
like
distribution
is
next
Steven.
H
H
I
think
I'll
dive
right
into
those
bullets
there
that
automate
the
deployment
of
large
scale
architectures
that
include
hae
veil
ability
and
geo.
One
of
the
the
newer
projects
that
we're
working
on
is
something
called
git
lab,
Orchestrator,
we've
noticed
from
product
and
other
sources
that
there's
a
variety
of
tooling
that
folks
used
to
deploy,
get
lab
at
scale.
It's
we're
trying
to
sort
of
rein
that
in
and
come
up
with
a
standard
that
allows
us
to
deploy
and
manage
customer
customer
instances
in
a
consistent
way.
H
H
Once
that
happens,
the
next
step
will
be
for
us
to
be
able
to
deploy
pages
into
a
kubernetes
environment
using
some
sort
of
an
object
store,
there's
other
things
that
are
happening
in
our
cloud
native
charts
help
three
is
reasonably
new.
One
of
the
negative
things
about
our
charts
is
they're
very
complex,
and
one
of
the
things
we'd
like
to
do
in
the
coming
year
is
use
as
leverage
elm,
trees,
libraries
and
other
optimizations
to
make
the
chart
a
little
bit
easier
to
manage.
H
Next,
one
enhance
the
install
upgrade
and
next
steps
experience
pretty
self-explanatory,
like
it's
one
thing
to
get
get
lab
installed
once
it's
another
to
have
lots
and
lots
of
users
on
it
and
have
to
keep
it
current.
One
of
the
things
that
the
team
really
prides
ourself
on
is
that
the
you
know
a
seamless
upgrade
experience
between
both
minor
and
major
versions.
We're
wanting
to
continue
that.
Obviously,
that's
a
big
part
of
the
success
of
the
team
is
keeping
customers
current
and
update
major
components.
This
is
one
that
Craig
alluded
to
as
well
right.
H
M
So,
there's
a
lot
of
work
to
be
done
to
to
to
get
the
geo
solution
up
to
more
complete
and
level
maturity,
and
a
lot
of
that
revolves
around
just
like
making
things
easier
to
set
up
it's
it's
quite
an
involved
installation
and
also
making
the
certain
processes
like
the
failover
process,
a
lot
friendlier
and
also
making
it
a
little
more.
The
experience
of
using
the
secondary
node
just
a
lot
more
seamless
and
sort
of
I
guess
not
quite
as
apparent
so.
The
Geo
team
is
six
back-end
engineers
and
one
front-end
engineer.
M
It's
also
a
pretty
mature
team.
I
think
most
of
the
engineers
on
geo
have
been
with
get
lab
for
at
least
a
couple
of
years.
We
have
I
think
four
get
lab
core
get
lab,
maintainer
x'
on
the
team.
So
that's
one
reason:
I'm
excited
to
move
in
the
geo
teams
just
to
get
the
chance
to
work
with
with
the
team
that
has
so
much
experience
in
the
company
and
yeah
I.
Think
a
couple
couple
of
the
big
items
that
were
working
on
now.
J
We
need
engineers
with
straw,
which
will
be
on
wheels
and
also
the
elastic
search
experience
and
also
in
order
to
increase
the
performance.
We
have
moved
part
of
the
functionality
of
our
Ruby
on
Rails
application
and
wrapped
into
a
golden
based
in
texture.
So
the
goal
extremes
is
also
desirable
for
the
team.
So
right
now
we
are
joining
out
the
feature
to
our
customers
on
K
dot-com.
J
J
We'll
be
working
some
other
very
challenging
features
like
reducing
the
index
size
and
how
implement
zero
downtime
ring
taxi
and
also
to
improve
the
search
performance.
Just
to
give
some
example
right
now
we
hope
we
could
enable
that
the
real
axis
search
based
search
for
connect
to
all
our
key,
that
welcome
user.
But
we
cannot,
because
the
cost
is,
is
quite
high.
So
it's
quite
challenging
and
very
important
for
us
to
fund
ways
to
manage
the
index.
J
A
Awesome
thanks
for
that
I'm
gonna.
This
one
is
the
configure
team
that
Nicolas
click
manages.
He
can't
be
here
today,
so
I'm
gonna
read
through
this.
This
is
a
full
stack,
possibly
front-end
engineering
position
on
the
configure
team.
Configures
focused
on
features
that
integrate
with
things
like
kubernetes,
terraform,
automate
infrastructure
on
major
cloud
providers.
So
it's
an
opportunity
there
to
dive
into
those
technologies.
A
If
you
have
an
interest
in
kind
of
operations,
cloud
native-
and
you
know-
can
do
it
kind
of
a
full
stack
type
role.
This
could
be
good
position
for
you,
so
yeah.
You
can
talk
to
Nick
more
about
that.
If
you're,
interested
or
I
can
answer
questions
about
it
hand
it
off
now
gross.
So
that's
I
think
you
drew
I
talked
about
telemetry
and
what
you're
doing
there
hey.
N
Everyone
so
we're
responsible
for
collecting
product
usage
data
across
gitlab.
We've
got
this
really
interesting
problem
of
trying
to
do
growth
while
respecting
our
users,
privacy.
So
this
includes
how
do
you
do
tracking
and
how
do
you
do
experimentation
on
both
gitlab
comm,
where
we've
got
access
to
data
and
then
on
self-managed,
where
we
actually
aren't
plugged
into
someone's
database
I
think
we
owe
our
users
of
gitlab
and
we
sort
of
understand.
You
know
what
our
users
are
and
are
comfortable
with.
N
So
that's
that's
the
tricky
part
which
we're
navigating
right
now,
it's
a
similar
sort
of
space
which
which
you
all
were
working
on
before,
where
has
to
do
with
product
analytics
and
product
usage.
One
of
our
big
goals
for
the
growth
team
this
year
is
to
move
towards
rapid
experimentation
across
the
entire
funnel.
N
We
have
two
open
rules,
one
is
for
the
front-end
and
one
is
for
be
back
end
and
we're
specifically
looking
for
people
with
strong
product
analytics
backgrounds.
Our
team
is
small
right
now.
We've
got
one
dedicated
back-end
engineer
and
we've
been
borrowing
engineers
across
the
growth
team
just
to
reach
hit
some
of
the
company
goals
across
growth.
We've
got
about
16
engineers
that
work
with
us.
A
Awesome
really
important,
stuff
and
I
think
it's
I
know
for
me.
You
know
if
I,
if
I
had
more
information
about
like
which
features
you
know
were
being
used,
that
would
be
very
informative
to
a
lot
of
decisions.
Next
group
is
verify
which
I
think
Darby
couldn't
be
here
Christopher.
Do
you
want
to
talk
about
CI
and
kind
of
how
core
and
important
that
is
really?
Would
you
rather
me
pitch
it.
H
I
can
do
that
just
give
me
a
quick
second.
This
is
what
happens
when
I'm
trying
to
look
at
something
else.
Real,
quick,
yeah,
so
CI
is
obviously
a
cornerstone
of
our
product.
It's
one
of
the
pillars,
big
pillars
right
from
prescriptive
of
of
things
that
we're
doing,
in
particular
the
verify
continuous
integration
team
is
really
challenged
this
year
with
trying
to
figure
out
how
we
basically
up
our
enterprise
sales.
H
We
don't
we
don't
want
to
emulate
Jenkins
fully,
obviously,
because
we
have
our
own
special
sauce
that
we
have
as
part
of
this
product,
but
we
do
want
to
give
them
a
good
experience
and
in
the
transition
associated
with
it,
this,
this
team
is
primarily
I,
believe
doing
most
of
its
work
and
go
at
this
point
related
to
some
of
the
work
they're
doing-
and
you
know,
the
milestones
are
extremely
full
variety.
As
far
as
the
the
work
items
that
you
potentially
could
consider
associated
with
it.
So
would
you
relevant
personnel
yeah.
A
That's
perfect,
Christopher
thank
you
and
yeah.
I
know
they're,
going
from
like
five
engineers
to
ten
I.
Think
it's
an
area
that's
really
being
invested
in,
and
you
know
my
understanding,
I
mean
just
to
echo
Christopher,
is
that
you
know
something
very
core
to
get
lab.
It's
very
important.
They've
got
a
lot
of
a
lot
on
their
plate,
and
so
it's
a
you
know
it's
a
great
place
to
make
an
impact.
If
you.
H
Yes,
and
just
a
highlight
that,
thanks
for
reminding
me
we're
doubling
down
there-
and
this
is
a
good
example
where
you
know
originally-
product
management
was
thinking.
Eight
people
and
we've
got
the
Jenkinson
Porter
in
there
and
I
said
no
we're
gonna
have
ten.
It
just
makes
a
lot
of
sense
just
for
the
complexity.
So,
if
you're
looking
for
a.
G
A
Absolutely
alright
I
think
that
next
we're
gonna
segue
into
the
static
site
editor,
which
I
think
has
at
least
one
position
left
up
and
another
couple
folks
that
recently
kind
of
transferred
through
this
process
and
into
that
group
or
and/or
in
the
middle
of
that
I'm
buddy
Eric.
You
want
to
tell
us
about
the
cool
stuff.
That's
going
on
there
yeah
glad
to
I.
K
So
we
want
to
be
a
little
more
general
and
offer
a
really
delightful
editing
experience
and
the
great
thing
the
great
opportunity
is
now
we
don't
really
know
what
that
is
yet
we're
still
learning
we're.
Just
starting
up
I've
been
here
for
two
months:
the
group's
only
existed
since
I
think
October
November
and
we're
still
defining
that
longer
term
vision.
While,
while
iterating
on,
like
immediate
improvements
to
the
handbook,
we
do
maintain
sort
of
the
technical
side
of
the
handbook
as
well.
K
So
we
work
a
lot
on
improvements
to
the
build
pipeline
and
the
the
middleman
project
itself,
there's
other
exciting
competitors
and
peers
in
this
space.
The
this
the
jam
stack
movement
is
a
very
exciting
area.
I
think
it
lab
is
positioned,
really
well
to
be
to
bring
a
powerful
and
flexible
solution
to
the
market,
whether
that's
adopting
various
other
projects
and
bringing
them
into
our
product
or
building
our
own
or
combination
of
the
two
I
think.
K
There's
some
interesting
challenges
that
we
have
to
solve,
like
tracking
changes
in
generated
static
production,
HTML
files
back
to
source
files
and
working
with
structured
data
in
a
visual
way,
things
like
JSON
and
CSV.
How
that
gets
represented
to
users
in
a
way?
That's
more
user
friendly
and
easier
to
edit
and
then
a
lot
of
challenges
around
performance
and
live
editing
is
a
big
part
of
the
the
experience
we're
going
for
either
in
page
or
side-by-side,
live
preview
or
not
quite
sure.
K
What's
going
to
be
the
right
answer,
but
performance
is
going
to
be
top
of
mind
for
anybody
working
on
this
group
and
we're
get
to
work
on
components
that
are
going
to
be
used
across
multiple
teams
on
collab.
We
were
already
talking
about
using
similar
components
in
the
editor,
with
the
knowledge
and
wiki
grew
the
web
IDE,
obviously
we'll
be
working
with
pages
and
potentially
bringing
these
improvements
and
to
review
apps
down
the
road.
So
there's
gonna
be
a
lot
of
cross
stage
collaboration
and
a
lot
of
really
important
work
going
on
I.
K
Think
yeah
for
for
the
front
end.
We're
really
looking
for
a
really
strong
javascript
experience
and,
and
ideally
some
experience
with
the
with
the
jam,
stack
or
static
site
generators
and
then
on
back-end
were
Ruby
Ruby
on
Rails
and
love
to
find
some
of
the
open
and
working
open
to
working
in
other
languages.
Though,
because,
as
the
listing
Sean
mentioned,
we
won't
be
building
some
plugins
and
go
or
Python,
depending
on
the
platform
that
we're
trying
to
target.
A
L
Yeah
thanks,
first
of
all,
Eric
great
summary,
all
of
the
technical
part
for
tips
that
excite
editor
as
Sean
is
not
here
today,
yeah
I
can
really
emphasize
its
it's
a
really
interesting
area.
We
have
one
of
the
most
complex
view.
Applications
in
the
lab
is
the
web
IDE,
and
a
lot
of
the
stuff
will
be
housed
in
there.
So
that
a
very
interesting
topic
and
on
the
other
hand,
we
have
a
lot
around
gem
snake
and
especially
going
awesome
to
the
handbook.
L
So
it
would
be
a
really
nice
and
interesting
mix
for
a
couple
of
different
areas
greenfield
starting
rebuilding
stuff,
but
also
building
super
new
stuff.
Oh
yeah
def
is
having
a
couple
of
open
positions
at
the
moment,
or
at
least
the
next
year.
Manage
is
our
biggest
focus
point
so
manages
everything
from
the
start
of
our
lifecycle,
also
its
housing
quite
different
areas.
Currently,
the
main
things
that
we
are
staffing
in
the
year
are
on
one
hand,
X's
and
spaces.
So
X's
and
spaces
are
all
around
user
management
group
management.
L
We
are
also
looking
for
plans
certified
planned,
certifies
everything
around
requirements-
management,
but
really
working
in
the
project
management
here,
but
with
a
really
different
outlook
all
around
especially
those
requirements,
topics
and
building
something
new
for
again
big
enterprises.
Again,
that's
the
pattern
here.
Looking
at
the
different
area
that
the
main
fragmentation
years
that
we
are
currently
looking
for
is
one
in
manage
compliance
and
one
in
create
static
site
editor
and,
as
we
are
speaking
right
now,
the
rest
is
really
classic
back
in
engineering
get
left
with
race.
So
that's
the
main
focus
point
there.
L
Then
we
have
a
complete
new
team
which
is
currently
built
and
is
combining
a
lot
of
different
topics
in
reality
for
different
topics,
which
is
the
ecosystem
and
contribute
experience
team
which
may
be
at
some
point.
We
will
find
even
a
better
name,
but
it's
combining
everything
that
nick
has
done
so
far
with
his
team
on
the
ecosystem
side,
so
really
integrating
with
other
products
JIRA
classic
one,
and
there
are
also
a
couple
on
the
roadmap
where
we
want
to
integrate
it
clip
nicely
into
it.
L
So
that's
also
I
think
a
really
interesting
part
to
connect
with
with
our
solutions
also
sometimes
are
the
languages
and
looking
at
different
topics
there
and
on
the
other
hand,
we
have
contributed
the
experience
which
is
also
housing
and
everything
that
we
are
want
to
drive
forward
in
the
sense
of
improving.
Simply
the
experience
for
every
contributor,
the
speed,
especially
and
the
performance
of
currently
being
able
to
contribute
internally
and
externally,
but
really
with
the
main
focus
internally.
L
So
one
of
the
big
focuses
the
GDK
so
really
improving
the
GDK,
making
it
faster,
making
it
more
stable,
making
it
more
productive.
So
mocking
is
a
huge
topic
most
probably
soon,
and
and
also
how
to
get
to
a
state
that
you
are
basically
able
to
lotta
stuff
inside
kid
lab.
So
those
are
really
the
focus
points
there
and
the
other
part
is
everything
around
pajamas
and
keep
let
the
I
so
the
component
libraries,
that's
more
of
the
front
of
the
area
that
we
are
looking
into.
L
A
H
This
is
a
lot
of
great
information,
I'm,
trying
to
figure
out
how
to
plate.
Lee
say
that
we
should
get
this
all
in
the
handbook
and
I
don't
have
a
flight
way
to
say
it,
so
we
should
probably
go
like
everybody
who
engineering
manager
thought
about
this.
This
should
be
think
about,
like
maybe
there's
something
we
should
put
intersections
like.
These
are
the
challenges
this
group
has
for
that
perspective,
because
it.
C
H
G
I've
reached
out
to
a
few
of
you
and
I'll,
probably
have
a
some
follow-up
questions
kind
of
after
this,
but
I
didn't
have
one
question
for
you:
Tim,
with
respect
to
the
manage
compliance
for
an
n
roll.
You
mentioned
the
and
I
looked
at
this
briefly,
but
the
Design
Systems
one
was
was
one
of
the
pieces
that
personally
stuck
out
to
me.
I
was
curious.
If
there
you
can
speak
to
any
of
the
other
UI
portions
of
that
roll.
What
else
would
be
encapsulated
in
that
role?
And
if
there's.
O
L
The
contribute
experience
team
is
that
the
one
around
design
system
and
the
air
we
have
a
very
clear
focus
for
the
front
end
engineers,
mainly
around
this
design
system
and
getting
our
design
system
fully
implemented.
So
currently
it
can
simply
happen
or
it.
What
happened
in
the
workflow
was
okay.
There
is
a
new
component
that
design
is
suggesting
that
we
want
to
have,
and
in
reality,
three
different
teams
needed,
and
one
team
was
like
okay,
I'm
thinking
this
I'm
doing
this
and
then
for
whatever
reason
it
took
longer
or
they
were
blocked.
L
In
that
sense,
what
happened
is
the
data
two
teams
where
especially
really
had
a
dependency
on
it
and
they're
blocked?
That's
what
we
are
trying
to
simply
reduce
by
having
dedicated
in
front-end
engineers
to
work
really
on
the
most
important
component,
so
that
we
are
not
hitting
roadblocks
there,
but
the
bigger
topics,
as
we
have
by
now
already
like
40
components
implemented,
but
they
are
not
completely
following
the
design
guidelines,
so
they
are
sometimes
it's
just
a
couple
of
pixels
missing
on
the
painting,
and
sometimes
it's
a
bigger
thing.
L
But
what
we
want
to
get
is
really
get
on
one
hand,
components,
integrator,
implemented
it
correctly
styled
and
then
the
first
step.
It's
really.
But
this
is
then,
although
more
of
the
work
with
the
product
teams
and
their
responsibility
is
to
get
it
also
into
the
product
and
especially
replace
everything
that
we
have
already
in
there,
that
which
is
then
the
third
part,
and
as
soon
as
all
those
three
steps
are
done,
then
we
have
a
green
checkmark
on
a
component.
L
That's
very
one
to
get
to
the
other
part
for
a
front-end
engineer
in
the
contribute
experience
team
are
also
working
with
the
GDK
team
or
working
against
GD
k,
for
example
improving
the
web
pipelines
so
really
deep
down
technical
stuff.
There.
You
know
the
other
hand,
although
of
course
the
whole
ecosystem
stuff
around
building
integrations
building
front-end
for
that
if
they
are
needed
in
their
product
or
if
we
need
to
add
something
to
our
product
to
make
them
successful.
So
it's
a
it's
a
good
mix.
L
A
A
A
A
You
know
one
thing
that
we
try
to
really
make
sure
we're
doing
is
following
all
of
the
local
labor
laws.
So
there
is,
you
know,
as
a
result
of
that
some
kind
of
process
and
making
sure
that
we're
you
know
building
all
the
right
documentation
around
this.
So
that's
something
that
you
know
in
general.
You
won't
have
to
deal
with,
but
something
that
you
know
I've
been
working
with
our
people
business
partner
around
in
general
kind
of
the
way
the
process
would
work.
A
Is
that
you've
gotten
some
information
now
about
kind
of
what
positions
are
available.
It'd,
be
anything
that
you're
interested
in
be
good
to
reach
out
to
the
hiring
manager.
For
that
position,
if
you're,
not
sure
who
that
is,
you
can
ask
me
and
I
can
track
that
down
for
you
and
then,
if
you,
you
know,
determine
yeah,
it
feels
like
this
is
a
you
know,
good
match,
for
something
I'd
be
interested
in
and
you
know
would
be
set
up
to
do
well
in
then.
A
You
know
that's
kind
of
the
next
step
in
moving
that
process
forward.
So
you
know
a
lot
of
it
is
about
you
trying
to
figure
out
what
you're
interested
in
you
know
where
you
feel
like
you
have.
The
biggest
impact
will
do
something
fulfilling.
We
are
very
also
focused
on
making
sure
there's
a
good
outcome
for
everybody
in
this
process.
So
you
know
one
of
the
goals
is
that
everybody
ends
up.
You
know
in
a
position
that
it's
really
exciting
and
that
they're
happy
about.
So
you
know
some
of
that.
A
B
A
H
Think
he's
actually
hired
somebody,
but
they
may
have
just
started
so
Marin
would
be
the
person
I'd
start
with
to
engage
that
one's
a
little
different
in
regards
to
the
like
most
of
the
positions.
We're
thinking
in
terms
of
the
role
doesn't
change
right.
Your
current
position
and
role
doesn't
change.
H
F
H
So,
in
that
case,
I
don't
want
to
speak
for
Marin,
but
it
may
be
a
little
more
like,
like
generally
Leonard,
will
transfers
no
interviewing.
Do
you
want
to
work
on
this
team
as
it
doesn't
look
like,
because
a
good
fit
major
curries
and
accepts
and
and
very
short,
circuited
role
changes?
Sometimes
it's
not
an
official
process,
but
you
know
Marin
may
say:
okay
well,
I'd
like
to
actually
go
through
more
of
a
formal
interview
process.
F
A
H
It
really
comes
around
the
legal
laws
for
locality.
So
that's
what
we're
trying
to
make
sure
of
in
the
US
as
an
example,
if
you're
an
engineer
and
you
move
positions
they
you
know,
they
don't
have
those
restrictions
but
other
countries.
Even
if
you
change
the
comma,
whatever
group
you're
assigned
to
literally
it's
it's
a
contractual
change.
N
G
Mean
I'm
doing
alright
I
guess
that's
just
the
reality.
The
situation
always
come
a
little
bit,
I
guess
with
respect
to
odds
in
terms
of
the
open
positions
from
a
front-end
perspective,
there's
there's
a
little
bit
less
opportunities.
I'm
looking
like
I,
said
I
kind
of
reached
out
to
a
few
folks,
there's
one
specific
that
I'm
very
interested
in
but
again
it
there's
no
guarantees.
So
who
knows
what's
gonna
happen
but
we'll
see,
but
it's
understandable
we
weren't
executing
as
well
as
we
would
have
ideally
like
to
do
so.
I
B
Yeah
I'm
gonna
echo
that
I
mean
it's
been
a
wild
ride,
so
we
we
explored
a
lot
of
things
and
also
one
of
the
thing
that
we
explore.
It
is
like
building
a
start-up
within
the
startup,
which
is
its
own.
Like
ecosystem
writes
its
own
like
thing
that
does
not
exist
that
much
so
we
learned
a
lot
I
think
and
hopefully
it's
not
all
gonna
be
lost.
D
Yeah
as
for
me,
the
situation
is
a
little
bit
different
because
I'm
not
leaving
mentality,
but
it
said
I
will
be,
but
yeah
I've
really
appreciated
the
last
six
months
that
I've
gotten
to
work
with
the
rest
of
this
team
and
I
feel
certain
amount
of
responsibility
to
not
have
their
work.
You
know
completely
kind
of
die
and
go
to
waste
now.
D
So
I
really
motivated
to
see
this
through
a
little
while
longer,
but
obviously
it's
going
to
be
a
completely
different
deal
by
myself
than
with
the
team
and
I
love
keep
reaching
out
to
them,
occasionally
with
questions
related
to
their
other
parts
of
the
code
face.
But
you
know
one
day
at
a
time
different.
So
for
me
it's
a
very
different
reality,
but
we'll
figure
out
what
it
looks
like.
E
Yeah,
we're
really
small
team,
so
it's
just
kind
of
weird
going
from
this
little
thing
that
was
off
to
the
side,
to
like
learning,
thicket,
lab,
org,
I,
don't
know
the
rest
of
the
team
feels
this,
but
I've
been
just
trying
to
learn
like
what
is
everything
and
what
do
all
the
groups
do,
and
just
it's
kind
of
a
that.
You
know
the
information
firehose
that
you
get
when
you
start
a
new
job,
but
like
you're
already
in
the
company
and
now
you're
experiencing
the
firehose.
E
So
it's
just
a
lot
of
kind
of
learning
to
navigate,
but
this
has
been.
This
has
been
super
helpful
that
I
totally
agree.
This
content
should
go
on
the
group
pages,
because
this
gave
me
a
lot
of
insight
into
what's
kind
of
the
nitty
gritty
like
needed
things
which
I
think
is
really
helpful.
So
but
ya
know
personally
just
like
adjusting
to
not
hanging
out
with
these.
These
guys
every
day
will
be
we
interesting
by
then
yeah
I'm,
a
kind
of
excited.
A
Awesome
ya
know
I
think,
there's
there's
definitely
a
lot
of
cool
stuff
going
on,
and
you
know
just
in
terms
of
other
individuals
that
have
you
know
kind
of
had
this
type
of
process
gone
through.
It
recently
obviously
there's
some
constraints
in
terms
of
like
what
roles
are
available,
but
in
general
it
seems
like
everybody's
done.
You
know
been
really
able
to
find
something
that
you
know.
It's
really
interesting
to
them
if
they're
excited
or
they
can
have
a
big
impact.
So
it's
been
nice
to
see
that,
hopefully,
that
will
continue
here.
A
All
right
well
we're
a
little
over
time,
but
I
think
it
was
good
good
to
get
through
all
that,
thanks
for
everybody
for
participating,
I
will
put
the
video
up
and
I'll
mention
it
on
that
issue.
That's
linked
in
the
agenda,
so
you
can
follow
it
there
and
they
try
to
get
some
more
of
this
like
into
the
handbook.
Also,
if
this
is
something
we're
going
to
be
doing
regularly
so.