Salesforce Developer Resume
Skills & ATS Keywords

The code spine of the platform. Apex classes and triggers with a handler pattern you can name out loud, queueable jobs for async work, batch Apex for heavy data, scheduled jobs for the nightly run, governor limits respected on every code path, bulkification baked into every trigger so a 200-record import does not blow up, Apex callouts to external systems through Named Credentials, and test classes that move past the 75% line and actually assert the business rule. The line between a Mid file and a Senior one is whether bulkification reads as habit or as remediation.

Apex, triggers + handlers, queueable, batch, scheduled, governor limits, bulkification, callouts, unit tests

The UI lane. LWC built on web standards, Aura kept in the file only where the org still runs it, the wire service for reactive Apex calls, Lightning Data Service for cache-friendly record work, the Lightning Message Service when a component family has to talk across tabs, the Lightning Design System for the look, custom components dropped into Lightning App Builder, and event composition that stops two components from fighting over the same record. Aura on a 2026 file should be the legacy slice, not the lead.

Lightning Web Components, lwc/wire, Lightning Data Service, LMS, SLDS, App Builder, events + composition

How the org actually stores work. Custom objects with the relationship type picked on purpose (master-detail when the child belongs, lookup when it points, junction objects on the many-to-many), SOQL with bind variables and selective filters that hit the index, SOSL for the multi-object search bar, large-data-volume patterns (skinny tables, custom indexes, deferred sharing recalc) on the estate that crossed 50 million rows, and a feel for when relational thinking helps and when the multi-tenant query optimizer is going to override you anyway.

Custom objects, master-detail / lookup / junction, SOQL bind variables, SOSL, LDV, indexing, skinny tables

The clicks-not-code surface a Salesforce Developer is expected to fluency-check on. Flow Builder for record-triggered, screen, and scheduled flows, the Process Builder and Workflow Rules migration story (everyone owes one of those right now), Validation Rules that block bad data before Apex touches it, Approval Processes wired with delegated approvers, Lightning App Builder for page composition, and Permission Sets and Permission Set Groups instead of profile sprawl. Senior files name the declarative-first call: Apex only where Flow runs out of room.

Flow Builder, Process Builder migration, validation rules, approval processes, App Builder, permission sets

How the org talks to the rest of the estate. REST and SOAP API for the standard request-response surface, Bulk API for the nightly ten-million-row load, Streaming API and Platform Events for the asynchronous push, Change Data Capture for source-to-target deltas, External Services on the lightweight third-party hook, Named Credentials so secrets stop living inside Apex strings, OAuth flows that match the consumer (JWT bearer on server-to-server, Web Server on user-context), and MuleSoft Anypoint when an API-led story actually justifies the licence.

REST, SOAP, Bulk, Streaming, Platform Events, CDC, External Services, Named Credentials, OAuth, MuleSoft

How the work actually ships. sfdx CLI on the local box, scratch orgs for the short-lived feature branch, unlocked packages as the release unit (change sets still around on legacy orgs but no longer the default), source-tracked development in Git so the org is reconstructible from main, GitHub Actions or Azure Pipelines on the CI side, Copado as the enterprise-default deploy pipeline, Gearset on the team that prefers a UI-first ALM, and a CI pipeline that runs Apex tests on every PR rather than once at release time.

sfdx CLI, scratch orgs, unlocked packages, source-tracked Git, GitHub Actions, Copado, Gearset, CI / CD

The piece every Salesforce review weighs heavily. Field-Level Security and CRUD checks enforced on every Apex entry point, sharing rules and role hierarchy designed instead of defaulted, Apex Sharing on the procedural path the declarative tools cannot reach, SOQL injection prevented through bind variables and not concatenation, Shield Platform Encryption on the regulated-data slice, the Audit Trail wired to the SIEM, and a Health Check score the team actually watches rather than ignores until the QBR.

FLS, CRUD, sharing rules + OWD, Apex Sharing, with sharing, SOQL injection prevention, Shield, Audit Trail

Show the credentials hiring managers actually filter on, paired with the cloud you ship inside. Platform Developer I as the entry credential, Platform Developer II at the Senior band, JavaScript Developer I on the LWC-heavy file, Application Architect or System Architect at the Lead seat. Pair them with the cloud you live in (Sales Cloud, Service Cloud, Experience Cloud, Health Cloud, Financial Services Cloud, Industries CRM) so the parser and the reader register both at once.

Platform Developer I / II, JavaScript Developer I, App / System Architect, Sales / Service / Experience / Health / Industries