Salesforce Technical Business Analyst

Job Title: Salesforce Technical BA
Type: FT
Location: Vancouver, BC Canada with travel as needed

Job Summary

We are seeking a Senior Technical Business Analyst / Salesforce Developer for a complex, multi-department Salesforce environment with significant third-party integrations and heavy Flow-based automation. This role is for someone who operates across the full lifecycle of a Salesforce solution: eliciting and documenting business requirements, designing the functional solution, configuring it declaratively, and — where declarative tools genuinely aren't enough — building it in code (Apex/LWC) and wiring up the integration.

Based on the requirement or project, the person can work as BA or a developer or both. This is a senior-level role. It requires independent, production-grade judgment on both the functional and technical sides — not someone learning either discipline on the job.

Responsibilities

• Lead discovery sessions with stakeholders across multiple departments (e.g., Sales, Service, Operations, Finance) to elicit, document, and prioritize requirements.
• Translate business requirements into clear user stories, acceptance criteria, process flow diagrams, and functional specifications suitable for developer handoff.
• Facilitate requirements workshops, gap analyses, and current-state/future-state process mapping.
• Own the backlog for Salesforce enhancements: intake, triage, prioritize, and manage through delivery in partnership with the project/product owner.
• Identify when a requirement should be solved declaratively (Flow, validation rules, page layouts) versus when it genuinely requires custom development (Apex, LWC) or an integration change — and make that call based on best practice, not convenience.
• Conduct UAT planning and execution with business users; manage defect triage and sign-off.
• Maintain traceability between business requirements, configuration changes, and release notes.
• Lead and collaborate for required upgrades, releases, and projects

• Own day-to-day Salesforce administration: user management, roles/profiles/permission sets, sharing rules, security model integrity, and data governance.
• Design, build, and maintain Flow automation (Screen Flows, Record-Triggered Flows, Scheduled Flows) following governor-limit-aware, bulkified, and maintainable design patterns.
• Actively audit and remediate legacy automation (Workflow Rules, Process Builder) by migrating to Flow where appropriate, avoiding automation conflicts and recursive triggers.
• Manage object model changes (custom objects, fields, record types, page layouts, Dynamic Forms) with proper change management discipline.
• Partner with integration teams to understand data flow between Salesforce and external systems (ERP, HubSpot, Spotio, Marketing Automations, in-house systems, middleware/iPaaS such as Boomi) — including monitoring for integration failures, sync errors, and data integrity issues.
• Maintain a clean, documented data model; enforce field-level governance to prevent org sprawl (duplicate fields, unused automation, orphaned objects).
• Manage sandbox strategy, release/change management, and deployment coordination (Change Sets, or CI/CD via SFDX/Copado/Gearset — depending on org tooling).
• Monitor org health: Optimizer reports, API usage limits, storage limits, and technical debt backlog.

Custom Development & Integration

• Design and build custom Apex (classes, triggers, batch/queueable/schedulable jobs) using enterprise-grade patterns: trigger frameworks, service/selector layers, bulkification.
• Build Lightning Web Components for UI needs beyond declarative capability.
• Write meaningful Apex unit tests (real assertions, not coverage-for-coverage's-sake).
• Design and build integrations with external systems via REST/SOAP APIs, Platform Events, or middleware/iPaaS tools (MuleSoft, Boomi, or similar); implement robust error handling and failure logging so integration issues are caught early, not discovered via a downstream data discrepancy.
• Handle authentication securely (named credentials, OAuth) — no hardcoded secrets in code.

Cross-Functional / Governance

• Serve as the point of escalation for multi-department process conflicts (e.g., where Sales teams and Service teams have competing requirements on the same object).
• Participate in and help enforce Salesforce governance/Center of Excellence standards: naming conventions, environment strategy, automation‑of‑record rules, and documentation standards.
• Coordinate with the integration/development team on API‑related changes to ensure admin‑side changes (e.g., field changes, validation rules) don't break integrations.
• Support change management and en