My career in IT actually started on a fairly common path: software development. Early on, I worked with web technologies such as PHP, frameworks like Laravel and CodeIgniter, and MySQL databases to build and maintain internal company systems. Beyond writing code, a big part of the job was maintaining existing applications, fixing bugs, and adjusting features to support the operational needs of different teams inside the company.

Over time, my role gradually expanded beyond pure development. Because I was working in a relatively small IT team, I also became involved in various operational tasks such as troubleshooting user devices, administering Windows servers, managing Microsoft 365 accounts, and maintaining internal network infrastructure. In many companies, especially those with smaller teams, this kind of overlap happens naturally IT professionals often need to ensure that systems keep running smoothly on a day-to-day basis.

Through these experiences, I started realizing that my interest was not limited to application development. I became increasingly interested in IT operations and infrastructure, particularly the behind-the-scenes work required to keep systems stable and reliable. This includes tasks such as server management, LAN/WAN troubleshooting, and making sure employees can work without technical disruptions.

Along the way, I also began developing additional skills that support operational IT work. I spent time learning Windows Server administration, Microsoft 365 user and email management, firewall and VPN configuration, and IT asset management. I also used basic scripting to automate small but repetitive operational tasks, such as database backups and internal system maintenance.

In some projects, I had the opportunity to work on the integration between hardware systems and digital platforms. For example, I supported the implementation of an RFID-based system used for operational processes in a factory environment. Experiences like this were particularly interesting because they showed how software systems interact with physical devices and real-world operational workflows.

The longer I worked in operational environments, the more I realized that IT Operations and IT Support roles are actually quite strategic. These roles sit on the frontline whenever systems break, when users need technical help, or when infrastructure must be maintained to keep business operations running. It requires a mix of technical knowledge, troubleshooting ability, and communication skills to coordinate with different teams across the organization.

Because of that realization, I eventually decided to position my career more clearly toward IT Operations and IT Support, rather than focusing primarily on software development. For me, this was not simply a change of role, but more of a discovery of where I feel my contributions are most meaningful helping ensure that the systems people rely on every day continue to run smoothly.

Interestingly, when I look back a few years ago, the situation felt quite different. Around 2022, when my profile was still more aligned with development roles, opportunities in that area seemed relatively open. In fact, some opportunities came directly without me actively applying, and the response rate to developer profiles at that time felt quite high.

Today, however, the situation feels very different. After making a conscious decision to pivot from software development toward IT Operations and IT Support, getting interview opportunities has become significantly more difficult compared to before. The response rate to applications has dropped noticeably compared to what I experienced a few years ago.

Changes in the industry landscape, the increasing number of candidates entering the tech field, and broader economic conditions may all be contributing factors behind this shift. These dynamics make career transitions feel more challenging than I initially expected.

Despite that, the experiences I've gained over the past several years have given me valuable perspective on how the IT field operates from multiple angles from development, to infrastructure operations, to user support. All of these experiences have ultimately shaped the direction I'm pursuing in my career today.

Perhaps that's one of the most interesting aspects of working in technology: career paths are rarely linear, and often we only discover the direction we truly want after exploring different roles along the way.

One thing that has been particularly noticeable during this career pivot is the dramatic change in interview response rates. A few years ago, opportunities in development sometimes appeared even without actively applying. Today, however, the response rate from applications I send out sits at roughly a 1% interview rate a stark contrast that may also reflect how the tech job market has evolved in recent years.