Full-stack Developer in Pearland, TX, United States

The Rate Integrity Suite of products was initially a POC conceived of by myself and Dan Wiser. At the time, auditing and verification of corporate hotel rates were done by hand, and each company had its own group of auditors that could spend months verifying the validity of the negotiated rate loads.

After conversations with significant players in the industry, a plan was formulated that could solve the issue.

Eight months after our initial meeting, I presented a working prototype to the board. Three months later, version one of Rate Audit was released. A patent was immediately filed on the technology.

14 months later, a more complex version of the software (Rate Integrity) was launched that allowed for standard auditing and more complex reverse auditing.

Recently, the interface was rebuilt using Angular to help with user interaction. The system relies heavily on reporting and analytics to express the outcome of the audits. This information can be complex to digest, and a highly graphical "drill down" interface using Angular allowed this vast quantity of data to end-users. The new interface allowed users to drill down to given areas of the report in real-time to see the information that's most important to them.

I was brought into Kaddra to help mentor and develop the US, Singapore, and London teams. Kaddra was developing and releasing the Keyyes Lifestyle mobile application. Designed to cater to the high-income shopper, the app was completely engineered for very decerning tastes.

I helped to design the back-end API interface as well as work with the data team on ETL processes, data lakes, and reporting systems to help the business follow the activities of its customer base.

The API back end was redesigned using Node.js and Express.js. We needed a lightweight engine that could be easily scaled and maintained. Express is easy to extend and handled the workloads under load testing with minimal setup effort.

One of the most challenging tasks assigned to the group was to release the application to China. For anyone that has worked with China-based distributions, especially mobile applications that require SMS-based messaging, there are many hurdles that I had to help the team determine and overcome.

Working closely with the group, we were able to get an AWS distribution in China that functioned (at least from the end-users perspective) exactly like its US-based counterpart.

The Lanyon Transient GDS Access system was designed to allow customers to communicate with the “Primary” GDS (Global Distribution Systems) without the need for private VPN’s or costly emulation software on every desktop. This was the first software to market to offer these capabilities within a browser-based editor.

My role on this project was extensive as I had to design, build, implement and maintain the system for several years before the company grew enough to have additional staff to help.

Embodiments of the present invention provide a system, method, and computer program product for reverse audits based on server access to databases.

In one embodiment, a data provider is determined, and a data request based on the data provider is sent to a server, wherein the data request promotes an entry of the data request to access a database. A server receives a data response, wherein the data response corresponds to the data request. A message is then output based on whether the data response includes specific data.

Embodiments of the present invention provide a system, method, and computer program product for auditing rates based on server access to databases. In one embodiment, an expected rate is received, and a rate request is sent to a server, wherein the rate request promotes an entry of the rate request to access a database.

The server receives a rate response, wherein the rate response corresponds to the rate request and includes a specified rate. A sales request is sent to the server, wherein the sales request corresponds to the rate request and promotes an entry of the sales request to access the database. A salesresponse is received from the server, wherein the sales response corresponds to the sales request and includes a sale rate. A message is then output based on the expected rate, the specified rate, and/or the sales rate.