EduAtlas

Salesforce Administrator

at iMentor, New York, United States

Listed on EduAtlas: live school vacancies from schools’ own careers pages and public job services. Apply on jobs.lever.co.

Salary
Not given in the advert
Closing date
Open until filled
Start
Not given in the advert
Type of post
Administration and business
A support post, not a teaching post.
First seen
9 November 2026, on a public job listing

Apply

On jobs.lever.co · Send it by: WhatsApp · LinkedIn · Email · X

Find posts like this from Claude: add EduAtlas to Claude.

The advert

Overview

Salesforce is iMentor's system of record for mentor recruitment and screening and for fundraising. It is a large, mature org with substantial custom configuration, fed continuously by several connected systems.

You'll be working alongside Recruitment, Screening, Program, and Development colleagues who are in direct contact with mentors and students every day — the data you steward is what makes that work possible. It's a good fit for someone who gets real satisfaction from finding the one broken field before anyone else notices, who'd rather build a system that catches problems automatically than rely on repeated manual fixes, and who likes being the first to know something's wrong, not the last to hear about it.

This role owns that data. Not just the configuration, the data itself: whether it is correct, whether it is protected, and whether the systems feeding it are working. When a record arrives incomplete, when Salesforce drifts out of step with the Platform, or when a field silently truncates and a mentor application disappears, you are the person who finds out first and traces it back to the source.

You will report to the Director of IT and work with Recruitment, Screening, Program, and Development. You will also be a first point of contact for colleagues who need help getting something out of Salesforce, and your job there is to make them more capable rather than to become their queue.

We have rolled out Claude across the organization. It is daily practice here, not an experiment, and this role is expected to use it: drafting flows, analyzing logs, writing documentation, first-pass triage. The judgment about what is right stays with you.

Responsibilities

\n

The data is correct

• Maintain data integrity across a large org with extensive custom configuration

• Build and maintain reconciliation checks between Salesforce and its source systems, so that drift surfaces automatically rather than being discovered by a colleague

• Deduplicate contact and household records; manage imports and extracts

• Recognize and prevent silent data loss, the class of failure where a source field exceeds a Salesforce limit and a record is rejected with no error reaching anyone

• Own the data-quality standard for what “correct” means, and be able to evidence it

The data is protected

• Administer users, profiles, roles, permission sets, sharing rules, and field-level security on a least-privilege basis

• Run periodic access reviews so that permissions are actively maintained rather than accumulated

• Handle mentor, student, and donor records in line with FERPA, donor obligations, and iMentor data protection policy

• Follow iMentor's policies on credential handling, software installation, and third-party access to iMentor systems, and raise concerns early

• Support the organization's SOC 2 work with evidence from your area

• This is data stewardship within the systems you administer. It is not an information security role; you will have security colleagues.

The integrations work

• Own the integrations that feed Salesforce: Form Assembly (mentor applications), our in-house Platform, Campaign Monitor, Eventbrite, Docu Sign, Calendly, Demand Tools, and our donation tools

• Diagnose failed and partial records end to end, using connector and integration logs alongside Salesforce, and trace root cause back to the source system rather than patching the symptom at our end

• Configure and maintain field mappings, record-matching criteria, and upsert keys

• Be consulted on changes to any system that writes into Salesforce, so that schema and process changes upstream do not arrive as surprises

Teams are Unblocked

• Triage and resolve requests through our ticket queue, keeping non-technical colleagues clearly informed in writing

• Train and enable staff through materials, demos, and sessions, so that routine requests become self-service over time

• Document configuration, workflows, and the reasoning behind decisions, so that knowledge does not sit with one person

• Administer NPSP, including households, affiliations, relationships, recurring donations, and rollup behavior, and support Development on donation data and campaign structure

• Manage the three annual Salesforce releases: review release notes, test in a sandbox (scheduled outside business hours where needed), and communicate what is changing

First 90 Days

• Build a working map of every system that writes into Salesforce, what it writes, and how failures currently surface

• Stand up reconciliation checks between Salesforce and at least two source systems, so divergence is detected automatically

• Complete a full access review and bring permissions to least privilege

• Clear the inherited backlog in the support queue and establish what routine looks like

Qualifications

• At least 3 years of Salesforce administration experience in an organization with 100+ users

• Demonstrated experience troubleshooting integrations between Salesforce and third-party systems, including reading logs to establish root cause

More vacancies in United States