Pega Developer

Responsibilities

• Act as the first line of technical support for project teams encountering platform bugs, environmental issues, or rule configuration roadblocks using tools like Tracer and Clipboard.
• Monitor application guardrail scores and review rule-sets across different business units to ensure compliance with CoE development standards.
• Help maintain, document, and promote the adoption of centralized, reusable components, data models, and UI templates across the enterprise.
• Aid in release and deployment assistance, assisting the CoE deployment leads with rule-set management, skim operations, product rule creation, and CI/CD pipeline deployments.
• Support the CoE in regression testing, impact analysis, and log monitoring (using PAL/PDC) during Pega platform upgrade cycles.
• Maintain the CoE wiki, document best practices, and help onboard junior developers or external vendors to the company’s specific Pega environment.

Qualifications

• Pega Certification: Pega Certified System Architect (PCSA) designation preferred; progression toward or completion of the Pega Certified Senior System Architect (PCSSA) is highly preferred.
• Hands-on Experience: 2 years of active development or technical support experience on Pega 8.x (or higher); Constellation experience is a plus.
• Enterprise Architecture Awareness: Strong understanding of the Pega Enterprise Class Structure (ECS), rule inheritance, and rule-set versioning.
• Diagnostics Toolkit: Proficient in analyzing Pega log files and using tools like Pega Diagnostic Center (PDC), Tracer, Clipboard, and Live UI to isolate issues.
• Platform Basics: Familiarity with Pega's security model (Access Groups, Roles, Privileges) and basic integration concepts (REST connectors and Data Pages).
• Software Foundations: Basic knowledge of SQL for database queries and an understanding of CI/CD concepts (such as Jenkins or Pega Deployment Manager).
• Service-Oriented Mindset: Strong patience and communication skills to assist and guide developers from various project teams.
• Attention to Detail: Analytical approach required to audit code quality and identify architectural deviations.
• Multitasking: Ability to handle support tickets from multiple projects simultaneously without losing focus on corporate standards.