RVP Solutions Engineering, Mid-Market and Enterprise
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real, specific content. The posting includes: Role Overview (that's about the role). Who You Are (maybe qualifications/skills). What You'll Do (responsibilities). What You'll Need (requirements/qualifications). What we offer (benefits, compensation). There's also compensation range. No explicit schedule. So we can have sections: About the role (maybe from Role Overview?), Responsibilities (What You'll Do), Requirements (What You'll Need), Qualifications (maybe overlapping with Requirements? Could combine but they want separate if content). Skills (maybe from Who You Are). Benefits (What we offer). Pay (Compensation Range). Schedule (none -> omit). Also we might include About the role as a summary of company? Actually "About the role" could be the Role Overview paragraph. We'll put that.
We must not include boilerplate like Who We Are (company description) maybe not needed as a heading; but we could include as part of About the role? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include those headings only if we have content. We have content for About the role (Role Overview). Responsibilities (What You'll Do). Requirements (What You'll Need). Qualifications (maybe we can extract from Who You Are? Actually Who You Are describes desired traits; could be Qualifications. But we also have Requirements (What You'll Need) which includes years experience etc. Qualifications could be similar; maybe we can treat Who You Are as Qualifications. Skills could be extracted from Who You Are as well (technical depth, communication). But to avoid duplication, we need to decide.
We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We must not repeat content unnecessarily but must preserve ALL substantive information. So we need to include all info from posting across sections without omission. We can distribute content appropriately.
Let's extract:
Company description (Who We Are) - maybe not needed as a heading but could be part of About the role? The About the role section could include both company overview and role overview. But we must not invent headings. We'll put company description in About the role? Might be okay.
Role Overview paragraph: "This is the leader who builds and owns Solutions Engineering at Serval...."
Who You Are bullet points (paragraphs) describing builder, leader, technical, talent magnet, AI frontier, systems thinker, comfortable in ambiguity.
What You'll Do bullet points (list of responsibilities).
What You'll Need bullet points (requirements).
What we offer bullet points (Impact, Growth, Culture, Compensation Range).
We need to produce - for any list of duties/requirements/benefits. So we need to turn bullet points into lists.
We also need
for prose.
Thus structure:
About the role
Company description + Role Overview paragraph(s).
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
Maybe combine Who You Are traits as prose? Or list? Since they are traits, could be
- ... but they are not duties. Could be
with sentences. We'll output as
containing the traits.
Skills
Maybe list technical skills: working fluency with modern IT and identity stack, etc. Could be
.
But we must not invent sections with filler. We have content for Skills: "Working fluency with the modern IT and identity stack, including IdPs and SCIM, ITSM and ticketing, SaaS administration, APIs, and how access is granted and revoked across an org." plus "Excellent communication and storytelling, translating complex concepts for both engineers and executives, and the leadership presence to represent Serval at the most senior levels." plus "Genuine technical depth: you can hold your own in an architecture review, debug an integration live, and answer a sharp security question without reaching for a deck, and you can teach others to do the same." plus "Experience with ITSM, IGA, access management, security, or AI automation products is a strong plus." These could be skills.
We'll put them in - .
Benefits: Impact, Growth, Culture. Also maybe "Compensation Range" is Pay.
Pay: "$300K - $350K"
Schedule: none -> omit.
Now ensure we don't repeat info. We'll allocate:
About the role: includes company description (Who We Are) and Role Overview paragraph.
Responsibilities: What You'll Do list.
Requirements: What You'll Need list (10+ years etc.)
Qualifications: Who You Are list (builder, leader, technical credibility, talent magnet, AI frontier, systems thinker, comfortable in ambiguity). Could be list.
Skills: technical fluency, communication, technical depth, experience plus plus.
Benefits: Impact, Growth, Culture.
Pay: Compensation Range.
Now produce HTML.
We must not include markdown fences. Just raw HTML.
Let's craft.
About the role paragraph: combine company description and role overview.
Company description: "Serval is an AI-native automation platform transforming how enterprises operate. We build intelligent agents that understand real-world workflows and execute them end-to-end — replacing manual processes and rigid legacy systems with adaptive, learning software. Founded in early 2024, Serval is already trusted by companies like Fox, Notion, Perplexity, Vercel, and Brex to automate high-volume, high-friction operational work across their organizations. At the core of Serval is an agentic AI platform that turns natural language into production-grade workflows. Our agents don’t just respond to requests — they reason, take action across systems, and continuously improve with usage. What began with operational use cases has quickly evolved into a horizontal AI automation layer used across IT, HR, Finance, Security, Legal, and Engineering. Our mission is to eliminate repetitive, manual work across the enterprise and give teams leverage through intelligent automation. Long term, we’re building the universal AI operations layer — a system of agents that sits across business functions and runs the workflows that keep modern companies moving. We’re backed by leading investors including Sequoia Capital, Redpoint Ventures, Meritech, First Round, General Catalyst, Elad Gil, and others."
Role Overview: "This is the leader who builds and owns Solutions Engineering at Serval. You'll define the function from the ground up: the strategy, the hiring bar, the playbook, and the technical motion that turns sophisticated IT and security buyers into customers. You'll start as a hands-on, player-coach leader, carrying technical deals yourself while you grow a team of technical sellers, set the standard for how Serval demos and runs technical evaluations, and build the systems SEs will use. You'll partner directly with the founders, GTM leadership, and Product to make the technical win repeatable and to feed the hardest field signals back into the roadmap. Because the function is new, you’ll get to write the playbook(s)."
We'll combine into one
maybe two
but okay.
Now Responsibilities list items from What You'll Do:
- Own Solutions Engineering at Serval: the strategy, the hiring plan, the team, and the technical motion that clears the path to pilot for every prospective customer.
- Hire, manage, and develop the SE team, starting with the founding Solutions Engineer, and set the standard for technical selling that the next generation of SEs will inherit.
- Operate as a player-coach: personally carry strategic and early technical deals (discovery, architecture conversations, security reviews, executive briefings) while building the team that takes them on at scale.
- Build the foundational SE toolkit from scratch: demo environments, reference architectures, technical evaluation frameworks, technical FAQs, competitive positioning, and enablement that ramps new hires fast.
- Define the technical sales motion alongside the founders and account executives, and codify the controlled scope of value-based use cases and success criteria that turn evaluations into pilots.
- Be the senior, credible voice on security and access: guardrails, approval workflows, least-privilege and just-in-time access, audit logging, and the compliance questions security teams press on.
- Stand up the metrics and operating cadence for the function: technical win rates, pilot conversion, time-to-value, and the forecasting inputs leadership relies on.
- Own a clean handoff to the Deployment team at pilot kickoff, and build the process that makes that handoff repeatable as volume grows.
- Act as the bridge between the field and Product: capture the hardest objections and feature gaps, prioritize them with engineering, and bring real customer signal into the roadmap.
Now Requirements list from What You'll Need:
- 10+ years in solutions engineering, sales engineering, or a comparable pre-sales technical role at a high-growth B2B software or infrastructure company, including 2+ years leading a Solutions Engineering Organization.
- A track record of building or scaling a Solutions Engineering function: hiring the team, setting the bar, and creating the systems (demos, eval frameworks, enablement) that make it repeatable.
- Proven ability to sell technical products to senior IT and security buyers, with hands-on credibility in front of CIOs, Heads of IT, and security leaders.
- Genuine technical depth: you can hold your own in an architecture review, debug an integration live, and answer a sharp security question without reaching for a deck, and you can teach others to do the same.
- Working fluency with the modern IT and identity stack, including IdPs and SCIM, ITSM and ticketing, SaaS administration, APIs, and how access is granted and revoked across an org.
- Excellent communication and storytelling, translating complex concepts for both engineers and executives, and the leadership presence to represent Serval at the most senior levels.
- A builder's instinct and high ownership, energized by being first, defining the function, and creating the systems that scale a team.
- Experience with ITSM, IGA, access management, security, or AI automation products is a strong plus.
Note some overlap with Skills; but we can keep Requirements as above.
Qualifications list from Who You Are:
- A builder and a leader: you can scope a deal, stand up a demo, and win the technical decision yourself, and you're energized by turning that instinct into a team that does it at scale.
- Deeply technical and credible, the kind of person who earns the respect of CIOs, Heads of IT, and security leaders in the first meeting, and who can coach others to do the same.
- A talent magnet who has hired, developed, and retained strong technical sellers, with a clear point of view on what great looks like and a high bar for it.
- Living on the AI frontier, fluent in how agents and LLM-powered systems get deployed and governed inside the enterprise.
- A systems thinker who builds repeatable processes: demo standards, evaluation frameworks, enablement, and metrics that make the function predictable.
- Comfortable in ambiguity, owning outcomes end-to-end, and moving without waiting to be told what to build next.
Now Skills list maybe we can extract distinct technical skills not already covered: maybe we can keep some from Requirements that are not duplicated? But we already have technical depth, communication, working fluency, experience plus plus. Those could be considered Skills. To avoid duplication, we could move those to Skills and keep Requirements more about experience/years. But instructions: preserve ALL substantive information; we can allocate as we like as long as nothing omitted
for prose. Thus structure:
About the role
Company description + Role Overview paragraph(s).
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
Maybe combine Who You Are traits as prose? Or list? Since they are traits, could be
- ... but they are not duties. Could be
with sentences. We'll output as
containing the traits.
Skills
Maybe list technical skills: working fluency with modern IT and identity stack, etc. Could be
- .
But we must not invent sections with filler. We have content for Skills: "Working fluency with the modern IT and identity stack, including IdPs and SCIM, ITSM and ticketing, SaaS administration, APIs, and how access is granted and revoked across an org." plus "Excellent communication and storytelling, translating complex concepts for both engineers and executives, and the leadership presence to represent Serval at the most senior levels." plus "Genuine technical depth: you can hold your own in an architecture review, debug an integration live, and answer a sharp security question without reaching for a deck, and you can teach others to do the same." plus "Experience with ITSM, IGA, access management, security, or AI automation products is a strong plus." These could be skills.
We'll put them in
- .
Benefits: Impact, Growth, Culture. Also maybe "Compensation Range" is Pay.
Pay: "$300K - $350K"
Schedule: none -> omit.
Now ensure we don't repeat info. We'll allocate:
About the role: includes company description (Who We Are) and Role Overview paragraph.
Responsibilities: What You'll Do list.
Requirements: What You'll Need list (10+ years etc.)
Qualifications: Who You Are list (builder, leader, technical credibility, talent magnet, AI frontier, systems thinker, comfortable in ambiguity). Could be list.
Skills: technical fluency, communication, technical depth, experience plus plus.
Benefits: Impact, Growth, Culture.
Pay: Compensation Range.
Now produce HTML.
We must not include markdown fences. Just raw HTML.
Let's craft.
About the role paragraph: combine company description and role overview.
Company description: "Serval is an AI-native automation platform transforming how enterprises operate. We build intelligent agents that understand real-world workflows and execute them end-to-end — replacing manual processes and rigid legacy systems with adaptive, learning software. Founded in early 2024, Serval is already trusted by companies like Fox, Notion, Perplexity, Vercel, and Brex to automate high-volume, high-friction operational work across their organizations. At the core of Serval is an agentic AI platform that turns natural language into production-grade workflows. Our agents don’t just respond to requests — they reason, take action across systems, and continuously improve with usage. What began with operational use cases has quickly evolved into a horizontal AI automation layer used across IT, HR, Finance, Security, Legal, and Engineering. Our mission is to eliminate repetitive, manual work across the enterprise and give teams leverage through intelligent automation. Long term, we’re building the universal AI operations layer — a system of agents that sits across business functions and runs the workflows that keep modern companies moving. We’re backed by leading investors including Sequoia Capital, Redpoint Ventures, Meritech, First Round, General Catalyst, Elad Gil, and others."
Role Overview: "This is the leader who builds and owns Solutions Engineering at Serval. You'll define the function from the ground up: the strategy, the hiring bar, the playbook, and the technical motion that turns sophisticated IT and security buyers into customers. You'll start as a hands-on, player-coach leader, carrying technical deals yourself while you grow a team of technical sellers, set the standard for how Serval demos and runs technical evaluations, and build the systems SEs will use. You'll partner directly with the founders, GTM leadership, and Product to make the technical win repeatable and to feed the hardest field signals back into the roadmap. Because the function is new, you’ll get to write the playbook(s)."
We'll combine into one
maybe two
but okay. Now Responsibilities list items from What You'll Do: - Own Solutions Engineering at Serval: the strategy, the hiring plan, the team, and the technical motion that clears the path to pilot for every prospective customer. - Hire, manage, and develop the SE team, starting with the founding Solutions Engineer, and set the standard for technical selling that the next generation of SEs will inherit. - Operate as a player-coach: personally carry strategic and early technical deals (discovery, architecture conversations, security reviews, executive briefings) while building the team that takes them on at scale. - Build the foundational SE toolkit from scratch: demo environments, reference architectures, technical evaluation frameworks, technical FAQs, competitive positioning, and enablement that ramps new hires fast. - Define the technical sales motion alongside the founders and account executives, and codify the controlled scope of value-based use cases and success criteria that turn evaluations into pilots. - Be the senior, credible voice on security and access: guardrails, approval workflows, least-privilege and just-in-time access, audit logging, and the compliance questions security teams press on. - Stand up the metrics and operating cadence for the function: technical win rates, pilot conversion, time-to-value, and the forecasting inputs leadership relies on. - Own a clean handoff to the Deployment team at pilot kickoff, and build the process that makes that handoff repeatable as volume grows. - Act as the bridge between the field and Product: capture the hardest objections and feature gaps, prioritize them with engineering, and bring real customer signal into the roadmap. Now Requirements list from What You'll Need: - 10+ years in solutions engineering, sales engineering, or a comparable pre-sales technical role at a high-growth B2B software or infrastructure company, including 2+ years leading a Solutions Engineering Organization. - A track record of building or scaling a Solutions Engineering function: hiring the team, setting the bar, and creating the systems (demos, eval frameworks, enablement) that make it repeatable. - Proven ability to sell technical products to senior IT and security buyers, with hands-on credibility in front of CIOs, Heads of IT, and security leaders. - Genuine technical depth: you can hold your own in an architecture review, debug an integration live, and answer a sharp security question without reaching for a deck, and you can teach others to do the same. - Working fluency with the modern IT and identity stack, including IdPs and SCIM, ITSM and ticketing, SaaS administration, APIs, and how access is granted and revoked across an org. - Excellent communication and storytelling, translating complex concepts for both engineers and executives, and the leadership presence to represent Serval at the most senior levels. - A builder's instinct and high ownership, energized by being first, defining the function, and creating the systems that scale a team. - Experience with ITSM, IGA, access management, security, or AI automation products is a strong plus. Note some overlap with Skills; but we can keep Requirements as above. Qualifications list from Who You Are: - A builder and a leader: you can scope a deal, stand up a demo, and win the technical decision yourself, and you're energized by turning that instinct into a team that does it at scale. - Deeply technical and credible, the kind of person who earns the respect of CIOs, Heads of IT, and security leaders in the first meeting, and who can coach others to do the same. - A talent magnet who has hired, developed, and retained strong technical sellers, with a clear point of view on what great looks like and a high bar for it. - Living on the AI frontier, fluent in how agents and LLM-powered systems get deployed and governed inside the enterprise. - A systems thinker who builds repeatable processes: demo standards, evaluation frameworks, enablement, and metrics that make the function predictable. - Comfortable in ambiguity, owning outcomes end-to-end, and moving without waiting to be told what to build next. Now Skills list maybe we can extract distinct technical skills not already covered: maybe we can keep some from Requirements that are not duplicated? But we already have technical depth, communication, working fluency, experience plus plus. Those could be considered Skills. To avoid duplication, we could move those to Skills and keep Requirements more about experience/years. But instructions: preserve ALL substantive information; we can allocate as we like as long as nothing omitted
- .
Benefits: Impact, Growth, Culture. Also maybe "Compensation Range" is Pay.
Pay: "$300K - $350K"
Schedule: none -> omit.
Now ensure we don't repeat info. We'll allocate:
About the role: includes company description (Who We Are) and Role Overview paragraph.
Responsibilities: What You'll Do list.
Requirements: What You'll Need list (10+ years etc.)
Qualifications: Who You Are list (builder, leader, technical credibility, talent magnet, AI frontier, systems thinker, comfortable in ambiguity). Could be list.
Skills: technical fluency, communication, technical depth, experience plus plus.
Benefits: Impact, Growth, Culture.
Pay: Compensation Range.
Now produce HTML.
We must not include markdown fences. Just raw HTML.
Let's craft.
About the role paragraph: combine company description and role overview.
Company description: "Serval is an AI-native automation platform transforming how enterprises operate. We build intelligent agents that understand real-world workflows and execute them end-to-end — replacing manual processes and rigid legacy systems with adaptive, learning software. Founded in early 2024, Serval is already trusted by companies like Fox, Notion, Perplexity, Vercel, and Brex to automate high-volume, high-friction operational work across their organizations. At the core of Serval is an agentic AI platform that turns natural language into production-grade workflows. Our agents don’t just respond to requests — they reason, take action across systems, and continuously improve with usage. What began with operational use cases has quickly evolved into a horizontal AI automation layer used across IT, HR, Finance, Security, Legal, and Engineering. Our mission is to eliminate repetitive, manual work across the enterprise and give teams leverage through intelligent automation. Long term, we’re building the universal AI operations layer — a system of agents that sits across business functions and runs the workflows that keep modern companies moving. We’re backed by leading investors including Sequoia Capital, Redpoint Ventures, Meritech, First Round, General Catalyst, Elad Gil, and others."
Role Overview: "This is the leader who builds and owns Solutions Engineering at Serval. You'll define the function from the ground up: the strategy, the hiring bar, the playbook, and the technical motion that turns sophisticated IT and security buyers into customers. You'll start as a hands-on, player-coach leader, carrying technical deals yourself while you grow a team of technical sellers, set the standard for how Serval demos and runs technical evaluations, and build the systems SEs will use. You'll partner directly with the founders, GTM leadership, and Product to make the technical win repeatable and to feed the hardest field signals back into the roadmap. Because the function is new, you’ll get to write the playbook(s)."
We'll combine into one