Baseten11 дней назад
Analyst, Revenue Strategy & Operations
Полная занятостьУдалёнка
Обязанности
- 01Contribute to the annual and quarterly GTM planning process in partnership with Finance, including headcount modeling, ramp assumptions, and revenue target-setting
- 02Build and maintain coverage models aligned to 2-year growth projections, incorporating territory design, account segmentation, and capacity planning
- 03Support quota framework development, helping translate top-down targets into field-level plans that are credible and motivating
- 04Develop and maintain Baseten's segmentation logic — how we carve the market by industry, company profile, consumption potential, and AI maturity
- 05Contribute a point of view on competitive dynamics, regional expansion priorities, and whitespace opportunities
- 06Partner with Central Ops on ICP and TAM database strategy to ensure segmentation is grounded in clean, enriched data
- 07Translate data into a clear business narrative for leadership and the field; democratize insights so the revenue org can self-serve
- 08Contribute to the design of the pipeline generation model — coverage ratios, qualified pipeline definitions, and input assumptions
- 09Support the PG cadence: track actuals vs. model, surface gaps early, and partner with field leadership to course-correct
- 10Play an active role in the weekly forecast process, helping build the business narrative that connects leading indicators to revenue outcomes
- 11Build and maintain the analytics layer that powers GTM decision-making — from pipeline dashboards to cohort analyses to efficiency metrics
- 12Partner with the field to identify gaps in the business and develop structured plans to address them - supporting real time actions as well as insights to guide QBRs, pipeline reviews, etc.
- 13Analyze regional pipeline health, win/loss trends, and rep productivity to proactively surface insights that feed back into refining the GTM plan
- 14Contribute to execution optimization projects — improving the sales process, post-sale journey, and conversion at key funnel stages
- 15Close the loop between what's happening in the field and what needs to change in the plan
- 16Support the design and execution of structured experiments to test new GTM approaches — new segments, new channels, new acquisition or expansion motions
- 17Help build the measurement framework to evaluate what's working and create a clear path to scaling what wins
- 18Partner with RevOps and Central Ops to operationalize successful experiments into repeatable playbooks
Требования
- 014–6 years in GTM strategy, revenue operations, sales strategy, or a related function — ideally at a high-growth B2B SaaS or infrastructure company
- 02Experience with consumption-based or usage-based business models strongly preferred; you understand the difference between ARR and revenue, and how to think about drawdown, expansion, and net retention
- 03Background at a company that has scaled through a Series B–D inflection point; you've seen what good looks like and know what breaks as you grow
- 04Background in consulting and/or banking / finance a plus
- 05Exceptional analytical chops — you can build a coverage model, a cohort analysis, and a board-ready forecast narrative, and you know which one the moment calls for
- 06Strong business judgment — you don't just surface data, you tell people what it means and what to do about it
- 07Structured thinker and clear communicator — you can take a complex GTM problem, break it down, and present a crisp recommendation to a senior audience
- 08Hands-on builder — comfortable working in AI coding tools, spreadsheets, BI tools, SQL, and CRM systems; you don't wait for someone else to pull the data
- 09Collaborative operating style — you work across functions (Finance, field leadership, Central Ops, Enablement) and know how to get things done without formal authority
- 10AI Fluency- You actively use AI tools to drive your own productivity — in how you analyze data, structure problems, draft communications, and accelerate your work
- 11Comfortable with ambiguity; you can define the problem before solving it
- 12Bias toward action — you'd rather ship something good and iterate than wait for perfect