Customer Success Engineer (Contract)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate. Preserve all substantive info. Include sections only when posting has real specific content. Must not emit heading with filler placeholder.
We need to parse the posting.
Content:
- Intro about Retell AI (company description). This is "About Retell Ai". Could be a section? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not limited. We can include "About the company" maybe but they didn't list. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests these are typical headings; we can also use other headings if appropriate? Probably we should stick to those headings when applicable. The posting includes: "About Retell Ai" (company overview). Could be considered "About the role"? No, that's separate. There's "About The Role". There's "Key Responsibilities". There's "What We're Looking For" (which includes Must Have and Nice to Have). There's "YOU MIGHT THRIVE IF". There's "JOB DETAILS" (Employment Type, Location, Compensation, Hours). Also "Recent Recognition" maybe not needed? It's substantive but not a standard heading; could be omitted? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info. But we need to fit into allowed headings? Could create a section like "Recent Recognition" using as it's a heading in the posting. The instruction didn't forbid other headings; just gave examples. So we can include headings as they appear: "About Retell Ai", "Recent Recognition", "About The Role", "Key Responsibilities", "What We're Looking For", "YOU MIGHT THRIVE IF", "JOB DETAILS". However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those standard headings where applicable, but we can also use others if needed. To be safe, we can map content to those standard headings:
- About the role: we have "About The Role". Good.
- Responsibilities: we have "Key Responsibilities". Could map to Responsibilities.
- Requirements/Qualifications/Skills: we have "What We're Looking For" with Must Have and Nice to Have. Could split into Requirements (Must Have) and Skills (Nice to Have) or Qualifications. But we need to preserve all info. Could create sections: Requirements (Must Have) and Skills (Nice to Have). Or combine.
- Benefits, Pay, Schedule: we have JOB DETAILS includes Compensation (Pay), Hours (Schedule), Employment Type, Location. Benefits not mentioned. So we can include Pay and Schedule sections.
- About the company: maybe not needed but we can include as a brief intro paragraph before sections.
- Recent Recognition: could be included as a section maybe "Recent Recognition". Not in standard list but we can include as Recent Recognition
with list.
- "YOU MIGHT THRIVE IF" could be considered as "Skills" or "Attributes". Could be included under Skills or maybe as a separate section "Attributes". But to avoid too many thin sections, we could incorporate into Skills or Requirements.
We need to avoid filler like "commensurate with experience". Not present.
We must not include boilerplate like cookie/navigation/legal/EEO etc. Not present.
We must not include application instructions. Not present.
We must not repeat job title as heading. Not needed.
We must not put Job ID/requisition numbers as headings. None.
We need to output only HTML fragment.
Let's structure:
About Retell AI
... company description ...
Recent Recognition
- ... list items ...
About the Role
... description ...
Responsibilities
- ... each responsibility ...
Requirements
- ... Must Have items ...
Skills
- ... Nice to Have items ...
Pay
$6000–$7500 USD/Month, based on experience
Schedule
Must be open to working some overlapping hours with our Pacific Time team and customers.
Optionally include Employment Type and Location maybe as a short paragraph under Pay or separate? Could add a Employment Type: Full-Time 1099 Contractor, Location: Remote
maybe under a "Job Details" section but we already have Pay and Schedule. Could add a Employment Type: Full-Time 1099 Contractor; Location: Remote
after Pay or Schedule.
But we must not create sections with filler. Employment Type and Location are substantive; we could add a under Pay or Schedule or a separate "Job Details" section. Since we already have Pay and Schedule, we could add a
after Schedule: "Employment Type: Full-Time 1099 Contractor. Location: Remote."
Let's extract exact text.
Company description:
"About Retell Ai Retell AI is using first-principles thinking to reimagine the call center with cutting-edge voice AI. Thousands of companies now use Retell's AI voice agents to handle sales, support, and logistics calls that once required large teams of human agents. Backed by Y Combinator, Alt Capital, and other leading investors, we've scaled to $80M in ARR with a team of 50, up from $5M at the start of 2025, and are now valued at over $1.5B. Our vision for 2026 is to build a modern CX platform where entire contact centers are powered by AI. Instead of basic automation that needs constant human tuning, we're creating intelligent AI “workers” that act as frontline agents, QA analysts, and managers, continuously executing, monitoring, and improving every customer interaction. We're growing fast and looking for ambitious builders who want to tackle hard technical problems, move quickly, and have a real impact on one of the fastest-growing voice AI companies in the world. Let's build the future together."
We need to preserve all that. Might need to fix spacing: "About Retell Ai" then space then "Retell AI". We'll just output as a paragraph.
Recent Recognition list:
"No. 1 Best Places to Work in the Bay Area, San Francisco Business Times 2026
Top 50 AI Apps, a16z (2025)
#3 Fastest-Growing Software Company, G2 Best Software Awards 2026
Best Agentic AI Software, G2 Best Software Awards 2026
#4 Fastest-Growing Software Vendor, Brex Benchmark 2025
Enterprise Tech 30 Class of 2026, Nasdaq & Wing VC
Top-Ranked Startup, Lean AI Leaderboard
Backed by Y Combinator"
We'll put each as
- .
About The Role:
"We're hiring a Mandarin-Speaking Customer Success Engineer on a long-term 1099 contract to help enterprise customers successfully deploy and scale AI voice agents in production. You'll work directly with customers to build AI voice agents, design integrations, troubleshoot deployments, and solve technical problems. The role sits at the intersection of software engineering, customer success, and AI deployment. You'll work closely with Engineering, Product, and Customer Success while partnering directly with customer technical teams."
Key Responsibilities list:
"Enterprise Customer Deployments
Support technical onboarding and deployment for enterprise customers.
Help customers launch and scale AI voice agents.
Build trusted relationships with customer engineering teams.
Technical Consulting
Build AI voice agents alongside customers.
Design conversation flows and deployment strategies.
Debug APIs, webhooks, SIP, telephony, authentication, integrations, and latency issues.
Troubleshoot production deployments and technical issues.
Work directly in customer codebases when needed.
Partner with Product & Engineering
Identify product gaps through customer feedback.
Translate customer needs into actionable product improvements.
Work closely with Product and Engineering teams.
Customer Growth
Help customers launch new AI use cases.
Identify opportunities to expand product adoption.
Become a trusted technical partner to enterprise customers."
We need to turn each bullet into
- . The headings like "Enterprise Customer Deployments" etc are subheadings but we can treat them as list items as well. Could also make them
- with bold? But we just need list.
What We're Looking For:
Must Have:
- Must be able to read, write and speak in Mandarin & English.
- Bachelor's degree in Computer Science, Computer Engineering, Electrical Engineering, or a related technical field.
- 2–8 years of professional experience, ideally in Customer Success Engineering, Solutions Engineering, Forward Deployed Engineering, Software Engineering, or a similar technical role.
- Strong technical problem-solving skills.
- Experience working with APIs and debugging technical issues.
- Strong communication skills and the ability to explain technical concepts clearly to customers.
- Comfortable working directly with customers and building technical solutions with them.
- Must be available to work some overlapping hours with our Pacific Time-based team and customers.
Nice to Have:
- Experience with Python or TypeScript.
- Experience with AI, LLMs, or Voice AI.
- Startup experience.
- Enterprise customer experience.
- Willingness to travel occasionally for customer launches or onsite work.
YOU MIGHT THRIVE IF:
- You enjoy solving technical problems directly with customers.
- You like building alongside customers rather than just supporting them.
- You're comfortable debugging complex systems.
- You move quickly and enjoy a fast-paced startup environment.
- You enjoy working across Engineering, Product, and Customer Success.
We could incorporate YOU MIGHT THRIVE IF into Skills or maybe as a separate "Attributes" section. But to avoid many thin sections, we could merge into Skills (Nice to Have) or Requirements. However they are more about personal traits. Could create a section "Attributes" but not in standard list. Might be okay to add as
Attributes
. The instruction didn't forbid other headings; just gave examples. So we can add.
But we need to avoid too many thin sections. However each of these sections has substantive content. It's okay.
Alternatively we could put YOU MIGHT THRIVE IF under Skills as well. But Skills currently is Nice to Have (technical). Might be okay to add personal traits there.
I'll create Skills section that includes both Nice to Have and YOU MIGHT THRIVE IF items.
Pay: "$6000–$7500 USD/Month, based on experience"
Schedule: "Must be open to working some overlapping hours with our Pacific Time team and customers."
Employment Type and Location: we can add a paragraph after Schedule: "Employment Type: Full-Time 1099 Contractor. Location: Remote."
Now ensure we don't repeat any content inadvertently.
Let's craft HTML.
We'll start with About Retell AI
...
Then Recent Recognition
...
Then About the Role
...
Then Responsibilities
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate. Preserve all substantive info. Include sections only when posting has real specific content. Must not emit heading with filler placeholder. We need to parse the posting. Content: - Intro about Retell AI (company description). This is "About Retell Ai". Could be a section? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not limited. We can include "About the company" maybe but they didn't list. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests these are typical headings; we can also use other headings if appropriate? Probably we should stick to those headings when applicable. The posting includes: "About Retell Ai" (company overview). Could be considered "About the role"? No, that's separate. There's "About The Role". There's "Key Responsibilities". There's "What We're Looking For" (which includes Must Have and Nice to Have). There's "YOU MIGHT THRIVE IF". There's "JOB DETAILS" (Employment Type, Location, Compensation, Hours). Also "Recent Recognition" maybe not needed? It's substantive but not a standard heading; could be omitted? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info. But we need to fit into allowed headings? Could create a section like "Recent Recognition" using as it's a heading in the posting. The instruction didn't forbid other headings; just gave examples. So we can include headings as they appear: "About Retell Ai", "Recent Recognition", "About The Role", "Key Responsibilities", "What We're Looking For", "YOU MIGHT THRIVE IF", "JOB DETAILS". However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those standard headings where applicable, but we can also use others if needed. To be safe, we can map content to those standard headings:
- About the role: we have "About The Role". Good.
- Responsibilities: we have "Key Responsibilities". Could map to Responsibilities.
- Requirements/Qualifications/Skills: we have "What We're Looking For" with Must Have and Nice to Have. Could split into Requirements (Must Have) and Skills (Nice to Have) or Qualifications. But we need to preserve all info. Could create sections: Requirements (Must Have) and Skills (Nice to Have). Or combine.
- Benefits, Pay, Schedule: we have JOB DETAILS includes Compensation (Pay), Hours (Schedule), Employment Type, Location. Benefits not mentioned. So we can include Pay and Schedule sections.
- About the company: maybe not needed but we can include as a brief intro paragraph before sections.
- Recent Recognition: could be included as a section maybe "Recent Recognition". Not in standard list but we can include as Recent Recognition
with list.
- "YOU MIGHT THRIVE IF" could be considered as "Skills" or "Attributes". Could be included under Skills or maybe as a separate section "Attributes". But to avoid too many thin sections, we could incorporate into Skills or Requirements.
We need to avoid filler like "commensurate with experience". Not present.
We must not include boilerplate like cookie/navigation/legal/EEO etc. Not present.
We must not include application instructions. Not present.
We must not repeat job title as heading. Not needed.
We must not put Job ID/requisition numbers as headings. None.
We need to output only HTML fragment.
Let's structure:
About Retell AI
as it's a heading in the posting. The instruction didn't forbid other headings; just gave examples. So we can include headings as they appear: "About Retell Ai", "Recent Recognition", "About The Role", "Key Responsibilities", "What We're Looking For", "YOU MIGHT THRIVE IF", "JOB DETAILS". However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those standard headings where applicable, but we can also use others if needed. To be safe, we can map content to those standard headings:
- About the role: we have "About The Role". Good.
- Responsibilities: we have "Key Responsibilities". Could map to Responsibilities.
- Requirements/Qualifications/Skills: we have "What We're Looking For" with Must Have and Nice to Have. Could split into Requirements (Must Have) and Skills (Nice to Have) or Qualifications. But we need to preserve all info. Could create sections: Requirements (Must Have) and Skills (Nice to Have). Or combine.
- Benefits, Pay, Schedule: we have JOB DETAILS includes Compensation (Pay), Hours (Schedule), Employment Type, Location. Benefits not mentioned. So we can include Pay and Schedule sections.
- About the company: maybe not needed but we can include as a brief intro paragraph before sections.
- Recent Recognition: could be included as a section maybe "Recent Recognition". Not in standard list but we can include as Recent Recognition
with list.
- "YOU MIGHT THRIVE IF" could be considered as "Skills" or "Attributes". Could be included under Skills or maybe as a separate section "Attributes". But to avoid too many thin sections, we could incorporate into Skills or Requirements.
We need to avoid filler like "commensurate with experience". Not present.
We must not include boilerplate like cookie/navigation/legal/EEO etc. Not present.
We must not include application instructions. Not present.
We must not repeat job title as heading. Not needed.
We must not put Job ID/requisition numbers as headings. None.
We need to output only HTML fragment.
Let's structure:
About Retell AI
Recent Recognition
with list. - "YOU MIGHT THRIVE IF" could be considered as "Skills" or "Attributes". Could be included under Skills or maybe as a separate section "Attributes". But to avoid too many thin sections, we could incorporate into Skills or Requirements. We need to avoid filler like "commensurate with experience". Not present. We must not include boilerplate like cookie/navigation/legal/EEO etc. Not present. We must not include application instructions. Not present. We must not repeat job title as heading. Not needed. We must not put Job ID/requisition numbers as headings. None. We need to output only HTML fragment. Let's structure:About Retell AI
... company description ...
Recent Recognition
- ... list items ...
About the Role
... description ...
Responsibilities
- ... each responsibility ...
Requirements
- ... Must Have items ...
Skills
- ... Nice to Have items ...
Pay
$6000–$7500 USD/Month, based on experience
Schedule
Must be open to working some overlapping hours with our Pacific Time team and customers.
Optionally include Employment Type and Location maybe as a short paragraph under Pay or separate? Could add aEmployment Type: Full-Time 1099 Contractor, Location: Remote
maybe under a "Job Details" section but we already have Pay and Schedule. Could add aEmployment Type: Full-Time 1099 Contractor; Location: Remote
after Pay or Schedule. But we must not create sections with filler. Employment Type and Location are substantive; we could add aunder Pay or Schedule or a separate "Job Details" section. Since we already have Pay and Schedule, we could add a
after Schedule: "Employment Type: Full-Time 1099 Contractor. Location: Remote." Let's extract exact text. Company description: "About Retell Ai Retell AI is using first-principles thinking to reimagine the call center with cutting-edge voice AI. Thousands of companies now use Retell's AI voice agents to handle sales, support, and logistics calls that once required large teams of human agents. Backed by Y Combinator, Alt Capital, and other leading investors, we've scaled to $80M in ARR with a team of 50, up from $5M at the start of 2025, and are now valued at over $1.5B. Our vision for 2026 is to build a modern CX platform where entire contact centers are powered by AI. Instead of basic automation that needs constant human tuning, we're creating intelligent AI “workers” that act as frontline agents, QA analysts, and managers, continuously executing, monitoring, and improving every customer interaction. We're growing fast and looking for ambitious builders who want to tackle hard technical problems, move quickly, and have a real impact on one of the fastest-growing voice AI companies in the world. Let's build the future together." We need to preserve all that. Might need to fix spacing: "About Retell Ai" then space then "Retell AI". We'll just output as a paragraph. Recent Recognition list: "No. 1 Best Places to Work in the Bay Area, San Francisco Business Times 2026 Top 50 AI Apps, a16z (2025) #3 Fastest-Growing Software Company, G2 Best Software Awards 2026 Best Agentic AI Software, G2 Best Software Awards 2026 #4 Fastest-Growing Software Vendor, Brex Benchmark 2025 Enterprise Tech 30 Class of 2026, Nasdaq & Wing VC Top-Ranked Startup, Lean AI Leaderboard Backed by Y Combinator" We'll put each as
Attributes
. The instruction didn't forbid other headings; just gave examples. So we can add. But we need to avoid too many thin sections. However each of these sections has substantive content. It's okay. Alternatively we could put YOU MIGHT THRIVE IF under Skills as well. But Skills currently is Nice to Have (technical). Might be okay to add personal traits there. I'll create Skills section that includes both Nice to Have and YOU MIGHT THRIVE IF items. Pay: "$6000–$7500 USD/Month, based on experience" Schedule: "Must be open to working some overlapping hours with our Pacific Time team and customers." Employment Type and Location: we can add a paragraph after Schedule: "Employment Type: Full-Time 1099 Contractor. Location: Remote." Now ensure we don't repeat any content inadvertently. Let's craft HTML. We'll start withAbout Retell AI
...
ThenRecent Recognition
- ...
About the Role
...
Then