RMS Product Engineering Team 📄
I'm currently working @ Mark43 as a software engineering intern for the RMS product engineering team.
My primary tech stack here involves java, typescript, react, and mysql.
In Progress
My current project involves redesigning some of our databases and the code that allows our tenants to export crime and incident reports for state and federal use! Some states have decided they want to try some interesting things, so it's my job to figure out how to enable our clients to comply with those regulations.
eCRM Integration Team 📊
During my summer @ CIBC, I worked on the eCRM integration team. We were responsible for developing and maintaining the infrastructure that allowed business teams to integrate their Salesforce applications and data with the bank's core systems.
Summary
Part 1.
I worked on several projects, the first of which was a complete overhaul of the data archival system used by every team in the ECRM department. You know how sometimes, you get introduced to a certain codebase and you just know that it's going to be a pain to work with? Well, that was this project. It was evidently a very ramshackle system that someone had put together and decided: "we'll fix that later".
Obviously, they never did. Thanks.
To give a quick rundown of what the existing archival pipeline looked like, I drew you a picture. Look!
I'm kidding. Mostly? Basically, our "archive" was just another container in ADLS (Azure Data Lake Storage) that we would dump data into. Other than the fact that it was a separate container, there was nothing different about it from the "live" container. The "archive" was quite sizable, and it was also using ADLS' hot tier (the most expensive one), usually meant for data that's frequently accessed. This sucked, because we were archiving data that was supposed to be kept for 7 years, and honestly, would probably never be accessed again.
Tier-ing aside, there was also no rhyme or reason to how the archival process was done for each team. Looking at the Azure Data Factory pipelines for each team, you could see that each team had their own way of doing things. Some teams used standardized ISO dates, some teams used a custom date format. Some teams would label each file they generated, others would use a generic name and put it in a folder with the date.
Honestly, I had a headache just looking at it. But someone's gotta pay back the techical debt, right? Might as well be me.
Counterparty Credit Risk 🕵️
While I was @ BMO, I worked on the Counterparty Credit Risk team. We were responsible for monitoring the bank's risk exposure to its counterparties, and ensuring that the bank was in compliance with the regulations set by the Office of the Superintendent of Financial Institutions (OSFI).
Summary