After Nearly Five Years, I Left My Job

Reflecting on my time there and why I pursued a new opportunity

Mike Wolfe

--

Photo by Marten Bjork on Unsplash

In September of 2016, I walked through the doors of my now previous employer for the first time. It was a pretty big moment because it was my first foray into the world of software development. Little did I know that it would take me on a journey across multiple teams and promotions. Working on both large and small projects as well as doing support on legacy applications. Then ultimately, deciding that it was time to move on to new opportunities.

Early Success

Software Developer Intern was my new title on that first day. Fortunately for me, this didn’t involve having to get the other developers coffee every time they ran out. However, I still had to deal with plenty of nerves about doing a good job and constantly thinking that they were going to fire me at any moment. To my astonishment, about six months later they hired me on as a Programmer and eventually, I was promoted to a Software Developer I. In my post Beginnings in IT, I explain in further detail the kickoff of my career and these two roles.

Switching Teams

As a Software Developer I, I was working with an awesome team and gaining experience on a wide range of technologies such as APIs, API Clients, SSRS reports, scheduled tasks, and much more. Everything was going great, but I started getting the urge to want to do something different for some reason. Some of this might be because I had already been with this company for over three years (usually developers stay with a company for three to five years), while some of it might have been attributed to meeting my significant other and wanting to diversify. My urge was soon satisfied, though not exactly what I had in mind because a position on another team opened up and I dashed at the opportunity.

A New Team

After a couple of transition weeks, I was able to join my new colleagues. Unlike my previous team, this one had a lot more work to be done. This is not always a good thing, because it can lead to developer burnout or the big problem this team faced high turnover. At the end of the day though, I knew exactly what I was getting myself into because I wanted some…

--

--