What Jared McCain Can Teach You About Nailing Your Next Interview

I was watching a Duke basketball game the other night, and it hit me. The way the freshman guard Jared McCain approaches the game is a blueprint for how to build a standout engineering career. It’s not about some secret algorithm or a magic bullet. Watching McCain dissect a defense, you see the same fundamentals that separate the engineers who get offers from Meta and Google from those who just collect rejection emails.

This isn't about sports. It’s about recognizing a pattern of high performance.

The Myth of the One-Trick Pony

Recruiters and junior devs love talking about the "10x engineer." It's a myth. The real value isn't in someone who can write esoteric C++ templates in their sleep but can't explain an API contract to a product manager. The real value is in versatility. Jared McCain isn't just a shooter. He defends, he passes, he brings energy. He has a complete game.

In engineering, we call this being "T-shaped." You need a deep specialty—your vertical bar of the "T"—like backend services in Go or building scalable data pipelines with Spark. That’s your core competency. But you also need the horizontal bar: a solid understanding of the adjacent domains. If you’re a backend engineer, you need to know how React state management works, you should be able to read a Terraform script, and you must understand what your SRE team cares about.

You don't need to be an expert in everything. Nobody is. But if you can't have an intelligent conversation about how your API will be consumed by the frontend or the cost implications of your database choice, you're a liability. You're a one-trick pony in a game that demands flexibility.

That’s how you fail the system design round.

Your Public Work Is Your Highlight Reel

McCain is famous on TikTok. It’s easy to dismiss, but it’s a masterclass in building a personal brand. He's showing his personality and his work ethic (all those shooting videos) to the world. He's not just a stat line on a piece of paper; he's a known quantity.

Your GitHub is your highlight reel. Your blog is your post-game interview. When I'm on a hiring committee and we're down to two equal candidates, I look for these tie-breakers. One candidate has a vanilla resume. The other has a GitHub profile with a pinned project—maybe a small CLI tool they built in Rust to solve a personal problem, with a decent README and a few commits.

Who do you think I'm going to advocate for?

It shows passion. It proves you can document your work. It demonstrates that you think about code outside of a 9-to-5 ticket queue. You don't need to contribute to the Linux kernel. Just build something. Anything. A simple REST API for a personal project, a script that automates a tedious task, or even just thoughtful forks of other repos with your own notes. It’s a signal that you actually care about the craft.

Performing Under Pressure

The biggest stage isn't so different from a final round interview loop at Amazon. The pressure is immense, the clock is ticking, and everyone is watching. McCain hitting a clutch three-pointer with a defender in his face is the same mental fortitude you need when an interviewer gives you a vague system design prompt like "design a news feed" and just stares at you.

Panic is the enemy. You freeze, start spouting buzzwords, and draw a bunch of meaningless boxes on the whiteboard.

The pros practice for these moments. McCain doesn't just show up and hope he's feeling it. He's spent thousands of hours in an empty gym. Your empty gym is LeetCode, but not just grinding problems. It’s practicing the performance. Set a 45-minute timer. Talk through your solution out loud, to a rubber duck if you have to. Start with the brute-force approach, then explain the trade-offs as you optimize. This is the routine. This is the muscle memory you build so you don’t choke under the lights.

This is the only thing that works. You can’t read a book and expect to perform. You have to do the reps.

Code Reviews Are Your Film Room

A freshman player's biggest growth comes from the film room, where a coach breaks down every mistake. Your film room is the code review. It's where you get direct, sometimes blunt, feedback on your work from senior engineers. Too many engineers get defensive. They see a comment on their pull request as a personal attack.

That ego will kill your career.

A good senior's comment—"This function is doing too much, split it into a validator and a processor"—is a gift. It's free coaching. It's the same as a coach telling McCain his footwork was sloppy on a closeout. You absorb it, you thank them, and you fix it. You get better. The goal isn't just to get your PR merged; it's to write code that doesn't need those comments next time.

Now, here's the caveat: not all feedback is good feedback. You'll occasionally get a comment rooted in personal preference or a misunderstanding of the requirements. Part of becoming a senior engineer is developing the judgment to know when to push back respectfully with data and when to just make the change and move on. It’s a skill you build by paying close attention, but your default mode, especially early on, should be humility. Assume you have something to learn. Because you probably do.

Ready to Ace Your Next Interview?

Practice with AI-powered mock interviews tailored to your target role and company. Start Practicing for Free | Explore Interview Prep