Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About a Time You Scaled a Process Question
Transcript
- Lucas: If you've been interviewing recently — especially for roles in operations, product, or any growth-stage company — you've probably heard some version of this question: 'Tell me about a time you scaled a process.' It's a question that more and more hiring managers are using to test whether you can think beyond your day-to-day tasks. Luna: I've seen that too. It's like the new 'tell me about a time you led a project' — but it feels harder to answer because scaling is usually a team effort. Lucas: Exactly. And that's part of what makes it tricky. When I was preparing for this episode, I found a really clean example from a logistics startup that went from handling about 200 shipments a day to over 2,000 in less than six months. The person who owned that transition was a mid-level operations manager, not a VP. Luna: So it's relatable. You don't have to be a director to have a scaling story. Lucas: Right. And that's the first thing to recognize — this question is looking for evidence that you can take something that works at a small scale and systematically make it work at a larger one, without breaking. The bottle line is: can you build a system that lasts? Luna: I like that framing. So what's the mistake people make when they answer this? Lucas: The biggest one is describing the solution instead of the problem. People jump straight to, 'I automated the order-picking process.' The interviewer doesn't know the baseline — they don't know how bad it was before. Without that, the story has no tension. Luna: So you need a before and after. What was the bottleneck? Lucas: Exactly. In the logistics example, the bottleneck was that orders were being picked using paper lists that had to be physically handed off between shifts. When volume was 200 shipments, it was manageable. But at 400, the handoff errors started climbing. The operations manager noticed that the error rate had gone from one percent to almost four percent in just three weeks. Luna: That's a concrete number. So the baseline is clear — one percent error at 200 shipments, four percent at 400. Lucas: Right. And then the action isn't just 'I implemented a digital system.' The real action is: she documented the paper workflow, identified the shift handoff as the root cause, tested a simple shared spreadsheet with a small team for two weeks, proved that the error rate dropped back to one point five percent, and then partnered with engineering to build a lightweight mobile app. That's a scaling story. Luna: I notice she didn't build the app herself. That's important — she coordinated. So the story shows leadership without claiming to be the sole hero. Lucas: That's the second biggest mistake: exaggerating your role. Interviewers can smell when someone claims to have single-handedly scaled a system. The best scaling stories are honest about the collaboration. You might say, 'I worked with the engineering team to prioritize this, and I trained the warehouse staff on the new process.' That's credible. Luna: What about when the scaling didn't fully work? I've had listeners ask me about that. Lucas: That's a great point. You don't need a perfect success story. In fact, a partially successful scaling attempt can be even more compelling if you show what you learned. Let me give you a second example — this one from a SaaS company I spoke with. Luna: Okay, I'm listening. Lucas: A customer success manager saw that her team of five was handling 200 accounts each, but the company was about to double the customer base. She tried to scale her team's outreach by creating a library of canned email templates — but within a month, the response rate dropped by half. Customers were complaining that the messages felt generic. Luna: Ouch. So her attempt at scaling backfired. Lucas: It did. But she didn't just give up. She analyzed the data and realized that the templates worked for standard onboarding queries but failed for anything personalized. So she restructured the workflow: templates for the first two touchpoints, then a personalized call for any account that showed a specific trigger — like not logging in for 30 days. Response rates recovered, and the team could handle 300 accounts each without burning out. Luna: That's a great story because it shows adaptability. The scaling wasn't the template — it was the system that balanced automation with human touch. Lucas: Exactly. And that's the core of a good scaling answer. You want to show that you can measure, test, iterate, and ultimately build something that holds up. So here's a simple structure: start with the baseline metric, then the bottleneck, then the action you took — including who you worked with — and finally the validated result. Luna: Let's say someone is listening who doesn't have a clear scaling story. How can they find one? Lucas: Look for any time you had to handle more of something — more customers, more data, more tasks — and the old way stopped working. Maybe you were a barista and the morning rush got so long that tickets were piling up, so you redesigned the station layout. That's scaling a process. It doesn't have to be tech. Luna: I think another angle is: scaling can also mean reducing complexity. Sometimes the bottleneck is too many steps, not too few. Lucas: That's a really good insight. I've seen a story where someone reduced a 12-step approval process to four steps by identifying which sign-offs were redundant. That's scaling by removing friction. It's still about handling more volume with fewer bottlenecks. Luna: So the formula is: metric, bottleneck, action, result. And the result doesn't have to be perfect — just honest. Lucas: Right. And if you prepare two or three of these stories, you're going to be ready for most scaling questions you'll encounter. The key is to practice them aloud so they sound natural, not like a script. Luna: Speaking of preparation — you know, we've been doing this show for a while now, and a few listeners have asked how they can support us. If you've gotten something out of these episodes — maybe a job offer, a promotion, or just a better way to think about your career — a couple of dollars a month genuinely makes a difference. You can find us at buy me a coffee dot com slash fexingo. We keep the show ad-free, and listener support is what makes that possible. Lucas: Absolutely. And we really appreciate it. Now, back to scaling — I want to talk about one more nuance. When you're answering, avoid saying 'we scaled the process.' Use 'I.' Even if it was a team effort, you need to frame your specific contribution. A good way is: 'I led the initiative to scale our customer onboarding process, working with a team of three to automate the data entry.' Luna: That's clear ownership without taking sole credit. I think that's a great place to wrap up. Next episode, we'll tackle another question that comes up a lot — 'Tell me about a time you had to deal with a difficult customer.' Lucas: I'm already thinking of a good example from my own experience. See you next time.