AI Agent Engineer

huntingcube

Kushalnagar 2 Years Exp Posted 4h ago

Job Description

  • Build agents that do real work. Design and ship LLM-powered systems that take a multi-step task and see it through, deciding what to do, taking action across our systems and third parties, and knowing when to hand off to a human.
  • Own quality and evaluation. Build the infrastructure that measures how well our AI performs, catches regressions before users feel them, and turns production signals into better prompts, retrieval, and models. Make quality a number we can move, not a vibe.
  • Build the knowledge layer. Design the retrieval systems our agents reason over and solve the harder half: keeping that knowledge accurate, versioned, and fresh as the underlying sources change.
  • Build AI into the product. Ship copilots and assistive features that make our users meaningfully faster, with clear judgment about when the model should act and when it should ask.
  • Close the loop on real usage. Deploy to production, watch how the systems behave with real users, and improve from what actually happens in days, not quarters.
  • Shape the technical roadmap. Work with the founders on what to build next. Bring a sharp sense of what current models can and can't do, and help us make smart bets on where the technology is heading.
  • Lay the foundation for scale. Make architectural decisions that hold up as usage grows by orders of magnitude, and build with the next engineer in mind.

Requirements:

  • You've built LLM-powered systems or agents and shipped them to production, not demos, but systems handling real usage by real people.
  • Strong overall AI fluency.
  • You can reason concretely about prompting, tool use, context management, retrieval, latency, cost, and failure modes.
  • You've built evaluation into your work, designed metrics, captured signal from production, and used it to systematically improve quality.
  • You've monitored and debugged AI systems in production, and you know what it takes to keep them reliable when real people depend on them.
  • Solid software engineering fundamentals. You write code others can maintain, and you own what you ship.
    • You're comfortable with ambiguity. The playbook doesn't exist yet, and you're excited to build it.

Similar Openings for You