Founding Sales Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate.
We need to preserve all substantive information. So we need to include company description? The "About Featherless" paragraph is substantive but not under a heading? Could be part of About the role? Might be separate "About the company". But headings list only includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we could also have other headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we could include "About the company" as a heading? Not in list; maybe better to incorporate into About the role section. However the About Featherless paragraph is about company, not role. Could we put it under About the role as a preamble? Might be okay.
We need to preserve all substantive information; we can include company description in a
under About the role heading.
Now structure:
About the role
Featherless.ai is building the world's most reliable open-model inference platform... (the About Featherless paragraph) ...
We're hiring our first Sales Engineer to pair directly with our founding Account Executive in North America. You are the technical half of a two-person deal team: ... (the rest of About The Role paragraph).
Then Responsibilities: combine "What You'll Own Immediately" and "Core Responsibilities". Could be a list.
We need to output - items.
Let's extract bullet points:
From "What You'll Own Immediately":
- Partner with the founding AE as the named technical owner on every active opportunity in North America
- Run technical discovery: map each prospect's models, workloads, latency and throughput targets, spend, and constraints
- Design and drive POCs and benchmarks that prove Featherless against the incumbent — closed-model APIs, another inference provider, or self-managed GPUs
- Build the demo environment and reusable technical collateral that the whole GTM team sells with
- Own technical objection handling end-to-end: performance, reliability, cost modeling, security, and data handling
- Be the field's voice into product and engineering — you'll know what we're losing on before anyone else does
From "Core Responsibilities":
- Lead technical calls tailored to each buyer's stack: architecture reviews, live demos, and working code against their real use case
- Build migration paths off closed-model APIs and onto open weights — model selection, evaluation, prompt and output parity, cutover plan
- Run benchmarks and produce the throughput, latency, and cost-per-token analysis that anchors the business case the AE builds
- Scope and execute POCs with clear technical success criteria, then hold the customer and us to them
- Write the technical sections of proposals, RFP responses, and security questionnaires; keep a reusable answer library so we never write the same answer twice
- Support onboarding and first production workloads, then hand off cleanly and stay available for expansion
- Feed structured field input to product and engineering — feature gaps, model coverage requests, reliability issues, competitive intel
- Build and maintain the technical assets that scale the team: demo apps, notebooks, reference architectures, integration guides, internal enablement for BDRs and future AEs
- Represent Featherless technically at conferences, meetups, and developer events
- Keep POC and technical-stage detail current in HubSpot so forecasting reflects technical reality, not optimism
We can combine them into one list under Responsibilities.
Now Requirements/Qualifications/Skills: The posting has "What You Bring" and "Nice to have". We need to decide sections. Could have Requirements (mandatory) and Skills (maybe nice to have). Or combine.
We have mandatory: 3–6 years in pre-sales engineering, solutions architecture, or forward-deployed/customer-facing engineering role — at a GPU cloud, inference provider, MLOps platform, AI/developer tooling company, or cloud infrastructure vendor. Genuinely hands-on: you write Python comfortably and build your own demos rather than requesting them. Working knowledge of modern LLM inference — serving stacks (vLLM, SGLang, TensorRT-LLM or similar), OpenAI-compatible APIs, quantization, LoRA and fine-tune serving, batching and KV cache behavior, and what actually drives tokens/sec and cost. Practical familiarity with the open-model ecosystem: Hugging Face, the major open weight families, and how teams evaluate one model against another. Comfortable with containers, Kubernetes, and cloud networking and security fundamentals. Credible with both audiences in the same meeting — the ML engineer who wants the numbers and the CTO who wants the risk and cost story. Strong written communication: your benchmark writeups and architecture docs should be good enough to forward to a buyer's CEO. Entrepreneurial and self-directed — comfortable being the first SE, with no playbook and no one to escalate the technical answer to. Use AI tools heavily in your own workflow to research, prototype, and move faster.
Nice to have: experience selling or building on AMD GPUs / ROCm; exposure to enterprise security and compliance review; open-source contributions or public technical writing; experience as the first technical hire on a GTM team.
We could put Requirements (mandatory) as a list, Skills maybe as separate list for technical skills? But the instruction says prefer few substantive sections over many thin ones. Could combine Requirements and Skills into one section "Requirements" covering both mandatory and nice-to-have? But we need to preserve all info; we could have two sections: Requirements (mandatory) and Skills (nice-to-have). However that may be thin but still substantive.
Alternatively we could have "Qualifications" for mandatory and "Skills" for nice-to-have. The list of headings includes Requirements, Qualifications, Skills. So we could use Requirements for mandatory, Qualifications maybe redundant, Skills for nice-to-have. But we need to avoid filler. Let's decide: Use "Requirements" for mandatory, "Skills" for nice-to-have. Omit Qualifications.
Now Benefits: we have "Competitive base + variable tied to the team's number, plus equity". That's a benefit. Also maybe mention "Backed by AMD, Airbus Ventures, 500 Global, Kickstart Ventures, HF0 Residency, Panache Ventures, and Oakseed Ventures" but that's company background. Benefits section: we can list: Competitive base salary + variable tied to team performance, equity.
Pay: we have compensation range $150K - $190K.
Schedule: not mentioned, so omit.
Now we need to output HTML fragment only.
Let's craft:
About the role
Featherless.ai is building the world's most reliable open-model inference platform. Backed by AMD, Airbus Ventures, 500 Global, Kickstart Ventures, HF0 Residency, Panache Ventures, and Oakseed Ventures, we're a well-funded team of researchers and engineers on a mission to democratize AI through performance and accessibility. Our cloud provides instant access to 40,000+ open-source AI models and the research innovations powering next-generation efficiency, reliability, and model optimization.
We're hiring our first Sales Engineer to pair directly with our founding Account Executive in North America. You are the technical half of a two-person deal team: the AE owns the commercial motion, you own the technical win. Our buyers are developers, ML engineers, and CTOs, and they don't buy on slides. They buy when someone credible sits with them, looks at their workload, and shows them that open models on Featherless are faster, cheaper, and more reliable than what they're running today. That's your job — hands on keyboard, in the customer's stack, from first technical call through production rollout. Because you're the first SE here, you'll build the function as you go: the demo environment, the POC playbook, the benchmark harness, the security answers, the migration guides. Every deal you win should make the next one easier to win. If you like being the person who can actually answer the hard question in the room — and want the technical foundation of a Series A GTM engine to be yours — this is for you.
Responsibilities
- Partner with the founding AE as the named technical owner on every active opportunity in North America
- Run technical discovery: map each prospect's models, workloads, latency and throughput targets, spend, and constraints
- Design and drive POCs and benchmarks that prove Featherless against the incumbent — closed-model APIs, another inference provider, or self-managed GPUs
- Build the demo environment and reusable technical collateral that the whole GTM team sells with
- Own technical objection handling end-to-end: performance, reliability, cost modeling, security, and data handling
- Be the field's voice into product and engineering — you'll know what we're losing on before anyone else does
- Lead technical calls tailored to each buyer's stack: architecture reviews, live demos, and working code against their real use case
- Build migration paths off closed-model APIs and onto open weights — model selection, evaluation, prompt and output parity, cutover plan
- Run benchmarks and produce the throughput, latency, and cost-per-token analysis that anchors the business case the AE builds
- Scope and execute POCs with clear technical success criteria, then hold the customer and us to them
- Write the technical sections of proposals, RFP responses, and security questionnaires; keep a reusable answer library so we never write the same answer twice
- Support onboarding and first production workloads, then hand off cleanly and stay available for expansion
- Feed structured field input to product and engineering — feature gaps, model coverage requests, reliability issues, competitive intel
- Build and maintain the technical assets that scale the team: demo apps, notebooks, reference architectures, integration guides, internal enablement for BDRs and future AEs
- Represent Featherless technically at conferences, meetups, and developer events
- Keep POC and technical-stage detail current in HubSpot so forecasting reflects technical reality, not optimism
Requirements
- 3–6 years in pre-sales engineering, solutions architecture, or a forward‑deployed / customer‑facing engineering role — at a GPU cloud, inference provider, MLOps platform, AI/developer tooling
for prose. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate. We need to preserve all substantive information. So we need to include company description? The "About Featherless" paragraph is substantive but not under a heading? Could be part of About the role? Might be separate "About the company". But headings list only includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we could also have other headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we could include "About the company" as a heading? Not in list; maybe better to incorporate into About the role section. However the About Featherless paragraph is about company, not role. Could we put it under About the role as a preamble? Might be okay.
We need to preserve all substantive information; we can include company description in a
under About the role heading. Now structure:
About the role
Featherless.ai is building the world's most reliable open-model inference platform... (the About Featherless paragraph) ...
We're hiring our first Sales Engineer to pair directly with our founding Account Executive in North America. You are the technical half of a two-person deal team: ... (the rest of About The Role paragraph).
Then Responsibilities: combine "What You'll Own Immediately" and "Core Responsibilities". Could be a list. We need to output- items.
Let's extract bullet points:
From "What You'll Own Immediately":
- Partner with the founding AE as the named technical owner on every active opportunity in North America
- Run technical discovery: map each prospect's models, workloads, latency and throughput targets, spend, and constraints
- Design and drive POCs and benchmarks that prove Featherless against the incumbent — closed-model APIs, another inference provider, or self-managed GPUs
- Build the demo environment and reusable technical collateral that the whole GTM team sells with
- Own technical objection handling end-to-end: performance, reliability, cost modeling, security, and data handling
- Be the field's voice into product and engineering — you'll know what we're losing on before anyone else does
From "Core Responsibilities":
- Lead technical calls tailored to each buyer's stack: architecture reviews, live demos, and working code against their real use case
- Build migration paths off closed-model APIs and onto open weights — model selection, evaluation, prompt and output parity, cutover plan
- Run benchmarks and produce the throughput, latency, and cost-per-token analysis that anchors the business case the AE builds
- Scope and execute POCs with clear technical success criteria, then hold the customer and us to them
- Write the technical sections of proposals, RFP responses, and security questionnaires; keep a reusable answer library so we never write the same answer twice
- Support onboarding and first production workloads, then hand off cleanly and stay available for expansion
- Feed structured field input to product and engineering — feature gaps, model coverage requests, reliability issues, competitive intel
- Build and maintain the technical assets that scale the team: demo apps, notebooks, reference architectures, integration guides, internal enablement for BDRs and future AEs
- Represent Featherless technically at conferences, meetups, and developer events
- Keep POC and technical-stage detail current in HubSpot so forecasting reflects technical reality, not optimism
We can combine them into one list under Responsibilities.
Now Requirements/Qualifications/Skills: The posting has "What You Bring" and "Nice to have". We need to decide sections. Could have Requirements (mandatory) and Skills (maybe nice to have). Or combine.
We have mandatory: 3–6 years in pre-sales engineering, solutions architecture, or forward-deployed/customer-facing engineering role — at a GPU cloud, inference provider, MLOps platform, AI/developer tooling company, or cloud infrastructure vendor. Genuinely hands-on: you write Python comfortably and build your own demos rather than requesting them. Working knowledge of modern LLM inference — serving stacks (vLLM, SGLang, TensorRT-LLM or similar), OpenAI-compatible APIs, quantization, LoRA and fine-tune serving, batching and KV cache behavior, and what actually drives tokens/sec and cost. Practical familiarity with the open-model ecosystem: Hugging Face, the major open weight families, and how teams evaluate one model against another. Comfortable with containers, Kubernetes, and cloud networking and security fundamentals. Credible with both audiences in the same meeting — the ML engineer who wants the numbers and the CTO who wants the risk and cost story. Strong written communication: your benchmark writeups and architecture docs should be good enough to forward to a buyer's CEO. Entrepreneurial and self-directed — comfortable being the first SE, with no playbook and no one to escalate the technical answer to. Use AI tools heavily in your own workflow to research, prototype, and move faster.
Nice to have: experience selling or building on AMD GPUs / ROCm; exposure to enterprise security and compliance review; open-source contributions or public technical writing; experience as the first technical hire on a GTM team.
We could put Requirements (mandatory) as a list, Skills maybe as separate list for technical skills? But the instruction says prefer few substantive sections over many thin ones. Could combine Requirements and Skills into one section "Requirements" covering both mandatory and nice-to-have? But we need to preserve all info; we could have two sections: Requirements (mandatory) and Skills (nice-to-have). However that may be thin but still substantive.
Alternatively we could have "Qualifications" for mandatory and "Skills" for nice-to-have. The list of headings includes Requirements, Qualifications, Skills. So we could use Requirements for mandatory, Qualifications maybe redundant, Skills for nice-to-have. But we need to avoid filler. Let's decide: Use "Requirements" for mandatory, "Skills" for nice-to-have. Omit Qualifications.
Now Benefits: we have "Competitive base + variable tied to the team's number, plus equity". That's a benefit. Also maybe mention "Backed by AMD, Airbus Ventures, 500 Global, Kickstart Ventures, HF0 Residency, Panache Ventures, and Oakseed Ventures" but that's company background. Benefits section: we can list: Competitive base salary + variable tied to team performance, equity.
Pay: we have compensation range $150K - $190K.
Schedule: not mentioned, so omit.
Now we need to output HTML fragment only.
Let's craft:
About the role
Featherless.ai is building the world's most reliable open-model inference platform. Backed by AMD, Airbus Ventures, 500 Global, Kickstart Ventures, HF0 Residency, Panache Ventures, and Oakseed Ventures, we're a well-funded team of researchers and engineers on a mission to democratize AI through performance and accessibility. Our cloud provides instant access to 40,000+ open-source AI models and the research innovations powering next-generation efficiency, reliability, and model optimization.
We're hiring our first Sales Engineer to pair directly with our founding Account Executive in North America. You are the technical half of a two-person deal team: the AE owns the commercial motion, you own the technical win. Our buyers are developers, ML engineers, and CTOs, and they don't buy on slides. They buy when someone credible sits with them, looks at their workload, and shows them that open models on Featherless are faster, cheaper, and more reliable than what they're running today. That's your job — hands on keyboard, in the customer's stack, from first technical call through production rollout. Because you're the first SE here, you'll build the function as you go: the demo environment, the POC playbook, the benchmark harness, the security answers, the migration guides. Every deal you win should make the next one easier to win. If you like being the person who can actually answer the hard question in the room — and want the technical foundation of a Series A GTM engine to be yours — this is for you.
Responsibilities
- Partner with the founding AE as the named technical owner on every active opportunity in North America
- Run technical discovery: map each prospect's models, workloads, latency and throughput targets, spend, and constraints
- Design and drive POCs and benchmarks that prove Featherless against the incumbent — closed-model APIs, another inference provider, or self-managed GPUs
- Build the demo environment and reusable technical collateral that the whole GTM team sells with
- Own technical objection handling end-to-end: performance, reliability, cost modeling, security, and data handling
- Be the field's voice into product and engineering — you'll know what we're losing on before anyone else does
- Lead technical calls tailored to each buyer's stack: architecture reviews, live demos, and working code against their real use case
- Build migration paths off closed-model APIs and onto open weights — model selection, evaluation, prompt and output parity, cutover plan
- Run benchmarks and produce the throughput, latency, and cost-per-token analysis that anchors the business case the AE builds
- Scope and execute POCs with clear technical success criteria, then hold the customer and us to them
- Write the technical sections of proposals, RFP responses, and security questionnaires; keep a reusable answer library so we never write the same answer twice
- Support onboarding and first production workloads, then hand off cleanly and stay available for expansion
- Feed structured field input to product and engineering — feature gaps, model coverage requests, reliability issues, competitive intel
- Build and maintain the technical assets that scale the team: demo apps, notebooks, reference architectures, integration guides, internal enablement for BDRs and future AEs
- Represent Featherless technically at conferences, meetups, and developer events
- Keep POC and technical-stage detail current in HubSpot so forecasting reflects technical reality, not optimism
Requirements
- 3–6 years in pre-sales engineering, solutions architecture, or a forward‑deployed / customer‑facing engineering role — at a GPU cloud, inference provider, MLOps platform, AI/developer tooling