►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everybody.
We
wanted
to
talk
a
little
bit
today
about
good
note-taking
practices,
especially
for
green
house,
because
we're
recording
everything
in
green
house
and
just
good
ideas
about
how
to
take
your
notes,
how
to
review
your
notes
and
make
it
accessible
to
everybody
else.
You
might
need
to
read
them
as
well
as
making
sure
that
you're
keeping
your
notes
relevant
to
the
job
posting
and
checking
for
bias.
A
So
what
I
try
and
do
when
I'm
taking
my
notes,
is
put
the
notepad
file
up
and
I
pre
fill
in
all
the
questions
that
I
might
ask,
because,
depending
on
the
prior
answer,
I
might
pick
one
of
two
or
three
follow-on
questions.
I
try
and
have
all
that
prefilled,
so
I'm
not
trying
to
type
it
at
the
last
moment.
A
I
took
from
the
candidate
to
ask
for
clarification
to
make
sure
that
I
captured
it
correctly
and
I
might
put
like
a
really
quick
stream-of-consciousness
note
at
the
bottom,
such
as
you
know,
I'm
concerned
about
docker,
so
that
this
way
I
can
maybe,
in
the
next
question,
either
try
and
dig
into
docker
as
a
follow-on
or
dig
into
docker.
Yes,
the
next
question
could
be
relevant
to
that
to
dig
into
it
a
little
bit
more.
A
So
that's,
at
least
how
I
think
about
taking
notes
in
the
moment
is
try
and
capture.
As
many
of
the
words
directly
from
the
candidate
as
possible,
underneath
the
relevant
question
that
I
asked
and
put
in
anything
that
I'm
concerned
about
following
up
one
immediately
or
maybe
in
the
next
question,
do
you
have
any
good
hints
and
tips
for
how
to
make
sure
you're
getting
the
best
notes?
Gerry
yeah.
B
So,
to
kind
of
build
off
of
what
you
just
said,
I
think
I
will
I
should
say
I
also
beforehand
try
to
load
in
the
questions
I'm
going
to
ask.
The
handbook
has
a
really
good
list
of
questions
that
are
available.
So
I
asked
myself,
who
am
I
interviewing
so
I
generally
interview
product
managers
are
gonna,
be
part
of
our
team.
B
I
met
engineering
managers,
engineering
directors,
people
within
UX
and
I
go
and
look
at
those
questions
and
find
ones
that
I
think
are
relevant
to
the
job
description
based
off
the
role
I
will
have
with
that
person
and
I.
Had
those
questions
in
ahead
of
time.
I
also
highly
suggest
that
as
you're
taking
the
notes,
Nicole
types
a
lot
faster
than
I
do
so
she
can
generally
get
everything
in,
but
if,
for
some
reason,
I
feel
like
I
missed
the
answer
or
missed
a
part
of
the
answer,
I
ask
them
to
be
more
concise.
B
A
lot
of
the
questions.
We're
asking,
as
part
of
interviews,
aren't
usually
requiring
a
paragraph
or
three
paragraphs
to
answer
the
usually
a
sentence
or
two,
and
if
you
can
get
the
candidate
kind
of
re
repeat
it
their
answer
in
a
more
like
hey.
What's
one
sentence
to
say
that
or
hey
how
would
you
say
that
in
two
sentences
you
can
end
up
capturing
a
more
absolute
version
of
what
the
candidate
said
with
that
I
also
recommend
and
I.
B
Don't
know
close
conversion
this
in
a
minute
here,
but
rereading
the
answers
after
the
fact
to
because
you
know
you
may
have
inadvertently
put
the
wrong
answer
with
the
wrong
question,
because
you
know
you
are
trying
to
pay
attention
be
engaged
while
also
taking
notes
so
making
sure
things
are.
Mapping
to
the
question
you
asked
and
the
answer
you
received.
A
I
understand
like
if
they
answered
the
actual
question
and
then,
as
part
of
if
they
answered
the
actual
question
I'll
do
a
quick
first
draft
of
do
I
feel
like
it
was
a
good
answer
or
not,
and
I
will
paste
all
of
that
into
green
house.
But
I
won't
score.
It
I'll
actually
just
save
it,
because
you
can
do
a
save
without
score
and
then
I'm
gonna
come
back
later
and
that
might
be
a
couple
hours
later
or
the
next
day.
A
I
try
not
to
make
it
anything
more
the
next
day
and
then
I
actually
look
at
the
job
posting
in
the
tab
in
green
house
and
I.
Look
at
my
notes
and
I
tried
to
make
sure,
as
you
said,
there's
some
good
questions
in
our
handbook
that
I
chose
specifically
for
that
role
and
so
I.
Try
to
make
sure
did
I
get
enough
information
about
the
requirements
for
the
job
and
in
some
cases,
I'll
say
I
not
applicable.
A
I
was
not
able
to
determine
if
they
have
experience
in
this
particular
thing
because
of
the
way
that
they
answered
things
or
failed
to
answer
follow-ups
but
I'll
kind
of
go
through
and
make
a
checklist
or
a
tldr
at
the
top,
and
when
I
make
my
TL
DR
I
actually
try
and
put
double
spaces
in
between
anything
and
a
little
because
green
house
doesn't
have
tabs.
It
doesn't
allow
for
multiple
spacing.
A
So
you
have
to
use
carriage
return
and
is
really
to
emulate
any
kind
of
readability,
so
at
the
top
TLDR
do
they
have
the
requirements
for
the
job.
Then
I
read
through
my
mental
notes,
one
more
time
and
I
check
for
is
there
anything
irrelevant
to
there
and
I
just
get
rid
of
it,
because
nobody
needs
to
see
it
if
it's
not
relevant
to
the
job.
Posting
I,
just
stream-of-consciousness,
take
notes
so
stuff
ends
up
in
there
and
then
the
second
thing
is
I.
A
Look
for
a
halo
effect,
which
is
where,
because
they
answered
one
question
positively.
I
might,
during
the
initial
interview,
felt
more
positive
about
their
answer,
a
second
or
third
question,
but
on
rereading
it,
maybe
that
really
didn't
show
depth
of
knowledge
around
something
and
we
require
technical
knowledge
in
a
particular
field.
B
So
I
do
highly
recommend
the
TLDR
or
whatever
you
want
to
call
it
summary
at
the
top
of
the
notes,
I
think
anybody
who's
worked
with
me
will
say
that
I've
been
given
the
gift
of
being
verbose,
and
so
my
interview
notes
can
be
rather
long
but
giving
somebody
whether
it's
the
hiring
manager
for
the
role
or
somebody
else
who's
going
to
need
to
interact
on
well.
Your
interview
was
about
giving
that
summary
is
really
helpful.
B
What
I've
been
doing,
which
I've
received
some
positive
feedback
on,
is
listing
pros
and
cons
as
part
of
them
so
again
doing
what
Nicole
just
said.
You
think
about
the
role
as
it
is
and
what
are
two
or
three
strong
points
and
weak
points
for
that
that
candidate
and
it's
really
important
to
be
I,
guess
factual,
no
statements
and
they're
not
be
full
of
opinion.
You
know
an
example,
being
you
know
we're
all
about
company?
B
Yes,
you
can
kind
of
get
a
sense
to
how
some
it
would
work
remotely
asking
the
questions,
but
you
can't
definitively
say
they
would
be
horrible
ever
not
working,
because
you
don't
have
that.
As
the
data
point
did
not
work
with
you
at
a
remote
company,
and
so
coming
back
to
that,
and
looking
at
your
notes
that
those
are
definitely
things
to
pull
out,
I
am
a
little
I.
Do
take
a
little
more
time
than
Nicole.
Does
I
give
myself
about
24
hours,
and
the
main
reason
for
that
is
one
calendars
can
be
very
busy.
B
We
get.
We
have
a
lot
going
on
and
two
I
do
want
to
take
a
chance
to
look
at
it
again,
a
fact-finding
mission,
type
response
and
looking
at
it
the
day
afterwards,
you
may
have
noted
something
that
was
very
subjective
at
the
time,
but
in
hindsight
it
doesn't
necessarily
apply
and
a
good
example
that
is
like
you
know,
energy,
something
we
always
pick
up
on
in
interviews.
B
B
They're
really
really
strong
technically
and
we
maybe
just
need
to
help
them
with
being
a
little
bit
more
outgoing
in
their
interactions,
and
so
you
want
to
be
able
to
pull
those
things
back
and
say
and
Nicole
said
well
like
look
at
the
job
description.
Does
it
actually
do
they
meet
that?
Do
they
have
that
technical
knowledge?
Looking
for
the
case
of
product,
the
product
knowledge
were
looking
for,
whether
it's
UI
research,
if
it's
UX,
you
know,
but
something
that
is
factually
as
part
of
the
job
description,
I
will
say
as
part
of
that
process.
B
I
also
do
then
trim
down
my
answers,
like
Nicole
said
as
well.
I'll
end
up
usually
with
four
or
five
bullets
for
each
of
the
questions
that
are
being
asked,
and
those
are
me
noting
what
to
ask
the
follow-up
question
about
and
then
I
go
back
and
I
just
put
the
actual
answer
in
there.
As
part
of
that
I
know,
one
thing
I've
started
doing,
and
it
it
was
a
probably
a
pointer
from
Nicola
might
have
been
a
pointer
from
somebody
else,
but
I'm
actually
putting
that
if
she
said
scoring
right
after
the
answer.
B
I'm,
usually
going
with
a
yes,
it
was
right,
so
you
do
correct
or
incorrect
as
the
follow-up
to
those
for
the
technical
questions.
So
that
way
somebody
who's,
not
technical,
like
myself,
is
or
that
I
am,
can
come
in
and
see
that
that
was
right,
or
that
was
wrong
because
we
do
ask
questions
like
you
know,
explain
the
structure
of
a
botnet
and
what
the
role
of
the
zombie
is
in
that
process.
A
B
Remember
at
the
time
that
was
able
allowing
me
to
be
able
to
catch
that
incorrect,
though
the
thing
that
I've
personally
noticed
and
it's
not
about
my
notes
and
catching
it,
but
the
difference
between
somebody
who
gives
me
the
scorecard
as
a
hiring
manager
right
after
they
talk
versus
like
within
five
minutes.
You
know
like
taking
their
own
notes
and
paste
in
the
VIN,
where
they've
given
themselves
some
time.
I
get
a
lot.
I
didn't
allow
this
of
the
that
conjecture
that
ends
up
in
there
like
well.
B
I,
must
assure
this
person
would
be
a
good
fit
because
they
said
this
thing
during
the
interview
and
it's
like
well,
what
was
the
context
that
thing
that
was
being
said
was
it
being
said
in
a
way
that
was
like,
oh
yeah,
by
the
way,
I
hate
me
on
video
calls
obviously
via
a
thing
that
would
stick
out.
That
would
not
be
good
right.
B
And
so
I've
noticed
that
those
are
less,
wouldn't
that
somebody's
taking
the
time
afterwards
to
put
the
notes
in
I
I
do
differently
than
a
clinicals.
She
just
said
she
puts
them
in
and
then
comes
back
and
reads
them
later.
It
doesn't
score.
It
I
take
all
of
my
notes
in
Google,
Docs
and
then
I
come
back
and
read
that
and
then
paste
in
and
give
the
score,
but
I
think
either
way.
B
A
So
if
somebody
says
my
team
did,
X
or
I
was
on
a
team
that
did
X
I,
always
try
and
ask
well
what
were
you
responsible
for
or
what
you
know
pieces?
Did
you
work
on
or
what
part
were
you
most
excited
to
be
contributing
into
in
order
to
pull
out
exactly
what
their
responsibility
was?
But
some
people
managed
to
evade
that
throughout
the
entire
interview,
and
although
that
is
sometimes
a
cultural
bias,
and
sometimes
that
is
a
gender-based
bias.
A
But
when
you
go
back
and
look
objectively,
you're
like
well
that
maybe
wasn't
a
exactly
technical,
correct
answer
or
I
couldn't
actually
assess
whether
they
can
work
remotely
or
whether
they
do
have
a
ton
of
experience
with
roadmaps
and
so
that
obviously
I'll
have
to
bring
it
down
and
I,
don't
necessarily
move
it
to
a
negative.
No,
so
I
tend
to
have
yes,
I'm,
confident
that
they've
done
this
before
and
can
talk
about
it.
A
I
have
a
can't,
assess
or
not
applicable,
I
wasn't
able
to
determine
and
then
I
have
a
no
they
outright
admitted
to,
or
they
were
completely
incorrect
talking
about
something.
So
that's
another
thing,
I
think
is
when
you
take
your
note,
so
it
doesn't
always
have
to
be
like
yes
or
no.
You
can
just
say,
cannot
determine
you.
Don't
always
have
to
grade
someone
negatively
about
something
you
can
just
say
can't
determine.
A
So
I
guess
next:
do
we
want
to
get
into
scoring,
maybe
sure
so
in
green
house
for
everyone
who's
gone
through
this
process
once
before
or
some
of
the
training
videos?
There's
a
ton
of
questions
that
everyone
has,
that
you
can
rate
with
little
emojis,
I.
Think
yeah,
because
there's
like
a
star
there's
a
thumbs
up,
there's
all
different
I
wish
it
was
just
numbers
but
they're
not
all
required.
A
A
B
I
would
definitely
say
when
it
comes
to
scoring
if
you're
giving
a
score
and
you're
unsure
whether
or
not
you
captured
it
in
your
notes,
above
in
that
area,
I
I
do
highly
recommend
you
use
the
notes,
functionality
that,
you
can
say
add
note,
and
then
you
can
write
what
your
thoughts
were
as
to
why
you
gave
this
wrong.
Yes,
yes,
no!
B
We're
strong,
now
I
find
that
that's
also
a
good
way
to
measure
whether
or
not
your
peer
eclis
giving
that
answer,
whether
its
objective,
because,
again
to
the
earlier
comment
that
a
lot
of
it,
if
it's
done
right
away,
is
very
emotionally
attached,
like
from
the
actual
conversation,
as
opposed
to
factually
looking
at
it.
In
hindsight
and
I
would
say,
with
that
handbook
change.
I
think
we
need
do.
You
need
to
be
a
little
bit
more
leaning
towards
more
strong
guesses
based
for
Nicole
just
shared.
B
B
Yes
is
actually
a
good
thing
in
your
opinion,
or
you
know,
I
gave
the
strongest
cuz
I
really
think
they
are
that
top
1%
or
top
5%
of
candidates
again
looking
at
those
things
after
the
fact,
there's
Nicole,
so
a
couple
of
hours
up
to
a
day,
you'll
feel
that
you
do
sometimes
maybe
think
differently
than
you
did
at
the
time.
In
fact
it
as
a
encouragement
I
was
just
anybody
watching
the
video,
whether
your
get
lab
or
your
knock
it
lab.
You
know,
look
at
notes
from
an
interview
took
a
well.
B
You
did
last
week
and
see
what
your
thoughts
are
of
those
notes
a
week
later,
if
you
haven't
done
one
in
a
while,
you
don't
remember
the
last
candidate
wait
till
that
happens,
and
then
you
can
kind
of
see
that
for
yourself
that
hey
my
opinion
has
changed.
Not
because
your
opinion
was
wrong.
The
last
time
it
just
it
was
an
opinion.
It
wasn't
based
off
the
job
description
or
they
exact
question
you're
answering.
A
Awesome,
so
is
there
any
other
good
points
you
want
to
bring
up,
I
think
my
summary
for
everyone
watching
the
video.
If
you
want
the
good
summary
is
Green
House
doesn't
respect
formatting,
please
use
double
carriage
returns,
where
possible
and
I
think
you
made
a
great
call
out
of
everyone,
looks
at
things
a
little
bit
differently.
So
sharing
what
score
you
gave
and
specifically
why
the
pros
and
cons
and
what
that
means
to
you
allows
everybody
else:
who's.
A
Reading
the
notes
about
a
candidate
or
who's
deciding
about
the
candidate
to
take
your
score
into
context
and
then
making
sure
that
you,
when
you
put
that
into
that
context,
are
being
as
factual
as
you
can
be.
Obviously,
you're
you've
only
spent
40
minutes
with
this
person,
and
you
can
only
I
know
so
much
and
do
so
much
but
be
as
factual
as
you
can
and
keep
it
as
relevant
as
you
can
to
the
job
posting.
B
Yeah
III
think
those
are
great
takeaways,
the
to
add
to
the
formatting
one
I
always
pretend
that
I'm
typing
it
and
I
think
it's
like
Ulysses
or
one
of
the
text.
Editing
apps,
for
you
have
to
use
like
pound
signs
and
make
headers,
and
all
that
like
pretend
you're
writing
in
that
application
or
an
application.
So
we're
like
are
mark
markdown
on
in
our
ID,
because
there
is
no
formatting
after
you
hit
save
and
the
biggest
thing
I've
seen
that's
caused
problems
in
my
time.
B
Interpreting
interview
notes
is
knowing
is
that
yellow
flag
of
red
flag
from
the
sentence
before?
Is
it
from
the
sentence?
After
how
do
am
I
supposed
to
be
interpreting
what
you
wrote
and
pretending
using
our
IDs,
probably
a
good
way
to
think
about
that
where's
Nicole?
So
you
got
multiple
blanks.
You
have
a
maybe
starting
to
paragraph
or
and
I
do
use
like
two
hash
tags
or
pound
signs
to
say
this
is
now
the
technical
questions.
This
was
the
product
questions
to
help
separate
it.
So
definitely
good
takeaways.