Agentic DevEx Engineer

Overview

We're hiring an Agentic Dev Ex Engineer — a systems-minded engineer who owns the infrastructure, standards, and tooling that make AI agents effective collaborators in our codebase. This is a rare role at the intersection of Platform Engineering, Developer Experience, and AI. You'll be responsible for transforming how humans and agents work together ay, AI coding agents are powerful but inconsistent.

They hallucinate file paths, miss context, violate conventions, and require constant hand-holding. Your job is to eliminate that friction.

Singular Mandate: Maximize the effectiveness of agents inside Ekho’s codebase so that both humans and AI can execute predictably, safely, and at scale.

• Codebase Architecture & Structure

  • Define and enforce architectural boundaries
    : establish clear domain separation, eliminate duplicated modules, and create discoverable code organization.

  • Build reproducible development environments
    : standardized commands (dev, test, lint, build) that work identically for humans and agents across all surfaces.

  • Maintain the single source of truth for how the codebase is organized, documented in ARCHITECTURE.md files per domain.

• Agent Infrastructure & Tooling

  • Own AGENTS.MD / CLAUDE.MD
    : transform our agent instructions from verbose, ad-hoc documents into concise, high-signal guides that improve agent accuracy.

  • Design and implement agent hooks
    : deterministic workflows for how agents plan, read context, execute changes, and validate output.

  • Build a library of reusable agent skills
    : well-defined, domain-specific capabilities (e.g., "analyze payment invoice", "update Firebase function safely") with clear contracts.

  • Ensure agents can navigate the codebase without tribal knowledge — predictable paths, explicit boundaries, and machine-readable context.

• Standards & Enforcement

  • Codify engineering standards
    : capture Ekho's conventions (formatting, naming, patterns, error handling) explicitly and enforce them through linters.

  • Improve the automated review layer
    : CI checks, static analysis, and AI-powered reviewers that catch misalignment before human review.

  • Own validation infrastructure
    : improve test reliability, reduce flakiness, establish schema guarantees, and ensure CI provides fast, accurate feedback.

  • Create the feedback loop: track recurring issues, refine standards, and continuously improve the system.

• Developer Experience & Adoption

  • Define work modeling standards
    : templates for tickets and specs that capture context, constraints, and acceptance criteria explicitly — so agents can execute without ambiguity.

  • Build canonical workflows
    : documented patterns for common tasks (bugfix, feature, refactor) that engineers follow with agent assistance.

  • Own AI observability
    : instrument engineering workflows to track PR cycle time, AI-assisted PR percentage, and other signals of agent effectiveness.

  • Drive adoption
    : train the team on agent collaboration patterns, create demos, and ensure the right way is the easy way.

• You Must Be AI-Pilled

  • This role requires someone who is obsessed with the AI tooling landscape — not casually interested, not wanting to merely keep an eye on it, but genuinely compelled to try every new agent, workflow, and integration the moment it drops.

  • You should be
    : Constantly experimenting. You've tried Claude Code, Cursor, Copilot, Windsurf, Aider, and whatever launched last week. You have strong opinions about where each excels and fails. You've probably built custom workflows or prompts that you're unreasonably proud of.

  • A forcing function for adoption. You don't just try new tools — you push the team to adopt the ones that work. You're opinionated about workflows that deliver step-function improvements in efficiency, and you're not shy about advocating for change.

  • A teacher and evangelist. You share what you learn — in Slack, in demos, in documentation. You get energy from helping others level up. You understand that tooling only matters if people actually use it.

  • Impatient with the status quo. You see manual, repetitive engineering work as a problem to be automated, not a fact of life. You're allergic to "that's just how we do it."

• If you're not spending personal time…