Time since we first saw it
Day 3
Similar jobs usually come down between day 1 and day 15.
From 1,376 similar postings that came down. Coming down is not always a hire.
Azumo builds and operates production AI systems for companies ranging from seed-stage startups to Meta. We are hiring an AI Engineer to own what those systems do once they are live: retrieval pipelines, tool-using agents, evaluation harnesses, and the guardrails that keep them dependable in front of real users. The role is fully remote across Latin America, aligned to your client's working day. You will not be building demos. Azumo has shipped production AI since 2016, and the work here starts where the prototype ends, making a system reliable, measurable, and affordable enough to put in front of customers.Read the full posting
Employment type in the employer’s posting: Full-timeFrom the employer’s posting
Build chunking, embedding, hybrid search, and reranking for retrieval systems
Build stateful agentic workflows with tool calling and MCP servers
Write test sets and regression tracking for prompt and model changes
Add prompt-injection defense, output validation, and PII handling
Run containerized deployment, CI/CD, and observability with latency and cost budgets
Chunking and embedding pipelines, hybrid search, reranking, and evaluation of retrieval quality
Stateful multi-step execution, tool calling, MCP servers, structured output enforcement
Test sets that reflect the decision the system is actually making, model-as-judge scoring, regression tracking across prompt and model changes
Prompt-injection defense, output validation, guardrails, PII handling
Containerized deployment on Azure or AWS, CI/CD, observability, and explicit latency, cost, and token budgets
4+ years building and shipping production software, with a modern backend language (e.g., Python) as your primary focus, plus the engineering fundamentals that go with it: testing, code review, CI/CD, Git, containers, API design, and async programming.
Experience with agent frameworks and tooling: LangGraph, LangChain, CrewAI, the Model Context Protocol (MCP), or native Python execution loops. We care that you have shipped a stateful, tool-using system, not which framework you used.
Bachelor's degree in Computer Science, Data Science, or a related field, or equivalent professional experience.
- Clear written and spoken English, C1 or above, and the confidence to explain a technical trade-off directly to a client. - Bachelor's degree in Computer Science, Data Science, or a related field, or equivalent professional experience. Preferred qualifications
From the employer’s posting.
We provide nearshore AI engineering teams to organizations that need production AI faster than they can hire for it: as an embedded engineering team, as AI staff augmentation alongside an existing team, or as a full project build.
In the employer’s words · Read in context
Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 3
Similar jobs usually come down between day 1 and day 15.
From 1,376 similar postings that came down. Coming down is not always a hire.
4 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
Basic qualifications - 4+ years building and shipping production software, with a modern backend language (e.g., Python) as your primary focus, plus the engineering fundamentals that go with it: testing, code review, CI/CD, Git, containers, API design, and async programming. - Demonstrable production experience with LLM-based systems: retrieval-augmented generation, function and tool calling, structured output enforcement, and prompt design as an engineering discipline rather than trial and error.
- Hands-on work with vector and retrieval infrastructure such as pgvector, Pinecone, Qdrant, FAISS, or Azure AI Search, including the retrieval-quality problems that come with it. - Experience with agent frameworks and tooling: LangGraph, LangChain, CrewAI, the Model Context Protocol (MCP), or native Python execution loops. We care that you have shipped a stateful, tool-using system, not which framework you used. - You have built an evaluation suite for an LLM system. Test-set design, model-as-judge or equivalent scoring, and regression tracking with Langfuse, Ragas, LangSmith, or something you wrote yourself. This is the requirement we screen hardest on.
- Reliability and safety. Prompt-injection defense, output validation, guardrails, PII handling, and graceful degradation when a model or tool call fails. - Production operation. Containerized deployment on Azure or AWS, CI/CD, observability, and explicit latency, cost, and token budgets that you own rather than discover after the invoice. - Work inside the client's environment. Their repositories, their standups, sometimes their customer calls. Azumo is SOC 2 certified, client code stays in client repositories, and some engagements carry additional requirements such as HIPAA.
- You have built an evaluation suite for an LLM system. Test-set design, model-as-judge or equivalent scoring, and regression tracking with Langfuse, Ragas, LangSmith, or something you wrote yourself. This is the requirement we screen hardest on. - Cloud deployment experience, Azure preferred and AWS acceptable, with Docker, CI/CD pipelines, and infrastructure as code (GitHub Actions, Terraform, or Bicep). - Working discipline around latency, token cost, and throughput. You can explain what a feature costs to run and what you did about it.
What you will build - Retrieval systems. Chunking and embedding pipelines, hybrid search, reranking, and evaluation of retrieval quality, built on pgvector, Pinecone, Qdrant, FAISS, or Azure AI Search. - Agentic workflows. Stateful multi-step execution, tool calling, MCP servers, structured output enforcement, context-window management, deterministic fallbacks, and human-in-the-loop gates for the decisions that need one.
- Demonstrable production experience with LLM-based systems: retrieval-augmented generation, function and tool calling, structured output enforcement, and prompt design as an engineering discipline rather than trial and error. - Hands-on work with vector and retrieval infrastructure such as pgvector, Pinecone, Qdrant, FAISS, or Azure AI Search, including the retrieval-quality problems that come with it. - Experience with agent frameworks and tooling: LangGraph, LangChain, CrewAI, the Model Context Protocol (MCP), or native Python execution loops. We care that you have shipped a stateful, tool-using system, not which framework you used.
Complete your application on apply.workable.com. The employer’s form will show what is required.
Already applied? Track this application
Azumo builds and operates production AI systems for companies ranging from seed-stage startups to Meta. We are hiring an AI Engineer to own what those systems do once they are live: retrieval pipelines, tool-using agents, evaluation harnesses, and the guardrails that keep them dependable in front of real users. The role is fully remote across Latin America, aligned to your client's working day.
You will not be building demos. Azumo has shipped production AI since 2016, and the work here starts where the prototype ends, making a system reliable, measurable, and affordable enough to put in front of customers.
Where this role sits
Azumo's engineering organization is built around four lanes. The Data Engineer lane owns pipelines, storage, and the retrieval layer. The Data Scientist lane owns the question and the method. The Software Engineer lane owns AI-augmented product delivery. This role is the AI Engineer lane, and it owns production behavior.
One question places the boundary: when the output is wrong, whose problem is it? "The method was inappropriate" is a Data Scientist question. "The system did the wrong thing with an appropriate method" is yours.
Not quite your profile? Check our other openings:
If you build the pipelines and retrieval layer models depend on — Data Engineer
If you decide what to measure and which method answers it — Data Scientist
If you ship product software with agents in your toolchain — AI-Augmented Software Engineer
If you've done all of the above and answered to the client directly — Forward Deployed Engineer
What you will build
How we work
Our engineers build with AI every day. Claude Code, Codex, and similar tools are part of the standard toolchain here, not an experiment. We run an automated audit across the whole codebase on day one and every day after, grading security, cost, and architecture findings by severity with the exact file and line, so a small team can move quickly without quality drifting. We stay vendor-neutral across OpenAI, Anthropic, and open-weight models, and we run Valkyrie, our own production layer, when a single interface to any model is the right call.
About Azumo
Azumo is a San Francisco based software development company that has been building intelligent applications since 2016. We provide nearshore AI engineering teams to organizations that need production AI faster than they can hire for it: as an embedded engineering team, as AI staff augmentation alongside an existing team, or as a full project build. Our engineers work from Latin America, aligned to United States time zones, and have delivered for Twitter, Meta, Discovery Channel, Omnicom, UnitedHealth, and CENTEGIX.
We hire for seniority and test for it before anyone joins a client team. We support engineers in going deep on the modern AI stack, and we give time back to open-source work, community teaching, and philanthropy.
Apply at https://azumo.com/join-our-team or write to us at people@azumo.com.
Requirements
Basic qualifications
Preferred qualifications
Benefits
New AI Engineer postings at the employers we follow are up 340% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under AI Engineer, by the work the posting describes.
AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.
Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.
An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Brazil
Azumo builds and operates production AI systems for companies ranging from seed-stage startups to Meta. We are hiring an AI Engineer to own what those systems do once they are live: retrieval pipelines, tool-using agents, evaluation harnesses, and the guardrails that keep them dependable in front of real users. The role is fully remote across Latin America, aligned to your client's working day. You will not be building demos. Azumo has shipped production AI since 2016, and the work here starts where the prototype ends, making a system reliable, measurable, and affordable enough to put in front of customers.
What you will build - Retrieval systems. Chunking and embedding pipelines, hybrid search, reranking, and evaluation of retrieval quality, built on pgvector, Pinecone, Qdrant, FAISS, or Azure AI Search. - Agentic workflows. Stateful multi-step execution, tool calling, MCP servers, structured output enforcement, context-window management, deterministic fallbacks, and human-in-the-loop gates for the decisions that need one.
More relevant text appears in the full description.
No clear work-authorization passage found. Eligibility is unconfirmed.