Before becoming an SSP junior developer, I was working hard in college. With me, I always strived to take on large roles. Being able to see the impact of my work felt exhilarating and motivated me to work harder. It made me want to take on even more responsibilities.

I didn’t want to be just a tester, nor did I want to be just a developer. I wanted to be involved throughout the entire process. I wanted to create a solution for my clients. And I wanted to see that solution work.

During this time in college, I worked as a QA tester at a big software company. Yes big. I felt like a small piece in a huge puzzle. Moreover, sitting isolated in a cubicle all day was not my ideal work environment.

Toward the end, just like the rest of the graduating herd at CU Boulder, I applied to many jobs. Then I went to a career fair and found SSP Innovations, a smaller company. A company with flair.

As soon as I finished my on-site interview with SSP, I had a good feeling. Everyone I met had seemed motivated and exceptional at their work.

It became clear SSP cared about more than just its clients. It cared about its employees. The SSP fearless elader, Skye Perry, took time to introduce himself to me and every other candidate. Skye explained the importance of the solutions his team created. He focused on the necessity of the safety and accuracy of data, in this case data related to the utility and telecommunications industries.

As an SSP junior developer, I worked with the most talented team I’d ever met

After a week of intense training, I learned the tools and products I’d use daily as an SSP junior developer.  I learned coding standards, object-oriented analysis, and project design. I learned how to provide true value to clients. Whereas in college I’d worked in mostly Linux/Unix, Python and Java, here I was going to use Windows and C#.Net.

That was just the technical side.

As with starting any new role, this one offered me many new opportunities, and challenges.  One of my favorite things about the work at SSP was the team’s open-door policy. Every day, I could ask any question. So I learned a great deal. I learned how to serve clients. I learned about the software behind GIS.

I honed my developer skills … 

… In communication, development, testing and deployment. I built relationships with coworkers in and out of the office. At the quarterly meetings, Skye briefed us on the company status. Every employee attends, regardless of role. So I got to see directly how my work affects our market position.

Not to mention, we had a lot of fun. My first year as an SSP junior developer was different than my first year at any other place else I’ve worked.

Every day, we break up our fast-paced work with ping pong, fantasy football, and other stress-reducing activities. We always have team events, reinforcing that we’re one team, we’re in this together, and we’re more than co-workers. My co-workers have become close friends.

We’ve built incredible relationships.

Relationships are the focus of everyone at SSP, both among ourselves and with our clients. In my SSP first year, I got to build bonds with everyone.

Everyone I work with is committed to their projects. We work as many hours as it takes until the client is satisfied. I know I can trust my team. My team knows they can trust me. And our clients know they can trust all of us at SSP.

I’m no longer part of the herd. I’m part of the family.