AI Tech Lead
Inorsa · Austin, TX
—
Jul 20, 2026
Austin, TX
Jul 21, 2026
What this job asks for AI summary
A senior AI engineering role focused on building and hardening agentic automation systems for infrastructure engineering verticals such as telecom and data centers. The work centers on designing multi-step agentic workflows with LangGraph, owning observability and evaluation pipelines via LangSmith, and collaborating with domain experts to encode specialized engineering knowledge into production-grade AI tooling. Suits an experienced engineer with deep hands-on LangGraph expertise and a track record shipping reliable AI systems.
Senior level · 6+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 3,100 people nationally plausibly meet what this posting asks for (software developers). range 1,300–4,700
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (9)
No work location or metro is specified in the posting; the role appears fully remote based on the absence of any office or location requirement.
The title carries no explicit seniority level ('Unspecified'), but the 6+ years requirement, expert-level LangGraph proficiency, and architectural ownership scope support a Senior classification.
LangSmith is listed as a hard requirement but the JD also says 'or equivalent observability tooling for agentic systems' — alternatives were not named, so LangSmith is captured as the primary with no alternatives (no well-known drop-in substitute exists at this specificity).
AWS and GCP are presented as interchangeable cloud targets ('AWS or GCP'); AWS is listed as primary with GCP as the alternative.
TypeScript/Node.js, SQL, and cloud infrastructure are described as 'familiarity with the broader stack' — a softer framing than the hard-gated requirements above, so these are marked preferred.
Cursor and GitHub Copilot appear in the 'Lead by example' narrative section rather than a formal requirements block, so they are marked preferred.
GIS data experience is mentioned as an example of domain-specific data types ('GIS data, or similar') within the requirements section, but the 'or similar' framing makes it illustrative rather than a hard gate — marked preferred.
The alt SOC 15-2051 (Data Scientists) is noted because the role has a meaningful ML/AI evaluation and modeling dimension, but the primary day-to-day work is building and shipping agentic software systems, which aligns more closely with 15-1252.
This posting reads as a fully-remote role, so it was scored against the national candidate pool rather than a single metro.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.