← Back to all jobs
C

Salesforce Developer

Cardiff

74d ago

0DevRemote, USjobspy_indeed
remoteindeed

Job Description

**About Cardiff** ----------------- Cardiff lends to small businesses. Since 2004 we've funded more than $12 billion across the country, to businesses in logistics, healthcare, construction, professional services, and plenty in between. We're building our own underwriting technology, and we still answer the phone; our customers need capital fast, and they want a straight answer from a person who can actually help. **Location:** Remote (U.S.) **Employment Type:** Full\-time **Department:** Engineering **Reports to:** Director of Engineering **Why This Role Matters** ------------------------- Salesforce is where Cardiff's business is recorded: every lead, deal, merchant, and funding decision runs through it. It also carries a decade of application logic that was built there because Salesforce was the only place to build it. That's no longer true, and it's holding back what we can automate. Today our average turnaround from lead to funded is 24 business hours; our goal is minutes. You're the engineer who writes the code that gets us there: the integration layer between Salesforce and our own platform, and the services that take over what Apex and Flow are doing today. **How We Build** ---------------- We are all in on AI, and we're deliberate about where it runs. **Automation lives outside Salesforce.** We build our own agents against our own AWS environment and the Cardiff API. We are not buying Agentforce, and we're not solving problems by stacking more managed packages on the org. When there's work to automate, the answer is usually an external service or agent calling Salesforce through the API, not another trigger. **Salesforce and Slack are the system of record and where our people work.** They hold the truth and they're the interface for the human team. Application logic moves out to AWS over time, where we can test it, version it, and let agents drive it. You'll write plenty of Apex; you'll also write the code that makes some of it unnecessary. **Coding agents are the default way we build.** Claude Code, Cursor, Codex, or whatever is best that month. We expect you to ship several times faster than you would have two years ago, and to read what the model produces before it merges. Judgment is the part of the job that doesn't get automated. If you've been waiting for permission to work this way, you'll like it here. If your instinct is to solve everything inside the platform, this will be a frustrating seat. **The Role** ------------ 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 an