Salesforce Developer Job Description | SalesforceTutorial

A salesforce developer job description should define the code, configuration, integration, testing, security, and release responsibilities that the role owns. A good JD also states the org context: clouds in use, custom Apex footprint, integration volume, DevOps process, and the level of production support expected.

This page gives hiring managers and architects a practical template for writing a salesforce developer job description that matches real Salesforce delivery work in 2026. It also helps candidates understand what a Salesforce developer, SFDC developer, or salesforce engineer is expected to do in enterprise orgs.

What is a Salesforce Developer Job Description?

A salesforce developer job description is the hiring document that explains how a developer will extend Salesforce beyond standard configuration. It should cover Apex, Lightning Web Components, integrations, data model changes, automated tests, deployment, and security review work. It should also state where declarative work ends and custom development begins.

Salesforce development is not only writing Apex classes. In many orgs, the developer reviews Flow design, builds invocable Apex only when Flow cannot meet the requirement safely, works with admins on permission sets, and checks whether a requirement can be solved with platform features before adding code. That context matters because a vague sfdc job description attracts candidates who may be strong in one area but mismatched for the actual work.

For a current technical baseline, align the JD with Salesforce’s official developer guidance for Apex governor limits, Lightning Web Components, user-mode database operations, and the Apex testing and code coverage rules. Salesforce requires at least 75% Apex test coverage for deployment or AppExchange packaging, and all tests must pass.

For release-specific requirements in 2026, verify the feature in the Salesforce Summer ’26 Release Notes or the release notes for your target org before adding it to a hiring scorecard.

Salesforce Developer Job Description Template

The template below keeps the salesforce developer job description specific without overloading it with unrelated administrator, architect, and support duties. Replace the bracketed items with your org details.

Role summary for a jd for Salesforce developer

Role: Salesforce Developer
Team: [CRM delivery / IT applications / Revenue systems / Customer platform]
Reports to: [Salesforce Engineering Manager / Technical Architect / Head of CRM]
Employment type: [Full-time / Contract / Remote / Hybrid]
Salesforce clouds: [Sales Cloud, Service Cloud, Experience Cloud, Data Cloud, Marketing Cloud, Revenue Cloud, or other clouds in scope]

Summary: We are hiring a Salesforce Developer to design, build, test, and deploy changes on our Salesforce platform. The role works with admins, architects, business analysts, and QA to deliver Apex, Lightning Web Components, integrations, automation support, and release fixes while following Salesforce security, data model, and governor limit constraints.

Core responsibilities for a Salesforce developer

• Build and maintain Apex classes, triggers, test classes, queueable jobs, scheduled jobs, and invocable services where declarative tools are not enough.
• Create Lightning Web Components for record pages, app pages, Experience Cloud pages, and custom UI workflows when standard components do not meet the requirement.
• Write SOQL and SOSL with bulk processing in mind. Avoid SOQL and DML inside loops, and design for transaction limits.
• Support declarative automation by reviewing Flow entry conditions, transaction order, recursion risk, and error handling.
• Develop REST or event-based integrations with external systems, using Named Credentials, clear retry behavior, and secure data mapping.
• Use Salesforce CLI, source control, scratch orgs or sandboxes, pull requests, and automated test runs as part of the release process.
• Enforce object permissions, field-level security, sharing behavior, and least-privilege access in Apex and Lightning components.
• Create technical documentation for data model changes, integration contracts, deployment steps, and support handover.
• Investigate production defects, read debug logs, identify root cause, and ship fixes through the agreed release path.

Required skills in a Salesforce job profile

A usable salesforce job profile separates required skills from nice-to-have skills. Required skills should describe what the person must use in the first 90 days.

• Apex development experience with triggers, service classes, batch or queueable jobs, and test classes.
• Lightning Web Components experience, including JavaScript modules, lifecycle hooks, wire adapters, Apex calls, and Lightning base components.
• SOQL knowledge, including selective filters, relationship queries, aggregate queries, and limits-aware query design.
• Understanding of Salesforce security: org-wide defaults, sharing rules, permission sets, field-level security, and record access.
• Experience with Salesforce CLI, metadata deployment, Git, pull requests, and sandbox-based development.
• Ability to review requirements and decide whether to use Flow, configuration, Apex, LWC, API integration, or a mix.

Preferred skills for a Salesforce engineer

A salesforce engineer title usually signals stronger software engineering expectations than a basic developer title. Add these items only when the role truly owns them.

• Experience with CI/CD pipelines for Salesforce metadata and automated Apex test execution.
• Experience designing integration patterns using REST API, Platform Events, Change Data Capture, Bulk API, or middleware.
• Knowledge of packaging, dependency management, unlocked packages, or multi-org release strategy.
• Ability to read performance symptoms such as CPU timeout, row lock errors, heap pressure, mixed DML, and non-selective SOQL.
• Experience with enterprise review practices: pull request reviews, static analysis, release gates, data migration dry runs, and rollback planning.

How should the JD change by experience level?

Do not use years alone to define a salesforce developer job description. A developer who has maintained a complex Service Cloud org for two years may be more ready for enterprise work than someone who has only built small admin-led customizations for five years. Use responsibility level instead.

What skills should a jd for Salesforce developer include?

A jd for Salesforce developer should include the skills that map to your delivery model. In an admin-heavy org, the developer may spend more time building Apex extensions for Flow. In a product-led org, the same role may focus on Lightning Web Components, APIs, and package-based releases.

Apex, SOQL, and governor limits

The JD should ask for bulkified Apex, selective SOQL, transaction-aware DML, and test classes that cover success, failure, and security behavior. Salesforce governor limits apply per transaction for many resources, so a candidate must know why one query outside a loop can still fail if it returns too many rows or starts a chain of expensive automation.

Lightning Web Components and UI development

For LWC work, list JavaScript, HTML templates, reactive properties, Lightning Data Service, Apex integration, and component communication. Avoid saying “Lightning” alone because it can mean Lightning Experience, Aura, Lightning Web Components, or Lightning base components. A salesforce developer job description should name LWC when the job requires LWC.

Security and permissions

Salesforce code often runs in system context unless the developer chooses patterns that enforce user access. Ask for experience with sharing keywords, user-mode database operations, permission sets, CRUD checks, field-level security, and secure Apex controllers. For permission assignment work, Salesforce Help defines permission sets as collections of settings and permissions that extend a user’s access.

Release management

Include the tools your team actually uses: Salesforce CLI, VS Code, Git, pull requests, sandboxes, scratch orgs, change sets, Metadata API, unlocked packages, DevOps Center, or a third-party pipeline. A vague sfdc job description that says only “deploy changes” does not tell the candidate whether the team has source control or whether production changes are still manual.

Certifications

Salesforce Platform Developer I is a relevant credential for many developer roles. Salesforce’s official Platform Developer I exam guide currently lists 60 multiple-choice questions plus up to five unscored questions, 105 minutes, and a 68% passing score. Do not make certification mandatory if your screening process already tests real Apex, LWC, and deployment skill.

What code standard should the Salesforce engineer role expect?

The salesforce engineer role should expect code that is readable, bulk-safe, testable, and secure. The sample below is not a hiring puzzle. It shows the level of clarity a salesforce developer job description can require in a code review.

public with sharing class ContactSearchService {
    @AuraEnabled(cacheable=true)
    public static List<Contact> findContactsByEmailDomain(String emailDomain) {
        if (String.isBlank(emailDomain)) {
            return new List<Contact>();
        }

        String domain = emailDomain.trim().toLowerCase();
        if (!domain.startsWith('@')) {
            domain = '@' + domain;
        }

        String emailPattern = '%' + domain;

        return [
            SELECT Id, FirstName, LastName, Email, Account.Name
            FROM Contact
            WHERE Email LIKE :emailPattern
            WITH USER_MODE
            ORDER BY LastName, FirstName
            LIMIT 50
        ];
    }
}

This Apex method uses a bind variable instead of dynamic SOQL, applies a limit, avoids queries inside loops, and uses WITH USER_MODE so object-level and field-level permissions are enforced for the query. It still needs tests that cover blank input, a matching contact, a non-matching domain, and the behavior expected for users without access to the selected fields.

@IsTest
private class ContactSearchServiceTest {
    @TestSetup
    static void makeData() {
        Account accountRecord = new Account(Name = 'Acme Services');
        insert accountRecord;

        insert new Contact(
            FirstName = 'Mira',
            LastName = 'Rao',
            Email = 'mira@example.com',
            AccountId = accountRecord.Id
        );
    }

    @IsTest
    static void returnsMatchingContacts() {
        Test.startTest();
        List<Contact> results =
            ContactSearchService.findContactsByEmailDomain('example.com');
        Test.stopTest();

        System.assertEquals(1, results.size(), 'Expected one matching contact.');
        System.assertEquals('mira@example.com', results[0].Email);
    }

    @IsTest
    static void returnsEmptyListForBlankInput() {
        Test.startTest();
        List<Contact> results =
            ContactSearchService.findContactsByEmailDomain('');
        Test.stopTest();

        System.assertEquals(0, results.size(), 'Blank input must not query data.');
    }
}

For an interview, ask the candidate to explain why the code uses a bind variable, why the method is cacheable, what with sharing does and does not enforce, and where field access is checked. A senior candidate should also discuss whether this belongs behind a selector/service pattern and how the method behaves in an Experience Cloud site.

How to screen candidates against a Salesforce job profile

The salesforce job profile should lead to a fair screening process. Do not ask trivia questions only. Give candidates a small scenario that reflects your org.

Common errors with an sfdc job description

An sfdc job description often fails because it combines too many roles into one posting. The result is a JD that asks for Apex, LWC, Flow, CPQ, Marketing Cloud, Data Cloud, MuleSoft, architecture, production support, admin work, QA, and business analysis without explaining the priority.

• Missing org context: Mention the clouds, number of integrations, user base, release frequency, and size of the Salesforce team.
• No security expectations: State that the developer must design for sharing, CRUD, FLS, permission sets, and data minimization.
• Too much admin overlap: Say whether the developer configures objects, fields, flows, and permissions, or only reviews them.
• No testing detail: Require meaningful Apex tests, not only the 75% deployment threshold.
• Unclear support duty: Tell candidates whether they join an on-call rota, handle release nights, or support only business hours.
• Wrong title: Use salesforce engineer when the role includes engineering standards, CI/CD, and platform reliability. Use developer when the role mainly builds assigned features.

Copy-ready Salesforce developer job description sample

You can adapt this salesforce developer job description for a job board or internal approval document.

Salesforce Developer

We are looking for a Salesforce Developer to build and maintain Salesforce features across [clouds/products]. You will work with admins, business analysts, QA, and architects to deliver Apex, Lightning Web Components, integrations, automation support, and release fixes. The role requires clear technical judgment: use configuration where it fits, write code where it is needed, and protect data with Salesforce security controls.

Responsibilities include: build Apex services, triggers, queueable jobs, and tests; create Lightning Web Components; review Flow and data model impact; write limits-aware SOQL; support integrations; document technical decisions; participate in pull request reviews; troubleshoot production defects; and deploy changes through our release process.

Required skills: Apex, SOQL, Lightning Web Components, Salesforce security, test classes, Salesforce CLI, Git, metadata deployment, and experience working in sandboxes. Experience with REST integrations, Platform Events, CI/CD, and Platform Developer I certification is preferred.

Related SalesforceTutorial resources

Use these guides to refine the technical parts of the JD: Apex code standards for Salesforce developers, Salesforce CLI deployment workflow, Salesforce Flow design and automation, Salesforce API integration patterns, and Lightning Web Components in Salesforce.

Frequently Asked Questions