Lately I have been getting a lot of questions about the Pega career path, especially from people with a CLSA ambition.
Is CLSA certification still worth pursuing? Does experience matter more than certification? With Blueprint, Infinity Studio, AI-assisted development, Solution Builder and Solution Designer entering the picture, what happens to the traditional LSA role?
These are valid questions. The Pega ecosystem is evolving, and whenever new tools and roles arrive, it is natural to wonder whether your existing skills and career plans are still relevant.
So here is my perspective.
Experience or certification, which matters more?
There are normally two sides to this discussion.
One side says:
“CLSA is only a badge. I have years of real project experience, and that matters much more than certification.”
The other side says:
“I have 10 or 15 years of Pega experience, but many architect opportunities still ask for CLSA certification. Not having it is limiting my career progression.”
To me, both sides have a valid point.
Real project experience is irreplaceable. A certification cannot fully test how you handle production incidents, difficult stakeholders, performance challenges, security concerns, changing requirements, team conflicts or architectural trade-offs.
Those capabilities are built through experience.
At the same time, certification carries value. It exists to provide a recognized benchmark. It helps an employer or customer understand, at least on paper, that a professional has reached a certain level of specialization.
This matters especially in the job market. Many service-based companies position certified architects for customer engagements. Some customers specifically request CLSA-certified professionals, and certain organizations use certification as one of the criteria for role levels or salary bands.
That does not mean certification is the only criterion. Companies will still look at your years of experience, projects, responsibilities, communication skills and technical depth.
In simple terms – experience demonstrates your capability, certification makes that capability easier for the market to recognize. Both go hand in hand.
If you already have significant Pega experience and are looking to progress into architecture or leadership roles, CLSA remains a valuable career milestone.
Why is there so much confusion now?
The obvious reason is the AI wave.
AI-assisted development is changing how applications are designed and built across almost every enterprise platform. Within the Pega ecosystem, we are seeing Blueprint-led application design, Constellation adoption, AI-assisted authoring, Infinity Studio and new role-based learning journeys such as Solution Builder and Solution Designer.
Naturally, this creates questions.
Will junior developer roles remain relevant? Will senior developers still be needed? What happens to Business Architects and System Architects? And finally, is the CLSA role also going to be affected?
The existing skills are not suddenly disappearing. Someone still needs to understand case lifecycle design, data modelling, user experience, integrations, security, background processing, performance, reuse and enterprise architecture.
The tools used to do that work may change. A Solution Builder may use Blueprint and Infinity Studio instead of starting everything manually. A Solution Designer may work much closer to business outcomes using blueprint delivered approach. AI may accelerate the creation of application artifacts.
But nobody is taking away the Pega knowledge and project experience you have built over the years. The delivery model is evolving, and our skills need to evolve with it.
What happens to the CLSA role?
Personally, I see the LSA role becoming more important, not less important.
Blueprint can help teams move from an initial business idea to an application design at incredible speed. Solution Builders and Solution Designers can connect business requirements with the application design using blueprint delivery.
But someone still needs to make sure the complete solution is architecturally sound. Someone must evaluate whether the proposed solution is scalable, whether the data and integration architecture is appropriate, and whether security requirements are addressed.
Someone must also check whether the application follows reuse and modularity principles, whether technical debt is being introduced, whether the design fits within the wider enterprise landscape, and whether the solution genuinely supports the intended business outcome.
That responsibility does not disappear because AI can create application artifacts faster. AI may reduce the effort needed to build, but it increases the importance of deciding what should be built and how it should fit into the enterprise.
Blueprint also needs experienced architects. A Blueprint can provide an excellent starting point, but it still needs people who can validate the design, challenge assumptions, identify gaps and guide the implementation.
Going Beyond Delivery
The LSA should also take Pega’s capabilities beyond the development team. One of the important responsibilities of an LSA or Pega CoE is to bring Pega knowledge to business stakeholders, enterprise architects and other departments.
Think about a department still struggling with a legacy application. They may know the system needs to be replaced, but they may not know what the future application should look like.
Blueprint can help them visualize and reimagine that workflow very quickly. I have seen this excitement from business stakeholders in my own project experience.
But it takes an architect to connect that excitement with a practical, secure and scalable enterprise solution.
What should LSAs do now, aspiring or already certified?
Do not wait for every role name, certification path or examination pattern to settle before you start learning. The ship is already sailing.
It is better to get on board, and this applies whether you are working toward your first CLSA or you already have the certification.
Explore the Solution Builder and Solution Designer learning journeys. Understand Blueprint-led application delivery. Learn how Infinity Studio and AI-assisted authoring are changing development. Stay current with Constellation.
At the same time, keep strengthening the architectural foundations that remain essential: application architecture, case design, data modelling, integrations, security, performance, background processing, cloud and deployment architecture, enterprise reuse, and architectural decision-making.
The future LSA cannot be someone who only knows how to configure rules. The LSA must understand the business problem, design the right solution, guide the implementation and help the customer realize value.
A few pieces of CLSA preparation advice
The CLSA certification journey and examination format will continue to evolve along with the platform. We have already seen significant changes to the Build component in the recent version Infinity ’25.
With Infinity Studio and AI-assisted development becoming more central, it is reasonable to expect further evolution. We will need to wait for official guidance before drawing conclusions about future examination formats.
The fundamental preparation principles remain the same though.
1. Do not look for one perfect solution. Almost every business problem can be solved in multiple ways. The CLSA examination may present a business scenario with certain expected architectural considerations, but architectural thinking is not about guessing one predefined answer.
Your solution may differ depending on business requirements, industry constraints, security and compliance needs, expected volumes, performance requirements, existing enterprise systems, delivery timelines, and cost and operational considerations. Good architects understand the available options, evaluate the trade-offs and explain why a particular approach is appropriate.
Develop your reasoning skills, not just your ability to remember Pega features.
2. Do not rush into the certification too early. I say this based on my own experience. I completed my CLSA certification with around four years of Pega experience. It gave me confidence and helped my career.
But in the same team, there were customer resources with 10 or 13 years of experience who did not have CLSA certification, and they were still highly capable technical leads. Passing CLSA did not suddenly make me more experienced than them.
A certification does not make someone a senior architect overnight. CLSA should validate your growing architectural maturity, not act as a shortcut to seniority.
3. Do not postpone it forever. The opposite problem also exists. Some experienced professionals keep postponing CLSA because the journey looks difficult.
When you hear about a long Build examination window, the first thought may be, how can I spend so many days on one certification, it already feels stressful. Yes, it requires serious effort, but some achievements are valuable precisely because they are not easy.
Give yourself a realistic target. Decide you want to complete your certification within the next six months, divide the preparation into smaller areas, and make consistent progress. Do not rush, but do not keep postponing it either.
4. Prepare ethically. This is one point I feel very strongly about. Training, mentoring, study groups and preparation courses are completely valid.
A good trainer can explain architectural principles, help you identify knowledge gaps and prepare you to approach scenarios correctly.
But there is a clear line between helping someone prepare and helping someone complete the actual examination.
Please do not use institutes or individuals who promise fake interviews, examination answers or unauthorized assistance during the exam. Prepare properly and complete the assessment on your own.
You will be much prouder of the certification, and more importantly, you will be ready to carry the responsibility that comes with it.
CLSA is more than an examination
The real journey starts after passing the certification.
An LSA is expected to look beyond individual rules and even beyond one application. You need to guide teams, communicate architectural decisions, connect Pega with the enterprise landscape and help stakeholders understand what the platform can achieve.
With Blueprint and AI-assisted development, LSAs now have an even bigger opportunity to bring Pega into new departments, modernization programmes and business transformation initiatives.
Do not pursue CLSA only to add four letters after your name. Earn the certification, but more importantly, grow into its responsibility.
Be the LSA who helps others and grows the Pega estate.
