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
Not all companies use whiteboarding as a practice in their interview process. Let's explore other practices that you might experience.
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
Not all companies use whiteboarding as
a practice in their interview process.
0:00
And with many companies
now working remotely,
0:04
they might opt into other
alternatives to learn how you work.
0:07
It'll differ at each company and
position, but
0:11
you'll want to familiarize yourself with
other tools in addition to whiteboarding.
0:14
[SOUND] A coding challenge with
an observer entails being given a coding
0:19
challenge or a series of challenges for
you to complete in a given amount of time.
0:24
The interviewer may ask you some
questions throughout but they are mostly,
0:30
they're just to observe.
0:34
You'll find that these are relatively
similar to whiteboarding,
0:36
just no whiteboard.
0:40
[SOUND] There are some tips to help
you successfully code challenge.
0:41
[SOUND] Make sure you have clarity
on what you're being asked to solve.
0:46
You might think that asking questions
shows you don't know what you're doing.
0:51
Remember in actuality,
0:55
asking questions shows a commitment
to search for the best solution.
0:57
[SOUND] Complete as many
challenges as you can and
1:02
provide details about
the decisions you're making.
1:05
Similar to whiteboarding, you want to
be explaining your thought process.
1:10
[SOUND] Compile and
1:14
test your code as necessary to
ensure you're on the right track.
1:15
Don't wait until the end to test it.
1:20
You wanna show that you check your
work throughout the process and
1:23
can adapt if changes are needed.
1:27
[SOUND] Making a mistake is not a problem.
1:28
What matters is that you are able to
identify a mistake and correct the error.
1:32
Make sure to verbally identify
what isn't working and
1:37
what you think you can
do to fix the issue.
1:41
Last but not least,
once you have a working solution,
1:45
identify ways to make it more efficient or
ways to improve.
1:48
This again shows your ability to
adapt if there's a better solution.
1:52
[SOUND] Pair programming may
be a new experience for you.
1:57
Maybe you're used to working solo.
2:02
Either way,
it's something that as you practice,
2:04
you'll become more comfortable with.
2:07
A company that has pair programming as
part of their interview process is likely
2:10
including this part to learn
your technical ability,
2:14
as well as what it's
like to work with you.
2:18
Essentially it is two or more people
working together to write code.
2:20
Pair programming is not a quiz or
trap to catch you off guard.
2:26
There's a perk to pair programming as much
as the interviewer is learning about your
2:31
skills and personality.
2:35
You're able to learn and see firsthand
someone you'll be working with.
2:37
It gives a peek into the work you'll
do and the culture at the company.
2:42
I wanna share with you some tips for my
peers to assist you in pair programming.
2:46
Determine what your role will be.
2:51
Usually driver or navigator.
2:54
If you're the navigator, your job
is to provide guidance to the other
2:57
developer on how to implement
a solution to a given problem.
3:01
As the navigator, make sure you understand
what resources are available and
3:05
utilize them when necessary.
3:10
If you're the driver,
your job is to do the coding and
3:12
take guidance from your navigator.
3:15
Whether you're the navigator or
driver, ask questions.
3:18
This is your time to learn about the
feature your building or designing, and
3:22
get clarification on the project, or code.
3:26
[SOUND] Depending on
the role you're applying to,
3:29
an employer may find it more valuable
to take a look at your portfolio.
3:32
This allows them to get a look
at the work you created and
3:37
hear your thought process around it.
3:41
Typically the portfolio review is
a presentation of some of your work to
3:43
an interviewer or a panel.
3:47
When tasked with a portfolio review,
you'll want to curate it with more recent
3:50
work or
hyper relevant work to the position.
3:55
Some folks choose to present their
work on their personal website.
3:58
While that can be one
way to show your work,
4:02
we have found that it isn't always
the best format to present it in.
4:05
Instead, consider making a presentation
deck even though it can take more work.
4:09
When putting together
your portfolio review,
4:14
we recommend that you gather
three projects to present.
4:17
You might be able to include more,
4:21
it really depends on the amount
of time you're given.
4:23
Make sure to be intentional when selecting
the projects for the portfolio review.
4:26
You want them to tied to either the
technical needs of the company based on
4:31
the job description or the industry.
4:36
I know you might be thinking that three
seems very little to showcase all the work
4:38
you've done.
4:42
But keep in mind that you will be
talking through these projects and
4:44
you'll be having a discussion around them.
4:47
So time will fill up quickly.
4:49
I mentioned that you'd be
talking through these projects.
4:52
Let me expand on that a bit.
4:55
For each project,
you should begin with a brief
4:57
high level explanation of the product,
and what your role was.
5:00
For example, were you working with a team?
5:04
Was it a solo project?
5:07
What were your contributions, etc?
5:09
Additionally, you should share any
research you gathered, testing you did and
5:12
show mock-ups or the wireframes.
5:17
Don't be afraid to call out the problems
or challenges you solved along the way.
5:20
The STAR method is a valuable tool
to help you organize your delivery.
5:26
This method is a technique that
can be used in interviews,
5:31
to make sure you share all
information while remaining concise.
5:34
STAR stands for situation,
task, action and results.
5:39
Check out the teachers notes for
more on the star method.
5:45
I realized this is a lot of information
that is why you wanna focus on being
5:48
concise and delivering that
information at a high level.
5:53
Try to focus on that big picture delivery.
5:58
If folks want more information,
they'll ask questions.
6:01
Here is some further recommendations and
tips for portfolio review.
6:07
[SOUND] Show artifacts from your project.
6:11
Make sure to provide visuals so
they can see the end product.
6:15
[SOUND] Give concise insights.
6:19
As I mentioned before, you don't wanna
get too caught up in the details.
6:23
With the information you share,
you wanna show them your thought process,
6:27
how you prepared the approach
you took in the results.
6:31
Don't talk through the minute
by minute process.
6:35
[SOUND] Share what you learned
from contributions and
6:38
how you learned from that.
6:42
If you're new to tech and
don't have many projects to show,
6:46
don't let that deter you.
6:49
If you don't have many examples to pull
from focus on showing your best work.
6:51
Keep in mind it doesn't have
to be paid work to count.
6:56
You can include side projects you
did as part of your learning or
6:59
something you voluntarily built to help
a friend or nonprofit organization.
7:03
[SOUND] The last option you might
find yourself doing in a technical
7:08
interview is a take home exercise.
7:13
A take home exercise involves being given
a work sample where you are asked to
7:15
complete an assignment.
7:19
This assignment could be related
to the company or random.
7:21
For example, they might ask you
to design a landing page for
7:25
meal delivery company even though
the company you're interviewing for
7:28
does something completely different.
7:32
You'll be given a due date and will have
to complete this on your own time.
7:36
Some companies will pay you for
your time to complete the assignment.
7:41
Let that be an indicator to you
about the type of company they are.
7:45
Ideally, you'd be paid for your work
as well as be given a flexible and
7:49
realistic due date.
7:53
Remember, just as much as
they're interviewing you,
7:55
you're interviewing them.
7:58
A company that pays for you to complete an
exercise shows how they value your time.
8:00
Another bonus of a take home exercise,
8:06
as pointed out by Tracy Philips in their
post, the pursuit of the well-designed
8:09
take-home coding assignment on Medium,
is it promotes equity.
8:13
Phillips shares, because they take place
in the comfort of a candidate's home or
8:18
wherever they prefer to work,
and not in your office.
8:23
Take-home assignments reduce
the likelihood of intrinsic biases
8:26
playing a role in preemptively screening
out candidates before you know what they
8:29
are capable of.
8:34
The playing field is also leveled for
more introverted candidates who
8:36
may not perform their best in a live or
a face to face assessment.
8:40
As always,
check out the teacher's notes for
8:45
more information if you're
looking to dig deeper.
8:47
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