Senior Java Developer

Name: Bing (Rosa) Lu

Email: addtf7@r.postjobfree.com

Phone: 413-***-****

QUALIFICATIONS

25+ Years of focused IT experience in all phases of SDLC (System Development Life Cycle) and fluent on Agile methodologies such as Scrum

20+ years of extensive experience in Insurance and Banking industry, hands-on skills in functional areas such as New Business and Underwriting, Policy Owner Service, Billing and Collection, Claim, Accounting, Product, Tax processing. Thorough knowledge on life insurance products of universal life, traditional life, Segregate fund, Wealth, CI, DI etc.

11 years on Java, 8 years on Linux, 25 years on Windows, 25 years 20+ years COBOL/MAINFRAME & AS400/iSeries, 8 years Linux, 25+ years RDBMS experience

Bachelor’s Degree in Computer Science

Sun Certified Enterprise Architect, Sun Certified Web Component Developer and Programmer on Java Technology

Expertise in Agile, Scrum, Kanban, JIRA, OOAD skills and Unified Modeling Language (UML) and JAVA EE architecture, Linux, AIX, Windows Server, Mainframe, AS/400, RDBMS, No SQL, CRM, Azure Cloud, Docker, Swagger

Strong consulting, business analysis, system design, development, testing and problem solving skills

Canadian Federal Government Security Clearance – Reliability

EMPLOYMENT EXPERIENCE

1.Government of Saskatchewan, Regina, SK Oct 17 – May 20

Consultant

Description:

1.1Lead Developer of multiple projects/applications on analysis, design, development, test, implementation and production support.

Development Languages: Java, Angular, Groovy, Linux Script, Windows batch script

Environment: Linux, AIX, Azure Cloud, Windows Server, Oracle, SQL Server, Mysql, Apache Httpd, Tomcat, WebSphere, Active Directory, Subversion, Git, DevOps

Responsible for following projects:

1.2Highly Scalable Micro services infrastructure based on Spring Cloud Framework (running on Azure Cloud and on-premise network)

1.3

Built for the Government’s Integration services. Major components include:

Spring Cloud Gateway Service - Act as front-door/edge/proxy/routing/load-balancing service and API gateway. Handle client-specific concerns as well as cross-service concerns like security.

Service Registry Server – eureka server to register services

Config Server - Environment specific info stored in on-premise Git repository. Same code base is used across all environments which is combined with environment info to make a dynamic build to automate starting a service instance.

Lifecycle Manager – auto scaling microservices on running metrics and pre-set business rules to make microservices elastically grow and shrink.

Application Admin Dashboard - manage and monitor Spring Boot applications. Send alert email when services are down.

Oauth2 Authorization Server - Build upon spring-security-oauth2 technology, issue JWT token

Resource Manager Server – Project backend services Build upon spring-security-oauth2 technology

1.4Microservices Centralized Monitoring and Logging with Elastic stack (running on Azure Cloud and on-premise network)

The Government’s Integration Services Platform footprint consists of multiple asynchronous and synchronous distributed services where the system health must be monitored transparently. This centralized monitoring architecture must be able to produce monitoring data in real-time in order to respond immediately to an issue with one of the services and/or the infrastructure hosting these services. For operational efficiency and business continuity the centralized monitoring must issue alerts and capture service metrics such as timeouts, exceptions, response times and errors. In addition to monitoring service health, the monitoring should be able to report business continuity metrics as they relate to service delivery and usage trends.

Recording detailed information about service events allow to observe what, why, and how the services are operating. This information is critical in operational triage and problem solving and would allow the technician to respond quickly to an abnormal event minimizing the impact to customers. Correlation of services requires traceability in order to observe a distributed service life-cycle. Centralized logging and presentation capability must be able to present this view to the appropriate audience for service management.

Technology Stack

FileBeat/MetricBeat to send operational data and application logs to message queue of Kafka. Logstash is data collection engine with real-time pipelining capabilities. It consumes message from Kafka, the send to Elasticsearch. Kibana is analytics and visualization platform to search, view, and interact with data stored in Elasticsearch indices. You can easily perform advanced data analysis and visualize your data in a variety of charts, tables, and maps.

Logging Framework use Log4J2, Logback.

Built-in error email alert within services to capture run time errors at first time.

1.5Integration of Single Sign-on Site (running on Azure Cloud)

Single Sign-on Site is a platform that enables the delivery of programs to connected Government services

with one profile. Single Sign-on leverages a robust identity and access management engine that provides

citizens the ability to control their profile and access connected Government’s public digital services from internet.

With a single attested profile, citizens no longer have to remember multiple username and password

credentials to access services. Through a multi-tiered architecture, Single Sign-on brokers the connection between the person and the multiple public services they wish to consume. Control of the business rules for the all services remain with the service providers.

Integration achieved following:

To provide the capability for the applications hosted on the Single Sign-on site to request services (such as citizen/business validation) from external business partners.

To provide the capability to connect with legacy systems of the Government.

To provide a subscription service for services to receive notification of data updates from both sides – single sign-on service and downstream services.

oDownstream application can be added to a subscription list

oNotification of data changes is sent to the application

oCitizen can grant and revoke consent to sharing their data with downstream applications

oApplication must be enabled to accept the data changes (for some legacy systems, this may be a flat file)

Data logging and audit capability

oAudit service to capture data changes – who, what and when

oMonitors all user-centric actions. All service calls are forked to the audit module. In addition to auditing all events and tagging them to a user, the log files from Audit and System are moved off site for deeper analysis if required

Capability to connect to business partner web services

oAccepts the request to an external web service

oLogs the request, sends the request to the external business partner

oAccepts the response, stores in the database if required, log the request, and pass the response back to the calling application.

oPortal that displays the business partner, web service, time, response

Capability to provide web services to connect between Government’s systems

oA business service layer allows a service provider to make additional services available to their users quickly and easily.

oFederated and Web Single Sign-On enables an Government to improve convenience for end users and reduce administrative overhead for accessing on premise, SaaS-based and partner-delivered applications.

Authentication capability for a number of technology solutions include

oActive Directory: Authentication with user/password stored in an Active Directory.

oLDAP: Authentication with user/password stored in any LDAPv3 compliant Directory Server.

oCertificate: Authentication with an X.500 certificate stored in a PKI Infrastructure.

oOAuth 2.0

oSAML2

1.6Multi Governmental Virtual Exchange (MOVE)

For use by the Government and external agencies, the project to provide secured exchange of data/files between Government and external parties to ensure relevant parties have access to the data or details about the data they require to complete their duties.

This framework of data exchange represents a federation of members, with mutual interest, who agree to provide and consume information. The information is defined in product packages so that services can be delivered incrementally, while building the future state technology and software infrastructure.

Technology Stack:

RabbitMQ, MoveIT, SFTP, Spring Cloud Stream, SpringBoot, Spring Batch, JAXB, XML(with embedded image), JSON, MS SQL server DB, Hibernate,Quartz, Swagger

1.7Enterprise Payment Gateway

The Payment Gateway is used for making secure payments from Government’s various websites. Customers are redirected to a secure enterprise payment hosted payment page, which handles the collection of sensitive payment information such as credit card numbers, then forward to Paysafe API to purchase and settlement.

Also generate accounting reconciliation report and interface file to feed into client applications.

Technology Stack: Angular, SpringBoot, Restful web service, MongoDB

1.8Integration of Advanced Education Application with Single Sign-on Site

Integrate with Government’s Single Sign-on site to leverage existing functionalities:

oSAML2 Authentication handshake between Single Sign-on Site and legacy application to allow citizen login Single Sign-on Site to access legacy application

oService card set up and profile web services

oAssociate citizen’s account in Single Sign-on Site with legacy application’s accounts

oSurfacing assessment letters in Single Sign-on Site

oEmail notifications to support status updates and assessment letters

1.9Address Validation Web Service

Provide Enterprise Address Validation which can be called by the Government’s various applications to validate postal code, mailing address etc.

Technology Stack: Regex, Restful web service, SpringBoot, Spring Batch, Oauth2, Oracle DB, Swagger, Mybatis

1.10Municipality Validation Web Service

Provide Enterprise Municipality Validation which can be called by the Government’s various applications to validate municipal information etc.

Technology Stack: Restful web service, SpringBoot, Spring Batch, Oauth2, Mysql DB, Swagger

1.11Business Entity Validation Web Service

Provide Enterprise Business Entity Validation which can be called by the Government’s various applications to validate business information. It is proxy service which to call third party service to validate from Canada Revenue Agency.

Technology Stack: Apache Httpd, Tomcat, Restful web service, SpringBoot, Oauth2, Swagger, Postgres DB

1.12Citizen Validation Web Service

Provide Enterprise Citizen information validation which can be called by the Government’s various applications to validate citizen information. It is proxy service which to call third party service to validate citizen.

Technology Stack: Apache Httpd, Tomcat, Restful web service, SpringBoot, Oauth2, Swagger

2.DXC Technology Inc., Winnipeg, MB Jan 17 – Oct 17

Senior Software Developer

Project: Bank Of Canada - Modernization of Bond Administration System (Rewrite the legacy Bond Admin system on Mainframe/DB2/CICS/COBOL/JCL into Windows/SQL server/Java). This multi-millions dollars project used Agile&Scrum methodology in development cross 2 years.

Application running on Apache Tomcat web server which deployed in cluster and in DMZ (De Militarized Zone) between two firewalls and accessed via HTTPS.

Responsibilities:

2.1System Design and Development of online and batch application components using technologies as: Java 8, JavaScript, SQL server, Tomcat, Spring Batch, Eclipse IDE, Spring Framework, JMeter, RESTful services (JAX-RS), AngularJS, Contexts and Dependency Injection (CDI), Spring Batch (JSR-352), Maven, Gradle, Google Guice, Hibernate, CA Autosys, PDFBox, JSON, XML, HTML, CSS, LOG4J, P6spy, WebSphere MQ, JBoss

2.2Developed java classes to access SQL data using Hibernate

2.3Developed user interface uses AngularJS on the client side and REST services (Jersey implementation of JAX-RS) on the server side, accomplished dependency injection by using JBoss Weld implementation of Contexts and Dependency Injection (CDI ) and Google Guice

2.4Developed batch jobs using Spring Batch

2.5Developed printing function using Apache PDFBox

2.6Used Apache Maven and Gradle as build tools, Package the Java EE application in an EAR (Enterprise Application Resource) file which contain JAR (Java Archive Resource) and WAR (Web Archive Resource) file(s). WAR files contain JARs and components related to Web deployments such as servlets, JSPs (Java Server Pages), Web pages, etc. JAR files contain Java packages and classes.

2.7Development Languages: Java, Groovy

2.8Environment: Mainframe z/OS, DB2, Unix, Oracle, Windows, SQL Server, WebSphere, MQ Series, CICS Transaction Gateway, LDAP, WSDL, Web Service, IBM 3270SNA, TSO/ISPF, DB2, CICS, Datasets/PDS, CS.N, INSYNC, SDSF, WS_FTP, FWB, XPEDITER, SQL/QMF, Hibernate, Spring MVC, jQuery, Bootstrap, HP ALM, Subversion, Junit, Jmeter

3.SUN LIFE, Waterloo, ON Dec 15 – Dec 16

Application Designer (Contractor) – Life Insurance Policy Admin System INGENIUM

Project of New Tax Regulation Change – System design and Development and Testing on Tax Exempt Test. Application running on Websphere Application server on AIX which deployed in cluster and in DMZ (De Militarized Zone) between two firewalls.

3.1Designed and Developed and tested new Tax Exempt Test component which add-on to existing Life Insurance Policy Administration system. The architecture is multi-tier with a browser-based presentation layer, an application logic layer and a relational data layer. The presentation layer operate within Websphere application server, to communicates with the online Mainframe application logic layer via WebSphere MQ calls. Well defined messages in XML are used as the transport mechanism for data that is the source or the result of a Business Function request. The application logic on mainframe which is pure server code in COBOL, is to execute Business Functions, then returns it back to the presentation layer with the results of that Business Function request.

The component is comprised of:

3.2New Tax Exempt Test Screens – web browser-based presentation layer of JSP, HTML, servlet, JAVA, which to view, update, delete Tax Exempt Record; invoke Tax Exempt Test function from server side

3.3MQ Message – which are the XMLs of Tax Exempt Test Input/output Parameters to/from Tax Exempt Test processor of server side

3.4Developed Tax Exempt Test web service which used WSDL + SOAP. Used SOIP UI as test tool

3.5Enhanced Business Activity Monitoring module (servlet) which is used to track events that occur during the execution of a process flow. It is implemented as a stateless session bean and is accessed using a standard EJB JNDI lookup. It uses the JMS (Java Messaging Service) API via JMS message queue to transmit event data to a MDB (Message Driven Bean), which then forwards the data to the Server EJB that logs the data to a database. JMX also performs operations on EJBs (e.g. clearing cache, reset definitions, etc.)

3.6Enhanced the processing engine (servlet) which is the dispatching mechanism that passes each request in a requests collection to the required data source for processing and packages the responses in a responses collection to be sent to the caller. It provides two processing engines: a single-threaded engine and a multi-threaded engine. The single-threaded engine services the requests in the collection sequentially in the same thread. The multi-threaded engine services each request in its own thread.

3.7Enhanced the Processing Flow upon receiving an Authenticate message, the servlet Connector will initialize internal state information (such as sequence number, valid security token etc.) for this connection. Business messages (transacted and transmittal) will then follow. For transacted messages, the servlet Connector will invoke the function that the messages are destined for and return the response from the function invocation to the client in a synchronous manner. If the unit of work completes successfully and a Commit message is received, the Connector will discard the transactions cached. If a Rollback message is received, meaning an error occurred and the unit of work needs to be rolled back, the Connector will retrieve all transactions from the cache for this unit of work and invoke the undo/reverse function defined in the configuration file for transactions that have the corresponding undo function defined.

3.8Development Languages: COBOL, Java, JSP/HTML/XML, Unix Shell Script, JCL

3.9Environment: Mainframe z/OS, DB2, WebSphere, MQ Series, CICS Transaction Gateway, LDAP, WSDL, Web Service, Unix sever, IBM 3270SNA, TSO/ISPF, DB2, ZEKE, CICS, Datasets/PDS, CS.N, INSYNC, SDSF, WS_FTP, FWB, XPEDITER, SQL/QMF, Charm, Serena Dimensions, Endeavor, HP ALM, StarTeam, Junit, Jmeter

4.GREAT WEST LIFE, Regina, SK Jan 10 – Nov 15

Senior Software Developer – INGENIUM

Great West Life acquired Canada Life and London Life, therefore the company has three independent Life Insurance Administration systems running on different platforms and databases and using different programing languages. In order to consolidate services and integrate systems, company decided to use one system as core backend system for new business and the other two systems to maintain existing business only. Also, to develop Java-based new business front end incorporated with underwriting rule engine to replace the core system’s mainframe CICS online system. Microservices architecture was adopted and the solution was based on Java Spring framework with Springboot and Restful services running on websphere application server behind firewall on intranet. Each legacy system wrapped existing functions and exposed as microservices such as Policy Details, underwriting histories, claim histories, policy tax exempt status etc. This multi-millions multi-year project used Agile&Scrum methodology in development and decomposed into many sub projects.

Applications running on Websphere Application Server which deployed in cluster and in DMZ (De Militarized Zone) between two firewalls.

4.1Product Services

Designed and developed Product component to provide product services Such as Retrieve Eligible Policy Products, Retrieve Eligible Optional Coverage product, Retrieve Investment Options, Calculate Premium, Validate Policy, Calculate Risk Amount, Retrieve Rates etc. The Application is deployed on Websphere Application server on AIX

Product component is comprised of multi-tier as

Application Tiers

Product component is implemented in two tiers as Application Tier and Database tiers. Application tier includes the product java archive that represents product components Services and Business Logic components, it is available as a Java Archive (JAR) and to be hosted by applications that is indenting to use the component.

Database Tier

Product Database tier is based on the RDBMS techniques. This tier is implemented on DB2 UDB version 9.7. Product services have no business logic such as Stored Procedures in data tier. Database views are used to de-normalize relational tables where necessary.

Services / Business Logic Layer

Business Logic layer is developed using standard Java standard edition (JSE 6.0) with the use of open source Java frameworks such as Spring IOC. All the product services in business logic layer and data access layer together are available as a java API and bundled in the Java Archive file (JAR) for consumption.

Spring framework is used for managing dependencies within the internal product services using the inversion of control module. Spring is also used as aspect oriented programming within product and allows the consumer to apply and control aspects such as logging and levels of logging.

Data Access Layer

Data Access Layer is also implemented using Java technologies and ORM framework. Open Source framework Hibernate is used for implementing ORM. All the product services in business logic layer and data access layer together are available as a java API and bundled in the Java Archive file (JAR) for consumption.

Hibernate is an Object Relationship Mapping (ORM) framework used to implement the interactions to the Data tier. Hibernate uses JDBC to manage connections to the database and allows consumer to provide the JDBC connection using the container managed persistence approach such as WAS data source. Hibernate is also used for dynamic SQL generation based on the use of data objects. In the occurrences where Hibernate does not support in providing dynamic SQL, native SQL and HSQL (Hibernate SQL) are used to implement the business logic.

4.2New Sales Tool which is comprised of

Thin user interface - Mustache Templates with JAX-RS (Jersey) services using JQuery

Design and Developed static Web content using pure HTML, CSS and JavaScript, AJAX (Asynchronous JavaScript and XML) augmented with the template solution available from JavaScript library Mustache.js making most of the presentation resources as static and allowing them to be cacheable by multiple levels of caching.

Pure data is transferred over the network using lean JSON data from JAX-RS services.

Server side business logic

Design and Developed RESTful services to focus only on business logic which support in providing functionalities especially to embrace the disruptive space of mobile and tablet applications.

4.3Java batch Jobs

Built over the Open Source QUARTZ Scheduler which comprised of scheduled jobs of

-Retrieve Placed Policies

-Daily E-mails

-Weekly E-Mails

-Stale Applications

-Restart Failed Apps

-Record Accepted Policy

-Vendor Outbound Requests

4.4Designed and Produced Design Statement for B2B: To provide CLIEDIS-CITS (Canadian Life Insurance EDI (Electronic Data Interchange) Standards - Canadian Insurance Transaction Standardization) compliant data feed electronically from Ingenium to Distribution Partners

4.5Developed and Tested for Face Page: Policy Face Page, Policy Provisions and an image of the application form and supporting documentation used in the assessment of the client’s insurance, together with the Acknowledgment Receipt to the policy owner after the policy is put in-force. The package also include a Premium Letter if the payment received is either greater or less than the minimum premium required to issue the policy.

4.6Developed and Tested for Cheque Processing: Provide a mechanism to store, track, account for, and automatically apply spot and post-dated cheques for an unlimited number of future billing modes. Cheques are accepted for all policies either list billed or regularly billed policies.

4.7Designed and Developed and Tested for Plan changes: Be allowed between plans of the same “product family” (E.g. Whole Life to Modified Whole Life) and between plans of a different “product family” (E.g. Whole Life to Endowment). Various rules apply depending on this, participation or non-participation and whether or not the plan being changed to is currently sold.

4.8Designed and Tested for Inter-System changes for Valuation System: Changes to the Valuation extract and reporting functionality of the policy administration to support the new series of Universal Life II products.

4.9There are various Valuation Extracts and Reports produced from the Ingenium system on a weekly, monthly and quarterly basis:

-Valuation (NOVA) extracts

-Investment Reporting (IV)

-Waiver of Premiums Feed

-Insurance Control Report, Policy Waived extract, Coverage Waived extract and Unmatched extract

-Data for Balancing OSFI to Valuation

-Valuation ACB Report

-Ingenium Internal Fund Report

4.10Designed and Tested for Death Claim Business Process for the changes on:

-Reversing a Death Claim

-Base Calculations for Death Claims

-Additional Calculations for Death Claims

-Information Updated by Death Claim Processing

-Accounting Generated by Death Claim Processing

4.11Development Languages: COBOL, Java, PL/I, JCL, CL, Javascript

4.12Environment: Mainframe MVS, DB2, TSO/ISPF, DB2, CICS, BTS, IBM 3270SNA, XPEDITER debugger, FILE-AID, SQL/QMF, IBM Rational tools RSA, iSeries, Use Case, SpringBoot, Microservices, MQ, Rest service, Subversion

5.HP CANADA, Toronto, ON Jul 07 – Sep 09

Consultant – INGENIUM

Application running on Weblogic Application server

Project: 6.5 implementation project for Prudential of Taiwan

Description:

5.1Provided support to the Model Office area by gathering and defining business requirements and creating functional specifications and technical specifications. Be responsible for providing business and technical expertise in the areas relating to project development on the INGENIUM system. Mentored and provided excellent consulting services to the Technical and Model Office team members to aid in their technical development and understanding of the INGENIUM system.

Responsibilities:

5.2SegFund Premium Application, Loads and Commissions: Modify base Ingenium to support target and scheduled Extra Premiums, Drop in extra payments, Front end loads levied against premiums based on policy payment duration instead of policy duration, commission is also paid on policy payment duration, not policy duration.

5.3ETI Processing: This enhancement define ETI Calculations that will be carried out by Product Xpress (PX), as an alternative to the existing COBOL-based Calculations in INGENIUM.

5.4New Complex Underwriting Tests: Tests to the Clear Case underwriting process need to be informed of such things as replacements, claims and high face amounts.

5.5Money Payment: Business need is to be able to enter all monies received from a Policy Payer from various payment channels on one page. The total amount received will then be allocated to various accounts and the account type will dictate the account to be utilized for allocation. The various payment channels accepted to be allocated for policy payments are: ATM, Cash, Credit Card and Cheque.

5.6Lapse and Permanent Lapse: Lapse processing is invoked on policies with a non-forfeiture option of APL, when the last APL has been processed and the final lapse date has been calculated. At the end of the 2-year reinstatement grace period, the status of the policy is automatically changed from Lapsed to Permanent Lapse and refund of the cash surrender value + interest on DOD is done.

5.7Development Languages: COBOL, Java, JSP/HTML/XML, Unix Shell Script, JCL, CL

5.8Environment: AS400/iSeries, DB2, ORACLE, WebSphere/Weblogic application server, MQ Series

6.NanShan Life Insurance Company, Taipei, Taiwan Jan 03 – Jun 07

Consultant - INGENIUM

Project: 6.4 implementation project

Description:

6.1Participated in Gap Analysis to gather and document client’s requirements. Prepared functional specification and technical solutions for NB, POS, Claims, Billing & Collection, Accounting and Disbursements processing on INGENIUM.

Responsibilities:

6.2Segregate Fund Product: Modify INGENIUM system to support segregate fund product, which include Fund processing for buying and selling, unitization, transferring, gain and loss, monthiversary charge, undo/redo, premium payment, fund accounting, termination and reinstatement, policy statement.

6.3Traditional Product: Modify INGENIUM system to support traditional product, which include waiver premium, dividend, coupon, ETI/RPU, maturity, loan and APL, policy change, automatic payout, surrender, major/ disability claim, lapse, reinstatement, undo/redo.

6.4Universal Life Product: Modify INGENIUM system to support Universal Life product, which include cash flow processing, monthiversary processing, undo/redo, termination and major claim.

6.5Billing and Collection: Modify INGENIUM Billing and Collection sub-system to support single premium, list bill, post-dated cheque payment, auto-pay.

6.6Data Conversion: To convert legacy Life Insurance Policy Admin System into INGENIUM via perform data mapping and conversion,Test of old policy in new system of online transaction, Daily Batch process, Weekly Batch process, Monthly Batch process, Quarterly Batch process, Yearend Batch process

6.7Development Languages: COBOL, Java, JSP/HTML/XML, CL

6.8Environment: AS400/iSeries, DB2, Weblogic, MQ Series, J2EE

7.Necho Systems Corp., Toronto, ON Jan 00 – Dec 02

Senior Systems Analyst

Description:

7.1Active team player involved in development of a global expense management automation (EMA) solution - Necho Expense, which is focused on helping mid to large, complex Governments optimize and manage their travel and expense policies and processes, based on J2EE technology

Responsibilities:

7.2Performed analysis and design of Expense Administration business modules using UML Use Case, class and sequence diagrams

7.3Performed application troubleshooting, remote debugging, deployment and server configuration

7.4Implemented presentation tier using Struts framework; JSP custom tags and Tiles feature

7.5Wrote Action programs and EJB programs to handle business transactions and validation

7.6Involved in development of system component integration and data conversion using XML

7.7Utilized Java 1.4, J2EE 1.3, Servlet 2.3, JSP 1.1, XML, Rational Rose 2002, Struts 1.1, Ant 1.x, WebSphere Application Server (WAS) 5.x, WSAD5.x, Oracle 7/8, DB2 UDB 7.x/8.x, Sybass, SQL Server, PL/SQL

7.8Development Languages: Java, HTML/XML/Java Scrip/JSP

7.9Environment: Windows 2000, DB2, ORACLE, SQL server, Weblogic

8.AIA Information Technology, GuangZhou, China Jul 88 – Aug 99

Senior Systems Analyst/ Programmer Analyst

Project: Individual Life Administrative System – LFCM (LIFE COMM)

Contact this candidate