History

I worked on our nuclear AI product NPX AI building a custom translation feature which is an Azure hosted AI translation service trained on nuclear documents to learn specific nuclear terminology.

I am currently working on a Equipment Stats Log which is a dashboard for tracking the live status of components and their sensors accross nuclear facilities.

I spent the majority of my time building a delivery management which helped organize the allocation of drivers, trucks, trailers and nuclear waste and components.

I created an interactive calendar which was the main interface to schedule shipments and deliveries with a drag and drop interface using FullCalendar.

In addition, I also made a custom Email service to send notifications of new shipments using Azure email services.

I worked on the Data Fabrication team building as an intern helping build their internal UI which all of capital markets uses to manage their databases from trading systems, risk analysis models all the way to logs of miscellaneous services.

The majority of my work was spent implementing a feature to promote your database from one environment to another. This involved working with designers, backend engineers, and even business analysts to determine the requirements as well as implementing the feature.

This feature was a complex one as we needed a responsive UI which illustrated clearly all the processes that were occuring in the backend such as the promotion of every dataset. This meant having live updates streamed to the user and maintaining the state of every dataset across different sessions.

I spent my time at Citi working in their Equities divison as an intern working on their trading platform.

Most of my time was dedicated toward building an intuitive and straight forward portal for traders to directly query my teams database for trade information.

The main purpose of this was to free up developer time whenever a trader had questions about the status of trades or was worried there were potenial errors not displayed on their platforms.

In addition to this I also constructed a few one time scripts to help my team clean up our databases of garbage data such as duplicates, stale and previously corrected data.

On top of this, before the end of my internship I made a recurring script that used stored procedures to find any duplicates or errors in recent data which would then quarantine the data in a new table and send out an email summary to the team.

This was my first full time job as a software engineer intern and where I actually learned Front End development for the first time. Shoutout to my mentor Eamonn who encouraged me despite my absolute non existent React knowledge. I can't thank him enough for his support and guidance as I probably would have never learned React.

My team was the FICC Cash analytics team. Specifically we maintained a service which simplified the pricing and risk analysis of bonds for other internal teams through. (Not exactly the most UI friendly team as 85% of the work was backend)

I spent half of my time working on performance analysis, which lead me to determine our JSON parsing was one of the largest drawbacks. Leading me to cut our average execution time to 1/3 of the original time.

The rest of my time was spent learning React and creating my first ever react app! I basically built a global dashboard my team could use to query logs across all of our servers whether it be development, testing or production. As well as monitoring each individual team who utilized our systems and the rates at which they consumed.