1 00:00:00,650 --> 00:00:04,920 A portion of the interview process may include whiteboarding. 2 00:00:04,920 --> 00:00:08,900 The purpose of having a candidate whiteboard is to gain an understanding of 3 00:00:08,900 --> 00:00:12,050 their communication and problem-solving skills. 4 00:00:15,030 --> 00:00:16,990 Whether you're a seasoned pro or 5 00:00:16,990 --> 00:00:21,400 new to the field you might be asked to whiteboard during interview. 6 00:00:21,400 --> 00:00:25,350 It doesn't matter your level, it just depends on if the company chooses to 7 00:00:25,350 --> 00:00:30,230 use this method and at what point in the interview they want to observe this. 8 00:00:30,230 --> 00:00:34,510 This typically involves a whiteboard and a marker, the interviewer or 9 00:00:34,510 --> 00:00:36,680 interviewers and no computer. 10 00:00:38,530 --> 00:00:42,700 Just the idea of white boarding is a bit intimidating. 11 00:00:42,700 --> 00:00:46,440 As you learn more about it and practice, it'll be simple for you to do. 12 00:00:47,830 --> 00:00:51,000 Here's the basic rundown of what whiteboarding will look like. 13 00:00:52,020 --> 00:00:56,620 First, the interviewer or interviewers will give you a problem that they want you 14 00:00:56,620 --> 00:01:00,840 to find a solution for by writing out your code on a whiteboard. 15 00:01:00,840 --> 00:01:05,600 The interviewer will observe how you process the task, ask questions and 16 00:01:05,600 --> 00:01:07,840 answer questions you might have. 17 00:01:07,840 --> 00:01:13,370 The purpose is so they can visually see how you think and process a problem. 18 00:01:13,370 --> 00:01:17,910 This is a very simple breakdown of what the whiteboard interview will look like. 19 00:01:17,910 --> 00:01:21,960 What's most important is how you handle that time you have to tackle the problem 20 00:01:21,960 --> 00:01:23,790 the interviewer gave you. 21 00:01:23,790 --> 00:01:27,063 So let's discuss some tips and then jump into some examples. 22 00:01:30,768 --> 00:01:35,540 It's important in every stage of this to write out everything on the board. 23 00:01:35,540 --> 00:01:40,030 The purpose is so they can visually see what you're thinking in your brain. 24 00:01:40,030 --> 00:01:44,130 Write down details from the prompt they give you to help you remember or 25 00:01:44,130 --> 00:01:46,620 any notes that will be helpful for you. 26 00:01:46,620 --> 00:01:49,380 You want to show them what you're considering, 27 00:01:49,380 --> 00:01:53,330 what code you're trying, what you've ruled out, and so on. 28 00:01:55,300 --> 00:01:58,920 Always make sure you have clarity on what you're being asked to solve. 29 00:02:00,210 --> 00:02:02,065 It's okay to ask questions. 30 00:02:02,065 --> 00:02:04,432 When you were given the problem or prompt, 31 00:02:04,432 --> 00:02:08,923 you may have some clarification questions such as, who is the target audience? 32 00:02:08,923 --> 00:02:11,475 Or is your data pre sorted? 33 00:02:11,475 --> 00:02:13,940 Or do you need to address that? 34 00:02:13,940 --> 00:02:17,990 Don't be afraid to ask them, it shows your attention to detail and 35 00:02:17,990 --> 00:02:21,020 gives you an understanding of the parameters you're working in. 36 00:02:22,820 --> 00:02:24,430 Articulate your thought process. 37 00:02:25,660 --> 00:02:28,780 It's okay to use pseudocode to get started. 38 00:02:28,780 --> 00:02:31,430 Make sure to leave room to write your code. 39 00:02:31,430 --> 00:02:35,220 If that will help you get organized and get the lay of the land, do it. 40 00:02:36,900 --> 00:02:41,050 Talk through your solution as you're coding. 41 00:02:41,050 --> 00:02:43,870 Don't worry about having perfect syntax. 42 00:02:43,870 --> 00:02:48,580 But you should use best practices and good naming conventions when possible. 43 00:02:49,580 --> 00:02:52,630 This might be difficult if you're an internal thinker, but 44 00:02:52,630 --> 00:02:56,910 try to talk throughout the entire process, so they hear what you're thinking. 45 00:02:59,060 --> 00:03:04,100 Make sure to test your code with as many edge cases as possible to identify errors 46 00:03:04,100 --> 00:03:05,780 in your logic. 47 00:03:05,780 --> 00:03:09,220 Do not wait until the end to begin testing what you created. 48 00:03:11,810 --> 00:03:13,850 Don't ask for acceptance. 49 00:03:13,850 --> 00:03:17,610 Refrain from asking, does this meet what you're looking for? 50 00:03:17,610 --> 00:03:19,790 Or does this look okay? 51 00:03:19,790 --> 00:03:22,298 And, does this seem right? 52 00:03:22,298 --> 00:03:26,050 You never wanna seem like you're doubting yourself or don't know what you're doing. 53 00:03:28,030 --> 00:03:31,590 If you make a mistake, it's okay to correct your errors. 54 00:03:31,590 --> 00:03:37,200 Identify what isn't working, and what you think you can do to overcome these issues. 55 00:03:37,200 --> 00:03:41,016 This does not mean you messed up your whiteboard interview whatsoever. 56 00:03:41,016 --> 00:03:45,583 It shows you're able to check your work, own mistakes and fix them, 57 00:03:45,583 --> 00:03:47,411 which is a strong quality. 58 00:03:50,317 --> 00:03:54,993 Once you have a working solution, identify ways to make it more efficient or 59 00:03:54,993 --> 00:03:56,840 ways to improve. 60 00:03:56,840 --> 00:04:01,210 This allow the interviewer to see how you're able to take a step back, and 61 00:04:01,210 --> 00:04:05,570 see what the others option are to make a product or design better. 62 00:04:05,570 --> 00:04:09,410 Also it allows you to take a moment to look at what you've done, 63 00:04:09,410 --> 00:04:11,100 to catch something you might have missed. 64 00:04:13,250 --> 00:04:15,650 Don't solve the problem right away. 65 00:04:15,650 --> 00:04:18,379 Even if you think you know the best solution, or 66 00:04:18,379 --> 00:04:23,021 you've worked a similar problem before, you will miss out on information by not 67 00:04:23,021 --> 00:04:26,859 asking clarifying questions or seeking alternative solutions. 68 00:04:29,407 --> 00:04:34,710 State your assumptions, because this is a random prompt you've been tasked with. 69 00:04:34,710 --> 00:04:37,820 You're not going to know the technical or time constraints. 70 00:04:37,820 --> 00:04:42,420 So you might tell them some assumptions you're making to arrive at a solution. 71 00:04:42,420 --> 00:04:47,590 For example, you might say, I'm assuming there is a stable internet connection. 72 00:04:47,590 --> 00:04:51,250 Or I'm assuming we collaborated with marketing to research 73 00:04:51,250 --> 00:04:53,290 the demographic needs. 74 00:04:53,290 --> 00:04:55,840 It shows your ability to make considerations for 75 00:04:55,840 --> 00:04:57,770 other folks who might be involved. 76 00:04:59,980 --> 00:05:02,090 Start over only if you need to. 77 00:05:03,260 --> 00:05:08,180 Maybe you feel like you made a mistake and want to erase and begin at the beginning. 78 00:05:08,180 --> 00:05:12,360 If you find that you've gotten yourself to the point that you're going the wrong way, 79 00:05:12,360 --> 00:05:14,960 start over in another area of the whiteboard, 80 00:05:14,960 --> 00:05:18,650 if there's room before fully erasing everything. 81 00:05:18,650 --> 00:05:21,920 This will allow you to look back on what you've done so far and 82 00:05:21,920 --> 00:05:24,590 borrow from your previous logic. 83 00:05:24,590 --> 00:05:27,558 Make sure to articulate what you're thinking to the audience, so 84 00:05:27,558 --> 00:05:29,360 they are following what you're doing. 85 00:05:31,583 --> 00:05:34,053 Whiteboard interviews are typically timed, 86 00:05:34,053 --> 00:05:37,540 which I know makes it all the more nerve wracking. 87 00:05:37,540 --> 00:05:40,688 Asking for a time check so you can properly budget your time, 88 00:05:40,688 --> 00:05:42,796 shows off your time management skills. 89 00:05:44,832 --> 00:05:47,480 Make sure to answer questions. 90 00:05:47,480 --> 00:05:49,280 Throughout your whiteboard interview, 91 00:05:49,280 --> 00:05:53,750 the interviewer may ask you questions regarding why you make certain choices. 92 00:05:53,750 --> 00:05:57,320 You're not being asked questions because you're doing something wrong. 93 00:05:57,320 --> 00:06:00,190 They're interested to understand how you think, 94 00:06:00,190 --> 00:06:03,080 what you know, how you address a problem, etc.