SUMMARY

• Outstanding technical and project lead able to pilot all teams to define and document scope of project, produce error - free and business-ready services, on time and within budget.
• With over 14 years Middleware experience, I have hands-on expert level knowledge of a wide range of Middleware applications, infrastructures, & programming languages; along with a strong passion for design and development.
• I've been with Chase for over 13 years in total, 5 of them spent in Data Mgmt & Quality both as a Data Steward, defining & certifying every aspect of a data element & as a DQ Rule Writer, monitoring every DS certified physical location to ensure the data found is as expected.

TECHNICAL SKILLS

EAI SOA Technologies: Web Services, WSDL, SOAP, XSD, XML, DTD, JMS, JSP, EJB, various Data transformation & Rule Engines, CVS, Clear Case, SVN

Web Services using: WebSphere Message Broker v7 (coded in ESQL), WAS & Composite Studio/ Designer (coded with JAVA), & Soap UI

WebSphere: MQ Series all thru v7, Message Broker all thru v7, Application Server (WAS) with Eclipse IDE, & Inter - Change Server

Programming: Java - including Spring & Hibernate, JavaScript, UNIX Shell scripting, MQ scripting, Control-M, ESQL, C/C++, SQL, PL/SQL, MS Access interfacing with SharePoint

Data Mgmt & Quality: 'Ab Initio' EME, ETL, MDR, MRDx, Express->IT DQE, JIRA

Databases: Oracle, DB2, SQL Server, Teradata, Access, JDBC/ODBC, TOAD, SQL Navigator, SQL Developer, SQL Plus, SQL scripting, PL/SQL, Teradata SQL Assistant

PROFESSIONAL EXPERIENCE

Data Quality Rule Writer

Confidential, Bordentown, NJ

Responsibilities:

• Using the 'Ab Initio' Express - >IT DQE rule engine, I wrote, tested, & promoted hundreds of rules to ensure data quality in the Mortgage Banking data. Rules without errors allowed the physical location to be certified; otherwise a JIRA would be opened to determine & fix the data issue found.
• When I joined this DQ team we had 3 people writing rules for Home Lending since HL accounted for over 70% of all LOB rules requested. Then in mid-Dec, we were down to just me & our team lead while our co-worker was on leave until May 2019. However, due to Chase cutbacks, we lost our lead on 3/22/19 leaving me alone to do the work of 3. I had to document (since none existed) & learned how to run all the daily MS Access jobs (Macros, queries, etc) which interfaced with SharePoint as the backend; all created by our lead & all totally new to me. I soon had to learn how to fix them when there was an unexpected system crash that caused many things to stop working.
• While quickly becoming the team lead, I assigned out priorities to resources made available to me, ran all the daily jobs (& fixed/changed when needed), was the point of contact for the HL LOB, created the weekly status report & ran the weekly meeting with the LOB, & still managed to write rules.

Data Steward

Confidential, Iselin NJ

Responsibilities:

• I became a Data Steward (DS) for Mortgage Banking Originations back when it was relatively new & small, since then it has grown from being just an MS Access DB front end with 'Ab Initio' Meta Data Repository (MDR) backend to now being a true online EME ETL DATA Database at the FIRMWIDE, LOB, & Multi\Sub - LOB levels. The MDR is intended to be as self-serve as possible for the end-user's needs now that it has grown so large & complete; yet still changing as SORs & Authoritative Sources (AS) move from Oracle to Teradata & Hadoop.
• Originally responsible for providing data mappings for projects - internal &/or external, government &/or legal related - depending on the needs and population of the data being requested. Then find, test, validate, & document the data needed to fulfil the project requirements & deliver those mappings to the requestor on time so they can begin to build their deliverable.
• As our 1st 'Ab Initio' MDR grew & later totally changed with the 2nd release of our 'Ab Initio' EME MDR, so did my role as DS. I was now responsible for defining every aspect of a data element including its Name& Definition (following new FIRMWIDE standards), the LOBs that use &/or own it, all physical locations where the element can be found - including the System of Record (SOR) & Authoritative Sources (AS) - and what data transformations occur as the element moves thru all these defined locations, & all Valid Values defined by each system and any relationships.
• Part of being a Data Steward is to request that physical data locations be profiled & to request that a specified rule be written to ensure data quality, These requests were submitted via SharePoint to be done by those specific teams. Both the profiling & DQ rules were coded using the 'Ab Initio' Express>IT tool.
• Once the rule was confirmed to be working as requested by the DS, the Rule Writing team would promote it to Production so that the DS could monitor the data for any fails. If any fails were found a JIRA ticket would be opened & worked by all teams involved as needed to have any issues fixed.

Oracle PL/SQL System Integration Developer

Confidential, Iselin, NJ

Responsibilities:

• A previous manager from JPMChase called me at the end of 2010 & asked if I would return to Chase to start another middle - tier application team using Oracle with PL/SQL on UNIX; knowing PL/SQL was a totally new language for me & therefore a great new challenge. In the 2 weeks before I started back at Chase I had bought 3 big books about PL/SQL & Oracle development & read all of them. That manager later told me that she knew how quickly I learn to work in new systems with new languages & how I always want to learn it all & that was why she had called me back to Chase.
• We started HLODS with just a concept, Real-Time replicated data available via Golden Gate from a Home Lending Oracle DB & a hardcopy of an existing nightly batch feed that we were to replace which made a lot of changes to the source data. A consultant & I designed, coded, & went live with HLODS, a Real-Time (RT) Pipeline process within 7 months which included more data & transformations for the target system than they had in the original batch feed.
• Once it went live, more interfaces were added, feeding a wide range of RT data to various internal systems & additional data was being added to the original Pipeline in every release. As we grew, my role went from being the primary developer to being the AD intake manager & lead developer. I became responsible for dealing directly with the different business groups, taking their desired requirements, designing codeable solutions & converting those into written TDDs. While managing both on & off shore resources, defining team structure, roles & responsibilities, I also distributed work evenly amongst the team & myself.
• Responsible for all AD intake work items through all aspects of the SDLC, I defined & executed a workflow for delivering error free code as well as all other deliverables required through each phase of the corporate defined SDLC.

Middleware Specialist Consultant

Confidential, Collegeville, PA

Responsibilities:

• Initially hired to migrate all of Confidential s IIM team s interfaces from MQ & WMB v6 to v7 as they moved to new HP TITANIUM servers. These interfaces included over 20 Web Services, a couple of Pub/Sub SAP to Oracle interfaces, a file transfer Java processing message flow & others.
• As an independent consultant, I designed, developed & delivered 5 key Developer Services using WebSphere Message Broker (WMB), v7 with ESQL, that allowed all on/off - shore developers to build WMB interfaces without allowing anyone access to the UNIX servers that host the Brokers, thus eliminating risk while meeting their aggressive timelines. These services (both Q2F based), MQGet & MQBrowse, allowed these developers to view/email the syslog entries & start/stop the Broker's User Trace. Each service allowed various input parameters for additional functionality.
• Using Composite Studio & Designer with JAVA & WSDL, designed, documented, created & provided SAP with 5 Web Services needed for their Approved Spending Limit (ASL) process. These Web Services allow SAP to lookup/validate an Employee, check an employee s ASL, and if needed, traverse up the ORG tree to return a manager that can approve an amount specified; as well as 2 ASL History Web Services to aid their support personnel in determining the cause of any ASL related issues.

Senior Systems Integrator/Middleware Application Developer

Confidential, Iselin, NJ

Responsibilities:

• As 1 of the 1st employees hired to build the new Middleware "HUB" team for Chase Home Lending, I played an instrumental role in designing and developing a standard Middleware Hub framework. This framework ran in a J2EE environment with WebSphere Application Server (WAS) in the Eclipse IDE, utilizing both Spring and Hibernate frameworks and was proven to be easily expandable to include MQ, JMS, SOAP and WSDL as provider or consumer.
• As Middleware technical lead (HUB PM) at Chase, I was responsible for moving 5 large scale projects through the complete development lifecycle and out to production, issue free and on time. This included working with the various internal LOBs and external vendors in gathering and documenting requirements, designing & creating all interfaces and Middleware components, & deploying these new Hub services thru the various UNIX test environments then out to production.
• After working to design & implement the EMI HUB framework, we developed all of our projects following this generic pattern beginning with gathering requirements and writing needed documentation to obtain business approval. Then using WAS in the Eclipse IDE, with or without MQ, coding JAVA application to obtain the inbound data (ftp file, or MQ Get), performing any file level validation and backup if needed, performing any record/message level pre - map logic needed, coding the JAVA MISMO maps & calling them for data transformation, finally performing any needed post-processing such as DB inserts, creating any output files/messages and sending them to given destinations.
• For the rare projects that didn t fit the Hub framework, I designed, developed & delivered services consisting of custom infrastructure and interfaces to meet the business needs. The first such project, Fraud batch processing, utilized MQ to communicate to external vendors. That project turned out to be so profitable that the 2nd phase, Fraud Real-Time processing, was moved up to 1 year. Phase 2 was much larger consisting of communication to more external vendors and internal lines of business using both MQ and some Web Services.

Senior Systems Integrator

Confidential, Chadds Ford, PA

Responsibilities:

• • As a consultant, I was the Senior Systems Integrator on numerous and various projects, including 3 large scale implementations (for SAP & HIPAA), where, in most cases, I was involved in the complete development life cycle. I've worked with clients, in a wide range of industries & infrastructures, from the design phase to production.
• • I have worked in complex environments of all kinds as a WBI/MQSI/ICS developer &, in addition to designing and building over 100 interfaces, I've also been responsible for working closely with clients to teach them interface design, development and on-going post production support of their System's integration.
• • Although my passion is in integration design and development, I have performed Middleware Admin duties in WAS, Msg Broker (WMB) & MQ. At times this was needed as part of development such as creating & configuring all needed WAS resources in order to code an application (MQ definitions, JMS/MDB settings, listener ports, DB/JDBC, etc) or creating/config MQ resources needed to create a Broker message flow. At other times, I had to step into the role of Admin at a client's request to design, build, &/or modify their infrastructure including all resources needed for their growing complex, high-volume, high-availability UNIX environments (MQ clustering, failover, external connectivity via transmission queues & channels, setting up triggering, ...).
• • As a key member on an SAP HR project, which lasted well over a year, I developed 26 interfaces - a majority of which went to various external vendors. I was one of the 1st people brought onto the project, to help get it defined & started, & 1 of the last to leave; occasionally called back to aid the client in fast development or production support.
• • I have provided Middleware production support for MQ and WBI/MQSI (Msg Broker) which included load balancing, high availability support, problem determination, & message tracking. I also created an application for a client to allow them to captured, replay/reprocess failed messages.