• Module Design and Requirement Analysis – Attending design sessions along with System Analyst for collection and documentation of user's requirements.
• Coming up with the conceptual design, high-level design plan before starting development. Review these with Enterprise Architect.
• Development of end to end functionality - Write, modify, integrate, and test software code. Development of logical specifications.
• Working closely with the client’s architecture team on day to day basis for design decisions.
• Supplementing System Analyst’s work by preparing deliverables like Component diagrams, data mapping documents.
• Design and development of ESB components to call external HTTP based REST API services to implement integration using Mule ESB.
• Module documentation - Prepare reports, manuals, and other documentation on the status, operation, and maintenance of software.
• Working closely with the testing team and User Acceptance testing teams for bug fixing.
• Bug/Defect analysis/fixing major issues faced by business users. Post-production support.

• Was part of the integration team to transform UBC's academic and administrative support processes and system environments for the entire UBC community. Work involved integration between several systems used by UBC (Some built in-house) and others primarily like Salesforce, Workday. The Integrated Renewal Program (IRP) unites previously independent projects, formerly known as Student
• Academic Systems Initiative (SASI), Procurement Modernization, and HR Finance Renewal to replace 20 -year old legacy systems. It will replace UBC's SIS (student), HRMS (HR), and FMS (finance) core systems with Workday.
• Worked on integration projects using external-facing API architecture to let business partners integrate with different Systems like Salesforce, Workday, Other in-house/external UBC systems for different purposes like financial common Services, Updating Student records (course, sections, enrollments, etc .), creating grants, and scholarship records. New integrations are developed in Mulesoft 4.x (Existing 3.x projects are getting migrated to 4.x). ActiveMQ is used for internal messaging between integration components.
• Design and development of ESB components to call external HTTP based REST API services to implement integration using Mule ESB.

Client: British Columbia Lottery Corporation (BCLC)

• Worked on component-driven development of integration projects using micro-services based external-facing API architecture to let business partners integrate with the BCLC system for different reasons like earning and redeeming loyalty points, generating draw results. These projects are the foundation to the Lotto Transformation program and are developed using the TIBCO BusinessWorks integration engine to let micro-services interact using HTTP SOAP and REST. TIBCO EMS is used for internal messaging between integration components.
• Working as a part of the Groundswell Design/Architect team to prepare and deliver functional/non-functional and Technical Design Documents for the integration projects. Working closely with the client’s architecture team on day to day basis for design decisions.

• Worked on Mulesoft POC and different TIBCO suite of products like TIBCO BusinessWorks, TIBCO ActiveSpaces, TIBCO Administrator, and TIBCO EMS.

Client: Kroger, USA

• Kroger used the TIBCO suite of products for the derivation of different attributes related to Item like Shelf tag descriptor, different flags. All these derivations are carried out in TIBCO BusinessWorks(BW) & BusinessEvents(BE) layer. BW & BE are used as adapters between upstream systems & downstream applications like Vendor Item Portal (VIP).
• Worked on developing integrations for deriving shelf tag descriptors.

Client: Kohl's Corporation

• Currently, Kohl’s has all its data (customer, product, and master data) scattered across different systems which includes some legacy systems as well. As part of Kohl’s MDM program, TIBCO is going to replace all these different systems with its product called Collaborative Information Manager (CIM). After implementation, CIM will be the only source of truth (Golden copy) for all customer data in Kohl’s.
• CIM maintains a master copy of data and downstream applications can query this data. TIBCO Active Spaces deal with fetching bulk and real-time data from the CIM system and storing the same in high-speed Active Space cache. Since TIBCO CIM stores the master data, which is frequently accessed by end systems, direct fetch from CIM would turn out to be slow & there could be easily thousands of fetch operations per day. To speed the data access, Active Spaces Services, on one side, always load data from CIM into AS cache and keep the data latest in cache & on the other side, Active Space services provide SOAP-based web services exposing APIs to get/search business entities.
• I was part of the integration development team to implement the TIBCO ActiveSpaces cache using TIBCO BusinessWorks.

Client: CLSA Technology

• CLSA Asia-Pacific Markets is Asia’s leading and longest-running independent brokerage and investment group. The company provides investment-banking, equity-broking, and asset management services to global corporate and institutional clients.
• Syn~ MiddleOffice Application takes transactions from any front office system like FMS or OMS (from Sungard Inc.) or client portal through channels like DMA, DSA, Agency, gets client allocations from third-party systems(like OASYS from OMGEO Inc.) manages and directs transactions to the back office settlement system and ensures that each transaction is enriched with standard settlement instructions, party, and other reference data while providing real-time information on client, profit & loss and depot positions via Client Confirmations. Syn~ MiddleOffice enables exceptionally high STEP (Straight Through Exception Processing) in a complex trading environment.
• Implemented the FX module. Worked on price, Settlement Amount rounding, Buy-In trades mechanism in Syn.
• Writing complex PL/SQL queries for reporting teams.
• Performance Optimization of software code / SQL queries.
• Preparing data-loads, TLE scripts, and merge version maps.

Client: AT&T, USA

• ASMS is an order managing system; it creates devices and establishes connections between them by interacting with Cramer inventory, third-party applications, and legacy systems. The workflow goes through Service orchestration, Service Fulfillment, and Service Assurance. IDIS will accept manual orders entered via GUI and orders from external systems such as GCP, MIC (from IBM). The order will always be submitted to ASMS. The order will undergo top-level decomposition based on the ASMS Service Catalog (SC). This decomposition generates Service Orders from the original order. An example of service order in IDIS is a single “OEM Access Service,” which represents a single connection to a customer premise. This service order is fulfilled after Cramer designs the circuit. ASMS executes the plan received from Cramer DE, handles dependencies, errors, and any manual tasks. For an automated interface, ASMS will have the ability to make the relevant calls to the external system, receive data, and handle any errors that occur (timeouts, invalid data, and error response).
• Module Design and Requirement Analysis – Attending design sessions along with System Analyst for collection and documentation of user's requirements.
• Coming up with a conceptual design, high-level design plan before starting development. Review these with Enterprise Architect.
• Development of end to end functionality - Write, modify, integrate, and test software code. Development of logical specifications.
• Working closely with the client’s architecture team on day to day basis for design decisions.
• Supplementing System Analyst’s work by preparing deliverables like Component diagrams, data mapping documents.
• Design and development of ESB components to call external HTTP based REST API services to implement integration using Mule ESB.
• Module documentation - Prepare reports, manuals, and other documentation on the status, operation, and maintenance of software.
• Working closely with the testing team and User Acceptance testing teams for bug fixing.
• Bug/Defect analysis/fixing major issues faced by business users. Post-production support.

Client: DBS Bank, Singapore

• The objective of the proposed system is to re-design the Multirec to handle the following:
• Providing a feature to add a new record without having to go to the last record in the list of pre-entered records. Providing a more intuitive control to add new records in the database. Providing a more intuitive feature to save records in the database.
• Development of end to end functionality for Multirec module.