The Salesforce developer’s toolkit has been rearranged from both ends. Flow now handles much of what once needed an Apex trigger, so a lot of automation is built declaratively, often by admins, and the end of support for workflow rules and Process Builder has left many orgs with a migration to plan. Meanwhile the code that remains is harder: integrations, large data volumes, Lightning Web Components with real JavaScript, and Agentforce actions that let AI agents call into the org. The Salesforce developer skills that matter in 2026 are less about writing triggers and more about knowing where code belongs and keeping a shared org safe.
This guide is for CRM leads, recruiters and hiring managers deciding who to trust with their org. Each skill comes with a question to ask, followed by the habits that make a developer easy to work with and an interview process that looks past certificates.
Core technical skills for Salesforce developers
1. Apex beyond the trigger
Every Apex developer can write a trigger. A strong one structures logic in handler classes or a trigger framework, uses asynchronous Apex well (Queueable, Batch and Schedulable) and handles errors so a partial failure does not leave records half-updated.
How to check: describe a nightly job that recalculates a value across every account in a large org and ask which kind of asynchronous Apex they would use, and why not the others.
2. Data modelling and query design
Choices made in the data model live for years. Good developers understand the difference between lookup and master-detail relationships and what each means for roll-ups, deletion and record access. They write selective SOQL that uses indexed fields, and they know the problems that come with large data volumes and record ownership skew.
How to check: sketch a new requirement, such as warranty claims linked to products and accounts, and ask the candidate to propose the objects and relationships. Ask what changes if a single account ends up owning a huge number of claims.
3. Lightning Web Components and JavaScript
LWC is standard web components with Salesforce services on top, so developers need modern JavaScript. Good ones use Lightning Data Service and wire adapters before custom Apex, communicate between components with events or Lightning Message Service, follow the Lightning Design System and write Jest tests for components.
How to check: ask when they would use a wire adapter, when an imperative Apex call, and how they would test a component that shows an error from the server.
4. Flow at a developer’s depth
Developers need to build, read and debug Flow, not just leave it to admins. That includes before-save and after-save record-triggered flows, fault paths, invocable Apex called from Flow, and the order of execution when several automations fire on the same save.
How to check: ask them to explain, in order, what runs when a record is saved on an object with a before-save flow, an Apex trigger, a validation rule and an after-save flow.
5. Security in code
Apex runs in system context unless told otherwise, so security is a coding skill. Strong developers choose with sharing or without sharing deliberately, use user mode in SOQL and DML or stripInaccessible to respect field and object access, and understand how Lightning Web Security isolates components.
How to check: show an Apex controller declared without sharing that returns records to an LWC on a community page, and ask what could go wrong and for whom.
6. Integration patterns
Most orgs talk to an ERP, billing or marketing system. Good developers know REST and SOAP callouts, store credentials in Named Credentials and External Credentials rather than code, and choose between synchronous calls, platform events, Change Data Capture, the Bulk API or MuleSoft depending on volume and timing.
How to check: ask what they would do to authenticate an outbound call to a partner API so that no secret appears in Apex or custom settings.
7. Source-driven development
Modern Salesforce work is driven from Git with the Salesforce CLI, scratch orgs or sandboxes and, on mature teams, second-generation packages. Copado, Gearset and DevOps Center sit on top. Developers need to know which metadata deploys cleanly and which, such as profiles, causes trouble.
How to check: ask what lived in version control in their last org, what did not, and what they did about the gap.
8. Debugging and limit analysis
Governor limits rarely fail in a sandbox with a few test records. Strong developers read debug logs fluently, use the Apex Replay Debugger, and can trace a CPU time or heap error back to a recursive trigger or an inefficient loop across automations.
How to check: give a trimmed debug log that ends in a CPU time limit error and ask where they would look first.
Working skills that separate good Salesforce developers from average ones
- Translating sales and service processes into design. Business users describe how they work, not what they need built. Good developers ask about exceptions, approvals and handoffs before touching the data model.
- Building what admins can maintain. The best developers leave clear names, descriptions on fields and Flows, and short notes on why code exists, so the admin who inherits the org is not afraid of it.
- Judgement on AppExchange versus custom build. A strong developer checks whether a managed package already solves the problem, and weighs its licence cost, data access and upgrade risk against building in-house.
- Following the release calendar. Salesforce ships seasonal releases that can change behaviour in an org. Good developers read the release notes, test in a preview sandbox and warn the team about anything that affects their customisations.
Salesforce skills rising and falling in importance in 2026
Rising
- Agentforce and AI features. Teams are building agent actions backed by Apex or Flow, and prompt templates in Prompt Builder. Developers need to think about what data an agent can reach and how its actions respect user permissions.
- Flow fluency for developers. With older automation tools out of support, developers who can migrate workflow rules and Process Builder into well-structured Flow are in demand.
- Security-aware Apex. User mode operations and Lightning Web Security have made secure defaults easier, and security reviews now expect developers to use them.
- Reviewing AI-assisted code. Agentforce for Developers and general coding assistants write Apex and LWC quickly, but they often ignore bulk behaviour, sharing and test quality. Spotting that is now part of the job.
- Event-driven integration. Platform events and Change Data Capture are replacing many point-to-point callouts, which needs a different way of thinking about retries and ordering.
Falling
- Aura and Visualforce for new work. Both still run in many orgs, so reading them is useful, but new components are built in LWC.
- Change sets as the main deployment method. They still work for small changes, but teams of any size now deploy from source control.
- Counting certifications. A long list of badges says less than one well-explained project.
Salesforce developer skills by level
| Area | Junior | Mid-level | Senior |
|---|---|---|---|
| Apex | Simple classes and triggers under review | Async Apex; trigger frameworks | Sets coding standards; designs for scale |
| Data model and SOQL | Adds fields and simple objects | Designs relationships; selective queries | Plans for large data volumes and skew |
| Lightning Web Components | Builds simple components | Uses Lightning Data Service; writes Jest tests | Sets component patterns for the org |
| Flow and automation | Builds simple record-triggered flows | Combines Flow and Apex; fault paths | Owns order of execution across the org |
| Security | Follows team rules | Uses sharing keywords and user mode | Leads security reviews |
| Integration | Uses existing integrations | Builds callouts with Named Credentials | Chooses integration patterns |
| Source and releases | Commits to Git with guidance | Works with CLI and sandboxes | Designs the release pipeline |
How to assess Salesforce developer skills in a hiring process
Map an object’s automation. Share screenshots or sandbox access for one object that has a trigger, two Flows and a validation rule. Ask the candidate to explain what happens on save and where they see risk. This reveals order-of-execution knowledge and the ability to read someone else’s org, which is most of real Salesforce work.
Review an LWC and its Apex controller. Prepare a small pull request with planted issues: a hard-coded record ID, a controller without a sharing declaration, no error handling in the component and a test that only creates data. Ask for review comments as if to a colleague.
Run a data model design conversation. Give a new business requirement and ask for objects, relationships and access on a whiteboard. Listen for the questions they ask before they draw.
Look at Trailhead with care. Superbadges involve hands-on work in an org and say more than module counts, but they still do not replace a conversation about real projects.
Red flags on a CV:
- Many certifications with no project or org described.
- “Salesforce development” with no clouds, objects or integrations named.
- Recent work described only in Aura, Visualforce or Process Builder.
- Agentforce listed as a skill with no action, prompt template or use case described.
If you are still writing up the role, our Salesforce developer job description covers the template and the split between developer and admin work. Zilo AI can help you hire Salesforce developers in India for the clouds you run, and the other IT talent we hire for includes the QA engineers and integration developers who work around a CRM.
Frequently asked questions
How much JavaScript should a Salesforce developer know?
Enough to write modern components comfortably: modules, promises and async/await, events and basic testing with Jest. Developers who only know Apex struggle with Lightning Web Components, which are now the default for custom UI.
Is Agentforce experience necessary for a Salesforce developer in 2026?
Not for every role. It matters if your company is building agents now. For other roles, solid Apex, Flow and security skills transfer well, since agent actions are built on those same tools.
Can a Java or .NET developer become a good Salesforce developer?
Often, yes. Apex will feel familiar, but governor limits, the multi-tenant model, declarative tools and the sharing model take time to learn. Give them a senior Salesforce colleague to review their early code.
Do Salesforce developer skills differ by cloud?
The core platform skills are the same. Service Cloud adds case routing and Omni-Channel, Experience Cloud adds guest and external user security, and CPQ adds its own configuration model, so name your clouds when you assess candidates.
If you are planning a Salesforce build, a migration off old automation or simply need more hands on your org, get in touch with Zilo AI and let us know which clouds you run and what the org looks like today. We hire for contract, contract-to-hire and permanent Salesforce roles.