Key takeaways
- →Decide the role first: administrators bill $40 to $95 an hour, developers $65 to $150, and a typical backlog is mostly configuration.
- →Plan about 8 days from brief to first deployed change through a vetted marketplace, 14 through a community referral, 21 through a consulting partner and about 50 through an in-house post.
- →US Salesforce developers bill $65 to $85 an hour at junior level, $85 to $115 mid-level and $115 to $150 senior; partners charge $140 to $250 and full-time base pay runs $110,000 to $180,000.
- →Five red flags in an Apex sample need no coding to spot: logic in the trigger, queries or writes inside loops, single-record code, hard-coded IDs, and tests without assertions.
- →Require a sandbox and a repeatable deploy in the contract, then let a two-week paid trial on a real ticket make the final call.
To hire Salesforce developers who improve your org instead of quietly breaking it, run three checklists in order: decide which Salesforce role you are actually buying (an administrator, a developer, or an architect, and for which cloud), source from the channel that matches your deadline, then put every finalist through the remaining four gates: a 30-minute Apex code review, an org walkthrough, two reference questions and a paid sandbox trial. In the US, vetted Salesforce developers bill $65 to $150 an hour depending on seniority, consulting partners charge $140 to $250, and full-time base salaries run $110,000 to $180,000. A vetted marketplace gets you to a first deployed change in about eight days; an in-house job post takes closer to 50. The rest of this guide is the checklist itself, including the five red flags a non-developer can spot in an Apex sample.
Name which Salesforce you are buying before you post anything
Salesforce is not one labor market: three roles with different prices work on it, plus specialists in clouds that barely overlap. The expensive mistakes happen before a candidate is contacted, by posting for a developer when the backlog is mostly configuration, or for a generic developer when the work is in Marketing Cloud.
Administrator. Builds with clicks: objects, fields, page layouts, permission sets, reports, and automation in Flow. An admin bills $40 to $95 an hour on a vetted marketplace and clears most of a sales-and-support backlog without writing a line of Apex.
Developer. Writes Apex triggers and classes, Lightning Web Components, and integrations with your ERP, billing or product database. This is the $65 to $150 an hour profile the rest of this guide is about. You genuinely need one when a requirement cannot be expressed in Flow, when code must call an external system, or when data volume is pushing declarative automation into limits.
Architect or consultant. Redesigns the process and the data model before anyone builds, in short engagements at the top of the range; worth it for a fresh implementation or a heavily customized org.
Then name the cloud. Sales Cloud and Service Cloud share the core platform; Experience Cloud, CPQ, Marketing Cloud and Commerce Cloud are different products with different skills, and a strong Sales Cloud developer is not automatically a Marketing Cloud developer. If the project is mostly plumbing between Salesforce and other systems, look at MuleSoft developers rather than a pure Apex profile. Write the role and the cloud in the first line of your brief; that sentence filters more applicants than any other.
The sourcing checklist: five channels and what each one costs you in days
Salesforce talent is scarcer than Python or JavaScript talent, and the good people are rarely on open boards. A channel that pre-screens is therefore worth more here than in a commodity language, and an in-house post takes longer because the pool of people who can pass a real Apex review in your metro is small.
| Channel | Days to first deployed change | Typical US cost | Best for | Where it fails |
|---|---|---|---|---|
| Vetted marketplace | About 8 | $65 to $150 per hour, no placement fee | Deadlines, budget control, trying before committing | You still own the final technical call |
| Open freelance board | About 12 | Wide spread, often below $50 per hour | Small, fully specified admin tickets | Screening and certificate checks are on you |
| Community referral | About 14 | Market rate, often senior | Long-running orgs that need a steady hand | Slow if nobody on your team is in the community |
| Consulting (SI) partner | About 21 | $140 to $250 per hour | Full implementations with a project manager | Bench swaps after kickoff, junior hours at blended rates |
| In-house job post | About 50 | $110,000 to $180,000 base, plus recruiter fee if used | An org you will keep extending for years | Seven weeks before any code, scarcity priced in |
The days are planning numbers from a signed brief to a first change deployed in a sandbox, not to a signed contract. Salesforce-specific sourcing that works: the Trailblazer Community group for your city, the people who answer well on the Salesforce Stack Exchange, and AppExchange partner listings when you want a firm rather than a person. All of them are visible through their work. For the shortest path, vetted Salesforce developers arrive pre-screened and your time goes to the org walkthrough instead of resumes.
Budget guardrails: what Salesforce developers cost in the US and how to keep the number honest
On a vetted marketplace, US Salesforce developers bill roughly $65 to $85 an hour at junior level, $85 to $115 at mid-level and $115 to $150 at senior level. Consulting partners charge $140 to $250, and a full-time developer costs $110,000 to $180,000 in base salary before benefits. Three things move a quote inside those bands: the cloud (Commerce and Marketing Cloud specialists price above core Sales Cloud work), the state of your org (years of customization mean discovery time), and integration scope. The full breakdown is on our Salesforce developer rates page; to compare against other stacks, see freelance developer hourly rates.
A worked example. Say the project is a Sales Cloud build: custom lead routing, two integrations (ERP and billing) and a reporting layer, estimated at 320 billable hours. A mid-level developer at $100 an hour comes to $32,000. A senior at $130 comes to $41,600. The same 320 hours through a consulting partner at a $195 blended rate comes to $62,400, before the partner's discovery phase. The blend that usually wins: a senior for the 80 hours of integration design and data model decisions ($10,400) and a mid-level developer for the other 240 hours ($24,000), $34,400 in total with senior judgment where it matters.
The admin split. Before you sign, have someone triage the backlog into configuration and code. If 40 percent of those 320 hours turn out to be Flow, layouts and permission work, that is 128 hours for an administrator at $70 an hour ($8,960) instead of a developer at $100 ($12,800). The $3,840 is the small saving; the real one is that developer hours go only to developer work, and the project finishes sooner.
Two guardrails to write into the contract: every change is built and tested in a sandbox and deployed with a repeatable process, never edited directly in production; and Apex ships with tests that assert behavior, not just tests that reach the 75 percent coverage the platform requires for deployment.
Gate 2: the 30-minute Apex code review, red flags one and two
Once you have named the role (gate 1) and sourced candidates, ask each finalist for an anonymized trigger and its handler class from a past project, or give them a small sandbox task with a two-day window. You do not need to write Apex to review it: five patterns separate developers who understand the platform's limits from developers who learned Java and discovered Salesforce last quarter.
Red flag 1: business logic written inside the trigger. Salesforce does not guarantee the order in which multiple triggers on the same object run, so the standard pattern is one trigger per object that only dispatches: it checks whether the event is a before insert, an after update and so on, and calls a handler class that does the work. Logic in the trigger body is hard to test and impossible to reuse. The trigger should be short and boring; the interesting code lives in a class.
Red flag 2: a query or a database write inside a loop. Apex runs under governor limits: a synchronous transaction gets 100 SOQL queries and 150 DML statements, and a trigger can receive up to 200 records at once from a data load or an integration. A single update inside a for loop over those records burns one DML call per record and throws a limit exception on the first bulk load, usually months after the code passed a one-record manual test. Look for select, insert, update or delete indented inside a loop.
The fixed version collects the account IDs in a set, runs one query with an IN clause, adds the records that need changing to a list, and issues one update after the loop. That is the whole difference between code that survives a 200-record batch and code that does not.
Gate 2 continued: red flags three, four and five
Red flag 3: code that handles one record. A trigger that reads Trigger.new[0] processes the first record in the batch and silently ignores the other 199. It passes every manual test, because a person saving a form sends one record, and fails on the first spreadsheet import. Bulkified code loops over the whole collection. This is the most common defect in Apex written by developers from other stacks, and it shows in the first three lines of a sample.
![Side-by-side Apex samples used when screening Salesforce developers: a trigger that reads Trigger.new[0] and handles a single record above a bulkified version that loops over every record in the batch of up to 200.](/blog/hire-salesforce-developers/shot-4.jpg)
Red flag 4: hard-coded record IDs. Record type IDs, user IDs and queue IDs differ between a sandbox and production, so an if that compares against a pasted 15-character ID works in development and fails on deploy. A developer who knows the platform looks the record type up by name or stores the value in custom metadata so an admin can change it without a release. Search the sample for strings starting with '012' or '005'.
Red flag 5: tests written to hit a number. Salesforce refuses to deploy Apex to production below 75 percent test coverage, and a whole category of developers writes tests that merely execute the code to cross that line. Open the test class. You want several methods with different scenarios, a negative case with bad data, and System.assert statements that check the outcome. A test with no assertions proves the code ran, not that it worked. For a language-agnostic checklist, see our guide to how to review a pull request.
Gates 3 to 5: the org walkthrough, references and the paid trial
Gate 3: the org walkthrough (45 minutes). Describe your org, or share a sandbox, and ask three questions. Which of these requirements would you build in Flow and which in Apex? Good developers reach for the declarative tool first; a candidate who wants Apex for everything will leave you an org only they can maintain. How would you get a change from your machine to production? You want to hear sandbox, version control and a repeatable deploy; a candidate who edits production directly is disqualified regardless of the code sample. And what would you do about automation built with the older Workflow Rules or Process Builder tools, which have reached end of support? The answer tells you whether they follow the platform's release cycle.
Gate 4: two reference questions. Ask a former client or manager two things. What happened the last time one of their releases broke production, and how did they handle it? And is the org easier or harder to change than before they joined? The second question is the whole job in one sentence.
Gate 5: the paid trial. Pick one real ticket, small enough for two weeks, that involves a trigger or a component and a sandbox deploy, and pay for it at the agreed rate. Judge it on the same five red flags, on whether the tests assert behavior, and on whether the developer left documentation an admin could follow. You are looking at their work in your org, not their answers about someone else's. When the trial goes well, our playbook to onboard a remote developer gets them productive in the first week.
Five mistakes that cost Salesforce buyers the most
Paying developer rates for admin work. The most common one. Triage the backlog first; in most orgs the majority of it is configuration.
Hiring for the wrong cloud. A Sales Cloud developer quoted for Marketing Cloud work learns on your budget. Put the cloud in the brief and ask for samples from that cloud.
Trusting certifications without verifying them. Platform Developer I and II are real signals and can be checked for free on the official credential verification page. Check them, then still run the code review: a certificate proves platform knowledge, not judgment in your org.
Skipping the deploy question. One developer editing production directly can undo months of work in an afternoon. Ask how changes reach production before anything else.
Ignoring the release calendar. Salesforce ships three major releases a year, and each can change how an existing automation behaves; someone who reads the release notes and tests in a preview sandbox is cheap insurance. If the CRM work is part of a larger data project, our CRM developers page covers the profiles that connect Salesforce to the rest of your stack.
What to do next
Write a one-page brief today that names the role, the cloud, the integrations, and the sandbox and testing rules you expect; our guide to writing a software project brief is the template. Pick the channel that matches your deadline from the table above, run every finalist through the five gates, and let the paid trial make the final decision rather than the interview. When you are ready, our Salesforce developers and Apex developers pages match you with pre-screened candidates in 48 hours, at $65 to $150 an hour with nothing to pay until you hire.
Frequently asked questions
How much does it cost to hire a Salesforce developer in the US?
On a vetted marketplace, expect $65 to $85 an hour for a junior, $85 to $115 for a mid-level developer and $115 to $150 for a senior. Consulting partners charge $140 to $250 an hour, and full-time base salaries run $110,000 to $180,000. Marketing Cloud and Commerce Cloud specialists and integration-heavy work price toward the top of each band.
Do I need a Salesforce developer or a Salesforce administrator?
Have someone triage the backlog first. Fields, layouts, permissions, reports and Flow automation are administrator work at $40 to $95 an hour. You need a developer when a requirement cannot be expressed in Flow, when you are integrating with an external system through code, or when you need Lightning Web Components. Many teams run a part-time admin and bring in a developer for specific tickets.
How do I evaluate a Salesforce developer if I cannot read Apex?
Ask for a trigger and its handler class and check five things: the trigger should only dispatch to a class, no query or database write should sit inside a loop, the code should loop over all records rather than read the first one, there should be no pasted record IDs, and the test class should contain assertions and a negative case. Then ask how they move a change from a sandbox to production.
How long does it take to hire a Salesforce developer?
About eight days from a signed brief to a first change deployed in a sandbox through a vetted marketplace, about two weeks through a community referral, about three weeks through a consulting partner, and around 50 days through an in-house job post, because the pool of developers who pass a real Apex review in any single metro is small.
Hire vetted talent