Senior AI Engineer, Release Engineering
Senior AI Engineer, Release Engineering
Posted 2 days ago
SENIORITY
Lead
About the role
- Design, build, and maintain the platform - including the agent API, MCP integrations, and intent-routing logic.
- Build MCP integrations that connect agents to CI/CD, source control, ticketing, and deployment tools, with clear schemas, robust error handling and logging, and defined scope boundaries.
- Build and maintain the skill and agent registry that matches user intent with the appropriate agent and context at runtime.
- Maintain a modular architecture so new agents, skills, and MCP integrations can be added without disrupting existing capabilities.
- AI Development Life Cycle (AIDLC) - Agentic Workflows
- Design multi-step, tool-using agents that select tools, reason across context, and produce reliable, structured output.
- Author, test, and iterate on prompts, skill definitions, and context structures while managing context windows and token budgets.
- Design for failure by anticipating how agents fail, context degrades, and prompts drift - and by defining how the system recovers.
- Build release and CI/CD agents for pipeline triage, release-readiness checks, change documentation, and rollback assistance in partnership with release and development teams.
- Curate and maintain the AIDLC, outlining best practices, and championing the process across the company.
- Experience with agentic technologies such as LangChain, LlamaIndex, LiteLLM, or AutoGen, along with the judgment to determine when a leaner custom approach is more appropriate.
- Experience in Node.js/TypeScript, Go, and/or Python
- Demonstrated experience building and delivering at least one production or near-production agentic automation/process that uses LLM APIs, such as Anthropic, OpenAI, and LiteLLM, with tool calling and structured output.
- Practical experience with MCP or equivalent tool-calling frameworks, including schema design, agent-tool integration, and scope management.
- Experience evaluating LLM outputs by using evaluation sets, regression testing, and quality metrics.
- Experience with retrieval-augmented generation (RAG) and vector databases.
- Experience with cloud AI platforms such as Amazon Bedrock, Azure OpenAI, or Vertex AI.Experience with internal developer platforms or platform-as-a-product models.
- Frontend development experience with React or Angular.
- Relational database design experience.
- Experience with LLM observability tools.
- Experience with infrastructure as code and configuration management tools such as Terraform, Ansible, Puppet, or Chef.
- Experience working in regulated or audited environments.
- Experience with Agile practices and automated testing.
- Experience with containers and orchestration platforms such as Kubernetes or OpenShift, along with proficiency in Linux environments.
- Experience troubleshooting distributed systems (e.g., Kubernetes workloads, CI/CD pipelines, message queues).What We Look ForAn engineer who treats agentic AI as a design discipline and has a demonstrated record of applying emerging LLM and agent capabilities in practice.
- A platform thinker who views agents, skills, MCP integrations, and the registry as one cohesive developer product.
- Someone who takes ownership of reliability, security, and quality, and makes failure modes explicit.
- A collaborative partner who reduces friction across the broader engineering organization and can build trust with skeptical teams.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
