Updated November 2026
Short answer
Vet a Salesforce developer by testing production evidence, not certifications alone. Confirm a Platform Developer credential, then run a live, time-boxed session on bulk-safe Apex, Flow-versus-code judgment, sharing and security, and a messy-org walkthrough. Check references from the same role, and score every candidate on the same weighted scorecard.
A developer can pass Platform Developer exams and still struggle when a trigger hits governor limits in a live org. The steps below move from credentials to a live work sample, then to references and engagement terms, so you compare every candidate on the same evidence.
On this page
Why Certifications Are Only a Baseline
Certifications show that someone has studied the platform. They do not show that the person can safely change a live org. Use each credential for what it proves, then ask for evidence that matches the work you need done.
| Evidence | What it proves | What it does not prove |
|---|---|---|
| Platform Developer I | Foundational Apex, triggers and Lightning Web Components knowledge | Production judgment or the ability to change a live org |
| Platform Developer II | Advanced development and design knowledge | Delivery on systems like yours |
| Trailhead superbadges (Apex Specialist, Advanced Apex Specialist) | Hands-on work in sandbox scenarios | Communication or maintenance skills |
| Portfolio or sanitized code sample | Coding style and design choices | Individual contribution, unless the candidate explains it |
| Live work sample | How they reason, test and debug today | Long-term maintainability |
| Technical reference | How they behaved in production | Current skill, if the reference is old |
Steps 1 to 5: Screen, Interview, Test and Verify
Step 1: Screen credentials and background
- Check credentials directly. Confirm Platform Developer I or II on the Salesforce credential verification page, and ask for the candidate’s public Trailhead profile.
- Look for hands-on superbadges. Apex Specialist and Advanced Apex Specialist require solving scenarios in a sandbox, which is harder to fake than a badge count.
- Match the clouds to your org. Ask which clouds they have run in production, such as Sales, Service, Experience or Marketing Cloud, and at what data volumes.
Step 2: Run a five-part technical interview
- Production experience: Which Salesforce clouds have you worked on in production, what did you personally build, and what was your role?
- Apex and LWC delivery: Walk me through one feature from requirement to deployment. What design decisions did you make, and how did you test it?
- Inherited environments: If you inherited an unfamiliar org tomorrow, what would you inspect before changing anything?
- Production troubleshooting: Describe a production defect you diagnosed. What caused it, how did you fix it, and what changed afterwards?
- Platform judgment: When do you choose a Flow over Apex? How do you avoid SOQL or DML inside loops, and how do you enforce sharing and field-level security?
Step 3: Set a time-boxed live work sample
Run a live session of about 90 minutes in a developer sandbox or scratch org. Keep it practical, and pay for the time where you can. Avoid multi-day take-home tests, which often turn into unpaid production work.
- Review a flawed trigger. Give them Apex with a SOQL query inside a for loop, and ask what breaks at 200 records and how they would fix it.
- Build a bulk-safe handler. Ask for a small trigger or handler with tests that cover positive, negative and bulk cases. Salesforce requires at least 75% Apex test coverage to deploy to production, but coverage alone does not prove the logic works.
- Test the Flow instinct. Include one requirement a Flow could handle. Strong candidates suggest the declarative option first and explain why.
- Explain the release path. Ask how they would move the change through source control (Git, with a pipeline tool such as Copado or Gearset), a sandbox and production, and how they would roll it back.
Step 4: Verify evidence and references
Ask for a sanitized architecture diagram or code sample where confidentiality allows, and confirm exactly what the candidate built personally. Then speak with at least two references, ideally a former technical lead who worked alongside them on production releases.
- Did they own the design, or implement a design someone else set?
- What broke on their watch, and how quickly did they fix it?
- Would you give them access to a live production org again?
Step 5: Vet the engagement, not just the person
Ask who manages the developer, who reviews their code, how technical decisions are documented, who covers absences, and how a replacement works if the fit is wrong. These answers matter as much as the coding test, because continuity keeps an integration healthy after go-live.
Weighted Hiring Scorecard
Score every candidate from 1 (poor) to 5 (excellent) on each row, multiply by the weight, and add the results to a total out of 100. Require evidence for every score, and treat security and coding quality as minimum requirements whatever the total.
| Category | Weight | What good looks like |
|---|---|---|
| Production experience | 20% | Named clouds, data volumes and a clear personal contribution |
| Apex and LWC depth | 20% | Bulk-safe design, decisions explained rather than recited |
| Flow-versus-code judgment | 10% | Declarative first, code where the platform requires it |
| Integration and security | 15% | Named Credentials, sharing, field-level security and secure callouts |
| Testing and deployment | 15% | Meaningful tests, source control, a rollback plan |
| Troubleshooting and inherited orgs | 10% | A method for diagnosing defects and auditing an unfamiliar org |
| Communication | 10% | Explains trade-offs clearly to non-technical stakeholders |
| Total | 100% |
Hiring Salesforce developers now? See how Folio3 CRM’s hiring service is structured, from team composition to engagement models.
See the Hiring ProcessIn-House, Freelance or a Vetted Team: Which Fits?
The same vetting steps apply to every option. What changes is who is responsible for the ongoing work and who covers the gaps.
| Option | Best when | What you still must vet | Watch out for |
|---|---|---|---|
| Hire in-house | You need long-term ownership of the org | The full five-part process, plus culture fit | Time to hire, and a single person becoming a point of failure |
| Freelance marketplace or vetted talent network | Short, well-scoped tasks | Production evidence, references, security practices, access and code ownership terms | Individual availability, and quality that varies by profile |
| Vetted team, such as Folio3 CRM | Hourly work, full-time teams, or delivery backed by architects and QA | Named developers, their certifications, replacement terms and code ownership | Confirm who reviews code and who covers absences |
How Folio3 CRM Vets Its Salesforce Developers
Folio3 CRM supplies Salesforce developers on hourly or full-time terms through its Salesforce developer hiring service. The page describes pre-vetted teams with hands-on experience across Sales Cloud, Service Cloud, Marketing Cloud and complex integrations, plus regular performance evaluations.
Each engagement sits inside a delivery organisation that includes certified architects, QA engineers and project managers. Developer work follows six stages, from discovery and strategy through to deployment and maintenance, with unit, system and UAT testing, as set out on the Salesforce development services page.
- 15+ years of CRM experience across platforms
- Full-time engagements with 100+ hours per month from certified Salesforce developers
- Replacement support if a hire is not the right fit [VERIFY written replacement terms before publishing]
- Pricing depends on scope, team size, experience and engagement model. No rates are published.
- Certification count: the hiring page shows 50+ Salesforce certifications, while the development services page shows 100+ [VERIFY before publishing]
Red Flags to Watch For
- Certifications listed, but no production project they can describe in detail
- Refuses to name the people who will do the work
- Writes SOQL or DML inside loops, or never tests for bulk data
- Reaches for Apex before checking whether a Flow would do the job
- Hard-codes record IDs or credentials
- Insists on a multi-day take-home test with no paid alternative
- Cannot explain sharing, field-level security or user mode
- Deploys through change sets or straight to production without source control
- No clear answer on who reviews code or covers absences
Questions to Ask Before You Hire
- Walk me through the last production feature you shipped: requirements, design, tests and deployment.
- What would you inspect first in an org you inherited tomorrow?
- How would you keep this trigger bulk-safe for 200 records, and how would you test it?
- When would you choose a Flow over Apex, and when would you not?
- How do you enforce sharing and field-level security in Apex?
- Describe a production defect you diagnosed. What caused it, and what changed afterwards?
- Who reviews your code, and who covers you during absences?
Frequently Asked Questions
What interview questions reveal real Salesforce production experience?
Ask candidates to walk through one feature from requirement to deployment, what they personally built, and what broke in production. Then ask what they would inspect in an org they inherited, and how they keep Apex bulk-safe. Strong answers name specific objects, the limit they hit, the fix, and what changed afterwards.
Are Salesforce certifications enough to prove a developer’s skill?
No. Platform Developer I shows foundational knowledge and Platform Developer II shows advanced development, but neither proves someone can safely change a live org. Use certifications as a baseline filter, then test with production evidence and a live work sample.
What should a Salesforce developer scorecard include?
A weighted scorecard covering production experience, Apex and Lightning Web Components depth, Flow-versus-code judgment, integration and security, testing and deployment, troubleshooting, and communication. Score every candidate on the same criteria, and require evidence behind each score.
How do you verify a Salesforce candidate’s past project experience?
Request a sanitized architecture diagram or code sample where confidentiality allows, and confirm exactly what the candidate built personally. Check their Trailhead profile, then speak with at least two references, ideally a former technical lead who saw their production work.
How Do You Vet a Salesforce Developer Before Hiring Them?
Combine credential checks with production evidence, a time-boxed live work sample on bulk-safe Apex and design judgment, a messy-org walkthrough, and two technical references. Score every candidate on the same weighted scorecard before you make an offer.
Want a developer who has already been through this process? Talk to Folio3 CRM about the Salesforce work you need built or supported.
Contact Folio3 CRM








