Heads up! To view this whole video, sign in with your Courses account or enroll in your free 7-day trial. Sign In Enroll
Preview
Start a free Courses trial
to watch this video
A portion of the interview process may include whiteboarding. We will break down what that involves as well as some best practices.
Resources:
Related Discussions
Have questions about this video? Start a discussion with the community and Treehouse staff.
Sign upRelated Discussions
Have questions about this video? Start a discussion with the community and Treehouse staff.
Sign up
A portion of the interview process
may include whiteboarding.
0:00
The purpose of having a candidate
whiteboard is to gain an understanding of
0:04
their communication and
problem-solving skills.
0:08
Whether you're a seasoned pro or
0:15
new to the field you might be asked
to whiteboard during interview.
0:16
It doesn't matter your level, it just
depends on if the company chooses to
0:21
use this method and at what point in
the interview they want to observe this.
0:25
This typically involves a whiteboard and
a marker, the interviewer or
0:30
interviewers and no computer.
0:34
Just the idea of white boarding
is a bit intimidating.
0:38
As you learn more about it and practice,
it'll be simple for you to do.
0:42
Here's the basic rundown of what
whiteboarding will look like.
0:47
First, the interviewer or interviewers
will give you a problem that they want you
0:52
to find a solution for
by writing out your code on a whiteboard.
0:56
The interviewer will observe how you
process the task, ask questions and
1:00
answer questions you might have.
1:05
The purpose is so they can visually see
how you think and process a problem.
1:07
This is a very simple breakdown of what
the whiteboard interview will look like.
1:13
What's most important is how you handle
that time you have to tackle the problem
1:17
the interviewer gave you.
1:21
So let's discuss some tips and
then jump into some examples.
1:23
It's important in every stage of this
to write out everything on the board.
1:30
The purpose is so they can visually see
what you're thinking in your brain.
1:35
Write down details from the prompt
they give you to help you remember or
1:40
any notes that will be helpful for you.
1:44
You want to show them
what you're considering,
1:46
what code you're trying,
what you've ruled out, and so on.
1:49
Always make sure you have clarity on
what you're being asked to solve.
1:55
It's okay to ask questions.
2:00
When you were given the problem or prompt,
2:02
you may have some clarification questions
such as, who is the target audience?
2:04
Or is your data pre sorted?
2:08
Or do you need to address that?
2:11
Don't be afraid to ask them,
it shows your attention to detail and
2:13
gives you an understanding of
the parameters you're working in.
2:17
Articulate your thought process.
2:22
It's okay to use
pseudocode to get started.
2:25
Make sure to leave room
to write your code.
2:28
If that will help you get organized and
get the lay of the land, do it.
2:31
Talk through your solution
as you're coding.
2:36
Don't worry about having perfect syntax.
2:41
But you should use best practices and
good naming conventions when possible.
2:43
This might be difficult if
you're an internal thinker, but
2:49
try to talk throughout the entire process,
so they hear what you're thinking.
2:52
Make sure to test your code with as many
edge cases as possible to identify errors
2:59
in your logic.
3:04
Do not wait until the end to
begin testing what you created.
3:05
Don't ask for acceptance.
3:11
Refrain from asking,
does this meet what you're looking for?
3:13
Or does this look okay?
3:17
And, does this seem right?
3:19
You never wanna seem like you're doubting
yourself or don't know what you're doing.
3:22
If you make a mistake,
it's okay to correct your errors.
3:28
Identify what isn't working, and what you
think you can do to overcome these issues.
3:31
This does not mean you messed up your
whiteboard interview whatsoever.
3:37
It shows you're able to check your work,
own mistakes and fix them,
3:41
which is a strong quality.
3:45
Once you have a working solution,
identify ways to make it more efficient or
3:50
ways to improve.
3:54
This allow the interviewer to see how
you're able to take a step back, and
3:56
see what the others option are to
make a product or design better.
4:01
Also it allows you to take a moment
to look at what you've done,
4:05
to catch something you might have missed.
4:09
Don't solve the problem right away.
4:13
Even if you think you know
the best solution, or
4:15
you've worked a similar problem before,
you will miss out on information by not
4:18
asking clarifying questions or
seeking alternative solutions.
4:23
State your assumptions, because this is
a random prompt you've been tasked with.
4:29
You're not going to know the technical or
time constraints.
4:34
So you might tell them some assumptions
you're making to arrive at a solution.
4:37
For example, you might say, I'm assuming
there is a stable internet connection.
4:42
Or I'm assuming we collaborated
with marketing to research
4:47
the demographic needs.
4:51
It shows your ability to
make considerations for
4:53
other folks who might be involved.
4:55
Start over only if you need to.
4:59
Maybe you feel like you made a mistake and
want to erase and begin at the beginning.
5:03
If you find that you've gotten yourself to
the point that you're going the wrong way,
5:08
start over in another
area of the whiteboard,
5:12
if there's room before
fully erasing everything.
5:14
This will allow you to look back
on what you've done so far and
5:18
borrow from your previous logic.
5:21
Make sure to articulate what you're
thinking to the audience, so
5:24
they are following what you're doing.
5:27
Whiteboard interviews are typically timed,
5:31
which I know makes it all
the more nerve wracking.
5:34
Asking for a time check so
you can properly budget your time,
5:37
shows off your time management skills.
5:40
Make sure to answer questions.
5:44
Throughout your whiteboard interview,
5:47
the interviewer may ask you questions
regarding why you make certain choices.
5:49
You're not being asked questions
because you're doing something wrong.
5:53
They're interested to
understand how you think,
5:57
what you know,
how you address a problem, etc.
6:00
You need to sign up for Treehouse in order to download course files.
Sign upYou need to sign up for Treehouse in order to set up Workspace
Sign up