Software Engineer with more than 17 years experience in developing and designing a wide variety of applications using .NET with heavy involvement in the software architecture and design. Key projects involved with include Sportsbook, Financial Systems, SMS Applications, CRM systems, ERP Systems, and others.
Experience
2023 — Now
2023 — Now
London, England, United Kingdom
2014 — 2023
2014 — 2023
Malta
Key Responsibilities:
• Work closely with team members to ensure successful completion of projects
• Enabling continuous improvement in the team’s processes and component
• Responsible for people management including resource planning
• Close collaboration with product teams to ensure timely delivery of projects and initiatives
• Close collaboration with architecture team to ensure architectural standards are followed
• Develop and maintain company's Sportsbook product
• Come up with technical design and solution to the various components that make up the Sportsbook product
• Support for end-users
Key Projects and Tasks:
• B2B
The B2B project is made up of various components that make up the company’s B2B product offering. This includes components that partners use to integrate and use the company’s B2B offering. Involved from the beginning to present.
Primary technologies used in the team include REST Api’s, RabbitMQ, Redis, SQL, nUnit, Moq, and more recently Kafka. Used different coding practices as well including IoC, use of design patterns, the Onion architecture, and microservices architecture.
• ISA
ISA is a set of different components that acts as the main point of integration between frontend and the backend. This project replaced the legacy systems used by the company before. The project includes an API and several different components working behind the API to aggregate data or push data to the front end or other teams.
Primary technologies used in the team include REST Api’s, RabbitMQ, Redis, RedisPub/Sub, SQL, nUnit, Moq, IoC.
• BetBuilder
BetBuilder is a set of components that make up the company’s Bet Builder product offering. As with other projects, I have been involved from the beginning. The project involved integration not only between internal components but also 3rd party providers.
Primary technologies used in the team include REST Api’s, RabbitMQ, SQL, nUnit, Moq, IoC.
2012 — 2014
2012 — 2014
Key Responsibilities:
• Develop and maintain internal applications used by the company.
• Assist in requirements gathering and analysis
• Support users
2010 — 2012
2010 — 2012
Key Responsibilities:
• Work on the technical architecture and design of .NET based applications
• Develop and test .NET based applications
• Assist in requirements gathering and analysis
• Support users during training and implementation
Key Projects and Tasks:
• Mercury
Mercury is a WCF-based service first developed as an integration service for AX and the legacy applications. The service was also used later on as an integration service for AX and the new .NET applications. Applying the principles of service oriented architecture (SOA), the service was redesigned as the service layer for all .NET based applications.
• Personnel Management System
PMS is a .NET based application for use; as the name itself; for managing personnel data. As some processes in the company cannot be handled by AX, PMS was developed to automate these processes. Modules include CNIA, Documents Management, Telecoms Register, and other modules not started yet including Accommodation Management, etc.
PMS uses Mercury as its service and domain layer. All business logic is in Mercury.
Responsibility: Technical Architect / Developer
• Super Item Application
Super Item is a .NET based application for use by the company’s procurement department to manage its items. Before the super item was developed, all items were just entered in the legacy system as it is thus the item database has blown up into a large list containing a lot of duplicate items or items that basically just have different dimensions. The application was developed to group these items into one super item and just differentiated by dimensions
Responsibility: Technical Architect / Developer
• Others
Other small applications/tools worked on include the Mercury User Administration Application developed using LightSwitch and a data extraction tool used to export data from the legacy application to be loaded in to AX.
2008 — 2010
2008 — 2010
Key Responsibilities:
• Apply the principles of software engineering to design, develop, test, and evaluate software and systems to meet the solution requirements using .Net technology.
• Perform coding and unit testing.
• Assist in technical software design.
• Assist requirements gathering and analysis.
• Work productively with broad instruction and limited supervision.
• Must demonstrate a degree of flexibility in resolving problems/issues that attest to in-depth command of all techniques, processes, tools, and standards within the relevant field of specialization.
Key Projects and Tasks:
• Mamut Online Desktop (http://www.mamutonline.com)
Mamut Online Desktop is the web-based access to the information and functionality from Mamut Business Software, along with services included in Mamut One. With MOD, you get access to the following features including Synchronization, Online Contact Management, Online Activities and Calendars, Online Status, Online Hour Administration, Online Management Reports, Mamut Validis, Business Year Planner, and Timesheet Entry.
Membership Sales Order Module
Responsibility: SCRUM Master (Sep 2010 - Present)
Membership Register Module (Jan 2010 – Aug 2010)
Responsibility: Developer / Soft Technical Architect
Asset Register Module (May 2009 – Dec 2010)
Responsibility: Developer / Soft Technical Architect
Timesheet Module (Jun 2008 – May 2009)
Responsibility: Developer
• Thermo Fisher Scientific
Group of software systems for the Thermo Fisher Scientific group of companies.
Responsibility: Support Developer/Technical Advisor
Education
Ateneo de Davao University