Salesforce Administrator

Location: Remote (U.S.)

Employment Type: Full-time

Department: Engineering

Reports to: Director of Engineering

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.

Why This Role Matters

Salesforce is where Cardiff's business is recorded: every lead, deal, merchant, and funding decision runs through it, and Sales, RevOps, Underwriting, and Marketing all depend on it being right. Today our average turnaround from lead to funded is 24 business hours; our goal is minutes. Getting there means clean data, reliable automation, and a platform that doesn't break when we change something.

It also means changing what Salesforce is for. Read the next section before you decide whether you want this job.

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 agent calling Salesforce through the API, not another chain of Flows.

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. Part of this job is keeping the org healthy; part of it is helping shrink what the org is responsible for.

AI is how you work, not a project you'll be assigned. We expect you to automate your own job: data cleanup, deployment checks, documentation, request triage, and the reporting you'd otherwise build by hand.

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 own Salesforce day to day: configuration, data integrity, deployments, integrations, and the requests that come in from across the business. You'll report to the Director of Engineering and work directly with the stakeholders who live in the system, taking a request from discovery through documentation, build, testing, and release without needing someone to project-manage you through it.

The team is small and senior. You'll be the person who knows the org best, and the one people come to when something in it doesn't add up.

What You'll Own

• Configuration. Flows, validation rules, formula fields, page layouts, permissions, and object-level design; built so the next person can follow what you did
• Data integrity. Field governance, deduplication, and reports the business can trust without checking them twice
• Deployments. Sandboxes, version control, and CI/CD, so a Friday release doesn't take out someone's Monday
• Integrations. The connections between Salesforce and everything around it: the Cardiff API, Snowflake, Twilio, our agent platforms, and lender APIs
• The request queue. Scoping, tracking, and closing out work from Sales, RevOps, Underwriting, and Marketing, with status they don't have to chase you for
• Documentation. What's built, why it's built that way, and what depends on it
• The migration path. Helping move logic out of Salesforce and into AWS as we build it, and retiring what it replaces

What Success Looks Like

First 30 days: You know the org: the objects, the automation, the integrations, and the parts that are held together with tape. You've given the Director of Engineering a written list of what's fragile and what you'd fix first.

First 90 days: Requests come in and go out on a predictable cadence, with the business able to see status without asking. At least one recurring manual process is automated and running. Deployments go through sandboxes and source control as a matter of course.

First year:

• The org is measurably simpler: fewer redundant fields, fewer overlapping Flows, fewer things only you understand
• Reporting people rely on without a side spreadsheet to check it
• Two or more processes moved off in-platform automation and onto agents or services running in AWS, with the Salesforce side cleanly retired
• A documented org, so a new admin could be productive in a week

Required Qualifications

• Salesforce Certified Administrator; Advanced Administrator or Platform App Builder is a plus
• 3+ years administering Salesforce, preferably in fintech, lending, or another high-growth environment
• Strong with Flow, validation rules, complex formula fields, and object-level configuration
• Experience with complex orgs integrated with APIs, third-party applications, and automation tools
• Deployment discipline: sandboxes, version control, and CI/CD rather than changes made straight in production
• A working understanding of how data moves between Salesforce and the systems around it
• Evidence you've used AI tooling to do this work faster: agents or coding assistants writing your Apex, SOQL, or scripts, automating data cleanup, or handling request triage and documentation. Bring a specific example from the last six months
• Enough scripting to work outside the platform: Python or JavaScript, REST APIs, and comfort reading a JSON payload

Nice to have:

• Apex, SOQL, and LWC
• Salesforce Data Cloud, Snowflake, or another warehouse
• Experience decomposing a Salesforce org: moving functionality out to services and retiring the in-platform version
• Fundingo or another lending or MCA platform

Who You Are

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

You're organized in a way other people can see: work is tracked, status is current, and decisions are written down.

You'd rather delete an unnecessary Flow than add a clever one.

You like operational problems, and you're comfortable telling a stakeholder that what they asked for isn't what they need.

This Role May Not Be a Fit If You

• Have a legacy admin mindset: clicks-not-code as an identity rather than a starting point
• Would rather buy Agentforce or another managed package than build against APIs
• Want to maintain a stable org for five years rather than help reshape one
• Prefer highly structured corporate environments, or need extensive direction and oversight
• Dislike fast-changing priorities
• Use AI tools occasionally, rather than having rebuilt your workflow around them

Compensation and Benefits

• Base salary: $80,000
• Performance bonus of up to $20,000, tied to delivery and business outcomes
• Medical, dental, and vision coverage
• 401(k) plan
• Flexible PTO and observed holidays
• Remote-first, with support for your home-office setup

How to Apply

Email

AI-Eng@cardiff.co

• A short note on the most complex Salesforce org you've owned: users, custom objects, integrations, and what you were responsible for
• A specific example from the last six months of using AI tooling to do admin work faster, and what it saved you
• Something you automated or simplified, with the before and after

Cardiff, Inc. is an Equal Opportunity Employer. We are committed to creating a diverse and inclusive workplace and do not discriminate on the basis of race, color, religion, sex, national origin, age, disability, veteran status, sexual orientation, gender identity, or any other characteristic protected by applicable law.