A Job Description That Wouldn’t Have Made Sense Three Years Ago
I was looking at a Salesforce architect posting recently. It listed Flow Orchestration, Einstein Trust Layer, agent design, data governance for AI workloads, and multi-system integration experience, all as requirements,
Multi-Agent Orchestration Isn’t an IT Problem
Salesforce's Summer '26 release ships next month and multi-agent orchestration is the headline. Multiple AI agents, coordinating with each other, running complex end-to-end workflows. Here's what that actually requires: someone
What “Passive Talent” Actually Means
The best Salesforce architects I know aren't on LinkedIn applying for jobs. They're the person their company calls when something breaks at 9pm on a Sunday. They're in back-to-back meetings
The Back Office Just Became a Salesforce Architecture Problem
Agentforce Operations just landed, and the scope of what a Salesforce architect is expected to own quietly got a lot bigger. Supply chain, procurement, finance. These aren't new problems, but
Headless 360 and What Salesforce’s New Architecture Means for Hiring
For the last 25 years, using Salesforce meant opening a browser. That assumption ended three weeks ago at TrailblazerDX. Salesforce announced Headless 360, and buried inside the architecture talk is
Agentforce Was Sold as Autonomous. It Still Needs Someone Who Knows What They’re Doing.
Agentforce was sold as autonomous. It turns out autonomous still needs someone who knows what they're doing. Salesforce recently added a deterministic scripting layer called Agent Script, essentially a structured
