Profile

• More than12 years of IT industry experience encompassing a wide range of skill set, roles and industry verticals.
• Experience in leading and managing teams. Handled multiple roles Software Developer, Senior Developer, Technical Lead, Project Lead, Onsite Coordinator and Lead Systems Analyst.
• Over 6 years of Team Lead experience including project planning, Estimation and design, technical mentoring and oversight, managing and Leading Vendor teams, off-shore teams and on-site teams.
• Extensive experience with requirement analysis, design, development, customizations, testing and implementation of software applications.
• Proficient in analyzing and translating business requirements to technical requirements and architecture.
• Strong database skills, Object Oriented Programming and development knowledge.
• Proven experience in dealing with customer requests/issues and driving them to acceptable solutions.
• Proficient in Java, JSP, Applets, Java Script, J2EE, JEE 5/6, Spring 2.x/3.x, Hibernate 2.x/3.x, SOAP, JAX-RPC, JAX-WS, Web services, Restful, HTML, DHTML, JDBC, XML, EJB, JMS, LDAP, IBM Websphere application server, JBoss, UML, SQL, PL SQL, Oracle 9i, Apache Tomcat server, XSLT, XSD, TOAD, Mule ESB, Camel EIP, WSDL, AJAX, Postgres, Active MQ.
• Experience is developing web services integration and orchestration with Mule ESB.
• Strong in Design Patterns with excellent knowledge in object-oriented design and development
• Experience in developing web services with Apache CXF Framework.
• Experience in developing middleware adaptor to integrate between client facing application and vendor application using Apache Camel EIP framework.
• Experience in developing enterprise applications using IDE tools such as Eclipse, NetBeans, STS, RSA.
• Experience in using IBM Websphere Application Server 6.x/7.x/8.x, BEA Weblogic server 9.x/10.x and Apache Tomcat server 4.x/5.x/6.x/7.x
• Experience in creating connection pools, configuring JMS Server, creating topics and managing queues using JMS.
• Experience in EJB 2.0 for Session Beans, Entity Beans and Message Driven Beans.
• Experience in Unix Shell Scripting and Operational Jobs.
• Experience in SQL/PL SQL for report generation, data retrieval from the production database.
• Experience in using the open source tools Log4j, ANT build tool and JUnit test Framework.
• Experience in Release Management, Application Maintenance and Enhancements
• Hands on experience in QA Process and Methodologies.
• Customer-focused individual with excellent communication and negotiation skills.
• Proven project, people management, leadership and mentoring skills.
• Experience in Defect management, Defect Resolution.
• Executed software projects for Insurance, Banking, Retail, Telecom and Software industry.
• Good communication skills, interpersonal skills, self-motivated, quick learner, team player. Ability to work individually and with team.

Skill Set

Programming Language: Core Java 1.5, 1.6, 1.7

Methodology: OOPS, UML, AOP

Framework: Struts 1.1/2, Spring 2/3, Hibernate 2/3, Apache CXF, Log 4j, slf4j

Technologies: EJB 2, Servlet 2.3, JSP 1.2, JSF, JDBC 2.0, JMS, Junit, XML, HTML, CSS, AJAX, JAX-RPC, JAX-WS, SOAP, WSDL,XSLT, JQuery

Web-Service, Restful Services, Active MQ, LDAP, Sharepoint

Scripting Language: Java Script

Web Server: Apache Tomcat Web Server 4.0/5.0, vFabric

Application Server: BEA Web logic 8/9, Websphere 5/6

Operating Systems: Windows 2000/XP/7, Unix, AIX

RDBMS: Oracle 8i/9i/10i, SQL Server 2005, Sybase, DB2, Postgres

Enterprise Service Buses Mule ESB

Enterprise Integration Pattern Apache Camel

Reporting tools: CrystalReport10, Actuate 8, Business Object 6

Versioning Tools Visual Source Safe, Tortoise SVN and CVS

Build tools Apache Ant, MAVEN

Processes: Agile, Waterfall

Development Tools: Eclipse, STS, ClearCase, Rational Rose, Toad, Isql,

RTC, RPM, RSA, TRAC, MS VISIO, Jenkins, Splunk, SOAP UI

Functional Modules: Banking, Finance, Insurance, Security, Telecom, Retail

Professional Experience:

Confidential

Role: Senior Technical Lead

• WMS involves four major types of activities: managing the system, completing transactions, processing, and accessing information.
• Managing the system involves procedures such as adding users and establishing system codes.
• Completing transactions consists primarily of adding loans and entering payments into the system. Most of the activity within WMS involves completing transactions, and many system users complete transactions as their primary WMS activity. Users can be specialized in just one type of transaction, or they can have the ability to complete all major transaction activities. WMS allows you the flexibility to choose where and how transactions can be completed.
• Processing must be completed at the end of each day and month to finalize transactions in the system. Only a user signed on as the system supervisor can complete processing activities all other system users must be logged out of the system for processing to proceed. Most processing activities are automatic and essential for proper operation of the system.
• Accessing information occurs simultaneously with the other activities. During most WMS activities, users are able to access related information in the system databases to assist them with their work. Some users, for example customer service or support personnel, utilize WMS solely as an information resource, retrieving information to assist customers or track account status.
• Involved in understanding the existing system functionally and technically by way of training and discussion and self-study.
• Involved in Offshore-Onsite Coordination.
• Involved in Estimationand design of new CRs.
• Involved in coding and code review of New CRs.
• Involved in problem fixing during QA testing Cycle.
• Involved in design review meetings and code reviews of new CRs.
• Helped offshore in technical trainings and hiring process by way of tech discussion.
• Helped offshore team in understanding requirements and design artifacts for new requirements for various releases.

Environment: Java, JSP, Servlet, EJB, Oracle Server, Weblogic Server, JMS, Spring, Hibernate, SOAP Web Service, GIT, JQuery, XML, AJAX, XSLT, WINDOWS 7, UNIX

Team Size: 8 to 10

Confidential

Role: Senior Developer

Project: Pricing System

• Pricing system project is about building an adaptor which will act as a bridge between the Sterling client facing application Admin client and Vendor application PPSS application. Sterling system will externalize all the pricing details of various screenings to PROS. Admin client application will make a call to pricing system adaptor to fetch any pricing details related to any screening. Sterling has various types of screenings/screening types, which results in a screening instance. Each screening hasbase costattributes that may affect base cost though these could be separate screening instances.
• Below are few of the important pricing dimensions which help in determining the price:
• Product: A product is a business entity that may map to a single screeningmay have logic applied to it that results in one or more screenings being executed against a screening subject e.g. a county criminal product may result in 1 to N of 3,500-ish county-specific screenings being performed . A product will have a price associated with it.
• Profile: A profile is a bundle of screening options. A profile does not have to have a price associated with it
• Customer: A customer is an entity on behalf of whom Sterling conducts the screenings.Each customer has at least one account.A pseudo-hierarchy may be established between accounts, but ultimately every account belongs to a customer. Pricing rules can be established at the customer level which applies to all accounts for that customer or at an individual account level.
• Jurisdictional fees: Fee charged by the owner of the system of record e.g. the individual court system or specific DMV
• Vendor fees:Sterling may use zero or more vendors to fulfill a given screening. The amount charge by different vendor to fulfill the request is termed as vendor fee.
• Involved in design and development of Service schema and service definitions.
• Involved in overall design of pricing adaptor studying the functional and non functional requirements of Admin client Client Facing and PROS system Vendor Application .
• Designed the Web services using Java/J2ee for interoperability between heterogeneous systems.
• Involved in developing and review of Low Level Design like Class Sequence Diagram using MS VISIO.
• Actively involved in development of Camel Routes and transformers to integrate between various services.
• Involved in coding and code review of pricing adaptor and Junit code.
• Involved in unit testing, integration testing, QA and DEV support.
• Involved in data load and setting up QA environment studying the configuration document provided by vendor team.

Environment: Java, SQL Server, vFabric Server,Active MQ, Apache Camel, Spring, Hibernate, SOAP Web Service, Restful Services, Tortoise SVN, XML, XSLT, WINDOWS 7, UNIX, Maven, Agile

Team Size: 8 to 10

Confidential

Role: Senior Developer

• This project involves the effort of migrating the MVR application from TIBCO to Tomcat vFabric environment. Rewriting all the existing processes in Java using camel framework.
• MVR Application Adaptors performs application specific validations, convert request into canonical format and board onto service bus, accepts responses in canonical format from service bus and take action in client application.
• Service bus accepts request from client adaptors in canonical format,route the request as per laid down rules and accepts responses from ADR / MVR adaptors and provides responses to client adaptors.
• When a MVR request is presented for fulfillment on the client application, Validations/ rule checks are performed as applicable. If validation fails, necessary actions are taken in the application.
• Searches for states enabled on MVR gateway should be routed to MVR gateway List of States to be fulfilled by MVR Gateway Searches for states not enabled on MVR gateway should be routed to ADR. List of States to be fulfilled by ADR Gateway States enabled on MVR gateway should be configurable.
• Involved in requirement analysis and high level design with the design team and architecture team.
• Designed the Web services using Java/J2ee for interoperability between heterogeneous systems.
• Involved in developing and review of Low Level Design like Class Sequence Diagram using MS VISIO.
• Actively involved in development of Camel Routes and transformers to integrate between various services.
• Involved in coding and code review of services and Junit code.
• Involved in unit testing, integration testing, DEV and QA support and Prod Deployment.

Environment: Java, SQL Server, vFabric Server, Apache Camel, Spring, Hibernate, SOAP Web Service, CXF, Active MQ, TIBCO, Tortoise SVN, XML, XSLT, WINDOWS 7, UNIX, Quartz Scheduler, Maven, Agile

Team Size: 7 to 8

Confidential

Role: Lead SA

• This team is responsible for developing the architecture business, application, data to be delivered to the subsequent implementation releases.
• The MFI effort will build a new CFPA database Customer Financial Profile Accounts that will be hosted on the new Technical Platform ICP . It will store financial information for customers only. This will provide more reliable performance and improvements in functionality.
• CFPA will have its own Admin screens to be used by the internal Service Support team.
• Customer financial accounts currently in CFFD will be replicated to the new CFPA database.
• SFPP customer bank accounts will be migrated from the SFPP database to CFPA.
• CFFD will continue to store the encrypted credit card number until an external vendor solution - called Tokenization - is implemented late in Phase 1. At some point, card numbers will be removed from CFFD and the full credit card number will be stored only at the Tokenization vendor.
• CFPA will hold all credit card information except the full card number.
• Current applications that interface with CFFD will be redirected/rewritten to interact with CFPA. This includes SFPP AIS/AMS/PVC , Internal Cash, Mobile apps, Life, Payment Fulfillment CPS/MPA/SFBank , and PEP .
• The CFPA database will provide account data for Business Partner metric research.
• Build Customer Financial Profile Accounts database CFPA on Technical Platform
• Provide functionality to display and maintain customer accounts on Admin screens.
• Develop services for calling applications to access new database
• Build Add screens for users in the new acquisition process
• Migrate existing customer financial accounts from CFFD and SFPP to CFPA
• As a Lead System Analyst, I was responsible for leading both onshore and offshore development team consisting of around 15 java developers and 5 Automation testers. I was involved in Analysis, design, development, testing and implementation of all Web services developed By MFI Base Team to interact with new CFPA DB.
• Responsible for leading a project team which involves both offshore and onshore teams.
• Involved in requirement analysis and high level design with the design team and architecture team.
• Involved in sprint planning, buying stories and maintaining sprint backlog and story wall.
• Responsible for effective communication between the project team and the client. Provide day to day direction to the project team and regular project status to the client.
• Designed the Web services using Java/J2ee for interoperability between heterogeneous systems.
• Involved in developing and review of Low Level Design like Class Sequence Diagram using MS VISIO.
• Implemented the fleet of web service operations using Apache CXF framework for communication between CFPA DB and customer facing website applications and SF internal applications.
• Involved in TDD documents review and presentation to business team.
• Actively involved in development of Mule ESB flows and transformers to orchestrate between various web services.
• Involved in development and code review of web services and Junit code.
• Establish Quality Procedure for the team and continuously monitor and audit to ensure team meets quality goals.
• Provided technical training to offshore team on Mule ESB, Apache CXF framework.

Environment: Java, J2EE, Web-Services, Spring 3x, SOAP, WSDL, Postgres, Mule ESB, MS Visio, STS, Tortoise SVN, Jenkins, Splunk, TRAC, WINDOWS 7, Sharepoint, MAVEN, Apache CXF, Agile

Team Size: 25 to 30

Confidential

Role: Designer from

• Leads Distribution System AID: The primary purpose of the Lead Distribution System is to update 'Unknown' leads to either 'Prospect' or 'Client' so that the leads can then be sent to a designated system for final distribution. Secondly, the LDS user interface is used to review all leads before they are sent for final distribution. Finally, analyses of the leads generated can be performed using the various reports provided by LDS.
• The objective of this Application Information Document AID is to provide an overview of the Leads Distribution System LDS application. The AID describes the function, structure, and configuration of the application and its technical environment. This document also describes relationship of LDS with other applications with which it interacts.
• Analyzed system archiecture of LDS application to document in AID.
• Analyzed LDS application functionalities and validation rules to include in AID.
• Prepared data flow diagrams and flow charts for LDS application and included in AID.
• Involved in various maintenance activites of NYL while working in Offshore.
• Involved in team selection by technically evaluating new profiles.

Environment: Java, J2EE, Oracle, WAS, PVCS, WINDOWS XP, MS VISIO

Team Size: 1

Confidential

Role: Project Lead

• Responsible for leading a project team, developing solution and providing support to end users.
• Deliver new and complex high quality solutions to clients in response to varying business requirements
• Responsible for managing scope, planning, tracking, change control, aspects of the project.
• Responsible for effective communication between the project team and the client. Provide day to day direction to the project team and regular project status to the client.
• Translate customer requirements into formal requirements and design documents, establish specific solutions, and leading the efforts including programming and testing that culminate in client acceptance of the results.
• Utilize in-depth knowledge of functional and Technical experience in java/j2ee and other leading-edge products and technology in conjunction with industry and business skills to deliver solutions to customer.
• Establish Quality Procedure for the team and continuously monitor and audit to ensure team meets quality goals.
• Providing training to end users regarding application.
• Key projects handled so far include SQATOOL, QPACE, QAM, RADAR CBMS.
• Involved in measure GID releases of SQATool Rel 7.0 8.0 and RADAR Rel 4.0.

Environment: Java, J2EE, JSP, Servlet, Struts, DB2, WAS, RSA, RPM, RTC, XML, CSS, WINDOWS XP, AIX, Quartz Scheduler, Agile

Team Size: 8 to 10

Confidential

Role: Project Lead

• The objective of CBMS application is to provide a web based solution that provides a centralized repository that captures and provides a collateral repository of case studies/capabilities/skills/past briefings across industries, service lines. CBMS application helps in planning and tracking all activities related to Client Visit. This application is intended to be used by users across all business units and Primarily GBS GD India. The business objectives of the system are listed below:
• Captures the best practice for client briefings from past experiences
• Supports the team to follow a recommended process/template
• Provide a collateral repository of case studies/capabilities/ skills/past briefings across industries, service lines
• Provide intelligence to address specific client objectives by showcasing appropriate IBM capabilities and assets
• Focus on ensuring a high impact client briefing thereby the chances of winning.
• Provides standardized framework for all client briefings not just limited to GBS GD India. This includes: educational briefings, capability review, orals, due-diligence, project / account review
• Provide a recommended workflow with timelines triggers for different type of client briefings right from plan, prepare, execute to follow-up as part of the workflow, incorporate checklist that should help smooth planning execution of any client briefings
• Ready to use templates/documents/decks, collaterals
• As a Tech Lead, I was responsible for
• Responsible for leading a project team, developing solution and providing support to end users.
• Involved in Analysis of Requirements preparation of Requirement Specification Document.
• Converting Requirements into Design Documents, Preparation of Detailed Design Documents.
• Coding, Code Review, Configuration of Websphere
• Solving Production issues, Packaging application as Executable Jar War Files.
• Involved in Unit Testing and Preparation of Test Cases for System Integration Testing.
• Prepared Estimation Impact Analysis document

Environment: Java, J2EE, JSP, Servlet, Hibernate, Struts 2, Spring, DB2, WAS, AIX, RSA, RTC, XML, CSS, Agile

Team Size: 5 to 6

Confidential

Technical Lead,

Wipro Technologies is a software service provider software product development company, having prestigious clients across all verticals. I had worked for a measure client of finance Industry Statestreet Corp.

Confidential

Role: Tech Lead

• OSA Reporting application developed on OSA Framework. OSA reporting is a core asset management function for the investment management outsourcing business. It involves pulling the data from multiple data sources, deals with high volume dynamic data and has direct impact on service level to the firm's client. It is an effective and efficient solution in the form of a cohesive reporting framework. It is a key to differentiate the state street's offering to the institutional clients. This application supports both dynamic static report generation. Its main Functionalities include:
• Authorization: Access to all the client reports is controlled. The users have access to a number of reports from among those published on the portal. The entitlement information will be in the entitlement database APMD / Site minder .
• Involved in Analysis of Requirements preparation of Requirement Specification Document.
• Converting Requirements into Design Documents, Preparation of Detailed Design Documents.
• Coding, Code Review, Configuration of Websphere
• Solving Production issues, Packaging application as Executable Jar War Files.
• Involved in Unit Testing and Preparation of Test Cases for System Integration Testing.
• Prepared Estimation Impact Analysis document
• Supporting team on technical issues, updating manager with the status of project
• Investigated causes of SLA non-conformance with profilers, Oracle traces and SQL-LAB.
• Performance tuning, SQL query enhancements, code enhancements to achieve performance targets

Environment: Java, J2EE, Servlet, JSP, XML, WAS, Tomcat Server, Oracle 9i, Sybase, Actuate, WINDOWS XP, UNIX

Team Size: 8 to 10