AI Engineer, Agents
- Discuss this with your agent
- Open in Claude
- Open in ChatGPT
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Role details
Tech stack
+4 more
Job description
Weâre looking for Senior AI Engineer, Agents - an Agent Architect who will be responsible for designing, building, and scaling AI-powered solutions across EveryWatch. Working closely with our engineering, product, sales, and data teams, they will identify opportunities where AI and LLMs can automate complex processes, improve decision-making, and create new capabilities for our users and internal teams. This is a highly hands-on role for someone who combines strong Python and LLM engineering skills with a creative, proactive mindset. You will not simply be given a roadmap. You will be expected to understand how the business operates, identify where AI can make a meaningful difference, propose new solutions, and take them from idea to production. Our existing AI work, including WatchChat, provides a foundation to build on. The opportunity now is to expand that foundation into a broader ecosystem of intelligent agents that can work with EveryWatchâs unique watch-market data and support collectors, dealers, sales teams, data operations, and engineering. In short, weâre looking for someone who doesnât just ask, âWhat can we build?â but âWhat should we build?â Requirements What youâll actually do
- Invent the agent roadmap. Sit with sales, data and product, find the repetitive expert work, and come back with a ranked list of agents worth building - with a real view on feasibility, cost and impact. This is the core of the job, and it doesnât stop after the first quarter.
- Build them yourself. You are hands-on. You design the architecture and you write the code - tools, loops, sub-agents, memory, state, evaluation. Not a spec-writer with a team underneath.
- Own the platform under the agents. Every new agent should be cheaper to build than the last: shared tool layer over EverWatch data (pricing, auctions, listings, references, portfolios), an MCP surface over our existing backend, shared memory, tracing, and a reusable eval harness.
- Harden WatchChat alongside us. Multi-turn state and memory, latency, cost, tool-call reliability, regression gates. Itâs live-bound and it has to stay right.
- Make quality measurable. Golden multi-turn datasets, programmatic verifiers for tool/argument correctness, LLM-as-judge on held-out sets. If we canât measure an agent, we donât ship it.
- Treat cost and latency as design constraints. Cheap models for routing and intent, strong models where they earn their keep; context budgets, caching, and - where it pays off - fine-tuning (SFT/LoRA on curated production trajectories) instead of ever-larger prompts., 1. Creative. You generate agent ideas the business hadnât thought of, and you can tell the difference between one that will work and one that demos well. You start from a use case, not a framework.
Requirements
- Strong architect. You can design an agent platform thatâs still standing in five years - state, memory, tool boundaries, sub-agent decomposition, evaluation, failure modes, cost. Youâll be asked to critique our current architecture in the interview, and we expect you to find things.
- Heavily hands-on. You ship. Deep production experience, writing the code yourself, at pace. Must have
- 6+ years shipping production software, of which 2+ on LLM systems that real users touched.
- Real agentic depth: ReAct or equivalent loops, tool/function calling, planners, state & checkpointing, long-term memory, HITL steps, streaming. Not âI called the OpenAI API.â
- Hands-on LangGraph (or a strong argument for something better) plus a tracing/observability stack - LangSmith, Langfuse or similar.
- Python in production: FastAPI, async job processing, clean service boundaries.
- RAG done properly: retrieval + re-ranking + relevance judgement, and honest evaluation of all three.
- Evaluation as a habit, not an afterthought (RAGAS/DeepEval/GEVAL, LLM-as-judge, pass@k).
- Cloud production experience - AWS (Bedrock, SQS, EC2/EKS, S3) or equivalent - with Docker and CI/CD.
Benefits & conditions
-
The spine pushes back on us. We explicitly want someone who asks âwhy did you build it like that?â Nice to have
- LLM post-training: SFT with LoRA/QLoRA, preference/RL methods, reward and verifier design.
- Voice agents (LiveKit/Pipecat or similar), or vision-language work.
- Multi-agent orchestration and MCP integrations.
- Text-to-SQL over a real, messy production schema.
- Report/document generation agents - structured, sourced, client-ready output.
- Guardrails, PII handling, hallucination detection, risk scoring.
-
Interest in watches, collectibles or market data. Not required - curiosity about the domain is. Benefits What you get
- Ownership of EverWatchâs entire agent layer, and the roadmap for it - not a corner of someone elseâs.
- A dataset that doesnât exist anywhere else, and users who care whether the answer is right.
- Direct line to the CTO; decisions in days, not quarters.
- Budget for models, tooling, and the coding agents you want to work with.
- Competitive compensation, remote-first. Inscribirse en esta oferta
About the company
Volver a la Ăşltima bĂşsqueda Trabajos ) Trabajos en ingenierĂa ) Senior AI Engineer, Agents ( volver a la Ăşltima bĂşsqueda Recibir ofertas similares por correo electrĂłnico No gracias, llĂŠvame a la oferta de empleo Al crear una alerta, aceptas nuestros TĂŠrminos y condiciones y PolĂtica de privacidad, y el uso de cookies. Inscribirse en esta oferta
Profesiones
- TĂŠcnico
- RecepciĂłnista
- Administrador
- Ventas
- Enfermero
Apply for this position
This job is hosted externally. Click below to view the full posting and apply.
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Good distractions
Talks and stories from around this role â technically off-topic, practically not.
Moments
Explore playlistsVideos
See allRelated articles
See all
From Prototype to Production: Build AI Agents with This Free 4-Course Learning Path
What is Agentic Programming and Why Should Developers Care?
How to Become an AI Engineer
A 5-Step Open-Source Setup for Agentic Engineering