During my time at T-Mobile I had the opportunity to work on some wonderful projects across the Customer-Welcome, Metro and FRESH teams. Below are some examples of my work: Migrate 28 Out Systems Apps to Salesforce Lightning Community Portals:Working with a very large team of developers over six months I worked to create a series of Lightning Web Components and web-pages that matched our existing apps as much as possible. This meant following the Lightning Design System and reusable CSS as much as possible. The effort took around six-months to complete and greatly reduced our yearly operating expenses. I am now working to clean up the work done by all the contractors we temporarily hired to handle the sheer volume of work.Developed Heroku Based API to Replace Salesforce Appointments Functionality:After further investigations it was determined that Salesforce was not the best tool for managing our retail users and appointments. So, I and my team decommissioned our current salesforce org in favor of a series of custom API’s and a Postgres database powered by Heroku. I took this opportunity to get some hands-on experience writing and testing APIs outside Salesforce.

Developed and Managed Lightning Components:During my time at MADSKY I developed several lightning web components for their internal team and partner users.Manage Dell Boomi-Salesforce Integration:MADSKY's Salesforce instance was heavily tied into our Dell Boomi platform, which allowed us to transpose data sent from other servers into the proper format for salesforce insertion. Boomi was also used to send data from salesforce to external databases. I have debugged and added new processes to our dell Field Service Lightning Netsuite Integration:This project involved creating processes, flows, apex code and several objects in order to make sure we could translate data from field service lightning objects into a format digestible by Netsuite.

While working at PushPay I had a unique opportunity to work as a developer and an architect. I worked closely with Personal Managers, End Users and Salesforce Admins to develop effective, time conscientious solutions to projects. If the projects involved code it was my responsibility to work on it. Here are a few highlights from my time there:Created Series of Nightly Apex Batch Jobs for Daily Record Updates:PushPay needed a way to preform nightly updates and computations for millions of records inside their system. I wrote a series of chained batch jobs that would efficiently preform these updates on a daily basis.DocuSign Buttons to Generate Custom Forms:We needed a way to attach DocuSign templates based on field level data on related child objects, my code would look at those select fields and generate a URL with the required template ids attachedMaintained and enhanced Slackbot:Pushpay uses slack and Slack-Bots (webhooks) to send data to members of the board and their sales team when various company metrics are met. I had a main Webservice Callout class called by various object triggers that handled the data processing and message sendingWorked to set up nightly backups of salesforce meta-data to a GitHub repo.:The end goal was to have the ability to revert unwanted changes through GitHub and the Salesforce Command Line Interface. I had an AWS server setup to run a custom script that backed metadata from production and from our primary sandbox then committed it to separate repos.Created and maintained a TestDataFactory and Apex Test Documentation:The Test Data Factory was used to generate test records for code that could pass duplicate checks and other various validation rules.

Worked as the only Salesforce Admin for the team

In addition to handling Salesforce Administrative duties, I handle all development including all Apex and Visualforce development Rajant needs. Below are some examples of the work I accomplished while at Rajant: REST API Between Internal Database and Salesforce:This link connects our contact and account databases to our support and partner-distributor portals. I serialize custom container classes with relevant contact and account fields into JSON, then post that data to an endpoint on our internal server. Finally, I created a Lightning Component for our contact object that allowed our sales and support teams to change relevant support portal information.Salesforce Classic to Lightning Upgrade:This was a relatively simple process as Rajant had little custom code that required re-writing. Most of my work was spent creating customized interfaces for each of our teams so they could use Lightning in the same way they used Classic.GDPR and CCPA Compliance:Working with Sales, DevOps and Legal I audited our various contact databases and created a new master contact list in Salesforce. Software Development then created a survey that was sent to this master list asking permission to contact in various forms. I then programed interface code that would auto-populate fields on contact objects indicating how each would like to be contacted. This data is used in report generation when sending anything to contacts.

Manager of internal sales for Rajant Corporation

Worked with a team to design and implement a UAS based Rajant instaMesh radio and traveled to preform on site demos and training(s) for Rajant. Training was conducted both domestically and internationally in both English and Spanish.

Systems Engineer whose primary goal is to integrate Rajant's proprietary InstaMesh technology into new platforms. This includes the development of a new radio for use on unmanned aerial systems, as well as the overlying hardware and software to enable autonomous swarm flight and deep neural networking to enable sensor-fusion.