Pega Lead System Architect LSA

London
2 weeks ago
Create job alert

Adword

Job Title: Pega Lead System Architect (LSA)

Location: Remote

Job type: Permanent

Salary: Open to the market rates

Job Description

Experience: 10-14 years overall; 3+ years as LSA; 2+ Pega CS end-to-end implementations

Role Summary: Design Authority. Owns architecture, quality, performance, security, and DevOps; leads CoE standards and AI enablement.

Key Responsibilities

Own solution blueprint: case taxonomy, microjourneys, interaction flows, CSR Desktop, Knowledge, and Digital Messaging.
Define non-functional requirements (scale, resiliency) and node strategy: Queue Processors vs. Job Schedulers, background processing, caching.
Integration architecture: REST/JSON, SOAP (if needed), OAuth2/SAML, eventing (Kafka/JMS), idempotency, pagination, circuit breaker and retry patterns.
Data design: enterprise data model, data pages (scope, refresh), reference data strategy, data obfuscation and masking for PII.
UX strategy: Constellation (preferred) / Cosmos; accessibility (WCAG), localization/i18n, responsive behavior.
DevOps: Deployment Manager pipelines, product packaging/versioning, branching/merge policy, automated quality gates, rollback patterns.
Observability and performance: PDC operating rhythm, PAL/Alerts analysis, log correlation; performance test strategy and tuning.
Security & compliance: GDPR-aligned retention/erasure, RBAC/ABAC, secrets management, auditability, encryption at rest and in transit.
CoE leadership: guardrails & code review checklists, reusable components, reference architectures, developer onboarding and enablement.
AI initiatives: seed NLP/Email Bot, Digital Messaging intent/sentiment, GenAI-assisted CSR (summarization, knowledge retrieval), and governance (prompt/data policies).Must‑Have Skills

Pega CS depth: Interaction Portal, Service Cases, Knowledge, Email Bot, Digital Messaging (e.g., chat/WhatsApp) with production go-lives.
Constellation experience: view templates, regions, editable tables, data-reference patterns; or strong Cosmos with migration path understanding.
Integration design mastery: REST with OAuth2 (client credentials, auth code), error handling frameworks, request/response mapping, timeouts, retries, backoff.
Event-driven patterns: Kafka/JMS producers/consumers, correlation IDs, exactly-once/at-least-once semantics, dead-letter handling.
Performance engineering: PDC triage, PAL reading, DB indexing considerations, cache invalidation, node classification, queue throughput tuning.
DevOps at scale: multi-stage pipelines in Deployment Manager, artifact versioning, approvals, infrastructure-as-code collaboration, release governance.
Security engineering: Access Manager, attribute-based access control (ABAC) using Access When, field-level encryption/obfuscation, secure logging.
Testing leadership: PegaUnit strategy, scenario tests, contract tests for integrations, test data management, coverage KPIs.
Documentation & stakeholder management: architecture decision records (ADRs), trade‑off analysis, executive communication, risk management.Nice‑to‑Have

Customer Decision Hub (CDH) to power NBA in service context and next‑best‑service actions.
GenAI/Agentic AI in Pega (e.g., summarization, knowledge buddy/coach patterns) and NLP model tuning.
Telephony/CCaaS: Genesys, Amazon Connect, Twilio, NICE; CTI handoff and screen‑pop patterns.
Cloud ops (Pega Cloud, AWS/Azure) and enterprise observability (Splunk/Datadog/New Relic).
Travel/e‑commerce domain: booking amendments, refunds/chargebacks, partner/supplier support, fraud/risk workflows.Certifications

Mandatory: Pega Certified Lead System Architect (CLSA)
Preferred: Pega Decisioning Consultant, badges in GenAI, Digital Messaging, PDCIf you're excited about this role then we would like to hear from you!

Please apply with a copy of your CV or send it to Prasanna . merugu @ randstaddigital . com and let's start the conversation!

Randstad Technologies Ltd is a leading specialist recruitment business for the IT & Engineering industries. Please note that due to a high level of applications, we can only respond to applicants whose skills & qualifications are suitable for this position. No terminology in this advert is intended to discriminate against any of the protected characteristics that fall under the Equality Act 2010. For the purposes of the Conduct Regulations 2003, when advertising permanent vacancies we are acting as an Employment Agency, and when advertising temporary/contract vacancies we are acting as an Employment Business

Subscribe to Future Tech Insights for the latest jobs & insights, direct to your inbox.

By subscribing, you agree to our privacy policy and terms of service.

Industry Insights

Discover insightful articles, industry insights, expert tips, and curated resources.

How Many Cloud Computing Tools Do You Need to Know to Get a Cloud Job?

If you are aiming for a role in cloud computing, it can feel like the skills list never ends. One job advert asks for AWS, Terraform and Kubernetes. Another mentions Azure DevOps, PowerShell and ARM templates. A third throws in Docker, Python, Linux, CI/CD, monitoring tools and security frameworks. It is no surprise that many cloud job seekers feel overwhelmed before they even apply. Here is the reality most cloud hiring managers agree on: they are not hiring you because you know every cloud tool. They are hiring you because you understand cloud concepts, can design reliable systems, manage costs, keep things secure and support real workloads. Tools matter, but only when they support outcomes. So how many cloud computing tools do you actually need to know to get a job? For most roles, the answer is far fewer than you think. This article explains what employers really expect, which tools are essential, which are role-specific, and how to focus your learning so you look capable and employable rather than scattered.

What Hiring Managers Look for First in Cloud Computing Job Applications (UK Guide)

anding a job in cloud computing can be highly competitive — especially in the UK market where demand far outpaces supply in many segments. Whether you’re aiming for roles in Cloud Engineering, DevOps, Site Reliability, Cloud Architecture, Security, Data/Analytics, or Platform Operations, hiring managers screen applications quickly and with specific priorities in mind. Hiring managers don’t read every detail at first; they scan for critical signals in the first 10–20 seconds. These early signals determine whether your CV gets read more closely, whether your LinkedIn profile gets clicked, and whether you’re invited to interview. This guide breaks down, in practical terms, exactly what hiring managers look for first in cloud computing applications — and what you should emphasise in your CV, cover letter and portfolio to stand out on www.cloudcomputingjobs.co.uk .

The Skills Gap in Cloud Computing Jobs: What Universities Aren’t Teaching

Cloud computing underpins almost every modern digital service. From financial systems and healthcare platforms to AI, e-commerce, government infrastructure and cybersecurity, the cloud is now the default operating environment for UK organisations. Demand for cloud professionals has grown rapidly, with roles spanning architecture, engineering, security, DevOps, platform operations and cost optimisation. Salaries remain high, and vacancies remain stubbornly difficult to fill. Yet despite a growing number of graduates with computer science, IT and software engineering degrees, employers across the UK report a persistent problem: Too many candidates are not job-ready for real cloud computing roles. This is not a question of intelligence or motivation. It is a structural skills gap between what universities teach and what cloud jobs actually require. This article explores that gap in depth: what universities do well, what they consistently miss, why the gap exists, what employers genuinely want, and how jobseekers can bridge the divide to build sustainable careers in cloud computing.