Solid on the data model and sharing model; experience changing a live production org
Experience rebuilding or replicating existing processes, not just new builds
Comfortable with CI/CD, code reviews and a sandbox → staging → production flow
Has shipped against a hard deadline
Scope:
Hard go-live April 1
Reverse-engineer Voyager’s processes and rebuild them in Client’s GovCloud Salesforce org, working from requirements from the architect
Build the first-party order flow to eliminate double entry
Build the customer portal MVP in Experience Cloud, with Voyager as the first business line
Help clean data for the migration
Integration work isn’t in scope
About 80% new code, 20% maintenance
After go-live, co-own the portal rollout to other business lines with a senior developer
Experience Cloud is a plus, not required
Growth Solutions builds and runs the Salesforce platform that Client’s business lines use to capture demand, quote work, and get product out the door. We're a small team, so you'd own real surface area from week one rather than picking up tickets someone else scoped.
This role is focused on one thing: getting the Voyager business line fully onto Client’s Salesforce instance and standing up the Customer Portal that goes with it. Voyager is currently running on a separate org, which means people are re-keying orders by hand every month. You'd be the developer who makes that stop.
The engagement is 13 weeks against a fixed go-live date. We're hiring it as contract-to-hire because we want this person on the team afterward, not because the work ends in April.
What you'll do
Build and configure Salesforce to support the Voyager migration: objects, flows, Apex where it's warranted, and the data model changes the migration needs.
Stand up the MVP of a customer-facing portal on Experience Cloud, shared across three business lines.
Build the order handling flow for first-party orders so manual double entry goes away.
Help scope the rest of the migration. A good chunk of it isn't specified yet, and you'd be in the room defining it rather than waiting for a spec.
Test, document, and hand off cleanly. We run on sprints and a shared backlog, not heroics.
First 90 days, roughly
End of January: migration backlog scoped and written up.
February–March: Customer Portal MVP built and tested; first-party order flow working in Salesforce.
Early April: Voyager work ready for go-live.
What we're looking for
3+ years building on the Salesforce platform — declarative configuration plus Apex, Lightning components, and integration work.
Comfortable with the core data model and sharing model, and with making changes in a production org that other people depend on.
You've shipped against a date before and know how to say early when something won't make it.
Can work independently and write down what you built. Most of our stakeholders aren't Salesforce people.
Salesforce certifications are a plus but we care more about what you've shipped.
Nice to have
Experience Cloud or any customer/partner-facing portal build.
Org consolidation, data migration, or a merger integration.
Sales Cloud, Service Cloud, or CPQ exposure.
Worked somewhere with a regulated or restricted environment (GovCloud, FedRAMP, ITAR)