SFDC Technical Product Manager

Night shift schedule

Discovery Site - 2x a month

Overview

Bridge between business requirements and SFDC technical delivery. They audit data, assess feasibility, recommend architecture, and—critically—identify when multiple teams are requesting conflicting things on the same system BEFORE design work starts. Not a developer, not a PM—a requirements gatekeeper who sees the full landscape and understands global functionality impact.

PRIMARY VALUE PROP

Identifies & Prevents Cross-Functional Conflicts

When one team requests changes to a system, a TPM catches that another team just modified the same system with different needs. When one team's request impacts multiple downstream projects, a TPM sees it and asks: Are these teams aligned What's the global impact Do we need to sync stakeholders before design

Without a TPM: Conflicting requests go to design. Rework happens downstream. Teams blame each other. Scope creeps. Timeline slips.

With a TPM: Conflicts surface early. Hold on—let's get both teams in the room, understand the global functionality impact, and agree before we design anything.

Protects the Intake Process

When leadership pushes to skip requirements gathering and jump straight to solution design, a TPM enforces the intake process. They say: I understand this is urgent, but we can't skip steps. Here's what we need before we can commit: formal requirement, stakeholder alignment, impact assessment, dependency mapping.

This prevents the common pattern: Random requests coming in from different stakeholders on the same system with no mechanism to identify conflicts, align teams, or enforce intake process—which creates a mess.

Understands Global Functionality & System Dependencies

They understand which teams own which systems and integrations. They know when a change in one area impacts three other projects. They know which requests are dependent on each other. They think in ecosystems and end-to-end workflows, not silos. They can map out: If Team A gets what they want, here's what breaks for Team B.

MUST-HAVE CRITERIA (Non-Negotiable)

5+ years Salesforce experience
Look for: Admin, developer, or implementation roles. Breadth of SFDC experience matters—not just one feature area.
2+ Salesforce projects shipped end-to-end
Look for: Led or owned project delivery from requirements through go-live. Must be actual shipped projects, not just configuration work.
Experience managing cross-functional complexity or integrations
Look for: Built workflows across multiple systems, managed dependencies, coordinated between teams, integration implementation, or similar. Evidence they've thought about how changes ripple across an ecosystem.
Experience identifying conflicting or competing requirements across teams
CRITICAL: Phone screen: Tell me about a time two different teams had competing needs on the same system or data. How did you identify the conflict When did you catch it Listen for whether they caught it EARLY (before design) or discovered it mid-project (too late).
Can articulate SFDC platform constraints and understand impact on global functionality
Phone screen: Ask about a time they couldn't do something in SFDC the way the business wanted. Good answer = specific constraint + understood impact on other systems. Bad answer = I don't remember or SFDC can do anything.

NICE-TO-HAVE (Preferred but Not Required)

Data auditing or SOQL query experience
Third-party integrations or middleware experience
BA or product management background
Experience enforcing intake processes or saying no to scope creep
Domain experience in finance, operations, or multi-stakeholder environments