Salesforce developer (8+ Years exp)
Contract
Local to Cary NC only ( F2F interview Must)
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.
—
