Jr. Salesforce Administrator / QA Tester

Role Summary
Prove Partners is consolidating two Salesforce orgs and migrating a legacy system of record into Salesforce. The program runs in continuous release cycles, and every cycle changes objects, page layouts, permission sets, flows, Apex, and integrations. Each of those changes has to be proven out end to end before it reaches production users.

We are looking for a junior Salesforce administrator (remote) who wants to spend the bulk of their time in structured, repeatable quality assurance. This person will execute full end-to-end test passes in our sandboxes, over and over, across each release: building and maintaining the test scripts, running them, logging what breaks, retesting fixes, and confirming regressions have not been introduced elsewhere.

Repetition is the job, not a side effect of it. The right candidate is someone who is genuinely comfortable running the same 200-step regression pass every sprint and catching the one step that changed — and who is methodical enough to keep the documentation accurate while doing it.

Engagement at a Glance

Working titleJunior Salesforce Administrator / QA TesterReports toDirector of Program Management & CRMLocationOffshore / nearshore, fully remoteTime zone requirementMinimum 6 hours of daily overlap with 9:00 a.m.–5:00 p.m. US EasternCommitmentFull-time, 40 hours per weekDuration6–12 months, with option to extendEngagement typeOpen — vendor staff augmentation, individual contractor, or employer-of-recordSeniorityJunior (1–3 years); this is a hands-on execution role, not a lead role
Time zone is a hard requirement. Testing is iterative and conversational — the tester needs to be able to ask an administrator or developer a question and get an answer inside the same working session. Candidates should be located where the standard working day overlaps with US Eastern.

Key Responsibilities

End-to-end and regression testing (primary, ~60% of time)

• Execute full end-to-end test passes across core business processes in the sandbox environments, following documented scripts, for every release cycle.
• Run regression suites after each configuration or code change to confirm that existing functionality still behaves as expected.
• Test across the full record lifecycle — record creation, field updates, stage and status transitions, automation firing, downstream record effects, and reporting output.
• Retest and close out defects after fixes are deployed, and confirm the fix has not broken adjacent functionality.
• Validate behavior after sandbox refreshes and deployments, including smoke testing of critical paths.

Test design and documentation (~20% of time)

• Write and maintain test cases and test scripts from user stories, acceptance criteria, and process documentation.
• Keep the test case library current as requirements change; retire cases that no longer apply and add coverage for new functionality.
• Log defects with clear, reproducible steps, expected vs. actual results, affected records, screenshots, and severity.
• Maintain test execution records so that release readiness can be assessed at a glance.

Test data and environment support (~10% of time)

• Prepare and refresh test data sets, including bulk loads via Data Loader or Data Import Wizard.
• Write basic SOQL queries to verify data state and confirm expected record changes.
• Test across multiple user profiles and permission sets to confirm record visibility, field-level security, and sharing behave correctly for each role.

Light administrative configuration (~10% of time)

• Perform straightforward declarative configuration under supervision — custom fields, page layouts, list views, validation rules, simple reports and dashboards.
• Assist with user setup, permission set assignment, and access troubleshooting.
• Support user acceptance testing cycles: prepare UAT scripts, walk business testers through them, and consolidate their feedback.

Required Qualifications

• 1–3 years of hands-on experience in a Salesforce environment as an administrator, QA tester, business analyst, or support analyst.
• Working knowledge of the Salesforce platform: standard and custom objects, record types, page layouts, profiles and permission sets, validation rules, and Flow.
• Demonstrated experience executing manual test cases and logging defects in a tracked system (Jira, Azure DevOps, or similar).
• Ability to read a user story or acceptance criteria and translate it into concrete test steps.
• Comfort with repetitive, detail-intensive work and a track record of sustained accuracy in it.
• Basic SOQL and comfort with Data Loader or a comparable data tool.
• Clear written and spoken English — defect reports and test notes are read by developers and business stakeholders, so writing quality matters.
• Availability for the required daily overlap with US Eastern business hours.

Preferred Qualifications

• Salesforce Certified Administrator (ADM-201) — preferred, not required. Hands-on experience carries more weight than the credential, and we will consider candidates who are working toward it.
• Experience testing during a data migration or multi-org consolidation.
• Exposure to integration testing between Salesforce and external systems, including basic API concepts.
• Familiarity with Jira, Confluence, or comparable tracking and documentation tools.
• Any experience with test automation (Selenium, Provar, Playwright) or reading Apex test results — useful, but this role is manual-first.
• Background in healthcare, insurance, legal services, or another regulated environment where access control and audit trails matter.

What Success Looks Like

• By 15 days: has run a full end-to-end pass on at least one core process independently, using existing scripts, and is logging usable defects without rework.
• By 30 days: is authoring new test cases from user stories with minimal correction, and owns the regression suite for at least one functional area.
• By 60 days: is the reliable go-to for release readiness on their areas — the team trusts that if this person has signed off, the release is safe to deploy.

Originally posted on Himalayas