Ameer Nasrallah

Developed a payment system for a freight marketplace (Ship.freightos.com) using Stripe Payment Gateway and Zoho Invoice.

The first part of the project was to enable business and person entities (vendors/shippers) to send/receive payments either online (Stripe Java API) or by wire transfer through our platform (the marketplace & the SaaS site but mainly the marketplace). This part included making a proper design that ensures secure payments and confidentiality—a proper data model that integrates easily with the existing business model and can be tracked easily for cases of failure.

The other part was to integrate with a SOR (system of records) to keep track on all the balances of our customers.

It was done by the integration with Zoho Invoice API.
Two challenges here:
1) A mapping between our data model and Zoho invoice model to ease transactions; handled by a transformation layer (not very efficient included only field names).
2) Catching failure scenarios without affecting user experience; handled efficiently by designing a fallback mechanism on the main scenarios (highest layer) that alerts by email failure received and point of failure (with data) enabling product and development teams to handle the issues.

This was a small project that I had to work on as a proof of concept. Its purpose was to build a back-end to serve API requests (regardless of the client) for a burger shop (menu items, orders, statistics, and others).

In this project, it was required to build the API using Django REST framework. Before starting with the project, I had little knowledge about Python and zero knowledge about Django. I had to finish it within one working (in another company) week including research.

I prepared the environment on the first day, managed to learn Django and Django REST framework within three days, and then I worked on the project for two days.

Even though I lacked basic knowledge (as you will see in the repository) about the requirement text and naming conventions (such as burger_api instead of API) but other standards including coding and modeling went very well.

In a networking course, we were asked to simulate P2P file sharing using socket programming.

I built this project using Java that uses threads to simulate a tracker with the communication with many peers, chunks, and acknowledgements with each other on downloading a certain input file.

The project will eventually be uploaded to GitHub.

During my experience with the front-end, some difficult and unexpected problems appeared which affected the main user experience scenarios.

For example, I solved an issue causing a crash in a specific request to Google maps API on IE 10 by finding a bug in error-handling in the GWT library.

Another example, there was a problem when we adopted the "number" type input for our website to enhance a mobile user's experience. The problem caused unacceptable behavior (from the business perspective) on both modern and old desktop browsers so I had to read how each browser intercepts and validates the "number" input. Then I implemented a solution that preserved the old experience for desktop users and kept the new experience for mobile users (with known limitations).