The Experience Cloud resume: it's LWR sites and Agentforce portals now

Experience Cloud is one of the better-paid specializations in the Salesforce ecosystem — the portals, partner sites, and self-service experiences that sit on top of CRM data — and it has quietly changed shape. In 2026 it is no longer "Communities": it is an LWR-powered site runtime, a digital-experience identity layer, and, increasingly, an Agentforce-first self-service portal. A resume that still says "built a Salesforce community" reads as three years out of date and buries a skill that commands strong salaries. As with every Salesforce specialization, the move is to name the current stack and prove the outcomes.

What Experience Cloud is now

It is the platform for building external-facing digital experiences — customer help centers, partner portals, self-service sites, and microsites — all wired directly to Salesforce data and secured for external users. The two things that changed: sites are now built on the Lightning Web Runtime (LWR) for performance, and self-service is increasingly answered by an Agentforce agent instead of a human queue. Naming both is what marks you as current.

Name the Experience Cloud stack

An Experience Cloud resume proves itself in the platform's own vocabulary:

• LWR sites. Build Your Own (LWR) and Microsites (LWR) — high-performance sites built on Lightning Web Runtime — versus the older Aura-based templates. Knowing the difference signals you build on the modern runtime.
• Experience Builder and components. The declarative builder, plus custom Lightning Web Components, themes, and standard web skills (HTML, CSS, JavaScript) for pixel-perfect pages.
• External-user security. Community/portal licenses, sharing sets, guest-user access, and the record-level security that keeps external users seeing only what they should — the part that separates a real implementation from a demo.
• Personalization and content. Audiences for targeted experiences, CMS for content, and SEO for public sites.

Naming these is the difference between "built a community" and "owns the Experience Cloud implementation."

The 2026 shift: Agentforce-first self-service

The pattern that changed self-service is Experience Cloud plus Agentforce: a help center whose deflection is powered by an Agentforce service agent (or a Flow, or a hybrid that escalates to a human) rather than a support queue. If you have built that, feature it — it ties your portal work to the AI-skills story and to Service Cloud deflection, and it is exactly what employers modernising portals are hiring for.

From vague to specialist

Before: "Built a customer community in Salesforce."

Invisible to anyone searching for the modern skill.

After: "Built an LWR self-service portal for 40,000 customers: custom LWCs and themes in Experience Builder, sharing-set security for external users, and an Agentforce agent answering tier-1 questions — deflecting 45% of cases from the support queue."

Same domain — now it names the runtime, the security model, and the quantified self-service outcome.

Lead with portal outcomes

Experience Cloud work is judged on engagement and deflection, so trade activity bullets for outcome ones: self-service deflection rate, portal adoption and active users, case reduction, and page performance. "Built a portal" becomes "raised self-service deflection to 45% and cut portal load times in half." Those are the numbers a hiring manager scans for, and they clear the ATS.

Certifications

• Salesforce Certified Administrator is the platform foundation — list it first.
• Salesforce Certified Experience Cloud Consultant is the credential that proves the specialisation: site setup, templates, sharing and security for external users, and rollout. It signals you can design a digital experience, not just drop in a template — put it in full, per the certification roadmap, framed like the delivery work in the consultant guide.

Clear the filter

Cover the vocabulary — Experience Cloud, LWR, Experience Builder, Lightning Web Components, digital experiences, self-service, portal, sharing sets, Agentforce — the way we lay out in the ATS tips. Recruiters staffing portal builds search these exact terms, and a resume that says only "community" never surfaces for the modern role.

Keep the specialist story in one place

An Experience Cloud history — the runtime, the security model, the AI-powered self-service, the certification — is easy to flatten into "built a community" when you rewrite from memory. In the SFCV builder your roles, imported Trailhead certifications, and outcomes live together, so you can keep the Experience Cloud vocabulary current and aim a specialist version at each role on the jobs board.

Experience Cloud in 2026 is LWR sites and Agentforce-powered portals, not the Communities of a few years ago — but only a recruiter who can see that on the page will know you kept up. Name the runtime, prove the external-user security and the self-service deflection, and your resume stops reading as "built a community once" and starts reading as the specialist who builds the modern digital experience.