Senior AI Developer Experience Engineer

NewInactive
S
ScribeDeveloper tools
Remote within the U.S.Full-TimeSenior
This job is no longer active. We keep the page for reference, but the employer may not accept new applications.

Open jobs in this role

  • Senior AI Developer Experience Engineer
    JobgetherBased in the United StatesCompetitive annual base salary based on location: Tier 1 (San Francisco, New York City, Seattle): $175,000–$240,000. Tier 2 (including Boston, Los Angeles, Chicago, Washington, D.C., and Denver): $160,000–$214,000. Tier 3 (all other U.S. locations): $160,000–$214,000.
    Apply

Job Details

Required Skills
PythonSQLTypeScriptGo

Requirements

  • Have deep, hands-on experience owning test, lint, build, or CI infrastructure in a substantial codebase.
  • Have experience in at least one ecosystem such as TypeScript, Go, or Python/Django, and the systems judgment to learn others.
  • Be able to diagnose slow pipelines, flaky tests, and broken development environments.
  • Have hands-on experience instrumenting production systems with error tracking, tracing, and logs.
  • Have experience designing, building, and maintaining dependable internal tools and integrations.
  • Use agentic coding tools daily and critically.
  • Have built or adapted at least one AI development workflow adopted by other engineers, including context management, validation, and failure handling.
  • Be comfortable with SQL and analyzing operational data.
  • Be able to define and defend useful metrics and recognize when they are being gamed.
  • Bonus: experience with Temporal or similar workflow orchestration engines, GitHub Actions internals, large test suite optimization, or agent harness customization.

Responsibilities

  • Own the speed and reliability of CI and test infrastructure on the main monorepo, including sharding, caching, flake detection, test discovery, and runner economics.
  • Define software instrumentation standards for error tracking, tracing, event context, and joining errors to traces.
  • Turn observability conventions into shared libraries, automated checks, and agent instructions.
  • Co-own engineering bots and deterministic checks that identify problems before human review.
  • Ensure each DevEx-operated system has a second operator, a runbook, and adoption and quality metrics.
  • Improve local setup, worktrees, seeded databases, and onboarding to make development environments easier to use.
  • Establish baselines and use operational data and developer feedback to evaluate tools and workflows.
  • Take tooling projects from proposal and success criteria through rollout and published results.