> Markdown version of [/jobs/ext/1915926-salesforce-developer](https://www.wearedevelopers.com/jobs/ext/1915926-salesforce-developer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Salesforce Developer

- **Company:** CARDIFF, INC.
- **Location:** United States (Remote available)
- **Experience:** Experienced
- **Salary:** $110,000.0
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Cloud Computing, Continuous Integration, Data Governance, Cursor (Graphical User Interface Elements), Python (Programming Language), Salesforce.Com, SQL Databases, Systems Integration, Twilio, TypeScript, Apex Code, Large Language Models, Snowflake, Git, Event Driven Architecture, Salesforce Object Query Language (SOQL), Software Version Control
- **Published:** August 4, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=e722855ceeae9b82

## About the Role

* 3+ years developing on Salesforce, with production ownership of what you shipped
 * Strong Apex and SOQL: triggers, async patterns (Batch, Queueable, Platform Events), governor limits, and bulk-safe design
 * Lightning Web Components and modern front-end fundamentals
 * REST and platform-event integrations between Salesforce and external systems, including auth, error handling, and retries
 * Source-driven development: sfdx, Git, sandboxes, and CI/CD rather than changes made straight in production
 * Real programming outside the Salesforce ecosystem: Python or TypeScript, SQL, and cloud deployment (AWS preferred)
 * Coding agents as your primary way of building; Claude Code, Cursor, Codex, or similar, with a specific example from the last six months of delivering something several times faster than you could have without them
 * The engineering fundamentals to recognize when AI output is wrong

Nice to have:

 * Experience decomposing a Salesforce org: moving functionality out to services and retiring the in-platform version
 * Fintech, lending, or MCA data models; Fundingo
 * Snowflake or another warehouse, and event-driven architectures
 * Salesforce Platform Developer I or II
 * LLM APIs, agent orchestration, or RAG in production

We weigh what you've shipped in the last 90 days more heavily than the brand on your resume. Show us code.

Who You Are

You ship: a working v1 in production beats a polished v1 in a sandbox.

You work independently and communicate proactively; when something is blocked, you say so the same day, in writing, with what you need.

You'd rather delete a trigger than add one.

You're comfortable telling a stakeholder that what they asked for isn't what they need, and you can explain why without jargon.

## Description

You'll build on top of Salesforce and build the path off it, often in the same week. That means Apex, LWC, and SOQL where they're the right tool, and Python services on AWS calling Salesforce through its APIs where they're better. You'll own the integration layer that connects the org to the Cardiff API, Snowflake, our agent platforms, and our lender partners.

You'll report to the Director of Engineering and work alongside our Salesforce Administrator, who owns configuration and data governance; you own code, integrations, and deployment. The team is small and senior; you'll work directly with the stakeholders in Sales, RevOps, Underwriting, and Marketing rather than through a layer of tickets.

What You'll Own

 * Apex, LWC, and SOQL. Triggers, async processing, batch jobs, platform events, and custom components, written to be read and tested
 * The integration layer. REST and platform-event integrations between Salesforce, the Cardiff API, Snowflake, Twilio, our agent platforms, and lender APIs
 * The migration path. Moving logic out of Apex and Flow into services on AWS, and retiring the in-platform version cleanly when it's replaced
 * Release engineering. Source-driven development with sfdx, version control, and CI/CD, so releases are boring
 * Data and performance. Governor limits, bulk-safe code, and queries that hold up as volume grows
 * Production support for what you build. When something you shipped breaks, you own the fix and the write-up

What Success Looks Like

First 30 days: You've mapped the org's code and integration surface: what the triggers do, where the Apex is, what talks to what, and where the risk sits. Your first pull requests are in production.

First 90 days: Delivering against stakeholder requests on a predictable cadence. At least one integration built or rebuilt against the Cardiff API. The path off one significant piece of in-platform logic is scoped, with a real date.

First year:

 * Two or more meaningful workloads moved out of Apex or Flow into services on AWS, with the Salesforce side retired
 * An integration layer people trust: it handles volume, fails loudly, and recovers
 * Deployments that go out without drama, through source control and CI/CD
 * A codebase measurably smaller and better tested than the one you inherited


## Related Videos

- [Building the Next Generation of Software](https://www.wearedevelopers.com/videos/100186-building-the-next-generation-of-software)
- [How Cisco embraced a DevOps culture within its network engineering team](https://www.wearedevelopers.com/videos/99-how-cisco-embraced-a-devops-culture-within-its-network-engineering-team)
- [20 billion requests a week: Upgrading Twilio's API gateway at scale](https://www.wearedevelopers.com/videos/100234-20-billion-requests-a-week-upgrading-twilio-s-api-gateway-at-scale)
- [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94)
- [Hacking AI at the Edge of the Indian Ocean](https://www.wearedevelopers.com/videos/100177-hacking-ai-at-the-edge-of-the-indian-ocean)
- [Minimal infrastructure for Real‑Time Phone Agents: transcripts in, responses out](https://www.wearedevelopers.com/videos/1736-minimal-infrastructure-for-real-time-phone-agents-transcripts-in-responses-out)

## Related Articles

- [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers)
- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)
- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)
- [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding)
- [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline)
- [Dev Digest 103 - Superb Owl Trafficking](https://www.wearedevelopers.com/magazine/388-dev-digest-103-superb-owl-trafficking)