Python Automation Engineer – AI Integrations

Automation Engineer — AI Agent Systems
Remote, Latin America | 3–4+ years of actually shipping things

Reports to:

Senior Operational Leader

We build multi-agent AI systems that do real Sales and Recruiting work, not demo-day theater. If it cannot survive a Tuesday with real users, it does not count.

You will build and run agent systems : routing, workers, tools, memory, retries, and the part where we find out it broke  work with a Lead Architect and with Sales and Recruiting humans who will tell you if it is useful. You will not disappear into a cave and emerge with a framework rewrite.

You will also sit with the developers building our CRM, ATS, and ERP. You represent this team in those rooms so those systems can talk to our agents, and our agents can talk back. You are the integration. You are not the CRM owner.

Ask questions. Show the work. If something is on fire, say so the same day. We have already lived the other version.

• Build Python agents that behave as a system, not as 14 clever prompts in a trench coat
• Wire them to real platforms: APIs, webhooks, data in, data out, no duplicate rows because the webhook got excited
• Work with the teams building our CRM, ATS, and ERP. Show up in their design conversations. Do not leave until the APIs and events actually work for automation
• Debug production like an adult. Trace the bad run to the tool call, the payload, or the prompt
• Log decisions, tool calls, and cost. Alert us before finance does
• Sit with users, watch them use it, then change it

(we will test these, not just admire them on a resume)

• 3–4+ years of backend, automation, or AI that ran in production. Walk us through something you shipped. "I contributed" is not a walkthrough.
• Production LLM APIs (OpenAI, Anthropic, Groq, or similar). Tool calls, rate limits, token burn, and what a failure looks like when it is not a blog post
• Python someone else can maintain. Tests and CI you actually run
• REST and webhooks: idempotency, retries, timeouts. Pop quiz: it fires twice. What happens.
• SQL past SELECT * . Joins, indexes. Postgres is a plus
• You can read logs and find the root cause. You assume failure is the default and you designed for it

• Clear English, written and spoken, with a US team. Your application is the first test. Use it.
• You surface problems the same day, not in the postmortem
• You will start without a 40-page spec
• You care if Sales or Recruiting actually used the thing, not just that it compiled
• You can sit with another engineering team, explain what we need in plain English, and not leave until the API and events actually work for automation. Salesforce / Hub Spot / Greenhouse / ERP experience is a plus, not a must. Surviving someone else’s system is the must.

(we can teach this)
Lang Chain, Lang Graph, Llama Index, or whichever library is fashionable this quarter. Vector DBs. AWS/GCP, Docker. Datadog. Prompt evals. If you have them, great. If you don’t, and you have shipped systems, we will live.

• Build on your Python and integration skills while learning AI systems alongside our senior team.
• Build solutions used directly by Sales and Recruiting teams.
• Work with real APIs, databases, automation, and AI integrations.
• Work remotely with a US-based team with clear collaboration hours and competitive compensation.

Remote, Latin America. Overlap live US hours or this does not work.
Pay is competitive and tied to what you have shipped, not how many libraries you can name. Equipment provided. Health insurance included.

Shipped systems. Clear communication. Curiosity. That is the whole interview.