[Hiring] AI Engineer @Azumo

Role Description

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
• 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.

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.
• Evaluation: Test sets that reflect the decision the system is actually making, model-as-judge scoring, regression tracking across prompt and model changes, and honest error analysis.
• 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.

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.
• 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.

Qualifications

• 4+ years building and shipping production software, with a modern backend language (e.g., Python) as your primary focus.
• Demonstrable production experience with LLM-based systems: retrieval-augmented generation, function and tool calling, structured output enforcement, and prompt design as an engineering discipline.
• Hands-on work with vector and retrieval infrastructure such as pgvector, Pinecone, Qdrant, FAISS, or Azure AI Search.
• Experience with agent frameworks and tooling: LangGraph, LangChain, CrewAI, the Model Context Protocol (MCP), or native Python execution loops.
• You have built an evaluation suite for an LLM system: Test-set design, model-as-judge or equivalent scoring, and regression tracking.
• Cloud deployment experience, Azure preferred and AWS acceptable, with Docker, CI/CD pipelines, and infrastructure as code.
• Working discipline around latency, token cost, and throughput.
• Active use of AI-assisted coding tools such as Claude Code, Cursor, or GitHub Copilot in real delivery work.
• Clear written and spoken English, B2/C1 or above.
• Bachelor's degree in Computer Science, Data Science, or a related field, or equivalent professional experience.

Requirements

• Fine-tuning and adaptation of open-weight models: LoRA, QLoRA, PEFT, and a clear view of when fine-tuning is the wrong answer.
• Self-hosted or open-weight inference and serving, and the cost and latency trade-offs against hosted APIs.
• Multimodal systems covering vision, speech, or document understanding alongside text.
• Security work specific to LLM systems: prompt-injection testing, red-teaming, and output sanitization.
• Delivery under a compliance regime such as SOC 2 or HIPAA.
• Streaming, real-time, or high-throughput inference workloads.
• Contributions to open-source AI libraries, published technical writing, or active participation in the AI engineering community.

Benefits

• Paid time off (PTO)
• U.S. Holidays
• AI Training and certifications
• Mentored career development
• Profit sharing
• $US remuneration