A few weeks ago, I explored why the Salesforce Certified Technical Architect (CTA) is still worth pursuing in 2026. Speaking with CTA Svet Voloshin, the argument made was that it sharpens how architects think, communicate, and make decisions under pressure, ultimately making you a more complete architect. As the platform grows more complex, those qualities have become more integral â but that doesnât automatically mean the CTA is right for everyone.
Across the ecosystem, more architects are stepping back from the path as cost, time, and trade-offs come into question. And when you start looking closer, the hesitation feels less like doubt and more like rational reconsideration. After sitting down with Salesforce Architect Frank Mamone and asking other architects about the CTA, it was clear that the conversation was a lot more complicated. The CTA process may be valuable, but the certification itself? Thatâs where things become more nuanced.
Why More Architects Are Stepping Back from the CTA Path
The overall hesitation around the CTA isnât new, but it does feel more prevalent at the moment. It seems as though more people are looking beyond whether they can do it, and are considering whether they should. When you break down the reasons, the decision often comes down to a series of practical trade-offs rather than a lack of ambition.
One consistent theme Iâve noticed across the ecosystem is that the CTA isnât defined by its hefty price tag, but by the scale of commitment it demands.
In SF Benâs 2025 Architect Survey, the top reason architects gave for avoiding the CTA was the time and effort it required, which is hardly surprising. Preparing for the CTA isnât something that you squeeze into evenings over a few months. Itâs very often a multi-year process that runs alongside full-time work and personal commitments.
That mammoth challenge becomes even harder when the scope itself feels unclear. As Principal Technical Architect Justin Dixon puts it, the breadth of the CTA can feel disproportionate compared to what is actually needed to pass.
âI was heavily disappointed with how large the scope of the CTA can be, which makes preparing for it so difficult,â he said. âItâs not shared explicitly in an open way with candidates.
âI will say the first year of learning CTA was very valuable to me. Deep analysis, presentation skills, architectural thinking. But it then moved to just memorizing facts and spending hours drawing the same diagrams.â
For many architects, this introduces a friction around whether they can really justify investing years of focused effort into something that isnât fully defined.
Alongside the time commitment, questions around return on investment also surface. The CTA still carries prestige, and thereâs no denying that. But as our survey showed, relatively few architects are pursuing certifications primarily for financial gain. For many â especially those already established in senior roles â the incremental benefit feels less certain.
Salesforce and AWS Technical Architect Chris Unitt captured this issue well, saying: âI donât think itâs as valuable as it was 5-6 years ago, but still a very prestigious certification. I personally canât justify the effort.â
As Chris suggests, the CTA hasnât necessarily lost its reputation, but the gap between effort and guaranteed outcome appears to be wider than it may have been before, especially when its value depends on how well employers understand it.
Overall, all these factors point to the fact that more architects are avoiding the CTA for very valid reasons, not because theyâre intimidated by it by any means. Time, relevance, and ROI all come into play, and when those are weighed up, skipping seems like a strategic decision.
Is the CTA Training More Valuable Than the CTA Itself?
One of the most interesting perspectives comes from Salesforce Technical Architect Frank Mamone, who went through the process himself and got all the way to the CTA review board.
This opens up an important perspective where he has experienced the full weight of what it takes to reach that level, even if he ultimately didnât pass the board itself. And because of that, his view isnât that the CTA lacks any value, but that the value may not sit where most people expect it to.
âAfter I did it, I didnât find having the paper itself, the certification itself, brings any much value except probably in certain circumstances,â Frank explained. âIn general, I’ve never seen anybody ask for a CTA.â
He also pointed out that in most cases, hiring decisions are still made based on real-world experience rather than credentials alone.
âWhat I see in the market is that people will hire you based on your accomplishments⌠having a paper doesnât necessarily mean youâre accomplished, it means youâre accomplished getting that paper, which is a different thing.â
Where his view slightly shifts is when the focus moves away from the eventual outcome and toward the whole process â which is exactly what makes it valuable.
âIf you ask me about the training itself, that is absolutely invaluable. The objective is to solve a very difficult scenario in three hours with no internet or resources. So what does that tell you? Itâs completely unrealistic! It doesnât apply to the real world at all.
â[But] the learning process to get there⌠because itâs such a difficult bar to beat, itâs fantastic, itâs really worth it.â
As he mentions, that three-hour scenario doesnât reflect how real architecture works in practice. But rather than dismissing that, he believes it’s important to frame it as a training mechanism that ultimately will make you think in a different way.
âIn a real-world situation, what you do there in three hours you probably do in months â you have meetings, you get all the details. Here, youâre working basically on huge assumptions.
âIt forces you to think differently⌠normally people stray away from stuff they donât know, but here it kind of forces you to consider everything. It changed everything for me⌠The time it takes me to solve solutions is very quick, because Iâm so used to doing it so quickly.â
âIt was a way of thinking. I was considering everything â security, data, large volumes, all of that.â
Perhaps the most telling part of Frankâs perspective is how he frames success. Even without passing the board, does he still see reaching that level and getting that far as meaningful validation?
âAbsolutely, completely validâ, he said in response. âWhen you go to these boards, thereâs a lot of luck involved⌠you donât know what scenarios youâre going to get, you donât know who youâre going to get [as judges].â
Because of this, his advice is not to treat the CTA as the only true, valid outcome from the full journey you go on.
âDo the training as if youâre going to the board. Even if you want to go to the board and fail, it doesnât really matter at that point.
âIf youâre doing it⌠Itâs more about personal accomplishment. But itâs not going to give you a lot of leverage anywhere else. It will give you some, but not a lot.â
Final Thoughts
Itâs important that we note that this isnât a critique of the CTA itself or the architects who have or are currently pursuing it. The certification, of course, remains one of the most respected achievements in the Salesforce ecosystem, and for many, itâs still a deeply worthwhile path. If youâre looking for that perspective, itâs worth revisiting our earlier conversation with CTA Svet Voloshin, which explores exactly why it continues to hold value despite its obstacles.
What weâre seeing change is how architects weigh it rather than its prestige. The decision is increasingly shaped by the trade-offs we mentioned â the time it consumes, how it aligns with your career, and the true ROI. For some, those factors still clearly point toward the CTA, but for others, they donât, and that choice is becoming more deliberate.
Frankâs perspective definitely offers an important middle ground on this. The cert itself may not always deliver proportional external value, but the journey toward it can be transformative. In that sense, the CTA may no longer be a universal end goal. But the level it represents and the path it demands still matter just as much, if not more, than the destination itself.







