The job was a constant challenge. In the call center, our performance was measured with something called HT (Handling Time), an indicator of how long we took on each call. Besides answering questions, we had to profile customers to refer them to the sales department. The problem was that we used over 20 different apps to gather customer information, which made the process tedious, chaotic, and slow. Among these tools was AS-400, an outdated but essential system for the workflow. Trying to juggle so many interfaces while talking to a customer felt like piloting a plane without any training.

Frustrated by the system’s inefficiency, I came up with an idea: why not program a piece of software that could gather all the information in one platform? But there was a huge problem: the company network was closed, and only corporate apps were allowed. I couldn’t download software or access online resources. But I refused to give up. I thought of the most basic tool I had available: Notepad. There, in the simplest form, I began writing code. Line by line, I built a rudimentary app that, against all odds, actually worked.

A fun fact: throughout the process of creating the app, I always had the permission of my team leaders to keep developing it, as they understood I was looking for a solution to speed up our workflow and improve efficiency. However, when the management team found out I’d created this tool without going through their official channels, they decided to suspend all my leaders for three days, which was a tense moment but also a key lesson about how innovation can be viewed in very different ways.

After testing my app during my calls, I realized how useful it was. It drastically reduced the time spent searching for information and made the profiling process much quicker. So, I decided to share it with my coworkers. At first, just a few of them started using it, but soon it became an essential tool. It wasn’t long before the entire team was using it. Then, other teams on different floors began adopting it. Suddenly, my little app, built in a simple Notepad, was helping hundreds of agents work better and faster. The feeling of having created something so useful was incredible. I felt proud and convinced I had found my true calling in programming.

But then, everything came crashing down.

The company reviewed one of my calls and discovered I was using software they didn’t know about. Instead of acknowledging my effort to optimize the workflow, they assumed the worst: they thought I was stealing banking information. I was called into an emergency meeting, and in the blink of an eye, I went from being an efficient employee to being under legal investigation. I was suspended for 30 working days while they conducted a full audit. Lawyers interrogated me, asked endless questions, and I had to prove that my app wasn’t doing anything illegal. It wasn’t stealing data, it wasn’t compromising the security of the system, it was just improving efficiency. In the end, they confirmed my software posed no risk, but still decided not to renew my contract.

It was a crushing blow. Instead of recognizing my potential and transferring me to an area where my skills could be more useful, they punished me for innovating. I felt devastated, but I knew I couldn’t let this define my future.

Shortly after, I saw a job opening for a frontend web design and development role. During the interview, I decided to share my story. I explained how I had identified a problem, found a solution, and built a tool to optimize the workflow. My future boss was so impressed that he called my previous company to verify the facts. When they confirmed what had happened, he decided to give me the opportunity I had been waiting for.

Another fun fact: in my second job, I had to work on two projects for Bancolombia. In one of those projects, one of the people who had been hired by the company that was developing the software for them remembered my story. I was surprised that they still remembered what had happened in my previous job, and when they found out I was working there, they were really impressed by how a seemingly small obstacle had eventually led me to where I was.

From this experience, I learned that we should always strive to improve and be the best at what we do, even if others don’t notice or appreciate it. My advice for anyone looking for their first opportunity in tech is: never underestimate the value of what you do. What seems like a disaster today may be the key that opens the door to your dreams tomorrow.

If you’ve ever been through a similar situation, let me know in the comments. I’d love to hear how you turned an obstacle into an opportunity!