Gaston

As a member of the cloud team, he was in charge of the design, development, and implementation of the new cloud solution and virtualization of Excel’s spreadsheets containing core logic and formulas and a new suite of apps interacting with it.

Tech Stack: AWS (Lambda, DynamoDB, S3, Kinesis, CloudFormation, SNS, SQS, AppSync, CloudWatch, EventBridge, Cognito); Datadog; C#, TypeScript, Java, Node, React; AWS SDK 2.x, 3.x; MyGet, Git, Bitbucket, Bitbucket’s pipelines, GitHub; Confluence, Jira; CI/CD; Visual Studio Code; TDD; Unit testing; RxJs, NPM, Yarn, Jest, Google proto; Docker, Dobi, Windows WSL; PowerShell; Agile/Scrum, Kanban

As a member of the Transcoding team, he was part of a vertical unit in charge of the design and development of new requirements and the maintained of the transcode cloud solution, a backend system to automatically transform a master video file into several layers and codecs to be streamed in the video platform. The design, development, and implementation of a new auto scaling strategy to minimize the costs of running instances. With the new version, costs were reduced at least 50% as the EC2 instances were started only when needed, and instance types (t2 and c5 families) were chosen according to the video file properties, allowing the use of smaller (and cheaper) instances.

Tech Stack: AWS (Lambda, DynamoDB, S3, Elastic Transcoder, CloudFormation, SNS, SQS, ECS, EC2, CloudWatch, API Gateway); C# (.NET Core 1.x, 2.x, .NET Framework 4.6); AWS SDK 2. x, 3.x; SQL Server; MySQL; CI/CD; VSTF; TDD; Unit testing; Dependency Injection; Agile/Scrum

As the main developer of the system’s backend, he was in charge of the design, architecture, and development of the WebAPI solution (code and database). The API is a gateway for credit card and bank clearing payments implementing the usual card transactions (Sale, Auth, Capture, Void, Refund, Verify) with extra functionalities such as invoices, recurring billings, and notifications for several payment sources (e.g.: Swipe, EMV, Internet).

• Complied with PCI DSS security standards and worked with payment processors (i.e.: TransIT -TSYS-, SAGE, ProfitStars) and other providers (e.g.: Cardinal Cruise for 3DS Secure, Magtek’s card readers).
• Designed a solution capable of generating a payment transaction in less than 2 seconds. It was accomplished by making all unessential operations asynchronous, with only the core functionality being synchronous (in a nutshell, register the request in the database, call external providers, update the data, call the payment processor, update the status, return the result).

Tech Stack: Azure; C# (.NET Framework 4.5); SQL Server 2012-2016; Rest API; WebServices; JSON; SOAP; Azure Key Vault & HSM; EntityFramework 6 (DB First); Threading; Dependency Injection; Strategy pattern; DDD; Agile.

Worked on a Credit card & Currency exchange system. As a member of the development team, he received the design of new requirements and he had to code and test the changes, modify related documentation and write the implementation guide for QA and the database teams.

• Investigated and proposed potential code refactorization to improve performance.
• Developed an API consumed by the Android and iOS app, for electronic invoice through AFIP’s (Federal Revenue Agency) systems, and a website as the user control panel
• Implemented critical modifications with short deadlines (2 or 3 days) to comply with Central Bank’s new regulations

Tech Stack: ASP.NET; SQL Server 2008; Oracle; WebServices; SOAP; XML; WinForms; C# (.NET Framework 3.0)

Worked on an Emergency line system. As the only member working on this project, he inherited a legacy application that studied to then work at the client’s premises. He had to evaluate the status of the system and suggest improvements and meet with the police staff to gather new requirements.

• Had to design, develop, test and implement the new changes and finally train the IT department to complete the product handoff.
• Improved the system performance, which was extremely slow due to a subpar database design and 3 years without maintenance. The solution was to redesign, code, and implement a new and better database to act as a historical repository and keep the original database as the transactional database with only 2 weeks’ worth of data.
• Stored procedures and scheduled events were created to transform and migrate the data.
• A considerable part of the application’s data access layer was modified as well to query the new database

Tech Stack: SQL Server 2008; WebServices; WinForms; C# (.NET Framework 3.5)

• Freelance Developer at multiple projects (2013-2014)
• Developer at Pentacom (Argentina) (2012)