Job search
Pega Certification: Compare System Architect and Senior System Architect Requirements
Check Pega’s System Architect prerequisite and current Senior exam scope, then distinguish free mission learning, version equivalency and actual project experience.
Pega System Architect establishes foundational application-development knowledge. Senior System Architect adds enterprise reuse, debugging, performance, integration and security depth. Pega also sets a credential dependency: you must hold System Architect certification to earn Senior System Architect. Completing a learning mission alone does not supply that credential.
This comparison checks current public Pega exam, mission and policy pages on October 23, 2026, plus one employer's published requirements. We did not log in, complete training, inspect anyone's private credential record, book an exam or apply. The two completed examples are fictional planning records. Compare their reasoning with the responsibilities and exact credential wording in recent LandOffer.ai roles.

Check the current exam code and credential chain
The Pega certification catalog explicitly requires Certified Pega System Architect status to earn the Senior credential. That is different from assuming every platform's administrator or foundation exam is an optional first step. Check Pega's stated dependency before paying for the next exam.
The current catalog links both of these exams to Pega Platform '25, even while some other Pega tracks already list '26. The System Architect exam and Senior System Architect exam show:
| Current public detail | System Architect | Senior System Architect |
|---|---|---|
| Exam code | PEGACPSA25V1 | PEGACPSSA25V1 |
| Questions | 60 | 60 |
| Standard exam time | 90 minutes | 90 minutes |
| Published passing score | 65% | 70% |
| Languages listed | English, Japanese, Spanish, French, German, Portuguese-Brazilian | English, Japanese |
| Retirement date displayed | N/A | N/A |
An N/A retirement field is not a promise that an exam will remain available forever. Match preparation materials to the code you intend to take; do not relabel an older course or credential as '25 because the current catalog uses that version.
An existing System Architect holder should also read the preparation FAQ. It says the System Architect and Senior System Architect prerequisites can be in any version. An older System Architect credential therefore does not automatically create a requirement to buy the latest System Architect exam again before pursuing Senior. Confirm the actual credential record instead of treating course completion, a remembered pass or an unverified resume label as equivalent evidence.
Compare what the two outlines ask you to understand
System Architect's current eight areas are case management, data/integration, security, DevOps, user experience, application development, Insights, and Pega GenAI. Case management carries 25%, data/integration 20%, and application development 15%; the other areas account for the remainder. Its scope includes case lifecycles, routing, approvals, data validation, access relationships and testing concepts. It is not simply a tour of menus.
Senior's six areas are application development at 30%, case management and data/integration at 20% each, system administration at 15%, security at 10%, and user experience at 5%. The outline calls out rule resolution, circumstancing, ruleset versioning, locking, connector errors, performance investigation and access-control distinctions.
The practical difference is the decision you can explain. Configuring an assignment route is one task; deciding how reusable rules behave across business lines is another. A developer who can describe a successful configuration still needs to explain its dependencies, failure behavior and maintenance. Equally, the Senior title does not mean every certified holder has led a delivery team. Employer responsibilities and certification scope overlap without being identical.
The percentages describe exam coverage, not the percentage of a real workday spent on each subject. Do not turn a 70% passing threshold into permission to ignore a security or integration gap. Use the outline to identify what you need to learn and the project evidence you would need to discuss honestly. For example, a rule-reuse explanation should identify which application layers share the behavior and what change could affect another business line. A connector investigation should separate the error observed, the analysis performed and any approved corrective change. These are useful evidence questions even when no certification is required by the employer.
Separate free mission learning from the paid exam
Pega's May 2026 Academy update describes its missions as free. The exam pages link to the corresponding missions under Prerequisites. A mission is a structured learning path; its modules, challenges, exercises and tests are not the Pearson certification exam.
The current Senior System Architect mission says required items unlock its mission test and badge. It lists 44 hours 55 minutes including embedded mission time, while its summary displays a shorter duration. Use the inclusive total when reviewing the published scope, then allow additional personal study time. Neither duration promises that someone can become professionally experienced over a weekend.
The System Architect mission introduces application development using App Studio and Dev Studio. Pega's preparation FAQ recommends completing the corresponding mission and explicitly says passing its assessments does not guarantee a certification pass. We inspected public descriptions; account access, challenge instances and learning results were not tested.
Keep separate entries for the earned certification, mission learning, and actual project work. This makes an interview explanation much clearer than a single line saying “Pega completed.” Instructor-led classes may be useful, but no class price or exam-voucher inclusion was established in this review.
Worked asset: an older credential and a realistic attempt plan
Jonah is fictional. His stipulated packet contains a verified System Architect 8.7 achievement and no Senior certification. He wants to study for the current Senior '25 exam. This example assumes the older achievement is genuine; we did not verify a real person's records.
His completed qualification-and-purchase record is:
| Question | Recorded evidence or rule | Disposition |
|---|---|---|
| Is System Architect already earned? | Yes, version 8.7 in this invented packet | Retain the original earned version |
| Must it be '25 first? | Current FAQ permits a different prerequisite version | Do not repurchase System Architect solely for version matching |
| Is Senior already earned? | No; mission work does not establish it | Leave Senior off the earned-credentials list |
| Which preparation target fits? | Current PEGACPSSA25V1 outline | Study '25 gaps, especially rule behavior and performance |
| What purchase is planned? | One Senior attempt after readiness review | No booking yet; keep contingency separate |
Pega's current fee FAQ lists USD 190 per Pearson VUE attempt, with possible tax and confirmation during registration. Jonah reserves $190 for the initial attempt and $380 for two possible retries: $570 total before other charges. Avoiding an unnecessary System Architect repurchase saves a possible $190 initial exam charge in this example; it does not remove the need to study unfamiliar foundation topics.
His separate hypothetical failure calendar uses November 2, 2026 as the first exam date. It is a paper calculation, not an appointment, an actual failure or a recommendation to use the earliest retry:
| Hypothetical event | Calendar result under the current minimum waits |
|---|---|
| First attempt fails November 2 | Second attempt no earlier than November 5 |
| Second attempt fails November 5 | Third attempt no earlier than November 19 |
| Third attempt also fails | No fourth same-version attempt inside the 12-month limit |
The retake policy specifies three calendar days before a second attempt and fourteen after a second failure before a third. The limit is three attempts per exam version in twelve months, starting with the first exam taken. Each attempt costs the full fee. The policy places a fourth attempt one year after the first; Jonah must confirm the actual scheduling system's permitted date and time.
His finished memo reads: “Preserve my original System Architect record. Prepare for Senior '25 without buying a replacement foundation credential merely to align versions. Hold the first booking until I can explain rule behavior and performance-investigation gaps. A failed result changes the study plan as well as the calendar; reserving retry money does not make three attempts necessary.”
Worked asset: an employer requirement and a separate project record
The public EY Alpharetta/Dallas Senior System Architect listing displayed requisition 1750510, dated October 7, 2026, when read. That displayed requisition differs from the numeric URL identifier. The complete public description was available; we did not enter its application flow or establish a future vacancy status.
It requires Senior System Architect certification at minimum, with Lead preferred. It separately specifies a relevant bachelor's degree and five years of progressive related experience, three years implementing Pega with version/team conditions, four-year database and development-related requirements, two years leading Pega developers, and travel up to 25%. These are this employer's requirements, not Pega's universal certification prerequisites.
Nadia is a different fictional candidate. Her invented packet contains System Architect certification, 32 months of Pega Infinity implementation on a four-person team, 18 months leading Pega developers, and 52 months of database work. The records are scenario inputs, not private projects we inspected. Her completed comparison preserves both gaps and useful evidence:
| Requirement or duty in the posting | Stipulated packet entry | Completed assessment note |
|---|---|---|
| Minimum Senior credential | System Architect only | Senior is not earned; do not mark the requirement fulfilled |
| Three years implementing Pega with stated conditions | 32 months, Infinity, team of four | Four months below the stated duration; retain version and role dates |
| Two years leading developers | 18 months of Pega leadership | Six-month duration gap; do not replace it with general tenure |
| Database experience | 52 months, with query-review notes | Duration alone does not confirm the required database scope; verify both |
| Solution architecture and configuration | A proposed shared-rule design and an approved configuration-change record | Distinguish the proposal from implemented work |
| Debugging and delivery | Connector-error investigation notes; no retained performance comparison | Retain the investigation; do not invent tuning results |
Her finished project-evidence summary reads: “The configuration record identifies my change, reviewer and release boundary. The shared-rule document is a proposal, not proof of enterprise adoption. The connector investigation records the symptom and authorized analysis. A performance-testing result is absent, so I cannot claim a measured improvement.” No customer identifiers, confidential rules or production logs are reproduced.
Her decision is to keep the credential and experience gaps explicit while comparing other roles. She can study Senior material and improve the evidence index while leaving the identified requirements unresolved. Degree, progressive-experience detail, other technical conditions and travel remain separately unverified in this fictional record. The table is not a hiring or eligibility decision.

Preserve the credential version and the cancellation boundary
Pega's verification FAQ currently says certifications do not expire, while reserving the right to change that policy. It describes completing new mission content to achieve version equivalency and retaining earned-version history. An updated mission should not be represented as passing a new-version proctored exam. Record the original achievement and the learning update separately.
Before paying, choose the correct exam code, language and delivery mode. Both current exam pages offer Pearson test-center and online-proctored routes. Check actual appointment instructions rather than assuming a 90-minute exam is the whole time commitment.
The cancellation policy requires at least 24-hour notice and also tells candidates to contact Pearson one business day before the appointment. Late cancellation and no-shows can forfeit the fee; late rescheduling is also subject to forfeiture. Act early and retain confirmation instead of relying on a last-minute calendar edit. No appointment was changed for this article.
Use the verified credential chain to plan the next learning or exam purchase, and use real project evidence to explain your work. Then review recent roles on LandOffer.ai, save their actual requirements, and decide whether the next gap is certification, Pega implementation depth, or delivery experience. Keep the exam code, earned version, mission update and project contribution in separate fields so a future revision does not silently turn one type of evidence into another.
Sources and Further Reading
- Pega certification catalog and credential dependencies
- System Architect '25 exam
- Senior System Architect '25 exam
- Preparation and prerequisite-version FAQ
- Current exam prices
- Exam retake, cancellation and rescheduling policies
- Certification verification, equivalency and expiry
- System Architect mission
- Senior System Architect mission
- Pega's May 2026 mission update
- EY current published Senior System Architect requirements


