Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Pass a Whiteboard Interview
Transcript
- Lucas: It's mid-2026, and a lot of the big tech companies — Google, Meta, Stripe — are bringing back the in-person whiteboard interview. After years of shared documents and CoderPad, they want to see you think in real time, standing up, marker in hand. Luna: Which is honestly terrifying if you're a bootcamp grad who's used to typing code in an IDE with syntax highlighting and autocomplete. Lucas: Exactly. And that's the gap this episode is about: how to prepare for the whiteboard when everything you've learned has been digital. We're going to focus on a specific framework — Clarify, Plan, Execute — and I'll walk through exactly what each phase looks like. Lucas: But before we get into the details, I want to mention something. This show has always been ad-free — no sponsored segments, no product placements. We deliberately don't run ads because we want every episode to be about what's useful to you, not about selling something. Luna: And that only works if listeners who find value chip in occasionally. If we've helped you think through a career move or decision, the link is buy me a coffee dot com slash fexingo. No pressure, no perks — just a way to keep this going. Lucas: Exactly. So back to the whiteboard. The first thing to understand is that the interviewer is not grading your code. They're grading your thinking. Luna: Right — they want to see how you handle ambiguity, how you break down a problem, and whether you can communicate clearly under pressure. Lucas: Exactly. So let's start with Phase One: Clarify. Before you write a single line of code, you need to make sure you actually understand the problem. That means asking questions. Lucas: A lot of bootcamp grads I've coached want to jump straight into coding because they're nervous and they want to show they can write syntax. But that's a mistake. If you solve the wrong problem, it doesn't matter how elegant your solution is. Luna: So what kinds of questions should you ask? Give me a concrete example. Lucas: Sure. Say the interviewer asks: 'Write a function that returns the most frequently occurring character in a string.' Before you start coding, you ask: 'Is the string ASCII or Unicode? What about ties — if there's a tie, do I return any one, or all of them? Should I consider whitespace and punctuation? Is case sensitivity relevant?' Luna: Those are good. And by asking them, you're also showing the interviewer that you think about edge cases. Lucas: Exactly. Phase Two is Plan. Once you've clarified, say out loud how you intend to solve it. 'I'll use a hash map to count frequencies, then iterate to find the max. That gives me O of n time and O of k space where k is the number of distinct characters.' Lucas: This is where bootcamp grads often freeze because they're used to just typing until something works. But the interviewer wants to hear your reasoning before you write anything. Luna: And if your plan has a flaw, they might nudge you in the right direction — which is way better than writing buggy code and then trying to back out. Lucas: Right. Phase Three is Execute. Now you actually write the code on the whiteboard. And here's the thing: your handwriting doesn't have to be perfect, but the interviewer needs to be able to read what you wrote. Use clear variable names, indent properly, and keep it organized. Lucas: One trick: write small, leave space between lines so you can insert corrections. And talk as you write. 'I'm initializing an empty hash map. Now I'm looping through each character. If it's already in the map, I increment the count; otherwise, I set it to one.' Luna: That running commentary is huge. It keeps the interviewer engaged and shows them your thought process in real time. Lucas: After you've written the code, you walk through it with a sample input — a dry run. That's when you catch off-by-one errors or logic gaps. And if you find a bug, just say 'I see an issue here, let me fix it' and do it. That's totally fine. Luna: What about data structures? Bootcamp grads often say they haven't practiced things like trees or graphs. Lucas: Great question. For a typical whiteboard interview at a company like Google, you need to be solid on arrays, strings, hash maps, and linked lists. Trees and graphs show up, but more often in senior roles. If you're a bootcamp grad going for entry-level or mid-level, focus on the basics and know the common patterns — two pointers, sliding window, recursion. Lucas: And practice on an actual whiteboard. Not on a laptop. Go to a classroom, buy a portable whiteboard, or use a window with a dry-erase marker. The physical difference matters. Luna: I've heard that some people record themselves solving problems on a whiteboard and then watch the video to see how they look. Does that help? Lucas: It's incredibly useful. You notice things like talking too fast, mumbling, or standing in front of the board blocking the interviewer's view. Small non-verbal things can actually affect your score. Luna: Do you have a sense of what percentage of bootcamp grads actually pass whiteboard interviews on the first try? Lucas: Industry data from 2025 and early 2026 suggests about 30 to 35 percent pass on the first attempt at a major tech company. But after three or four attempts, that number jumps to over 60 percent. So persistence matters. Luna: So it's not about being a genius — it's about learning the format and getting comfortable with the pressure. Lucas: Exactly. And I'll add one more thing: if you blank out completely, it's okay to say 'I'm a little nervous, give me a moment.' Interviewers are human. They'd rather see you regroup than spiral. Lucas: Let's do a quick example walk-through. Say the problem is: 'Given an array of integers, return the two numbers that add up to a target.' You'd start with Clarify: 'Is the array sorted? Can I use the same element twice? What should I return if there are multiple pairs?' Luna: Classic two-sum. The classic plan is to use a hash map for O of n time. Lucas: Right. So you say: 'I'll iterate once, storing each number and its index in a hash map. For each element, I check if target minus current is already in the map. If yes, I return the pair.' Then you write it. Then you dry run with and target 9. Index 0: 2, not in map, store it. Index 1: 7, map has 2? No. Wait — sorry, I'm rushing. Let me be precise. Luna: No, that's actually perfect — you just demonstrated what it looks like when you slow down and correct yourself. Lucas: Exactly. And that's the kind of thing that impresses interviewers. They're not looking for perfection; they're looking for someone who can work through a problem methodically. Lucas: So to wrap up: Remember the three phases — Clarify, Plan, Execute. Practice on a real whiteboard. Talk through everything. And don't be afraid to ask for a moment if you need it. Luna: And keep applying. The first attempt is just data. The second and third are where you really learn. Lucas: Exactly. If you have a whiteboard interview coming up, try the framework and let us know how it goes. We'll be back next episode with another angle on navigating your career change.