Sr. Pega Developer

CORE SKILLS NEEDED

•            10 + years of total IT experience preferably progressive starting as programmer and growing into a Pega developer

•            At least, 5 years of progressive experience in Pega

•            Pega Certified with a CSSA

•            Broad based technology footprint (should have worked in various technology stacks: Cloud, DevOps, IBM, Oracle, UNIX, AIX, Windows, Java/J2EE, Databases, and Mainframe etc.)

•            At least 2-4+ years of financial industry preferably banking industry experience

•            CSSA’s experience must include high level architecture and roadmap delivery

•            Advanced verbal and written communication skills

•            Leadership attributes and experience

•            Effective analytical thinking skills, including summarizing information and clearly identifying key elements, patterns, results, or relationships

•            Experience with iterative development and the Agile methodology as it applies to software development.

•            Experience in working effectively with diverse internal and external contacts

Responsibilities:

•            Work on major projects of complex scope and features. Drives the technical task of identifying, analyzing, designing, and maintaining Pega solutions that align with documented business requirements, goals, and standards

•            Work as part of Scrum delivery team to code/integrate solutions of quality, standards and/or design patterns, within planned sprint timelines

•            Work on parallel efforts to transform legacy workflow applications to Pega

•            Partner with solution architect(s) and the Pega COE to deliver to architecture compliance guidelines, security requirements, and design and development standards

•            Ensure development of robust, scalable technical solutions with reusable components/common elements

•            Ensure the product delivery quality is in adherence to best practices and standards

•            Create new documents or modify existing documentation, including but not limited to, status reports, proposals or presentations, system diagrams, maintenance or change related documentation