r/SalesforceDeveloper

Salesforce is enforcing some contractual rule that employees accessing our org's experience cloud site cannot have community-based licenses and must have platform licenses instead. How would you approach this conversion? Our site exposes data based on the Contact/User relationship, but now that won't be the case for this population because that same relationship doesn't exist for platform users. Does anyone manage an experience cloud site that has both platform and community users logging in?

I've been thinking about a different way to learn Salesforce Admin skills, and I'd like some honest feedback from people who are actually learning/using Salesforce.

The idea is a 2D retro pixel-art career RPG where you're hired as a Junior Salesforce Admin at a fictional company.

Instead of:

>

you actually play the role of the Admin.

For example:

Sales Manager:
"I can't see any of my team's Opportunities. Can you help?"

You investigate the company's CRM, figure out what's wrong with the configuration, make a decision, and see the consequences.

As you progress:

• You gain XP and level up
• Your Admin skills improve
• You build reputation within the company
• You unlock new departments and increasingly difficult problems
• Coworkers interact with you through AI-powered conversations
• Missions become progressively closer to the kind of problems an actual Admin would encounter

I'm particularly interested in the gap between "I understand Salesforce concepts" and "I could actually walk into a company's org and solve problems."

Trailhead and Superbadges already do a good job with structured learning and hands-on challenges, so I'm not trying to make a Trailhead clone.

The question I'm trying to answer is whether a persistent career simulation/RPG would make practicing those skills more engaging and useful.

This is an early concept, not a finished product.

https://preview.redd.it/g1gooee94dkh1.png?width=1402&format=png&auto=webp&s=ea07e5c3aaee3884b5242308e49d314c2aba041c

For people currently learning Salesforce:

1. Would something like this actually help you learn?
2. What would you want the missions to involve?
3. Would you rather have realistic business scenarios or more traditional exercises?
4. What do you feel is missing from the way you're currently learning Salesforce?
5. And honestly—does this sound useful, or just like a gimmick?

I'd especially like to hear from people currently studying for the Admin certification or trying to get their first Salesforce Admin job.

Partner drops a CSV on SFTP every night, ~40k rows of order line items, we upsert into a custom object on an external ID through Bulk API.

Most nights a few dozen rows fail. Usually a lookup that doesn't resolve, sometimes an external ID with trailing whitespace nobody trimmed upstream. Bulk API hands back the error file, and right now that file lands in a folder on the same box the script runs on, where it is read by nobody.

So the org ends up incomplete and there's no sign of it from the inside. A report comes back short and there's nothing in Salesforce explaining why.

Trying to work out where failed rows should actually live. Write them to a custom object so ops can fix and requeue from the UI, push a rejects file back to the partner's SFTP and make it their problem, or fail the whole load once the error rate crosses some threshold.

Anyone built the requeue-from-UI version? Wondering whether it's worth it or whether it becomes a second product nobody maintains.

I have 5 yrs of experience in Salesforce development, certs and masters in USA. I have been applying for multiple job opportunities in the US, I don't know the reason but I get very few callback from the recruiters. Even if I get a callback they want to hire strictly Green card holder or a citizen. Even with a lot of technical experience and skills I face a lot of rejection based on my immigration. I don't know my options, maybe build a Salesforce product here in the US sell directly or move to a different country.

Im looking for a study mate to start learning Salesforce Development

Hello everyone , I have around 7 years of salesforce experience and from past one year I am working on Mulesoft integration also little amount of netsuite admin stuff . What kind of salary is out in the market . I feel the pay is very less what I am getting right now . Need your guys advice . Also is it safe to be in salesforce career itself or should I change the career ?

I’ve been trying to break into Salesforce, but almost every job I find asks for 2-3+ years of experience, even when it’s labeled junior.

And being based in a third-world country makes it even harder. There are barely any entry-level Salesforce opportunities locally, and most remote/international positions still want people with years of experience.

It feels like there’s no realistic way to get that first opportunity. Companies want experience, but how are freshers supposed to get experience if nobody hires freshers?

For people who managed to break into Salesforce from countries with very few opportunities, how did you do it? Is it even worth continuing down this path?

Any Salesforce fde’s here? I am interviewing for the role and have been invited for an half hour onsite interview , so need some advice and prep help!!!

Hi all,

I am new to Salesforce and I want to understand the best place to learn service cloud and especially routing and Omni channel different use cases along with flows and what certifications are recommended please help me

I’m looking for some honest advice from people who have made a similar transition in the Salesforce ecosystem.

I have 5+ years of experience working with Salesforce, primarily in QA and test engineering across Service Cloud, Sales Cloud, and Financial Services Cloud.

Currently, I’m working as an SDET, where my work involves Salesforce application testing, test automation, API testing, and building/maintaining automation frameworks using Playwright, TypeScript/JavaScript, and related technologies.

Over the years, I’ve moved beyond purely manual QA into automation and development-adjacent work. My technical experience includes JavaScript/TypeScript, Java, Playwright, Selenium, REST APIs, SQL/SOQL, Git/GitHub Actions, etc.

I also hold:
Salesforce Certified Platform Developer I
Salesforce Certified Platform Developer II
Salesforce Certified Associate
Salesforce Certified AI Associate

My question is specifically about the Indian Salesforce job market in 2026.For someone with my background — 5+ years Salesforce QA + current SDET role + Platform Developer I/II certifications — is transitioning into a Salesforce Developer role realistically achievable without starting from scratch?

I understand that QA/SDET experience doesn’t automatically translate into developer experience. I’m particularly interested in understanding:

How do recruiters/hiring managers view QA/SDET engineers applying for Salesforce Developer roles?
Does having 5+ years of Salesforce QA experience provide a meaningful advantage?
Would my current SDET role make the transition easier compared with someone coming purely from manual QA?
Should I target Salesforce Developer, SDET with Salesforce development responsibilities, or some hybrid role first?
What technical gaps would I need to close to be considered a genuine Salesforce Developer?
How important is hands-on experience with Apex, LWC, Triggers, SOQL, asynchronous Apex, integrations, and Salesforce DX?
Would building a few serious Salesforce projects/GitHub repositories be enough to demonstrate developer capability?

Has anyone here actually made the QA/SDET → Salesforce Developer transition in India? If so, how did you make the switch, and how long did it take?

I’m not looking for generic “yes, anything is possible” advice. I’d especially appreciate real experiences from people who have hired Salesforce developers or personally transitioned from QA/SDET into development, particularly in the Indian market.
My goal is to understand whether this is a practical career move and what I should focus on before making the transition.

I don't mean what feature you like the most. I mean the feature your org has become so dependent on that removing it tomorrow would cause absolute chaos.

For some orgs, I'm guessing it's Flow.

For others, it might be reports, validation rules, Apex, a particular integration, or some ancient piece of automation that nobody wants to touch anymore.

It got me thinking about how much of Salesforce architecture is built around dependencies that aren't always obvious until something changes.

The scary part isn't necessarily losing the feature.

It's realizing how many other things were built around it.

What's the one Salesforce feature your org absolutely could not live without?

And if you've ever actually had something deprecated or removed, what happened?

What approach and architecture would you choose for integrating Salesforce REST with an external system? The operations to be performed are GET and POST. The main question is whether APEX alone can handle all of this, or should we use Flow? Where should the Bearer Token be stored? How should we authenticate with the external system—using APEX or an External Service?

What are your thoughts and approaches to this topic?

Anyone who recently attended infosys AI interview for Salesforce Developer role? Need tips and tricks to crack AI interview. My past experience with AI interview was not good

Hi everyone,

I recently got shortlisted for a Salesforce LWC interview at Accenture and would really appreciate some guidance from those who have attended Salesforce Developer interviews recently.

My background:
Currently working as an Application Support Engineer.
I primarily support Salesforce production issues, work with incidents, user requests, debugging, and coordination with different teams.
I’m now trying to transition into a Salesforce Developer (LWC) role.

I would really appreciate your help with the following:

What LWC interview questions are commonly asked at Accenture?
Are there any scenario-based or coding questions I should prepare for?
How deep should I prepare JavaScript, Apex, LDS, @wire, imperative Apex calls, events, lifecycle hooks, and Lightning Data Service?
Are live coding rounds part of the interview?
If you’ve interviewed at Accenture recently (2025–2026), could you share your experience and the questions you were asked?

Any interview tips, preparation resources, or recent experiences would be greatly appreciated.

How you will teach me like junction object I m literally not getting it . Why we need to create it ?

Please give me simplest example .

fade up asking ai .

Like can you explain it simply cuz when I go to sales cloud to understand it . All I go blank 😞 . How do I understand it like I don't want to memorize I want to understand it better .

All I get till now is that if you want to look how much a products are linked to how many opportunities for that we have junction we can look up in related list for example we open opportunity record from there we can see how many products it has .

Anyone 🙏🏻

Hey again, quick follow-up since a bunch of you helped me out last time with the booth games thing, I really appreciate that!!

Disclosure: I work in marketing for the company behind this, and this is something I planned. Mostly just wanted to show you what became of the ideas you gave me so thank you for that.

So here's the context I skipped over before. The company I work for is a sponsor at Dreamforce this year, and for the first time we're actually putting our own product at the center of the booth instead of just showing up with a banner and hoping people wander over. It's called ChargeOn, a payment processing app that lives inside Salesforce. We've already got a handful of clients using it, but this is our very first time we are taking it to a big reveal on a big enough platform. So yeah, the pressure to not have a boring booth was very real, hence the whole post.

And if I talk about the goodies, we genuinely went a little overboard (since we are sponsoring for the first time, so wanted to make it a deal ngl). Not the usual pens and stress balls that end up in a drawer within a week; we sat down and actually picked stuff people would want to hold onto. Worth stopping by just for these honestly, even if you don't care about the product at all.

Anyway, that's how we landed on a small arcade-style runner game and a giant Jenga on the floor instead of the spin-the-wheel thing we were originally going with. honestly, a lot of it came from stuff people said in that sub, so credit where it's due (thanks all!).

On the product side, without making this a whole pitch, it handles payments, recurring billing, invoicing, all natively inside Salesforce. One thing we really cared about was keeping pricing reasonable since a lot of similar tools quietly get expensive once you actually need the advanced stuff, so yeah, that's something we leaned into.

If you're heading to Dreamforce and want to swing by, play the game, grab some goodies, or just say hi, would genuinely love to meet some of you in person. Happy to answer questions about the product too if you're curious; drop a comment or DM, whatever's easier.