Technical AEO/SEO Specialist

Telnyx

13h

About The Position

Telnyx is hiring a Technical AEO/SEO Specialist to own quality for telnyx.com on the AEO team. The role ensures that pages published by Product Marketing, DevRel and Dotcom work for people, search engines and AI agents. The specialist reviews pages before and after launch, verifies claims and pricing, keeps HTML pages synchronized with their markdown twins, and maintains the site's agent-readiness score. When possible, the specialist makes fixes through pull requests; otherwise, they create evidence-based Linear tickets for the appropriate team. The role also tests AI-agent journeys, monitors whether AI crawlers can access the site, maintains discovery files and crawler policies, and performs daily crawls of telnyx.com and satellite sites. It owns launch and migration QA, builds automated checks to detect content and technical drift, and reviews emerging agent standards to recommend potential adoption. Telnyx describes itself as a profitable company building global connectivity infrastructure, including a private global multi-cloud IP network and API-based edge technology. It emphasizes innovation, automation, continuous learning and growth.

Requirements

2 to 3+ years of experience in technical SEO, web QA or web development, or equivalent demonstrable hands-on work.
Strong attention to accuracy, including checking source information before approving prices and feature claims.
Advanced Screaming Frog skills, including daily crawls, custom extractions and segments, and prioritizing fixes from crawl exports.
Comfort with Git and GitHub and the ability to open clean pull requests for metadata, schema, links or copy fixes, while knowing when to involve Engineering.
Working knowledge of HTML, CSS and JavaScript sufficient to debug rendering, canonicals, redirects, status codes and headers.
Understanding of how AI agents access websites, including llms.txt, markdown twins, Accept: text/markdown, AI crawler user agents and robots.txt policies.
Knowledge of search fundamentals, including crawling, indexing, sitemaps, structured data and Core Web Vitals, and how these relate to Google and AI agents.
Ability to QA a steady volume of pages from fast-moving teams without missing details or becoming a bottleneck.
Experience using scripts, APIs or AI agents—such as Python, JavaScript, Claude Code or Cursor—to automate audits, comparisons or alerts.
Comfort with Google Search Console, GA4 and Ahrefs or Semrush, and the ability to evaluate the impact of fixes.
Clear, friendly and evidence-based communication when reporting issues and fixes.
Organization in Linear, ensuring issues have tickets, owners and statuses.

Nice To Haves

Experience with Next.js, React or Vercel, including server-side rendering, static generation and JavaScript SEO.
Experience shipping llms.txt, markdown twins or agent discovery files on a live site, or improving agent-readiness using Ora.ai, is-agentic or Lighthouse's agentic browsing audit.
Experience with a headless CMS such as Contentful or Sanity, including content models and publishing workflows.
Familiarity with CDN and firewall configuration, including caching, bot rules and headers on Cloudflare or Vercel.
Experience analyzing server logs to identify which search and AI crawlers visited pages and what they received.
Experience with automated testing such as Playwright or Cypress for detecting SEO or content regressions in CI.
Python or SQL skills for retrieving data, comparing crawls or checking pages at scale.
Familiarity with OpenAPI specs, API documentation or MCP servers.
Experience at a developer tool, API, cloud or telecom company where technical accuracy of web content is important.
Site migration experience, including URL mapping, launch-day checks and post-launch cleanup.
International SEO experience, including hreflang and localized pages.
Accessibility fundamentals, including accessible names, form labels and document structure.

Responsibilities

Review every new and updated telnyx.com page before and after publication, checking titles, meta descriptions, H1s, canonicals, schema, internal links, images, forms and mobile layout.
QA pages published by Product Marketing, DevRel and Dotcom, catching broken, inaccurate or poorly discoverable content.
Verify that claims about Telnyx features, regions, models, numbers and compliance are accurate and current, and correct misleading or incomplete pages.
Fix issues directly through pull requests when possible; otherwise, create clear Linear tickets with supporting evidence and the required fix.
Run AI agents through key user journeys, including checking prices, signing up and making a first API call, and address failures.
Keep each page's markdown twin synchronized with its HTML, test responses to Accept: text/markdown requests, and ensure pages link to their twins.
Run Ora.ai scans on every release and during daily checks, and address findings to maintain an A+ agent-readiness score.
Ensure important content on the homepage, pricing pages and documentation is available in raw HTML rather than only through JavaScript.
Test firewall and bot rules for major AI crawlers, including GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot, and review server logs for access problems.
Maintain valid root and section llms.txt files under the v2 spec, with working links and content that matches the live site.
Keep llms.txt, the API catalog, OpenAPI spec, agent skills index and MCP server card current, valid and linked from page headers and the footer.
Maintain accurate robots.txt and content signals describing which AI crawlers may search, fetch or train on content, and ensure the file does not error or return HTML.
Use Screaming Frog to crawl telnyx.com and satellite sites daily, identifying broken links, redirect chains, orphan pages, metadata issues, canonical errors and indexing problems.
Own QA checklists for new sections, redesigns and URL changes; validate sitemaps, indexing, markdown twins and llms.txt on launch day and monitor for regressions afterward.
Build post-deploy checks that compare pages with their markdown twins, pricing sources and discovery files, and alert when content no longer matches.
Review emerging agent standards each quarter, including NLWeb, A2A, Web Bot Auth and agent payment protocols, and recommend which Telnyx should adopt.
Use data from Google Search Console, GA4 and Ahrefs or Semrush to assess whether fixes have an effect.
Track discovered issues in Linear with an owner and status, and communicate findings clearly and constructively.