Salesforce Developer

Responsibilities

• Own the Salesforce platform end to end. Over 100 users across 7 key teams, a data model that carries real weight, and a growing set of markets on top of it. You are accountable for how well the whole thing works and where it goes next.
• Build in Apex and Flow, and know which one the problem calls for. Triggers, classes, async processing, test coverage, and declarative automation where declarative is the right answer. You write code the next person can maintain, and you leave the org better structured than you found it.
• Own the integration layer. Connected tools, APIs and middleware. When data crosses a boundary, you know where it came from, what shape it should arrive in, and what breaks when it stops.
• Own ETL and reverse-ETL. Getting data into Salesforce and back out to the warehouse and the rest of the stack. You design these pipelines, you run them, and you fix them when they drift.
• Keep the connected stack healthy. Outreach, Modjo, Kubaru, Lusha, Clay, Hightouch and other tools. You don't need to arrive an expert in each, but you should become the person who understands how they fit together.
• Set the technical standard. Architecture decisions, review of what gets built declaratively versus in code, and honest calls about technical debt. You work alongside our Salesforce Administrator and Data Ops Analyst, and you are the technical reference point for both.
• Push the vision forward. We want all day-to-day sales work to happen in Salesforce: the data our teams need to see, the actions they need to take, and the AI and automation solutions that multiply their productivity. You are the person who makes the hardest parts of that possible.
• This is an individual contributor role. As the platform and the function grow, there may be opportunities for it to develop toward technical leadership, depending on business needs and how the team evolves.
• How we build
• Three principles guide everything we ship

Languages