SUMMARY:

• 12+ years of Strong Technical Experience in Design, Development of BPM BRE Applications/Solutions in Confidential .
• Experience as a Pega Developer in writing, debugging, creating flowcharts, coding, and documenting programs and with Business Rule Engine, Business Process Management process for Pega Rules Process Commander ( Confidential ).
• Excellent experience in Java, Servlets, Java Server Pages, EJB, Java Mail, JMS, Struts, Hibernate, Spring, JDBC, JNDI, XML, DOM, MQ - Series.
• Extensive knowledge in Design, Development, Migration and Deployment of Confidential (PegaRULES Process Commander) and Java/J2EE based applications.
• Designed Object Model (Class Diagrams), Functional Model (Use Cases, Sequence Diagrams) for software applications using UML with Rational Rose
• Experience in Eclipse, IBM Web Sphere, BEA Web Logic, Apache Tomcat and knowledge on EAI Tools like Web methods.
• Expert in Confidential construction and debugging tools such as Tracer utility, Clipboard, Application accelerators and Expression builders

SKILLS:

• pega pega ConfidentialQA
• Business requirements
• PEGA SCRUM
• Stored Procedures
• WebSphere
• Weblogic
• Java
• .Net business process engine
• SOA
• J2EE
• LANGUAGES
• English
• Fluent

PROFESSIONAL EXPERIENCE:

Pega CSSA System Architect

Confidential

Responsibilities:

• Experience in Confidential Pega Rules and Process Commander Development of flow, flow action, section, class, data model, activity flow, migration of ruleset and managing ruleset
• Followed agile model for project execution and task activity are updated weekly.
• Creation of Rules for Validation, Integration rules like Rule-Connect-SQL using methods like RDB save, RDB Open, RDB list, Creation of Work Objects, assigning to Operators
• Created Activities for implementing core Business logic
• Designing and developeing the Confidential application based on the requirements
• Performing Code review for offshore deliverables
• Involved in Bug Fixing Activities with System Architects.
• Involved in executing POCs to cater the business requirements.
• Maintaining project documentation and revision as and when required.
• Developing Activity, flow, section, class, data modle, Agent and other objects in PEGA.
• Sound skills in troubleshooting performance tuning of Confidential applications using Clipboard, Tracer, PAL, SMA and loggers.
• Development support for the existing application.
• Fixing existing application ticket, bugs, and runtime issues to ensure uninterrupted application processing.

Pega Lead System Architect

Confidential, Pittsburgh, Pennsylvania

Responsibilities:

• Work with business users to understand business requirement and ensure a feasible solution is provided.
• Involve in Confidential sessions to create Application Profile, Discovery Maps and Run the Application Accelerator.
• Involved in capturing Application Use Cases and Application Requirements as part of the Confidential sessions
• Create high level Process Flows, Data Model, Security, Access Groups, Ruleset Stack.
• Configured Case Type rules to design the hierarchy of sub cases and tasks.
• Worked on the Interaction Driver setup
• Created Intent tasks according to client needs
• Worked on the Provider and member authentication flows embedded as per business requirements.
• Worked on the customizing Confidential Composite Tabs.
• Worked on the configuring Confidential portals.
• Worked on the Dialog changes for flow action.
• Create reports using Report Definitions to provide real time reporting capability to Managers.
• Design approach to fetch updates from external downstream systems processing the complaint and move the case in Pega accordingly.
• Perform weekly analysis on PAL/PLA Reports to identify slowness/errors and optimize code.
• Perform code reviews before releases to ensure coding is done per standards and provide suggestions to optimize where required.
• Created Agents that run activities that support implementations which routes the work objects to the appropriate flow. pega, pega Confidential, QA, Business requirements, PEGA SCRUM, Stored Procedures, WebSphere, Weblogic, Java, .NetPega Lead System Architect

Confidential, Pittsburgh, Pennsylvania

Responsibilities:

• Involved in identifying the project stakeholder goals and defining project scope.
• Managed customer expectations for project outcomes to ensure full understanding of risks, trade-offs and scope alterations.
• Involved in using the OOTB features such as Confidential functionalities, In-bound correspondence.
• Identified business objectives and the corresponding business requirements.
• Created Business Use Cases and corresponding Atomic Use Cases.
• Led and facilitated Confidential sessions with impacted business unit SMEs to capture detailed project requirements.
• Followed up on parking lot items in timely manner with corresponding owners in order to get closure on the product requirements.
• Creation of activities for implementing the core business logic.
• Involved in designing the business and data flow designs using UML diagrams.
• Involved in configuring the Confidential gadget to embed the project as an embedded gadget into an existing application.
• Worked on timeout mechanism to handle the Confidential timeout when user spends more time in the portal.
• Extensively worked in generating reports using List View and Report definitions. business process engine, SOA, J2EEPega System Architech

Confidential, Pittsburgh, Pennsylvania

Responsibilities:

• Designed and developed Enterprise Level Architecture for common modules thus facilitating the reusability of code across the applications in the Enterprise.
• Had extensive knowledge in reporting using Summary View and List View.
• Proficiency in designing User Interface using Harness, Sections, HTML rules etc.
• Extensive experience in creating Activities, Decision rules, Declarative rules, Validation rules etc.
• Used SOAP, JMS, HTTP and RDB methods to interact with the database for database transactions.
• Worked on timeout mechanism to handle the Confidential timeout when user spends more time in the portal.
• Responsible to optimize and refactor code by conducting code reviews to ensure ease of maintainability and better performance.
• Responsible in assisting the build master team to co-ordinate with the migration process to other environments.
• Testing the performance of the application using PAL, DB Trace, Log Files etc.
• Responsible in designing a technical design document before start of each sprint to aide developers in implementing user story functionality.
• Involved in sprint planning preparing time estimates for user stories consumed during a sprint.
• Escalated the issue as necessary and facilitated resolution in accordance with existing procedures.

Pega Developer

Confidential

Responsibilities:

• Understand the future prospect and design the system accordingly.
• Discuss the design with Client.Help Offshore Team in Technical Aspective
• Code Review as per Standard Governance Doc
• Provided solution that will allow customers, agents, partners HSBC and Citibank to have a more direct access to AXA products, thereby increasing sales.
• Understand the current Business requirement.
• Implemented Class Structure using Confidential 's
• Designing flows for Notification, Configure Accounts, Configure Claimant
• Providing Solutions to fix Performance related Warnings Alert Log Issues
• Implemented Web Service for EForms.Help Offshore Team in Technical Aspective
• Code Review as per Standard Governance Doc.PAL check for every iteration.

Java Developer

Confidential

Responsibilities:

• Extensively involved in writing PL/SQL or HQL to implement Confidential Create Retrieve Update Delete data in Oracle Database.
• Implemented the Graphic User Interface GUI by coding in HTML5, CSS3, Bootstrap, JavaScript, jQuery, and jQuery UI.
• Extensively involved in writing JavaScript/ jQuery Ajax call to retrieve the data from the back-end then display on the screen in a well-organized way.
• Wrote JUnit test case for back-end logic implementation development.
• Wrote QUnit test code for JavaScript test case for front-end tests.
• Provide Log4J for QA, and communicated with QA for further modification.
• Modified the web.xml and inject Spring Security to ensure back-end security.
• Enhanced the doPost method in servlet to prevent multiple submission.
• Used Subversion SVN for version control, and JIRA for tracking bugs.
• Configured and set up JBoss 4.0 Server for deployment.