Business Systems Analyst, GTM Systems

Required

• Systems and domain depth
• Domain and tenure — 6–8 years in business systems, sales systems, revenue systems, or GTM systems, with Salesforce as your primary platform throughout.
• Sales process depth — you've partnered with Sales Ops on the things reps feel every day: territory and account coverage, lead qualification and routing, stage gates, and pipeline and forecast hygiene.
• Sales systems / RevOps depth — experience across quote-to-cash, CPQ, territory and lead routing, forecasting, or adjacent revenue processes.
• Technical fluency — you can read a data model, a Flow, and enough Apex to design against what's really there, even though you are not expected to write production code.
• Program leadership
• Program ownership — you've been the single accountable owner, at the working level negotiating the commitments yourself, of a program that spanned four or more functions and changed how a revenue org works day to day.
• Release risk — you've delivered a program into a core system on a release process you didn't control, where another team's change could break your release.
• Re-scoping under change — you've re-scoped a program mid-flight because the business changed under it, a sponsor moved, or the original scope no longer matched reality.
• Holding the line — you've turned down a request with executive backing and kept the relationship; you hold the line when something breaks pricing discipline, a legal constraint, or the architecture, and you arrive with the alternative.
• Judgment and communication
• One tradeoff, two audiences — you write for the reader in front of you, not the one you find easiest: the VP gets the page, the engineer gets the spec.