Introduction

My Ceridian internship was a massive part of my education and gave me insight on the work I may be doing once completing my degree.

General

January 2022 to September 2022 had a major that spread its reach out across the world, COVID-19 and my co-op was nonetheless effected. However, by the time of this internship Ceridian had already adopted the remote work almost fully and had very good systems in place already. While there may be have been some things left out from being in office, the resources and help was still available to me regardless.

Starting my internship, I was brought on to work on the maintenance of legacy data analytic product, MyDashboards, which was built on C# (ASP.NET) and part of the monolith structure of Dayforce at the time. Recieving mentorship from a senior developer Steven, I was able to quickly pick up the codebase and beginning resolving issues mostly around the ETL pipeline that it was depedent on. This was a mix of C# and mostly T-SQL (SSMS) store procedure fixes.

However, as my internship continued after a few months and Steven's eventual departure from the company, MyDashboards was officially sunsetted to recieve only fixes for critical issues and I was then moved onto the development team for its successor, Data & Analytics. Growing the size of the team and now working on a new stack of code, mostly front end as we were mostly developing the MVP, I picked up TypeScript (React + Redux) and began work at a rapid pace. A highlight being even leading the investigation of charting library to use to display graphs, of which was chosen as the base in use for the feature to this day.

It does have to be said that it was my first time working with a strong system of software development and putting all of those engineering techniques, SCRUM, Agile, etc. into practice. Overall it was an amazing experience to work on teams with structure and with teamates that were more than happy to elevate my abilities.

Non-Technical Challenges

Having been my first larger team, working in an Agile environement and leveraging the communication and, well, agility of the framework was a new challenge. Moving work around and not being as rigid as requirements change and discussions happen, then being able to actually contribute to these discussions was a worthwhile lesson.

Additionally, due to the circumstances of my internship, switching between tech stacks at a relatively quick paste was a challenge, however since it was technologies I was already familiar with it was a little easier.

Technical Challenges

• DevOps (again...)

• Redux

Lessons

DevOps pipeline.

React/Redux. C#/ASP.NET and many technical skills.

Conclusion

A great experience, and a desire to return - which I do end up doing in May 2024 as a Full-time Software Developer (2024-09-17).