Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Transition Into Startup Operations
Transcript
- Lucas: So there is a path that I think gets overlooked by a lot of bootcamp grads, and it is not engineering, it is not product, it is not data science. It is operations at a startup. Luna: You mean like COO track? Or more of a generalist ops manager role? Lucas: Both, honestly, but I want to start with a specific person I came across. Sarah Chen — she graduated from a full-stack bootcamp in early 2025. She had a background in retail management, eight years at a regional grocery chain, overseeing inventory and staff scheduling. She did the bootcamp thinking she wanted to be a backend engineer. But after about six months of applying, she realized she actually liked building systems for people, not just APIs. Luna: And she made the pivot into operations? Lucas: Yeah. She joined a twelve-person SaaS company that makes billing software for small law firms. They didn't have a dedicated ops person. The founders were doing everything from vendor contracts to customer onboarding to payroll themselves. Sarah came in as their first operations hire — no official title at first, just 'ops and growth' — and within four months she had built three systems that saved the company about thirty hours a week collectively. Luna: Thirty hours a week is like almost one full-time employee worth of time. What were the three systems? Lucas: First, she wrote a Python script that automated their customer onboarding checklist — pulling data from their CRM, sending welcome emails, provisioning accounts. That alone cut the onboarding time from two hours per client to about fifteen minutes. Second, she built a simple vendor payment tracker in Airtable linked to their accounting software, so the founders could see at a glance which invoices were due and which were paid. Before that, they were using a shared spreadsheet and a lot of sticky notes. Luna: The sticky note ERP system — classic early-stage startup. Lucas: Exactly. And the third one was a cross-team communication dashboard that aggregated updates from Slack, their project management tool, and their support ticketing system. So the whole team could see what was happening without attending four status meetings a week. Luna: So she basically used her bootcamp coding skills to solve operational bottlenecks. That's a really interesting hybrid — she's not writing production code for the product, but she's writing code that makes the company run better. Lucas: Right. And the founders told me they hired her specifically because she had operations instincts from retail — she understood process, inventory, scheduling — and she could build tools to automate them. They didn't want an MBA who would want to 'strategize' for six months. They wanted someone who could show up on day one and make something work better by Friday. Luna: I think that's a huge insight for bootcamp grads who might feel like they don't have the traditional background. If you worked in any operational role before — retail, hospitality, logistics, even administrative work — you have concepts that translate directly. The question is how to frame it. Lucas: Exactly. And that's the core of this episode. We're going to talk about what startup operations actually looks like at the early stage, why bootcamp grads are often better fits than MBAs for those roles, and three concrete steps you can take to position yourself. Luna: Let's start with the elephant in the room — what does 'operations' even mean at a ten-person company? It's not exactly a defined job description. Lucas: It is not. At a company with fewer than thirty employees, operations usually means everything that is not building the product and not selling it directly. So that includes customer onboarding and support, vendor management, payroll and benefits administration, internal tooling and automation, data reporting for the founders, sometimes even office logistics if they have a physical space. It is a generalist role that touches every part of the business. Luna: And the key skill is being able to quickly identify a repetitive task, figure out the root cause of the inefficiency, and build or buy a solution. For a bootcamp grad, that's a perfect application of the problem-solving muscle you developed while learning to code. Lucas: A hundred percent. And I think the reason bootcamp grads can beat MBAs for these roles is that MBAs are trained to delegate and hire. Early-stage startups can't afford to hire for every function. You need someone who can personally build the first version of the process, even if it's janky, and then iterate. That is essentially the bootcamp project experience. Luna: Yeah, but a lot of bootcamp grads I talk to say they feel like their projects are too technical or too narrow to demonstrate ops skills. They built a weather app or a to-do list — how does that translate to operations? Lucas: It does not translate directly. That is the mistake. You have to reframe the project. Instead of saying 'I built a full-stack to-do app,' you say 'I designed a task management system with user authentication, deadline tracking, and data persistence — skills I could apply to building an internal vendor tracking tool or a customer onboarding workflow.' You are selling the underlying capabilities, not the app itself. Luna: And I think you can also build projects specifically for operations. Sarah did not just reframe her bootcamp projects — she built new ones. The vendor payment tracker she built in Airtable was something she created after she got the job, but she could have built a prototype beforehand and used it as a portfolio piece. Lucas: That is a great point. If you are targeting operations roles, your portfolio should include at least one project that automates a real-world business process. It does not have to be for a real company — you can simulate it. For example, build a script that pulls data from a public API, processes it, and sends a summary email. That demonstrates exactly the kind of work you will do in an ops role. Luna: And you want to be able to talk about the impact in terms of time saved or errors reduced, not just lines of code. That's something bootcamp grads sometimes miss — they focus on the technical implementation instead of the business outcome. Lucas: Totally. So let's talk about three concrete steps. Step one: identify the operational pain points in any organization you have been part of — a previous job, a volunteer group, even the bootcamp itself. Write down one process that was inefficient and how you could improve it using automation or tooling. That becomes your story. Luna: So for someone coming from retail, like Sarah, that could be the inventory ordering process or the schedule creation workflow. For someone from food service, maybe the shift handoff process. Lucas: Right. Step two: build a small prototype of that solution. It does not have to be production-ready. An Airtable base with a few automations, or a Python script that reads a CSV and outputs a report. Something you can show in an interview and say, 'This is the kind of tool I built to solve a real problem.' Luna: Step three: find startups that are at the right stage. You want companies that have between five and thirty employees and have not yet hired a dedicated ops person. How do you find those? Lucas: Look at job boards like AngelList or Work at a Startup, but filter for roles like 'operations generalist,' 'business operations,' or 'growth and operations.' Also look at LinkedIn for startups that have recently raised a seed or Series A round — they are often in the stage where they realize the founders cannot keep doing everything. Luna: And when you apply, your cover letter should explicitly connect your previous operational experience — even if it's not from tech — with your new technical skills. That combination is your differentiator. Lucas: One thing I hear from founders is that they worry bootcamp grads will be too focused on engineering and not on the human side of operations. So you need to demonstrate that you understand communication, change management, and stakeholder buy-in. Operations is as much about people as it is about systems. Luna: That's a real risk — over-engineering a solution that nobody uses because you didn't talk to the people who would use it. Sarah told me she spent her first week just shadowing the founders and asking them what annoyed them most about their weekly routine. She didn't build anything until she understood the context. Lucas: That is a perfect example of the soft skill that matters more than the hard skill in this role. And I think bootcamp grads who have worked in customer-facing or operations roles before have a leg up because they already have that instinct. They just need to combine it with the technical confidence to build the tool. Luna: You know, it's funny — we talk a lot on this show about pivoting into specific technical roles, but operations is one of those areas where a bootcamp grad can create a role for themselves that didn't exist. Sarah's title now is 'Operations Manager,' but she essentially designed the job herself. Lucas: And she is making more than she did in retail, has equity in the company, and says she finally feels like she is using her brain in a way that combines her past experience with her new skills. I think that is a really compelling path for a lot of bootcamp grads who might be struggling to break into a standard engineering role. Luna: Before we wrap, I want to mention something that makes this show possible. We do not run ads — we keep the content focused and listener-supported. A handful of people chip in a few bucks a month through buy me a coffee dot com slash fexingo, and that honestly helps us keep making episodes like this one, diving into specific career paths that might not get a lot of mainstream coverage. Lucas: Yeah, we really appreciate those of you who do that. It keeps the show independent and ad-free. And if this episode helped you think about a direction you had not considered, maybe consider joining that group. But either way, we are glad you are here. Luna: So to sum up: startup operations is a viable, often overlooked path for bootcamp grads. You bring a rare combination of operational intuition and technical building ability. Build a portfolio piece that solves a real process problem, find early-stage startups that need generalist help, and lead with your problem-solving narrative, not just your code. Lucas: And do not be afraid to reach out to founders directly on LinkedIn with a short message like, 'I noticed you are a small team. I have experience in and just learned to code. I would love to help you streamline something.' That is how Sarah got her first interview. Luna: That is great advice. Thanks, Lucas. Lucas: Thanks, Luna. And thanks to Sarah for sharing her story. Next episode, we will talk about how bootcamp grads can transition into technical recruiting — another role that blends people skills with tech understanding.