GTM Systems Support and Agentic Engineer

Details

• Serve as the primary point of contact for Salesforce and sales systems support across a fast-growing sales organization
• Triage, debug, and resolve issues across our Salesforce environment — including using debug logs to trace root causes quickly and accurately
• Administer and support adjacent sales tools, including LinkedIn Sales Navigator, ZoomInfo, Gong, e-signature and contract generation tools and others
• Go beyond the immediate fix: diagnose the underlying technical or UX root cause and address it at the system level so the same problem doesn't resurface for the next user
• Bring a thoughtful eye to UX — if a workflow is confusing, a field is misplaced, or a process creates unnecessary friction for reps, flag it and fix it
• Track and identify patterns in support volume, then design system automation and/or agentic workflows to address them at scale — auto-routing, intelligent response drafting, or fully automated resolution for the right categories
• Build agentic automation with architectural rigor: not just what to build, but how to structure it so it scales, stays maintainable, and yields higher quality outcomes over time
• Document solutions and contribute to a growing knowledge base that reduces future support load
• Strong Salesforce admin and engineering experience, including hands-on Apex and SOQL
• LWC experience is a plus
• Real Salesforce debugging experience — you know your way around debug logs and can trace a root cause under pressure
• Comfort owning frontline support directly: triaging, troubleshooting, and fixing rather than escalating by default
• Familiarity with the modern sales tech stack — tools like Gong, LinkedIn Sales Navigator, ZoomInfo, Chili Piper, DocuSign, or Conga are a plus
• Demonstrated experience building agentic systems — not just one-off automations, but infrastructure that handles context, orchestration, and durability
• A self-starter orientation: you see problems before they're assigned to you, and you build the solution rather than waiting for direction
• A pattern-recognition mindset: you don't just solve the ticket in front of you, you ask what structural change makes this class of ticket disappear