Pega Lead System Architect @ Toronto, Canada Hybrid

Position: Pega Lead System Architect

Location: Toronto, Canada Hybrid

Duration: Long Term Contract

Detailed JD (Roles and Responsibilities)

Role Summary

The Pega Lead System Architect is responsible for the end-to-end architecture, technical design, development governance, and successful implementation of enterprise applications built on Pega Platform. The role provides hands-on technical leadership, translates business needs into scalable solution designs, guides engineering teams, and ensures that applications are secure, performant, maintainable, and aligned with Pega guardrails and delivery standards.

Key Responsibilities

• Lead scope definition, requirements analysis, solution architecture, functional and technical design, application build, testing, deployment, and production transition.
• Architect complex Pega solutions for case management, workflow automation, business rules, integrations, data access, security, and user experience.
• Own application architecture decisions, including enterprise class structure, ruleset strategy, reusable components, data model, deployment approach, and integration patterns.
• Provide technical governance through design reviews, code reviews, guardrail compliance checks, architecture checkpoints, and quality gates.
• Lead and mentor System Architects, Senior System Architects, developers, and technical leads; assign technical work and remove design impediments.
• Collaborate with clients, product owners, business analysts, program management, infrastructure teams, security teams, and integration partners.
• Ensure non-functional requirements are addressed, including performance, scalability, availability, security, auditability, maintainability, and operational support.
• Guide performance analysis and tuning using appropriate Pega diagnostic and monitoring capabilities, including Pega Diagnostic Cloud where applicable.
• Oversee integrations between Pega applications and enterprise systems using REST/SOAP services, messaging, file interfaces, databases, and other approved patterns.
• Support release planning, deployment validation, production readiness, post-release monitoring, root-cause analysis, and resolution of critical technical issues.
• Maintain architecture artefacts, technical specifications, decision records, deployment guidance, and knowledge-transfer materials.
• Identify opportunities to improve delivery through reusable assets, automation, platform capabilities, and Pega best practices.