Salesforce Developer
Summary
Salesforce Developer building and maintaining integrations between Salesforce and internal/external systems for a cloud-based accounts receivable platform, primarily using Apex, Lightning Web Components, Flow, and REST/SOAP APIs.
About Versapay
Versapay’s purpose is to remove financial friction so business ecosystems can transact smarter, faster, and with greater resiliency. We build cloud-based accounts receivable solutions that help finance teams accelerate cash flow, improve visibility, and operate with confidence. We are a remote-first organization across the U.S. and Canada. Our teams operate with a high degree of trust and autonomy, and we succeed because our people take ownership of their impact, communicate clearly, and follow through on commitments.
Our Values:
- Own Your Impact – Accountability is not negotiable. We take responsibility for outcomes, not just effort.
- Show Grit – We persevere through ambiguity and challenge with resilience and determination.
- Unite to Win – We create value with and for others, working respectfully toward shared goals.
- Act with Courage and Candor – We give and receive feedback openly, knowing it makes us better.
- Energize and Build Joy – We seek understanding, celebrate wins, and take care of ourselves and each other.
About Our Salesforce Platform:
Salesforce is a mission-critical enterprise platform within our organization. We manage it with a strong emphasis on architectural discipline, governance, and long-term sustainability. We are hiring a Salesforce Developer who will work closely with our existing platform team and business stakeholders to ensure the platform remains scalable, secure, and reliable as we evolve. This is a high-ownership position within a mature, integration-aware environment.
The Role — Salesforce Developer (Integrations & Platform)
This is an individual contributor role. You will lead your assigned integration design, build, and ongoing health work while sharing broader Salesforce platform delivery ownership with the team. You will work directly with vendor and partner technical teams, translate business needs into supportable designs, and build in the error handling, monitoring, and documentation that keep payment-adjacent workflows trustworthy. You will operate with a high degree of independence and partner closely with our team and business stakeholders.
Key Focus Areas
- Share ownership of Salesforce solution design, development, and support, including integrations between Salesforce, internal customer-facing applications, third-party vendors, and business partners supporting customer applications and ACH / credit card processing
- Support the workflows behind merchant onboarding, transaction processing enablement, and customer billing
- Build with Apex, Lightning Web Components, Flow, and platform APIs, choosing declarative or programmatic solutions deliberately
- Design resilient error handling, retry, reconciliation, and monitoring patterns so integration failures are caught early and diagnosed quickly
- Serve as the technical point of contact in vendor and partner conversations, from scoping through go-live and ongoing support
- Reduce technical debt in legacy integration code and improve performance, testability, and supportability
- Maintain clear technical documentation and support structured release, validation, and version-control practices
Who Thrives in This Role
- You think ‘in’ systems, not just in Salesforce. You understand what happens on both sides of an integration, and you design with the downstream system, the data contract, and the failure mode in mind.
- You own integration outcomes, not just your code. When something breaks between a partner and us, you help investigate, coordinate across teams and vendors, and drive your workstream toward resolution rather than routing a ticket onward.
- You are credible in a room with a vendor. You can lead a technical conversation with an external partner, hold a design position, ask the questions that surface hidden assumptions, and keep the relationship productive.
- You respect the weight of money movement. Payment and billing workflows leave no room for casual assumptions, and you bring the rigour, testing habits, and attention to data integrity that this work demands.
- You communicate clearly across dev and business. You can talk design with engineers and outcomes with business stakeholders, tailoring the message to the audience. This is critical to the role.
- You are a calm, trusted partner under pressure. You handle competing priorities, production issues, and candid feedback with composure, keeping stakeholders confident and focused on solutions.
- This is your primary professional focus. A permanent, full-time, in-house role — not a contract or consulting engagement — for someone who wants to go deep on a single Salesforce org.
- You build with AI. We actively encourage AI-assisted work. Wherever you are on that journey, we value curiosity, a willingness to fold AI into your workflow, and the judgment to validate its output.
Required Experience
- 4+ years of hands-on Salesforce development experience in a professional environment
- Demonstrated ownership of Salesforce integration work with both internal applications and external vendors or partners
- Strong proficiency in Apex, Lightning Web Components, SOQL/SOSL, and Flow
- Working command of integration patterns and APIs (REST, SOAP, Bulk, platform events), authentication models, and error-handling design
- Experience with Salesforce DX, Salesforce CLI, Git-based source control, and CI/CD or structured deployment tooling
- Comfort with admin-level configuration such as page layouts, validation rules, permission sets, and data model design
- Strong systems thinking and independent, self-directed execution
- Excellent, plain-language written and verbal communication with technical, business, and external partner audiences
Preferred
- Fintech or payments background, including exposure to ACH, credit card processing, merchant onboarding, or billing — valued, but not required for the right candidate
- Working knowledge of Salesforce CPQ / Revenue Cloud and Asset Lifecycle Management
- Salesforce Platform Developer I, Administrator, or App Builder certification
- Experience in a Scrum or Agile environment using Jira for sprint and support management
- Experience working within structured governance and release models
- Comfort using AI tools in day-to-day development work
To Apply
Please begin your application by confirming that you are applying for the Salesforce Developer role, then complete the application and answer the short questionnaire.
As published by lever
Resume/CV, Full name, Email, Phone, Current location, Current company, LinkedIn URL, GitHub URL, Portfolio URL, Other website, What is your age range?, I identify my ethnicity asSelect all that apply, What gender do you identify as?, Do you have a Disability, Do you identify as a Veteran?, Do you identify as LGBTQ+
- Which best describes the role you’re looking for? choose one · optional
- How many years of hands-on Salesforce development experience do you have (Apex, LWC, integrations — not admin-only work)? choose one · optional
- What was your actual level of ownership over Salesforce integrations in your most recent role? choose one · optional
- How have you worked with third-party vendors or business partners on integration projects? choose one · optional
- A nightly integration posts records to a partner API. The partner intermittently returns timeouts on roughly 2% of calls. How do you design for this? choose one · optional
- What is your working knowledge of Salesforce CPQ / Revenue Cloud and Asset Lifecycle Management? choose one · optional
- You’re handed a new user story with incomplete requirements. What is your first move? choose one · optional
- In two or three sentences, describe a specific Salesforce integration you personally built or fixed — name the systems on both ends, what made it hard, and how you knew it was working. written answer · optional
- Will you now or in the future require any work authorization or sponsorship? choose one · optional