Global Head of Sales Engineering
Rimes · New York, NY · 3 wk ago
HybridBusiness Development$250k–$280k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About Rimes (company description) but not "About the role". There's a "The Role" paragraph describing role. Could map to "About the role". Also "Key Responsibilities" -> Responsibilities. "Required Qualifications" -> Requirements? Actually "Required Qualifications" could be Requirements. Also "Preferred / Ideal Qualifications" could be Qualifications? But we have separate sections: Requirements and Qualifications. Usually Requirements = required qualifications, Qualifications = preferred? We'll map accordingly. Also "What Success in This Role Is Not" maybe not needed. "What We Offer" includes benefits, compensation, etc. There's a specific base salary range: $250,000 - $280,000 annually. So Pay section. Benefits: "Competitive base salary and performance-based incentive compensation. Comprehensive benefits package including health, dental, vision, and retirement. Flexible, remote-friendly work environment..." So Benefits section. Schedule: Not mentioned explicitly; maybe remote-friendly work environment implies flexible schedule but not explicit. We should not create Schedule unless stated. So omit Schedule. Skills: Could be derived from required qualifications: e.g., hyperscaler platform fluency, AI application, etc. But we need to avoid filler. Could create Skills section summarizing technical skills: Snowflake, Databricks, Microsoft Fabric, AI in solutions, etc. However the instruction: "Prefer a few substantive sections over many thin ones." We could combine Skills into Qualifications? But we have both sections. Might be okay to include Skills if there is specific content. The posting lists required qualifications: building SE function, 15+ years experience, VP level, hyperscaler fluency, AI application, redesigning SE org, technical depth & GTM judgment, track record driving adoption, communication, travel willingness. Those are more qualifications/experience than skills. Preferred qualifications include leadership experience in hyperscaler, financial services, domain knowledge, APIs, modern data integration, cloud security, enterprise data architecture, advanced degree. Those could be skills. So we can have Requirements (required qualifications) and Qualifications (preferred). Skills maybe not needed. But we have to use headings only when posting has real specific content for it. We could omit Skills if not clearly defined. However we have "Required Qualifications" and "Preferred / Ideal Qualifications". So we can map Required to Requirements, Preferred to Qualifications. That seems fine.
Now we need to include About the role: The "The Role" paragraph plus maybe the initial description about Rimes? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have About the role section containing the description of the role (the paragraph after "The Role"). Also maybe include the company description? That's not about the role but about Rimes. Could be considered "About the role"? Probably not. But we could include a brief About the role summarizing the role's purpose. The posting includes: "The Global Head of Sales Engineering is a senior leadership role responsible for building Rimes' global pre-sales technical function for its next stage of growth. This is a builder mandate—not a role focused on maintaining or incrementally optimizing an inherited model. The successful leader will define the operating model, methodology, playbooks, organizational design, and global leadership bench across North America, EMEA, and APJ, while serving as a critical bridge between our commercial teams, Product and Engineering organizations, and prospective clients. Reporting directly to the Chief Revenue Officer, this role combines hands-on technical leadership with go-to-market strategy. The successful candidate will be equally credible in a CTO/CIO architecture discussion and a pipeline review, lead strategic deals directly, and bring a forward-looking point of view on how AI transforms both investment management workflows and the Sales Engineering operating model. They will help sophisticated clients design on modern cloud data platforms while driving platform adoption, consumption growth, and durable client value—not simply deal closure."
That's substantive. We'll put that in About the role.
Responsibilities: Use the "Key Responsibilities" section with subheadings? We need to output
- for any list of duties/requirements/benefits. So we can create a
- with each responsibility as
- . The responsibilities are grouped under headings: Leadership & Team Development, Pre-Sales Execution & Client Engagement, Cross-Functional Collaboration, Strategy & Operational Excellence. We could either keep those as subheadings inside
- or flatten. Probably better to keep each bullet as a responsibility item, maybe include the subheading as part of the bullet text. We'll produce a list. Requirements: Use the "Required Qualifications" bullet points. We'll list each as
- . Qualifications: Use the "Preferred / Ideal Qualifications" bullet points. Benefits: Use "What We Offer" paragraph plus maybe the bullet points? It's a paragraph describing benefits. We'll extract the benefits: Competitive base salary and performance-based incentive compensation. Comprehensive benefits package including health, dental, vision, and retirement. Flexible, remote-friendly work environment with a collaborative global culture. Opportunity to shape and build a world-class Sales Engineering function from a position of influence. Regular exposure to senior leadership and involvement in key strategic decisions. We'll put each as
- under Benefits.
Pay: The anticipated base salary range: $250,000 - $280,000 annually. We'll put that in a
maybe. We must not include boilerplate like EEO, diversity statement, application instructions, etc. Remove those. Now produce HTML fragment: start with maybe? Not required but we can just output headings and content. Use
for section headings. Then content:
for prose,
- for lists.
We must not include / or markdown fences.
Let's craft.
Sections:
About the role
... (the paragraph)
Responsibilities
- Leadership & Team Development: Build the global Sales Engineering function and leadership bench across North America, EMEA, and APJ, establishing the capability, structure, and standards required for Rimes' next stage of growth; define and implement the global SE operating model, technical sales methodology, playbooks, governance, coverage approach, and engagement frameworks; assess and redesign the current organization rather than inherit it unchanged, including appropriate use of solution architects, regional and global leadership roles, specialist capabilities, and tiered support by deal complexity or client segment; recruit, develop, and retain high-performing technical sales talent across geographies and time zones, fostering a culture of technical excellence, curiosity, accountability, and client-centricity; operate as a hands-on player-coach in strategic and complex deals while developing capability and succession depth of the broader SE team; partner with Sales leadership to deploy SE resources effectively across the pipeline, balancing global consistency with regional commercial environments and client cultures.
- Pre-Sales Execution & Client Engagement: Lead discovery, solution architecture, technical presentations, demonstrations, and proof-of-concept engagements for strategic and complex opportunities; engage credibly at the architecture level with sophisticated clients building on Snowflake, Databricks, Microsoft Fabric, and related cloud data ecosystems, translating platform capabilities into secure, scalable solutions; lead executive and technical client conversations on how AI can transform investment management workflows, data infrastructure, and operating models—not simply demonstrate product features; develop deep expertise in Rimes' platform, data capabilities, and integration ecosystem to address complex technical and functional questions from investment management clients; craft compelling solution narratives that connect Rimes' capabilities to client priorities across benchmark and index data, ESG, performance measurement, regulatory reporting, data governance, and modern data architecture; build trusted-advisor relationships with CIOs, CTOs, data officers, architects, operations leaders, and senior business stakeholders.
- Cross-Functional Collaboration: Serve as the primary feedback loop between the field and Rimes' Product and Engineering teams, translating prospect and client needs into actionable product insights; partner with Marketing to develop technical content, case studies, competitive positioning materials, and thought leadership that supports pipeline development; collaborate with Account Management and Customer Success to support smooth transitions from pre-sales to post-sales and ensure long-term client value realization; work closely with Sales Operations to instrument and report on SE team performance, pipeline contribution, and win/loss analysis.
- Strategy & Operational Excellence: Define the vision and strategy for a global, AI-native Sales Engineering function aligned with Rimes' revenue, product, and go-to-market priorities; establish a clear point of view on where AI should augment or replace traditional SE workflows, and translate that view into changes in team structure, role design, tooling, productivity, and client engagement; design a tiered SE model based on deal complexity, client segment, technical architecture, and strategic value, with clear engagement and escalation paths; establish and maintain scalable demo, sandbox, data, and reusable solution assets across core hyperscaler and cloud data platforms; define success measures that connect SE activity to technical validation, platform adoption, consumption growth, pipeline progression, win rates, and long-term client value; contribute to forecasting, territory and capacity planning, and deal reviews as a key member of the GTM leadership team.
Requirements
- Demonstrated success building a Sales Engineering function from the ground up—not solely inheriting and optimizing an established organization—including defining its operating model, methodology, playbooks, structure, and global leadership bench.
- 15+ years of experience in enterprise technology, including meaningful Sales Engineering, technical pre-sales, or solutions consulting leadership experience.
- Experience operating at VP level or above, with direct leadership accountability for teams across North America, EMEA, and APJ, multiple time zones, commercial environments, and client cultures.
- Deep and current hyperscaler platform fluency: hands-on working knowledge of Snowflake, Databricks, and/or Microsoft Fabric, with the technical credibility to engage sophisticated clients at the architecture level.
- Demonstrated application of AI in client solutions and in the design or evolution of internal SE workflows, team structures, tooling, and productivity—not simply thought leadership or product demonstration.
- Experience redesigning an SE organization and challenging legacy structures, including evaluating role mix, specialist or solution architect capabilities, coverage models, and segmentation by deal complexity.
- The combined technical depth and GTM judgment to move between CTO/CIO architecture discussions, strategic client engagements, pipeline reviews, and executive decision-making.
- A track record of driving platform adoption and consumption growth alongside deal progression, technical validation, and revenue outcomes.
- Strong communication, executive presence, and the ability to translate complex technical architecture into differentiated business value.
- Willingness to travel globally and remain hands-on in strategic deals while leading through a distributed leadership team.
Qualifications
- Leadership experience within a hyperscaler, cloud data platform, or AI-native enterprise technology company.
- Experience in financial services, investment management, or another data-intensive regulated industry.
- Domain knowledge is valuable and learnable; the required technical and leadership profile is essential.
- Knowledge of financial benchmark and index data, ESG data, performance measurement, regulatory reporting, or reference data management.
- Experience with APIs, modern data integration, cloud security, governance, and enterprise data architecture.
- Advanced degree in Computer Science, Engineering, Finance, Mathematics, or a related field, or equivalent practical experience.
Benefits
- Competitive base salary and performance-based incentive compensation.
- Comprehensive benefits package including health, dental, vision, and retirement.
- Flexible, remote-friendly work environment with a collaborative global culture.
- Opportunity to shape and build a world-class Sales Engineering function from a position of influence.
- Regular exposure to senior leadership
- for lists.
We must not include / or markdown fences.
Let's craft.
Sections: