Tech Lead (Salesforce CRM)

RESPONSIBILITIES:

Salesforce Delivery Ownership: You own the "how" of the Salesforce build — data model, automation (Flows + Apex), UI (LWC/screen flows), permission sets, Record Types, and packaging — from detailed technical design through deployment.

Platform-Level Design Authority: You are the guardian of the org's data model and automation architecture. Schema changes, sharing/visibility, and process design go through you, and you keep them coherent as the solution grows.

Engineering Rigor & Quality: You enforce production-grade Salesforce standards — Apex test coverage ≥ the org bar, FLS/sharing correctness, governor-limit awareness, and metadata/CLI-based deployment (SFDX/`sf`).

Integration Contract Ownership: You define and protect the API/data contracts between Salesforce and the backend integration services (identity validation, CRM sync, e-signature, and the SFCC B2B commerce component). You coordinate — not necessarily hand-build — the non-Salesforce layers, ensuring changes stay backward-compatible.

Proactive Risk Management: You surface dependencies, scope creep, and technical debt before they block delivery — especially coupling between the org schema, its automations, and the services that consume them — and bring solutions, not just problems.

Communication & Alignment: You translate Salesforce platform constraints (limits, callout/identity constraints, packaging realities) into plain language for non-technical PMs and client stakeholders, and keep engineering, PM, and design aligned on decisions and status.

Engineering Leadership & Mentorship: You lead and mentor Salesforce (and adjacent) engineers through technical reviews, coaching, and hands-on support, fostering a psychologically safe, high-accountability, high-quality culture.

REQUIREMENTS:

Proven Salesforce Technical Leadership: A significant track record (Senior/Lead level) delivering complex Salesforce Platform (Sales/Service Cloud, Core CRM) projects and supporting them in production. You can take a vague goal and turn it into shipped, stable org configuration and code.

Deep Salesforce Platform Expertise (hands-on):

Apex (triggers, services, async, test classes) and governor-limit-aware design.

Flows — record-triggered and screen flows — as a first-class automation tool.

LWC for custom UI where declarative isn't enough.

Data model & security: custom objects, Record Types, permission sets/permission-set groups, FLS, sharing.

Deployment & ALM: SFDX source format, metadata/CLI deployment (`sf`), sandboxes, change/branching strategy, CI-based deploys.

Integration surface: REST/Apex callouts, Connected Apps & OAuth 2.0 (incl. M2M client-credentials), Platform Events/outbound patterns.

Integration & Cloud Awareness (coordinate, not necessarily build): Enough fluency in API-based integrations and a cloud/microservice backend (Node/NestJS on AWS is the current stack, including an SFCC B2B commerce component) to own the contracts and reason about the end-to-end flow. Deep AWS/Terraform/backend build experience is a plus, not a requirement.

Multi-Workstream & Multi-Party Delivery: Comfortable running structured build and live operational/support work in parallel, and aligning technical direction across agency, client, and corporate platform teams within a controlled, security-gated environment.

Communication: Excellent English (written and verbal); Spanish strongly preferred for day-to-day work with a Chile-based client and team.

People Leadership & Mentorship: Proven experience leading and mentoring engineers through coaching, technical guidance, and constructive feedback.

NICE TO HAVE:

Salesforce certifications: Platform Developer I/II, App Builder, and/or an Architect-track credential.

Familiarity with test-driven development (TDD) / high-coverage delivery as a working practice.

DocuSign eSignature for Salesforce (or comparable managed-package e-signature) configuration experience.

Domain exposure to financial services, credit bureau, or identity/KYC onboarding flows, and comfort in regulated / enterprise-security contexts (VPN, corporate proxies, restricted egress, DevSecOps gates).

Familiarity with Node.js/NestJS, AWS (ECS Fargate), Terraform, Okta/SSO, and Jenkins/Bitbucket CI/CD as the surrounding platform.

CMS-driven frontends (Next.js / Contentful) exposure.