What Hailey Van Lith Taught Me About Surviving Big Tech

A junior engineer on my team asked me what I thought about the noise around Hailey Van Lith. He’s a big college basketball fan and saw the transfer from Louisville to LSU, the struggle, and the next move to TCU. My first thought wasn't about basketball. It was about that time I left a comfortable senior role at a hot startup to join Amazon. The parallels between what happened to Hailey and what happens to countless engineers who make the "big leap" are impossible to ignore. Her journey is a masterclass in career strategy, ego management, and knowing when to pivot.

Turns out, you can learn a lot about navigating a FAANG interview loop and career path from a point guard.

The Superteam Ego Trap

At Louisville, Van Lith was the system. The offense ran through her, she took the big shots, and her brand was synonymous with the team's success. This is like being the lead engineer at a 200-person company. You know the whole stack, you probably wrote the original authentication service, and when the site goes down, you're the first person they call. Your impact is visible. You feel essential.

Then she went to LSU—a team already loaded with stars like Angel Reese. She joined a "superteam." This is the exact feeling of walking onto the Google or Meta campus for the first time. You were a star, but now you're on a team with ten other people who were also stars at their old jobs. The person sitting next to you might have written a popular open-source library you use. The architect down the hall literally wrote the book on distributed systems.

Suddenly, your scope shrinks from "the entire backend" to "this one specific API endpoint in the Ads Manager service." Your first project isn't a massive greenfield build; it's a six-month slog to migrate a legacy feature from one internal framework to another, a project with zero external visibility. The ego blow is brutal. You go from being the go-to expert to feeling like an imposter who has to ask where to find the team's runbooks. Surviving this requires you to redefine "impact" from "I built it all" to "I made this one complex thing 2% more efficient, saving the company millions in compute costs."

It's a huge mental shift.

Your Role Just Changed. Adapt or Drown.

The biggest issue for Van Lith at LSU wasn't just the other talent; it was the role change. She was forced to play more of a traditional point guard, a facilitator role she wasn't as comfortable in. She's a natural scorer, but the team needed something else.

This happens constantly in tech. You get hired as a backend Python expert, but three months in, a re-org happens. Your new manager comes to you and says, "The team's highest priority is the new dashboard. We need you to pick up React and TypeScript. Here's a link to the docs." You have two choices. You can complain that it's not what you were hired for, silently struggle, and watch your performance reviews tank. Or, you can swallow your pride, tell your manager you'll need some ramp-up time, and spend the next two weeks glued to tutorials.

The best engineers I know are adaptable. They see a role change not as a threat, but as a paid opportunity to learn a new skill. When you're in an interview and they ask, "Tell me about a time you had to learn something quickly," this is the story you tell. Don't talk about that fun side project; talk about the time your team's survival depended on you learning Go in a month to fix a critical microservice, and you did it. That's what hiring managers want to hear.

Knowing When the Pivot Is Smarter Than Prestige

After one season, Van Lith left the LSU superteam for TCU. The public narrative was loud: she "failed," she "couldn't handle the pressure." I see it differently. I see a professional who recognized a bad fit. The role and the system weren't maximizing her strengths, so she made a strategic decision to move to a place where she could be the focal point again. She traded the prestige of a national title contender for the opportunity to do her best work.

This is the hardest decision an engineer will make. You might be two years into a job at Apple, with the golden handcuffs of RSUs vesting, but you're stuck on a project you hate with a manager who doesn't support you. Your skills are getting stale. Every day is a grind. The "prestige" of your email signature is the only thing keeping you there.

Leaving is terrifying. But staying in a bad-fit role for years just for the brand name on your resume is career suicide. Here's the caveat: this isn't a license to job-hop every 11 months. If you're running away from every challenge, that's a you problem. But if you've given it an honest try—say, 18-24 months—and you've tried to switch teams, talked to your manager, and the situation is still untenable, a pivot is a strategic move, not a failure. It shows you have self-awareness and are optimizing for your long-term growth, not short-term status.

Your Brand Is Built Under Pressure

Hailey Van Lith has a fiery, intense public persona. She plays with a chip on her shoulder. Whether you like it or not, it's her brand. That brand gets tested under the media microscope, especially when the team is losing or she's in a slump.

Your professional brand as an engineer isn't your carefully curated LinkedIn profile. It’s forged in the crucible of a production outage at 3 AM. It’s defined by how you respond to a blunt comment on your pull request. Do you get defensive and start a flame war in the comments? Or do you take a breath, write "Good catch, I'll update the logic," and move on? Your brand is the sum of how you act when things are hard.

When I'm interviewing a candidate for a senior role, I don't just care if they can solve a LeetCode hard. I want to know how they handle disagreement. I'll often push back on their system design proposal: "What if that database fails? Your proposal has a single point of failure." A junior person gets flustered. A good senior candidate lights up. They see it as a collaborative exercise. "Great point. We could introduce a read replica for failover, or maybe a caching layer like Redis to reduce DB load and provide some resilience."

They don't see criticism of the idea as criticism of them. They see pressure as a chance to show their work. That’s the brand that gets you promoted.

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