I made the transition from low-code developer to Solutions Consultant at Pega around 90 days ago.
As a developer, I was asked WHAT to build. Requirements came down, tickets were made and completed, code was shipped, and I moved onto the next sprint.
An SC role is fundamentally different. And it took in-person training, shadowing my team across multiple accounts, and working new opportunities to understand why.
Learning Pega. Learning Clients.
The first 30 days were intense. In-person training was designed to give me breadth across the platform—case management, decision management, AI/ML capabilities, reporting, process intelligence. I went from being deep in one area to understanding the whole landscape.
But here’s what I didn’t expect: understanding the full platform doesn’t automatically tell you which parts matter to this client.
The Gift of a Good Team
Something I did not expect when I took this job, and what’s made all the difference—is how positive and supportive my team has been through this learning process. Asking “why” isn’t intimidating; it’s collaborative. When I don’t know something, I ask. When I make a mistake in approach, they course-correct me without making me feel dumb.
The casual group chat culture especially has been a revelation. It’s relaxed, genuine, and honest. People ask questions without ego. They share what worked and what didn’t. There’s no gatekeeping, no “you should already know this.”
That environment has made me comfortable asking dumb questions. It’s made me willing to learn in public instead of trying to figure everything out on my own.
That’s huge for someone transitioning into a new role. You’re not just learning Pega’s breadth or client dynamics—you’re learning in a community that actually wants you to succeed.
How My Mindset Has Changed
The in-person training taught me what Pega can do. Shadowing real accounts taught me what Pega should do for different clients.
It’s changed how I should approach client interactions too. Instead of jumping to “here’s how we configure case types,” I’m asking questions first. What are you trying to achieve? Why is this a priority now? What’s already frustrated you in your current system?
Those answers tell me whether I’m talking to someone who understands their own problem or someone who’s latched onto a solution.
The Learning Curve
In full honesty, I’m still learning what the answers to WHY actually are. The in-person training gave me the platform knowledge, but no training can teach you how to translate “we have a 6-week case backlog” into “they need workflow automation, intelligent routing, and probably some process intelligence” into “here’s the Pega configuration that solves it.”
After 90 days of in-person training, shadowing, real opportunities, and being part of a genuinely supportive team, I’m learning more about Pega’s capabilities, but more importantly, I am getting better at asking the right questions - asking the WHY.
What Advice Would You Give a New SC?
I’m curious…if you’re an experienced Solutions Consultant at Pega, what would you have told me on day one? What did you wish you’d known in your first 90 days?
I’m still learning—both Pega and how to be an effective partner for our clients. Would love to hear from the community.