Pega BPM Technical Lead and Developer

Professional SUMMARY :

* ***** ** ** ********** in design and development of web based, distributed and enterprise applications by using PEGA BPM tool.

Worked in the healthcare, insurance and banking industries.

Coordinated across multiple technical and business teams to accelerate issue resolution.

Led requirement discussions with business partners to identify functional and technical needs.

Directed onsite/offshore coordination, ensuring seamless communication and timely delivery.

Served as a Technical Lead/Module Lead, acting as the primary point of contact for applications and interteam communication.

Kept project quality high by running code reviews and QA checks and analyzed requirements and delivered accurate estimates for upcoming project phases.

Managed Incident Management, Change Management, and deployment activities using tools such as JIRA.

Worked with Jenkins for pull request handling and CI/CD support.

Handson experience with Pega UI components such as Sections, Harness, Flow Actions, and Flows.

Utilized Splunk, Dynatrace, Pega Diagnostic Cloud, Pega SMA, and Pega logs for application monitoring, troubleshooting, and performance analysis.

Implementation experience across Pega 6, Pega 7, Pega 8, and Pega Infinity 23, including Case Management and latest platform capabilities.

Created and managed data instances such as DataAdminDBName, DB Tables, and implemented rules like ConnectSQL and RDB methods for external database integrations.

Developed background processing automations using Connectors, REST/SOAP Services, File Listeners, Job Schedulers, and Queue Processors.

Updated and maintained keys in Bitbucket repositories.

Troubleshot and optimized PRPC applications using tools such as Rules Inspector, Clipboard, Tracer, Admin Studio, Log Analyzer, and DB Tracer.

Gathered enhancement requirements, performed analysis, and delivered highlevel estimates for new initiatives.

Contributed to Pega upgrade projects across multiple PRPC versions.

Supported production activities including Change Management processes and documentation in Confluence.

Possess theoretical understanding of advanced Pega features including Constellation UI, Pega Blueprint, and GenAI functionalities.

EDUCATION

Master of Computer Application (MCA) from Andhra university

Certifications & Awards:

PEGA Certified Senior System Architect (CSSA 6.2 & 8.5v)

PEGA Certified system Architect(CSA 6.1)

Pat on the back award from AIG project

EMPLOYMENT EXPERIENCE

Working as senior application developer in Blue Shield of California from Mar 2023 to Sep 2025

Worked as a Pega developer in Infinite computer solutions(Client Molina healthcare) from Oct 2021 to Nov 2022

Worked as a Sr.Engineer in Anthem from Jan 2019 to Oct 2021

Worked as a Sr. Engineer in Virtusa Consulting Pvt.Ltd from Jul 2013 to Oct 2014

Worked as a Pega Developer in Pyramid IT Consulting Pvt.Ltd from Dec 2012 to Mar 2013

Worked as a Software Engineer in Venture SoftTech India Pvt.Ltd from feb 2010 to Dec 2012

TECHNICAL SKILLS

BPM Tools : PEGA (PRPC) V6.1, V6.2, V7.1, V8.4,V8.7,

Pega infinity 23

Programming Languages : JAVA, C and C++

Operating Systems : Windows Family.

RDBMS : Oracle 10g, 11g, DB2

DB Tools : SQL Developer

Web Technologies : HTML, XML, JavaScript

Web/Application Servers : WebSphere & Tomcat

IDES &Tools : ANT, log4j, Maven Eclipse 3.4, RAD7, JIRA

Project Details:

Employer:Blue Shield of California

Project:Medicare Enrollment Automation(MEA)

Role: Senior application developer

Environments: PEGA Infinity 23

Medicare Enrollment Automation (MEA) is the process of enrolling individuals aged 65 and above into Medicare.

The MEA application has two primary methods for enrollment intake:

Paper - manual data entry.

Electronic - either by file or service.

File intake is typically through a private exchange that provides their own enrollment interface for data collection, then submits a flat csv file to BSC via secure FTP. The file is then transferred via MQMFT to an MEA background node, into a folder with a listener. Once the listener notices a file, it creates an event, which triggers a queue process to retrieve the file, parse it, and create case records from the data. If the enrollment data for a case is complete and passes validation, the case is then automatically submitted to MAM and picked up for batch processing to downstream systems (EAM, Facets).

Service intake starts differently, with individual enrollment records pushed to the MEA Enrollment Intake service, which creates the record in MEA, then proceeds down the same path as file intake, however the OEC Enrollment service follows nearly the same path as file intake. It only differs in that a job within MEA is scheduled to run daily to call the service, which retrieves the records and generates a flat csv file that it saves to the file intake path, then a Tidal job transfers the file and the remaining intake steps are identical.

FILE INTAKE

1.CMS / OEC API and file intake

2.DRx

3.Private Exchange:

a.Alight

b.eHealth

c.Towers Watson Private Exchange

d.Sunfire

Project Responsibilities:

Completed the user stories in the sprint in a timely manner

Communicate accurate status of the stories to the scrum master in scrum ceremonies

Work closely with Business partners and stake holders this helped to develop more robust solutions

Take ownership of the stories end-to-end, right from requirement gathering, development, testing and implementation

Work with peers to share and exchange knowledge on business systems to create a better solution

Supported the maintanace activities to update the service keys in absence of AIP resource.

Participated in team meetings and scrum ceremonies

Performed some POC's and Implemented some key changes to improve systems in PEGA where we had session termination issues

Worked with Mypower users to fix access related issues

Supported deployments activities late hours for successfull implementaions ( Viz MEA, accumsrite, Mypower etc )

Worked on supporting accumsrite application.

Extended my support to offshore team to work on completing user stories.

Completed all the organisational tranings needed for my profile to be in compliance.

Employer:Infinite Computer Solutions

Client: Molina Healthcare

Project:Utilization Management

Role: PEGA CSSA

Environments: PEGA 8.4, 8.7, WINDOWS, IE 11, WAS, ORACLE, JIRA

Utilization management involves prior authorization.As part of prior authorization,it has different roles.

1.CRP(Care review processor)

2.CRC(Care review clinician)

3.MD(Medical Director)

4.CP(Correspondence Processor)

5.SP(Secondary Reviewer)

CRP receives patient details and route the case to CRC workbasket.CRC receives the case & verifies all the details, CRC has the ability to deny or approve the particular case.CRC can also route this case to MD.MD can either approve or deny the case.If MD needs additional information, MD will route back the case to CRC.If CRC approves the case, it will generate letter case & we can open that letter case from SP role. If CRC denies the case, it will generate letter case & we can open that letter case from CP role.

Project Responsibilities:

Implemented the column filtering feature using table optimization

Implemented iframe code to embed powerbi reports with in pega application(same screen)

Involving in the grooming sessions gathering business requirements

Involving in the presenting demo to product owners and business team

Involving in the code review and make sure follow the PEGA best practices

Involving in the daily scrum calls

Implemented different integrations like REST & SOAP services capture required details.

Involving in the UI design

Involving code deployments and create product file.

Employer: Anthem

Project:NICU,VA

Role: PEGA SSA

Environments: PEGA 8.4 WINDOWS, IE 11, WAS, ORACLE, JIRA

NICU receive the feed file from the BCBS and create NICU case and send notifications to nurses to get information’s new born child and mothers information and send MD’s to review. MD’s will take action based on information provided new child mother information.

Project Responsibilities:

Involving in the grooming sessions gathering business requirements

Involving in the presenting demo to product owners and business team

Involving in the code review and make sure follow the PEGA best practices

Involving in the daily scrum calls

Implemented different integrations like REST & SOAP services capture required details.

Involving in the UI design NICU application

Involving code deployments and create product file.

Employer:Virtusa

Project:One Claim NAM, HYD,India

Client:AIG

Environments: PEGA 7v WINDOWS 7, IE10, WAS, DB2

Role: Sr. Software Engineer

2013 Jul to 2014 Oct

1)UnderWriting 2) Specialty 3) Casualty 4) Fire and Marine

Underwriting is a term used by insurers to describe the process of assessing risk, ensuring that the cost of the cover is proportionate to the risks faced by the individual concerned.

I worked on the AIG customer underwriting module for the NAM One Claim project.

Employer: Pyramid Consulting

Project:Policy Administration

Environments: PEGA 6.1, WINDOWS XP, IE, WAS, DB2, HPQC

Client: WIPRO

Role: PEGA Developer

The Policy Administration Framework deals with the issuance of Homeowners Insurance for Personal Lines of Business. The Application begins by collecting the details from the customer who is applying for the Quote. The system automatically calculates the Premium on how much a Homeowners policy will cost an individual based on the coverage limits required by the individual. The customer is also allowed to select any Optional Coverage’s. If the customer is not satisfied with a quoted price, then another quote can be established with different criteria. Each quote is maintained with a Unique ID number and status of the quote for easy reference.

Project Responsibilities:

Implemented User interface like Flow Actions, Harness and Section rules.

Involved in the defect fix's

Involved in the Unit test creations and executions

Involved in the Use case documents preparations

Worked on different types of Agents like Advance and Standard Agents

Involved in the Integration concepts: Service SOAP and Connect-SOAP

Project Responsibilities:

Implemented User interface like Flow Actions, Harness and Section rules.

Implementation of activities, Connect-SQLs.

Involved in the client’s daily calls

Involved in the defect fix's

Involved in the Unit test creations and executions

Involved in the Use case documents preparations

Involved in the release notes preparation for the projects

Worked on different types of Agents like Advance and Standard Agents

Involved in the Integration concepts: Service SOAP and Connect-SOAP

Employer: VENTURE SOFTTECH

Project :dbCAR

Client:DuchBank

Role: CSA

Environments: PEGA 6v, WINDOWS, IE 11, WAS, ORACEL

Deutsche Bank is a German global banking and financial services company

DBCAR application is Deutsche Bank’s global solution for new customers on-Boarding with all personal details and supporting documents and location specific customer due diligence.

Project Responsibilities:

Functions as a member of an agile team and supports consistent development practices tools, common components, and documentation

Implementation experience on PEGA 7 Case Management and latest features.

Implemented User interface like Flow Actions, Harness and Section rules.

Familiar with Agile or other rapid application development methods

Involved in leading design team for web services (SOA) and GUI services for meeting both functional and non-functional requirements like extensibility, maintainability and scalability in PEGA Technology.

Involved in consume the REST connectors & SOAP connectors.

Involved in preparing presentations and demos for Product owners and business owners.

Involved code migrations in different environments.

Involved daily scrum calls and business requirements gatherings

Contact this candidate