Pega RPA Developer

need US Citizen only at this time.

Role- Official Title: Pega Developer - 4 openings


Company: Allied Solutions


Onsite/Hybrid/Remote: Open to remote candidates. The current team is a mix of EST and PST, so they are completely open to time zone


Terms: Contract through end of September, potential for extension


Rate- $62hr C2C


Visa - US citizen only

Need Pega RPA Developers. Need to have PEGA RPA, REST API's, and either Java or .NET

Duties:


This will be all greenfield work. They are currently doing foundational work to get things stood up, but this person will come in will validate the architecture, ensure best practices are met, GitHub integrations, and help them move from proof of concept to production.


There are 3 buckets of work with the project and multiple processes to automate within each scope:

• Screen scraping on insurance websites. This is using the BOTS to execute the process of automated web verification. There are 24 processes to automate in this bucket.

• Document Management - Multi-processes will split large documents and move documents into different areas. The document management system will ingest the document, scan the document, and then split it into chunks associated by policy numbers or other various factors. So, people can send all pages in one email and then the system will automatically split out the docs. There are 3 processes in this bucket.

• Claims - There are 5 processes that are very complicated. It is system manipulation within their claims organization to reduce manual processes by agents and automating a lot of hands on keyboard type work. It also automates logging into systems and claim portals so an adjustor does not have to do it.

Required Skills:

• Experience with Pega Systems or Pega RPA. They are okay if someone does not have Pega RPA experience and just has experience with Pega Systems.
• Mid-level engineer, it does not need to be an architect or lead developer.
• Experience with Git/GitHub
• Experience with API integrations
• Exposure to some form of web-programming - frontend development, C#, Java, etc.

Preferred Skills:

• Industry experience is helpful but not required
• Experience migrating from UiPath to Pega RPA is required

Where to stretch: Open to candidates with Pega experience but no RPA experience. Would potentially look at a solid Engineer who has UiPath experience but not Pega.


Reason for Opening: Project to get the companies RAP tool off of UiPath and onto Pega.

Sizzle: Opportunity to be part of a large initiative for the company. These are business critical RPA processes they are moving.