Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Break Into Sports Tech
Transcript
- Lucas: So Luna, were you glued to the Olympics last summer? Because I was, and I couldn't stop thinking about how much tech goes into every single event now. Luna: Oh absolutely. The cameras alone, the instant replays, the tracking data they flash on screen. It's a whole different world from even ten years ago. Lucas: Exactly. And that's what I want to dig into today, because for bootcamp grads, sports tech is this incredibly appealing but kind of mysterious industry. Everyone loves sports, but how do you actually break in? Luna: Right, it's not like there's a 'sports tech' major you can pick up. So what's the reality for someone with twelve weeks of coding bootcamp experience? Lucas: Well, the reality is that sports tech is a huge umbrella. It's everything from the computer vision systems that judge a tennis serve to the analytics platforms that tell a coach which player is most likely to get injured. And the skills needed are actually pretty standard tech skills. Luna: So you're saying you don't need to be a former athlete? You just need to know how to code? Lucas: Mostly, yes. The one place where domain knowledge really matters is in performance analysis, because you're working with coaches and athletes who speak in terms of sprints and loads. But for the broader tech stack, it's just software engineering with a sports context. Take Hawk-Eye, the system that calls line calls in tennis and cricket. That's classic computer vision, object tracking, and real-time data processing, nothing that a bootcamp grad couldn't learn. Luna: Okay, but those are big, established companies. What about the smaller startups? Is there a path there? Lucas: That's actually where most of the entry-level jobs are. Think of companies like Catapult, which makes wearable GPS trackers for athletes, or Strava, the fitness app. These places need people who can build dashboards, manage databases, write APIs. And they're often more open to bootcamp grads than the old-school tech giants. Luna: Wait, I thought everyone wanted to work for the big names. Why would a startup be more willing to take a chance on someone with a bootcamp credential? Lucas: Because they need people who can ship code fast. A bootcamp grad has spent twelve weeks doing nothing but building projects, often with modern tools like React or Python. That's more useful to a startup than someone with a four-year CS degree who's never actually deployed anything. Luna: Huh, that makes sense. So what's the typical job title? Is it always 'software engineer' or are there other entry points? Lucas: You see a lot of titles like 'data analyst', 'product engineer', 'application developer'. And there's also the whole fan-facing side, building the apps that let you buy tickets or track your fantasy team. Those are basically e-commerce and mobile development gigs, just with a sports flavor. Luna: So if I'm a bootcamp grad listening right now, what's the first step? Do I need to go learn computer vision or something? Lucas: No, don't overcomplicate it. Start with the fundamentals you already have. If you did a web dev bootcamp, build a sports-themed project. Use a public API like the one from the NBA or FIFA, and create a dashboard that shows player stats. Or if you're into data, scrape some data from a sports site and do some analysis. Lucas: Exactly. And here's a concrete example. I remember reading about a guy who got hired by a Major League Baseball team just because he'd built a tool that predicted pitch outcomes from public play-by-play data. He wasn't a data scientist; he'd done a bootcamp and just loved baseball. That project made him stand out from a hundred other applicants. Luna: That's such a good story. And it makes the whole thing feel doable. But let's talk about the other side: what are the actual challenges? Lucas: One of the big ones is the seasonality. Sports tech companies often have all their big launches around the start of a season, so hiring can be bursty. You might see a wave of job postings in July and August, then nothing for months. That can be frustrating if you're job hunting in February. Luna: So you're saying you've got to time your search? That's tricky for someone who's just finished a bootcamp whenever they finish. Lucas: Yeah, it's not ideal, but it's a reality. And another challenge is that sports tech is often geographically concentrated. You've got clusters in places like Seattle, Boston, and London. Remote work is opening things up, but for in-person roles, you might need to relocate. Luna: But is the salary competitive? I mean, sports is a passion, but we've all got bills to pay. Lucas: Actually, on average, sports tech salaries are pretty comparable to general tech. A junior data analyst might start around $70,000, and a software engineer can easily hit six figures within a couple of years. The passion component isn't just a trade-off; it's often a bonus on top of a solid market rate. Luna: Okay, that's reassuring. Now, I've got to ask the practical question: how do you actually find these jobs? Is it just LinkedIn or are there specific places you should look? Lucas: There are a few niche job boards, like Work in Sports, but a lot of it is still networking. And I don't mean sending cold messages to a CTO. I mean going to meetups, hackathons, and even local sports tech events. Bootcamp grads have a big advantage here because they're used to working on teams and presenting projects. That translates into networking. Luna: That's a good point. And it ties back to something we've said before: your bootcamp cohort can be your first network. Some of them might already work in tech, and if they know you're into sports, they might pass along a lead. Lucas: Absolutely. And I want to bring up something else that's specific to sports: the data is often public and rich. Sports stats are like candy for an aspiring data engineer. You can practice your skills on real data sets without any NDAs. That's not true in, say, fintech where everything is locked down. Luna: Yeah, and it keeps the show free and ad-free for everyone. But back to the tech, Lucas, you mentioned data. Are there any other specific skills that you see in job postings all the time? Lucas: Definitely. For data roles, you'll see a lot of SQL and Python. For front-end roles, React and some mobile dev like Flutter or Swift. And for the more niche stuff like computer vision, you'll see OpenCV or TensorFlow, but those are usually for more senior roles. For a bootcamp grad, I'd say focus on the foundation: SQL, Python, and a framework. Luna: And what about certifications? Are there any that specifically help in sports tech? Lucas: Not really, and I'd be wary of any sports tech specific certificate that a random company is selling. What matters more is showing you can apply your skills to sports problems. So instead of paying for a certificate, contribute to an open-source project or build your own tool. Luna: That makes sense. So, if I'm a bootcamp grad, what's the biggest mistake I could make when trying to break into sports tech? Lucas: I think it's assuming you have to be a huge sports fan to get in the door. You don't. You just need to be genuinely interested in the problems. And if you love sports, great, but don't fake it. Recruiters can tell when you're just trying to sound enthusiastic about a team you don't actually follow. Luna: Ha, true. So, is there like a 'right' time to start applying? Like, should you wait until you've built a really polished portfolio or just go for it? Lucas: Go for it early and often. Even if your first project is rough, applying and getting feedback is the fastest way to improve. And remember, a lot of people never apply because they feel they're not ready. Just by submitting, you're already ahead of the curve. Luna: That's encouraging. And I've got to ask, what's the actual day-to-day like? Is it all coding in a dark room or do you get to be around athletes? Lucas: It depends. If you're on the product team, you might be doing user testing with coaches, which can be pretty cool. But if you're on the data infrastructure side, you're mostly in front of a screen. The glamour of being on the sidelines is rare for engineers. That's more for the camera operators and the data scientists who get to travel with the team. Luna: So it's not all glitz, but it's still a cool industry to be in. I think we've got a really clear picture here. Do you have any final advice for someone who's listening and thinking, 'Yeah, I could do this'? Lucas: My advice is simple: pick one sport, find a real problem, and build something that solves it. It doesn't need to be perfect. It just needs to show you're curious, resourceful, and willing to learn. That's exactly what sports tech companies are looking for. Luna: And if you're nodding along, go check out the job boards today. The next season is coming up, and there might be a spot with your name on it. Lucas: Absolutely. Thanks for joining us, everyone. We'll be back next week with another episode, and until then, keep coding and keep watching the game.