IT Support and Salesforce Administrator

New hire IT setup. Ordering and provisioning computers and equipment ahead of start dates, so day one is ready to go instead of a scramble-

Offboarding logistics. Overseeing equipment returns and deactivating accounts when an employee is terminated, so nothing lingers after someone's gone

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.

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

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

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.

Required Qualifications

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

Salesforce Certified Administrator

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

Advanced Administrator or Platform App Builder is a plus

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.

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