Hey
There

Introduction

I did my first co-op term as an Application Developer at ERCO Worldwide this winter. It was a great experience that helped me both technologically and professionally. My primary project was to recreate and enhance an internal audit application which was being used to track and manage environmental and safety audits across the company.

What I Did

From the beginning, I was given a lot of responsibility. I spoke directly with stakeholders to understand what they needed from the new system. After gathering requirements, I designed a full database in SQL Server Management Studio (SSMS) and began building out the application in Power Apps.

The app is meant to let users create audits, add findings to each one, and have those findings go through a multi-step approval and review process. I also set up workflows using Power Automate to automate CRUD functionality for files and documents.

Learning Objectives and Reflections

Challenges and Future Goals

One thing I didn't get to do was handle support tickets or write official documentation for the app. Since the project wasn't finished yet, we weren't at that stage. In my next term, I want to focus more on things like writing user guides, handling feedback, and supporting the app after launch. I think learning how to maintain software is just as important as building it.

Conclusion

Overall, this was an amazing first co-op term. I learned a ton, got to work on something real, and grew a lot as a developer. Being trusted with such a big project and receiving a return offer meant a lot to me. I'm excited to go back and finish what I started and to keep improving as both a developer and a teammate.

Introduction

I continued my co-op at ERCO Worldwide for a second work term as an Application Developer. Having spent my first term building the foundation of a new internal audit application, this extension allowed me to further enhance and stabilize the system. The application plays a critical role in managing environmental, health, and safety audits across the company. During this term, I focused less on learning the basics and more on refining the system, improving user experience, and preparing it for long-term use.

What I Did

This term was about expanding and solidifying the foundation laid in my first four months:

New Features: I implemented several new modules, such as advanced reporting dashboards, action tracking enhancements, and extended audit role functionality. These additions gave stakeholders more visibility into audit progress and compliance status.

Database Improvements: I optimized SQL Server tables and views to handle larger datasets more efficiently, reducing load times and improving query reliability.

Automation Enhancements: I extended Power Automate flows to handle more complex approval chains and automated email notifications, cutting down manual follow-ups.

Permissions and Roles: I worked with my manager and stakeholders to refine the role-based access system, ensuring that different user types (auditors, assignees, supervisors) only had access to what they needed.

Testing and Feedback: I spent more time this term coordinating with end users, gathering feedback, and making iterative adjustments. This gave me a stronger appreciation for the importance of user experience in enterprise apps.

Learning Objectives and Reflections

Challenges and Future Goals

The biggest challenge was balancing feature requests with stability. Stakeholders often wanted new functionality quickly, but I had to ensure the system remained reliable. This taught me how to prioritize work and communicate trade-offs clearly.

Looking ahead, I want to:

• Gain more experience in testing strategies and error handling.
• Explore integration with Power BI for richer reporting.
• Continue to improve documentation so the project remains sustainable.
• Learn more about security practices in SQL and Power Platform apps.

Conclusion

My second co-op term at ERCO Worldwide was just as rewarding as the first but in different ways. Whereas the first term was about learning new tools and building a system from the ground up, this term focused on refinement, optimization, and preparing the app for real-world use. I grew more confident in working with stakeholders, balancing technical and business needs, and thinking about software longevity.

This experience confirmed my interest in full-stack and enterprise application development, and I'm grateful for the opportunity to contribute meaningfully to ERCO's digital initiatives over two terms.

Introduction

I completed my third co-op term at KPMG Canada as a Student Intern on the Network Support Team, working alongside the Network Engineering team. After two terms in application development, this was a chance to learn more about the infrastructure that keeps a large company running. I helped with day-to-day network operations while also working on longer-term projects involving documentation, repository organization, audit support, and network upgrades.

As the term went on, I became more comfortable with ServiceNow, change management, and coordinating SDWAN router upgrades. Working with experienced network engineers and administrators helped me understand how much planning and teamwork goes into maintaining an enterprise network.

What I Did

My work was split between supporting daily operations and helping the team improve its processes:

Network Repository Restructuring: One of my biggest projects was reorganizing the Network Engineering repository. I reviewed thousands of files and folders, worked out what needed to be kept, archived, or moved, and put together a more consistent folder structure. I also created tracking spreadsheets and repository guides, then presented the structure to the team for feedback. The goal was to make information easier to find and maintain.

IPCR Audit Support: I helped with the annual IPCR audit by gathering evidence, documenting controls, and keeping tracking records up to date. This involved following up with people across different teams and paying close attention to details so the audit requirements could be completed on time.

ServiceNow and Change Management: I reviewed and assigned incidents, service requests, and change requests, tracked service-level agreement (SLA) activities, and helped keep support work moving. As I learned the platform and the team's workflows, I became more confident handling tickets and change management tasks on my own.

SDWAN Router Upgrades: I supported the upgrade program by creating and tracking Change Requests (CRs) and Quality Assurance (QA) requests, maintaining schedules, and coordinating upgrade activities. I also helped track implementation progress and document the process so future upgrades could follow a consistent set of steps.

Documentation and Process Improvement: I worked on onboarding guides, network inventory records, Enterprise Analytics repository documentation, and procedures for operations, access, and upgrades. I also helped develop EA/Visio diagrams and network architecture documentation. These tasks gave me more practice turning technical information into resources the rest of the team could use.

Operational Support: Alongside my projects, I helped with ticket management, after-hours implementations, Change Advisory Board (CAB) reviews, on-call rotation updates, network monitoring initiatives, security access requests, and repository maintenance. This gave me a better picture of the ongoing work needed to support the network each day.

Learning Objectives and Reflections

Challenges and Future Goals

The biggest challenge was balancing daily support work with longer-term projects. Tickets, change requests, and implementations often needed immediate attention, while repository restructuring and documentation required steady progress over several months. It pushed me to think more carefully about how I organized my time and priorities.

There was also a lot to learn at once. ServiceNow workflows, audit requirements, documentation standards, repository management, and change procedures all took time to get comfortable with. Working through these different areas helped me understand how closely they connect in day-to-day operations.

Looking ahead, I want to:

• Build a deeper understanding of network infrastructure and routing technologies.
• Learn more about network monitoring and performance management tools.
• Continue developing automation and reporting solutions that make operational work easier.
• Expand my knowledge of network security, access management, and compliance.
• Keep improving documentation and making processes more consistent.
• Gain more experience with larger infrastructure projects and network upgrades.

Conclusion

My third co-op term at KPMG Canada gave me a new perspective on enterprise IT. Through repository restructuring, audit support, ServiceNow tasks, SDWAN upgrades, and documentation, I got to contribute to both daily operations and longer-term improvements. I built my technical knowledge while also becoming more organized and confident working with others.

This experience strengthened my interest in network engineering and IT operations. I'm grateful for the chance to work on meaningful projects and learn from the engineers and administrators who supported me throughout the term.