Interns Don't Fetch Coffee Here

How we went from fearing mistakes to finding our voice in a team that actually listens.

That line sounded bold when we first heard it. At the time, we did not fully understand what it meant, or if we were even reading it right. We understood it properly only after being put on an actual project and realising very quickly that we were not here to watch things happen. We were expected to understand what we were building and why it mattered.

At the start, we thought execution would be the hardest part, and that everything else would fall into place. Doing the task right and shipping it on time. But it became obvious that none of that mattered if we did not understand the business requirements behind the work assigned. Without that clarity, even good work could end up solving the wrong problem.

We spent more time than we should have trying to figure things out quietly on our own, mostly because asking felt awkward. Going back through messages, rereading threads, guessing what was expected instead of asking directly. Eventually we learnt to stop doing that, mostly because it was slowing everything down. If we were stuck for more than thirty minutes, we asked. Most of the time the answer was simple and saved us hours of wrong work.

As we got more comfortable, we started speaking up when something did not make sense or when we thought there was a better way to do it. Not every idea landed, but a few of them fixed things that had been broken for a while. That was the moment we stopped feeling like we were just helping and started feeling like we actually belonged here, even if we were still figuring things out.

We messed up properly, not hypothetically but in ways that actually affected the work. What surprised us was how quickly things got sorted once it stopped being about who caused it and more about fixing it together. No panic, no blame game, just sorting stuff down one by one as a team and moving on with it.

That is when the title finally made sense to us.