SUMMARY:

• Insurance professional with diverse experience across business systems analysis, application development, and technical writing including creation of training manuals.
• Knowledge of Software Development Life Cycle (SDLC) best practices.
• Approach includes first to thoroughly understand the business need(s) being supported and then conceptualize required data relationships as a means of understanding current technology and process flow requirements, as well as to expedite the pace of fully understanding new business needs and process flows.

TECHNICAL SKILLS:

• Agile, Waterfall and a mixture of the two methodologies.
• High level and deep dive process flow creation. Data mapping. User screen design. Have held Data Quality Assurance lead roles including test plan creation and execution. Defect logging and resolution. Business Intelligence (data banding, forecasting, etc). Experience spans health, life, and property casualty insurance.
• Technical Writing: Accomplishments include writing above mentioned requirements, use and test execution documents as well as training manuals, such as for a data aggregation application, and published work for Investopedia.
• Data field transformation, involving a large number of modules, and building an electronic funds transfer feature into an application. Comfortable working with vast amounts of data from multiple sources. Expert level development: ISPF, TSO, COBOL, CICS, DB2, SQL, JCL, Endevor,Xpediter, VBA for Excel. Other development: SAS, TOAD, VB, Java, and HTML with some C#. Can achieve an expert level in any of these.
• IT Controls: Experience implementing IT controls/ audit requirements resulting from the Sarbanes Oxley (SOX) Act of 2002.

PROFESSIONAL EXPERIENCE:

Confidential, Omaha, NE

Business Systems Analyst

Responsibilities:

• Collaborated with business experts to gather and document logical requirements and use cases in a structured format that was traceable to each other as well as back to the relevant application programs and functional business units.
• Built test plan execution plan derived from logical requirements and use cases. Test cases were traceable back to related requirements and use cases.
• Built code, to partially automate testing. Process included building techniques, including data banding, that are used in many current Business Intelligence applications such as Crystal reports.
• Executed test plan and created supporting documentation for test case validation/ problem resolution.
• Created regression test plan. Wrote code to put source data in expected format to be used in regression testing. Test plan is repeatable saving time and money.
• Wrote thorough training documentation for new application to be distributed to current and new hires. Collaborated with client subject matter experts to ensure clear written record of the new application.

Confidential, Bloomfield, CT

Business Systems Analyst

Responsibilities:

• Validated Teradata target data against Db2 and Oracle source data. Created procedures in Toad and SAS.
• All results were documented to show integrity between subsets of both old and new data.

Confidential, Windsor, CT

Senior Consultant

Responsibilities:

• Identified requirements for multiple lines of business such as Auto and General Liability.
• Ensured that use cases existed for requirements.
• Mapped use cases to requirements to ensure that all requirements have a least one use case.
• Performed post build testing of new application.

Confidential

Business Architect

Responsibilities:

• Gathered high level requirements
• Gathered high level use cases to be used to build user stories
• Mapped use cases to requirements to ensure that all requirements have a least one use case

Confidential

Requirements Engineer

Responsibilities:

• Gathered business and technical requirements detail through the use of interviews, SME meetings, and questionnaires with stakeholders and application SME’s
• Compiled the gathered requirements details into business, functional and technical specifications
• Business requirements and functional requirements that were collected were used in the creation of use cases and test cases. Granularity at the point of initial requirements gathering enables more detailed use cases and test cases enabling reduced risk at the point of implementation.

Confidential

Business Systems Analyst

Responsibilities:

• Worked with both business and technical SME’s to update additional business requirements into already existing documentation detailing how the new document storage application should behave under various scenarios.
• Amended existing documentation as part of a team effort.

Confidential, New York, NY

Technical Analyst

Responsibilities:

• Identify financial data used in reporting and other decision making processes.
• Tracked and identified data back to source of record on the legacy mainframe platforms.
• Captured and documented financial data, such as actuarial assumptions, that could not be tracked to source of record
• Produced Summary Document of finding including a health check with recommendations for improvement (such as using centralized data store to replace email as a data delivery system.

Confidential, Parsippany NJ

Business Process Collection/Mapping/Reporting

Responsibilities:

• Created/updated mappings of process flows across Confidential ’s global reinsurance business using Confidential ’s Industry Print process modeling tool.
• Converted completed process flows to HTML format to enable global business viewing via the internet.
• Maintained audit logs and organization of critical process flow documentation within SharePoint.
• Provided various reporting such as identifying historical sequence of process updates.
• Developed VBA for Excel modules to loop through multiple rows within Excel to automate report generation processing over large blocks of transaction data.

Confidential, Austin, TX

Business Systems Analyst

Responsibilities:

• Created end to end business process mappings, including identification of manual and automated inputs, of events related to target financial calculations.
• Analyzed and mapped incoming data back to its source. Data relationships were validated to be used in the development of the automated product.
• Provided consulting assistance to Quality Assurance team to ensure proper testing scenarios were identified and documented.
• Created thorough technical documentation of both current state and proposed future state process flows and data mappings.
• Collaborated as part of technical team in producing technology requirements specification for production of automated solution of financial calculations.

Confidential, East Hartford, Ct

Senior Developer

Responsibilities:

• Systems analysis and development of risk modeling application.
• Utilized systems/data analysis ability to gain a level of competence with object oriented risk modeling application provided by 3rd party vender, Vanguard Software Corporation, with no formal training. Technology area was newly developing where no formal training, documentation or audit processes yet existed.
• Data mapping to tie data back to the application. Approach taken was to extract much of the data on a field by field basis and then analyze how it mapped back to the application. This expedited the ability to grasp the application flow as well as the inter - programming module relationships.
• Development of code within the above referenced Vanguard tool which is an object oriented programming (DScript) application. Code requirements ranged from basic bug fixes such as ensuring data integrity amongst various file records, to developing a tool that imported the data, stored as objects into Excel for analysis. This required detailed data mapping to properly extract the object oriented data as much of it contained embedded lists and other idiosyncrasies that had to be properly broken up and formatted for proper import.

Confidential, Newark New Jersey

Business Systems Analyst

Responsibilities:

• Developed Access database (with underlying VBA code) that took in a client feed of legacy platform nightly job run data. Database was designed using ‘3rd Normal Form’ guidelines to ensure proper data integrity. Data was manipulated using VBA and the final database fed to Excel for the creation of heat map to display bottlenecks in the nightly batch cycle.
• Researched and documented business impacts of new and upcoming financial regulation (VACARVM, Sarbanes Oxley (SOX), Convergence of US and European accounting principles, etc.).
• Collaborated with technology architects in the creation of key deliverables regarding current state and recommended future state technology infrastructures.

Confidential, Harford, CT

Business Systems Analyst

Responsibilities:

• Verification of the accuracy of mortgage backed securities data in an SQL Server 2005 Analytics Cube that was being converted from older data warehouse technology.
• Creation of advanced SQL queries as well as Excel pivot tables to link to SQL Server environment to analyze data.
• Performing data analysis testing to confirm proper conversion to new data analytics cube. This was done via data extracts and bit level compares for accuracy.

Confidential, Pennsylvania

Business Systems Analyst

Responsibilities:

• Collaborating with actuaries in the identification of key business conditions that needed to be accounted for in test matrix during an actuarial unit conversion to the SunGard iWorks Prophet stochastic risk modeling tool.
• Providing support in installation of new financial modeling tool onto client’s server environment
• Quantitatively measuring and documenting the performance gain realized by the new stochastic modeling processes.

Confidential, Springfield, Massachusetts

Senior Developer

Responsibilities:

• Developed/Supported mainframe applications with tools such as CICS, DB2, and FOCUS. Highly experienced with JES/ACF2 mainframe environment. Strong data analysis/mapping skills. Able to track through data at the bit/byte level when analyzing a system during problem identification/resolution.
• Implemented all development work via Systems Development Life Cycle guidelines. Supporting documentation for all aspects of the SDLC, from initial analysis and requirements gathering, to testing and sign off, was written in a thorough, yet concise and easy to understand fashion.
• Developed applications using PC based tools such as Visual Basic, VBA, SQL, and MS Access.
• Strong data analysis/mapping skills. Tracked through data at the bit/byte level when analyzing a system during problem resolution.
• Collaborated with actuaries and other business partners in creation of design for specifications for needed changes within business processing.
• Coded complex financial calculations such as cash value and cost basis to be used in valuation of financial products (GUL, GVUL, etc.).
• Solid knowledge of regulatory requirements (SOX, Gramm-Leach-Bliley).