When my company decided to move away from Salesforce and build our own stack, my first reaction was concern. Fifteen years of deep platform expertise — would any of it transfer?
It did. Almost all of it.
What I thought I knew
I thought I was a Salesforce architect. Apex, LWC, Flows, Governor Limits, deployment pipelines — these felt like the substance of my expertise.
When I started working in Spring Boot and gRPC, I expected to feel lost. Instead, I found myself solving the same problems I’d always solved. Just with different tools.
What I actually know
The patterns were the same. Event-driven architecture. Data modeling for scale. Service boundaries. Idempotency. Retry logic. Async workflows.
Salesforce had abstracted these things behind platform constructs. Moving to open source just made them explicit.
That’s the thing about deep platform expertise — if you’ve gone far enough, you’ve been solving distributed systems problems all along. You just had someone else’s API in front of them.
The shift worth making
Stop describing your expertise by what platform you use. Start describing it by what problems you solve.
“I design event-driven systems that route customer interactions across multiple channels” is more durable than “I implement Salesforce Service Cloud omni-channel routing.”
Both are true. One travels.
This is the first post in a series on platform-agnostic architecture thinking.