Salesforce Analyst

Description:

Our Sales, Customer Success, and Marketing teams can only move as fast as the systems underneath them. When Salesforce is wrong, a forecast can't be trusted, a deal sits in approval for days, a Chili Piper meeting never lands on the right rep's calendar, and a Customer Success Manager chases an account that was reassigned a month ago. You'll sit on the Revenue Operations team and be the person who keeps that foundation clean, fast, and trustworthy, working daily with Sales, Customer Success, Marketing, and Finance.

Here's the hard part. Your queue will never be empty, and the easy path is to close each ticket and move on. We want the opposite: when the same issue shows up twice, you find out why, fix it for good, and write down what happened so it doesn't come back. You'll also own small-to-medium systems projects from first request to launch with no one handing you a spec, and you'll do it on US Pacific hours from your own time zone.

What You'll Own
 

• The day-to-day health of our GTM stack, which means triaging deal desk questions, opportunity routing, approvals, and access requests across Salesforce and the tools around it, and getting reps unstuck while the deal is still live.
• Root cause for recurring issues, which means spotting ticket patterns, tracing them to the source, and shipping a durable fix (a Flow, a validation rule, an automation, or an AI-assisted workflow) instead of answering the same question again next week.
• GTM systems projects from intake to launch, which means gathering requirements, designing the solution, building it, testing it, documenting it, and driving adoption until the team is actually using it.
• Salesforce as our source of truth, which means running data hygiene, maintaining the data dictionary, leading cleanup projects and imports, and putting SOPs and system controls in place so bad data stops at the door.
• User provisioning and access across GTM systems, which means new hires are productive on day one and permissions stay tight as the team grows.
• The documentation that keeps RevOps from living in one person's head, which means SOPs, process maps, release notes, and onboarding content that people actually use.