Technical AEO/SEO Specialist

The role

Telnyx ships pages fast. Product Marketing, DevRel and Dotcom publish constantly, and every page has to work for people, search engines and the AI agents developers now use to choose providers. One wrong price, a broken markdown twin or a page that agents can’t read costs us signups. Your job is to make sure none of that reaches production.

You’ll own quality for telnyx.com on the AEO team. You’ll review every page that ships, crawl the site daily in Screaming Frog, keep pages and their markdown twins accurate down to the pricing, and keep our agent-readiness score at A+. When you find a problem, you fix it yourself with a pull request whenever you can.

What you’ll do

Quality and accuracy

• Be the quality gate for telnyx.com. Review every new and updated page before and after it goes live, covering titles, metas, H1s, canonicals, schema, internal links, images, forms and mobile layout, and catch problems before customers or search engines do.
• QA the work of fast-moving teams. Product Marketing, DevRel and Dotcom ship constantly. You check their pages so nothing goes live broken, inaccurate or invisible.
• Hold the line on accuracy. Every claim about what Telnyx offers has to be true and current, including features, regions, models, numbers and compliance. If a page overstates, leaves something out or misleads, you fix it.
• Fix it, don’t just flag it. When you can fix something yourself, open the pull request. When you can’t, write a clear Linear ticket with the evidence and the exact fix needed.

Agent readiness

• Test real agent journeys. Regularly run AI agents through key tasks such as checking a price, signing up and making a first API call, then fix whatever breaks.
• Keep every page and its markdown twin in sync. Make sure the .md twin of each page says exactly what the HTML says. Check that requests sent with Accept: text/markdown get clean markdown back, and that each page links to its twin.
• Own our agent-readiness score. Run the Ora.ai scan on every release and on a daily check, and keep telnyx.com at A+ by fixing anything it flags before the drop compounds.
• Make sure AI agents can actually read our pages. Key answers on the homepage, pricing and docs have to be in the raw HTML, because agents that only fetch pages can’t run JavaScript.
• Keep AI crawlers from getting blocked. Test our firewall and bot rules against the major AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and the ones that fetch on a user’s behalf), and check server logs, because a single 403 shuts them all out.

Discovery files and policy

• Maintain llms.txt for the site and docs. Keep the root and section llms.txt files valid under the v2 spec, with every link resolving and every file in step with what’s live.
• Keep discovery files current and linked. Keep llms.txt, the API catalog, the OpenAPI spec, the agent skills index and the MCP server card live and valid. Link them from page headers and the footer, because agents mostly find these files through links, not by guessing paths.
• Run our AI crawler policy. Keep robots.txt and its content signals accurate about which AI crawlers may search, fetch or train on our content, and make sure the file never errors out or returns HTML.

Crawling, launches and automation

• Live in Screaming Frog. Crawl telnyx.com and our satellite sites every day to find broken links, redirect chains, orphan pages, missing or duplicate metadata, canonical errors and indexing problems.
• Validate every launch and migration. Own the checklist for new sections, redesigns and URL changes. Confirm sitemaps, indexing, twins and llms.txt on launch day, then watch for regressions over the following weeks.
• Catch drift automatically. Build checks that run after every deploy and compare each page against its twin, the pricing source and our discovery files, with an alert when anything stops matching.
• Track new standards each quarter. Review emerging agent standards such as NLWeb, A2A, Web Bot Auth and agent payment protocols, and recommend which ones Telnyx should adopt.

What we’re looking for

• Experience that fits. 2 to 3+ years in technical SEO, web QA or web development, or equivalent hands-on work you can show us.
• Obsessed with accuracy. A wrong price or a feature claim we can’t back up bothers you, and you check the source before you sign off on a page.
• A Screaming Frog power user. You run crawls daily, set up custom extractions and segments, and can turn a crawl export into a prioritized fix list quickly.
• You fix things yourself. You’re comfortable in Git and GitHub, can open a clean pull request for metadata, schema, links or copy fixes, and know when to hand something to Engineering instead.
• Solid web fundamentals. You read HTML, CSS and JavaScript well enough to debug rendering, canonicals, redirects, status codes and headers without help.
• You understand how AI agents read the web. You know llms.txt, markdown twins, Accept: text/markdown, AI crawler user agents and robots.txt policy, and why JavaScript-only content and 403s lock agents out.
• Fluent in search fundamentals. You understand crawling, indexing, sitemaps, structured data and Core Web Vitals, and you know which of these matter for Google and which matter for AI agents.
• Detail-obsessed, at speed. You can QA a steady stream of pages from fast-moving teams without letting the small things slip, and without becoming a bottleneck.
• You automate the repetitive checks. You’ve used scripts, APIs or AI agents (Python, JavaScript, Claude Code, Cursor or similar) to automate audits, comparisons or alerts.
• Data literate. You’re comfortable in Google Search Console, GA4 and Ahrefs or Semrush, and can show whether a fix actually moved anything.
• Clear, unemotional communication. You can tell a PMM their page has a pricing error in one Slack message, with the evidence and the fix, and keep it friendly.
• Organized in Linear. Every issue you find has a ticket, an owner and a status, and anyone can see where things stand without asking you.

Bonus points for

• Experience with Next.js, React or Vercel, including server-side rendering, static generation and JavaScript SEO.
• You’ve shipped llms.txt, markdown twins or agent discovery files on a real site, or improved a site’s agent-readiness score with 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.
• Comfort with CDN and firewall settings, like caching, bot rules and headers on Cloudflare or Vercel, enough to see when they block crawlers.
• Server log analysis, so you can see which search and AI crawlers hit which pages, and what they got back.
• Automated testing, such as Playwright or Cypress checks that catch SEO or content regressions in CI.
• Python or SQL for pulling data, comparing crawls or checking pages at scale.
• Familiarity with OpenAPI specs, API docs or MCP servers, so you can QA developer-facing pages and the files agents use.
• Experience at a developer tool, API, cloud or telecom company, where pages have to be technically accurate.
• Site migration experience, including URL mapping, launch-day checks and cleanup afterward.
• International SEO, including hreflang and localized pages.
• Accessibility basics, like accessible names, form labels and document structure, which help both screen readers and browser agents.

#LI-RH1