Andrew Giangrant

A replacement audio video streaming application to improve performance and dramatically cut operational costs. This work involved research in making smart, long-lasting decisions on core functionality and features on the roadmap. The entire streaming engine was replaced, and features were added, such as referrable participants where actions are accredited to referrers, presenter mode where participants can join with audio and video, waiting room functionality capable of holding thousands of participants until the session starts, and a brand new user interface and experience.
I was the top contributor to this project and a heavy influencer across the platform.

An SMS application was built for one of the largest health insurance companies. The SMS application authenticated customers and fully integrated with existing chat systems. Features included voice XML files that recited a message on call, many hooks into APIs to relay messages to data analytics, customer service storage, and other important divisions. Built entirely with maintenance and scalability in mind.

A mock fax server that uses Linux, Hylafax, Asterisk, IAXModem, and Node.js to send and receive faxes within a network. Everything was written behind a VPN for testing purposes. It was used in an automation workflow to detect suspicious faxes and the application's overall functionality of a virtual faxing module.

An application that organizes travel plans into a React user interface. The back end was written in Node.js with Babel. Docker was used to isolate the development environment, and unit tests were written for front-end components and back-end functionality. Users can register and log into the application, where trips can be created, deleted, or modified with destination details, comments, and other information.

I built an Angular application to calculate observed vs. expected stay ratios; made with Angular and Elixir with the Phoenix Framework. The most difficult challenge with this project was the lack of knowledge of Elixir before working through the tasks. The front-end application featured charts and data displays (tabular and detailed summary paragraphs) about the current month's stay ratios. The API featured a caching layer for non-PHI lookups and PDF generation for reports. Data processing and the application as a whole were implemented on an existing EMR database offset. The project was deployed to AWS on an EC2 instance.

A dashboard built in Angular to show energy consumption data from users with services with energy providers. The Angular front end used observables via RxJS to fetch and cache data from an API. The dashboard was used to display the differences between reusable energy consumption and non-renewable energy consumption. This involved charts and graphs which sampled large amounts of data from the API at different zoom levels.

The integration created organization charts and panels using the data to and from the ADP workforce API. There were a lot of abstractions to make the API requests and filter the proper data. The ADP API, in general, is quite verbose, requiring specific attributes along with the payload for requests to work. Other APIs were investigated, including time-off management and scheduling. In a previous project, the ADP API was used to sync workforce members with the database, which allowed the application to associate any of its data with any related data in ADP. I was responsible for that entire integration.