Enterprise Account Executive, East

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 Telnyx (company description) maybe not needed as heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need sections like About the role (maybe summarizing role description), Responsibilities (What You'll Do), Requirements (What We're Looking For?), Qualifications maybe overlapping, Skills maybe bullet list, Benefits maybe not present? Pay and Schedule not present. So we should not create Pay/Schedule/Benefits sections unless posting actually states them. The posting does not mention benefits, pay, schedule. So we omit those sections. We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO etc). The posting includes "About Telnyx" description; we could put that under About the role? Actually "About the role" heading likely for role description. Could include company description under About the role or maybe separate? The instruction says use those headings for sections; we can include About the role with role overview (The Role section). Could also include About Telnyx as part of About the role? Probably better to put company description under About the role as introductory paragraph. Responsibilities: "What You'll Do" bullet list. Requirements: maybe "What We're Looking For" includes experience etc. Could split into Requirements (experience) and Qualifications (maybe education? none). Skills: list of skills like consultative selling, methodology, tools, communication, travel willingness. Bonus Points could be under Skills or Qualifications? Might be extra qualifications. We'll treat Bonus Points as additional qualifications/skills. We must not invent placeholders. Ensure we include all specifics: numbers, accounts, etc. Let's extract: About Telnyx paragraph: description of company. The Role: description of owning named list 30-40 accounts, pod model, etc. What You'll Do: bullet list items: - Own 30–40 named enterprise accounts in US East, narrowing to about 10 Tier 1 accounts, each worth $1M+ in annual potential - Write a workload thesis for every Tier 1: the specific production outcome, who owns it, what it's worth, and what has to be true to win it - Get in the room with CIOs, CTOs, VPs of Engineering, and the line-of-business owners who actually hold the budget - Run the full cycle alongside your FDE — prospect, qualify, design the commercial architecture, negotiate, close - Agree the commercial destination before any custom work begins. No free discovery, no free development. - Hold the line on POC discipline: named executive sponsor, written success criteria, production pricing already discussed, a decision date, and a signed commercial document. POCs end in production or they end. - Expand the account — one workload becomes three, one $500K customer becomes a $2M customer - Forecast accurately and keep the pipeline clean. No surprises. What We're Looking For: bullet list: - 5+ years of enterprise sales experience selling CPaaS, UCaaS, CCaaS, telecom, or AI/ML platforms - Consistent overachievement against a seven-figure quota, with individual deals over $1M - Credible with executive and technical buyers alike — you hold your own in the boardroom and in the architecture review - Hunter mentality. You build your own pipeline and you like doing it. - Consultative selling range: you can build the ROI case for a CFO and the technical case for a VP of Engineering, and hold your ground against Twilio and Vonage - Disciplined with a methodology (MEDDPICC, Challenger, SPIN) and with the stack (Salesforce, Outreach, Gong) - Excellent written and verbal communication. You listen before you pitch. - Willing to travel across US East to meet customers in person Bonus Points For: - Fortune 500 or large-enterprise new-logo experience in the US East market - Complex sales cycles involving RFPs and competitive bake-offs, plus procurement, security, and legal review - Working knowledge of SIP trunking, number provisioning, carrier networks, or AI/ML infrastructure - Established relationships in the US East enterprise ecosystem — financial services (Goldman Sachs, JPMorgan Chase, Citigroup, Morgan Stanley, BlackRock), media/tech (Bloomberg, NBCUniversal, Warner Bros Discovery, Verizon), healthcare (Pfizer, NewYork-Presbyterian, Northwell), or Boston/DC/Atlanta markets We need to decide sections: About the role (maybe include company description + role overview). Responsibilities (What You'll Do). Requirements (What We're Looking For). Qualifications maybe could be same as Requirements? Could separate: Requirements = experience, Qualifications = education/certifications (none). Since none, we could omit Qualifications. Skills: maybe list of skills like consultative selling, methodology, tools, communication, travel. Could be under Skills. We must not create sections with filler. So we will include About the role, Responsibilities, Requirements, Skills. Possibly also Qualifications if we have something like "Bonus Points For" could be qualifications. But we could put Bonus Points under Skills or Qualifications. Since they are extra qualifications, we could put them under Qualifications. Let's do: Qualifications includes the bullet list under "What We're Looking For" plus Bonus Points? Actually "What We're Looking For" is requirements. Bonus Points are extra qualifications. We could combine them under Qualifications. But we need to avoid duplication. Let's decide: - About the role: company description + role overview (The Role paragraph). - Responsibilities: What You'll Do bullet list. - Requirements: core requirements (5+ years experience, overachievement, credible, hunter mentality, consultative selling, disciplined methodology, communication, travel). - Qualifications: Bonus Points (Fortune 500 experience, complex sales cycles, working knowledge, established relationships). - Skills: maybe we could list specific skills like consultative selling, methodology, tools, communication, travel. But that overlaps with Requirements. Better to put skills under Requirements? The instruction says use those headings for sections; we can have overlapping content but we need to avoid thin sections. Perhaps we can combine Requirements and Qualifications into one section? But we need to follow instruction: use headings for sections when we have real specific content. We can have multiple sections: About the role, Responsibilities, Requirements, Qualifications, Skills. Ensure each has substantive content. Let's assign: About the role: includes company description and The Role paragraph (overview). Responsibilities: What You'll Do bullet list. Requirements: core requirements bullet list (5+ years experience, overachievement, credible, hunter mentality, consultative selling, disciplined methodology, communication, travel). Qualifications: Bonus Points bullet list. Skills: maybe we can list specific skills like "Consultative selling, ROI case building, technical case building, MEDDPICC/Challenger/SPIN, Salesforce, Outreach, Gong, written/verbal communication, travel willingness". But that duplicates Requirements. Could instead list "Technical knowledge: SIP trunking, number provisioning, carrier networks, AI/ML infrastructure". That's part of Bonus Points though. Hmm. Maybe we skip Skills section to avoid thin content. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications. That's four sections. That seems fine. We must not include Benefits, Pay, Schedule. Now produce HTML fragment:

About the role

Telnyx is an industry leader that's not just imagining the future of global connectivity—we're building it. From architecting and amplifying the reach of a private, global, multi-cloud IP network, to bringing hyperlocal edge technology right to your fingertips through intuitive APIs, we're shaping a new era of seamless interconnection between people, devices, and applications. We're driven by a desire to transform and modernize what's antiquated, automate the manual, and solve real-world problems through innovative connectivity solutions. As a testament to our success, we're proud to stand as a financially stable and profitable company. Our robust profitability allows us not only to invest in pioneering technologies but also to foster an environment of continuous learning and growth for our team. Our collective vision is a world where borderless connectivity fuels limitless innovation. By joining us, you can be part of laying the foundations for this interconnected future. We're currently seeking passionate individuals who are excited about the opportunity to contribute to an industry-shaping company while growing their own skills and careers.

The Role: Most communications platforms resell someone else's network. We built ours — a private global IP network, our own carrier interconnects, and the voice, messaging, wireless, and inference stack that runs on top of it. When latency and uptime are the product, owning the infrastructure is the difference between a demo and a deployment. We're hiring Enterprise Account Executives to sell that stack across US East. You'll own a named list of 30–40 accounts and work in a pod with a dedicated Forward Deployed Engineer (FDE) to turn them into production Telnyx customers. This is not a remote overlay on an existing territory. One AE, one FDE, full cycle — executive relationship through production deployment. You win together. Nothing gets thrown over the wall. You sell the workload, not the SKU. Enterprises buy a production outcome — an AI contact center, a SOC/NOC agent, global communications, connected mobility, enterprise inference — that runs on Telnyx primitives. You lead with the outcome, not the product menu. The Pod Model Enterprise AE — owns the named-account list, builds the executive relationships, gets in the room, runs commercial qualification and close, expands the account. Forward Deployed Engineer — owns technical discovery, designs the architecture, builds the proof of concept when one is required, gets the first workload live, clears blockers and finds the next workload.

Then Responsibilities:

Responsibilities

• Own 30–40 named enterprise accounts in US East, narrowing to about 10 Tier 1 accounts, each worth $1M+ in annual potential
• Write a workload thesis for every Tier 1: the specific production outcome, who owns it, what it's worth, and what has to be true to win it
• Get in the room with CIOs, CTOs, VPs of Engineering, and the line-of-business owners who actually hold the budget
• Run the full cycle alongside your FDE — prospect, qualify, design the commercial architecture, negotiate, close
• Agree the commercial destination before any custom work begins. No free discovery, no free development.
• Hold the line on POC discipline: named executive sponsor, written success criteria, production pricing already discussed, a decision date, and a signed commercial document. POCs end in production or they end.
• Expand the account — one workload becomes three, one $500K customer becomes a $2M customer
• Forecast accurately and keep the pipeline clean. No surprises.

Requirements:

Requirements

• 5+ years of enterprise sales experience selling CPaaS, UCaaS, CCaaS, telecom, or AI/ML platforms
• Consistent overachievement against a seven-figure quota, with individual deals over $1M
• Credible with executive and technical buyers alike — you hold your own in the boardroom and in the architecture review
• Hunter mentality. You build your own pipeline and you like doing it.
• Consultative selling range: you can build the ROI case for a CFO and the technical case for a VP of Engineering, and hold your ground