Senior Salesforce Developer

• 7+ years hands-on Salesforce administration/configuration, including real Sales Cloud ownership
• Demonstrated experience with large-scale data migrations — Data Loader, Bulk API, and building your own matching/dedup logic when the built-in tools aren't enough
• Experience integrating Salesforce with marketing automation (Pardot/Account Engagement) and a CMS (WordPress), via native connectors, web-to-lead, or REST APIs
• Strong SQL and data-analysis skills; comfortable writing scripts (Python or similar) to profile, transform, and validate data before it touches production
• Experience designing custom objects and data models for industry-specific processes — financial services, retirement plans, or insurance strongly preferred
• Salesforce Administrator certification required; Advanced Administrator, Platform App Builder, Sales Cloud Consultant, or Data Architecture and Management Designer strongly preferred
• Excellent written communication — able to explain a technical data decision to an engineer and to a client in the same afternoon, in two different registers
• Experience with multi-org Salesforce consolidation (M&A, platform migration) is a strong plus.

Sales Clou

• dTranslate requirements from Sales leadership into scalable configuration — Lead/Opportunity/Account/Contact processes, assignment rules, validation rules, Flow
• sBuild and maintain reporting and dashboards for pipeline, plan-level KPIs, and data-quality metric
• sManage the security model: profiles, permission sets, sharing rules, field-level securit

yMarketing integration — WordPress & Account Engagement (Pardot

• )Own the integration between the WordPress website and Salesforce (form submissions, lead capture, sync behaviour, error handling
• )Configure and maintain Account Engagement: connected campaigns, scoring/grading, automation rules, list segmentation, and the Salesforce-Pardot connector syn
• cTroubleshoot sync failures and data mismatches between WordPress, Pardot, and Salesforc

eDocumentation & stakeholder communicatio

• nDocument every migration and integration decision — mapping specs, matching rules, known edge cases, and why a rule exists, not just what it doe
• sCommunicate migration status and data-quality findings to non-technical stakeholders and clients — plain-language summaries with real numbers, not internal jargo
• nEstablish pre-load validation practices (sandbox testing, integrity checks against the target org) so nothing gets loaded on fait