AI Integration Engineer

Who we are

Eightx is a growth-economics consultancy that serves ecommerce, DTC and CPG brands doing $2M–$150M in revenue. We act as fractional CFOs and growth advisors who sit inside our clients' businesses, running financial models, managing ad performance, and tracking every deliverable.

We're now building an internal AI agent system that automates the work our team does every day: reading call transcripts, updating financial models, monitoring ad performance, tracking client deliverables. Three agents are already live in production on a self-hosted VPS, wired to Slack, Fireflies and Meta. You'll be the engineer who builds everything next.

The role

You'll work directly with our founder, Matt Putra, to build, ship and maintain the AI agent infrastructure. This is not a research or architecture role. It's a build role. We move extremely fast. You'll take a spec, pick it up in Claude Code, and have something working the same day.

You'll own

• Building MCP servers (Node.js) that connect our AI agents to external APIs: Fireflies, Gmail, GoHighLevel CRM, Google Sheets, Meta Ads
• Writing skills and .md files that let our team put LLMs to work in their daily workflow
• Google Sheets automation: scripting financial model updates and building data pipelines from call transcripts to spreadsheets
• Infrastructure: Docker, SSH, container health monitoring, environment variables, network isolation
• Debugging fast: reading logs, finding the failure point, shipping the fix

Your first two weeks

This isn't a vague "ramp-up." A realistic first deliverable: ship an MCP server that wires one of our data sources (say, Fireflies call transcripts or a Google Sheet financial model) into an agent that posts to Slack, where "shipped" means it runs on the VPS and the team uses it. From there you'll build out four secure agents (we'll show you how, and you'll deliver), replicate a couple client-side, and start enabling the team. The specs exist. The VPS is running. You're shipping into production from day one.

What you must have

Non-negotiable

• You use Claude Code (or Cursor) as your primary development environment, not as a novelty but as your main way of working
• You ship today, not next week. If the spec is clear, you build it the same day. That's the bar.
• Node.js: comfortable with async/await, HTTP servers, API integrations, the npm ecosystem
• Docker: build images, run containers, read logs, manage env vars, debug networking
• REST and GraphQL integration: reading API docs and implementing against them is bread-and-butter work for you
• You understand how LLMs think, how they ingest information, and how to structure prompts for maximum effectiveness

Strong preference

• Experience with MCP server development or any similar tool-server pattern
• Google Sheets API or Apps Script
• Slack bot development or webhook integrations
• Prior automation work: n8n, Make, Zapier, or custom API glue you outgrew and replaced with code
• Comfortable with Linux and SSH. This is not a managed cloud environment

What you'll get in return

• Pay, in writing, before any unpaid step. We benchmark your rate to your market and put the number in writing up front, then raise it as your ownership grows.
• AI training that actually compounds. We use Claude Code heavily and we'll share our patterns, prompts and learnings. You'll get better at the most valuable skill in software, fast.
• Room to grow. We're small and scaling our AI practice quickly, and early builders grow into bigger ownership as the team expands.
• Real autonomy. Async-first, most communication via Slack, no daily standups. Clear written specs, then you build.
• Range. Your work touches finance, ops, marketing and client delivery across a portfolio of brands, not one narrow codebase.
• Ongoing engagement. Full-time contractor, not a one-time project. LatAm or India preferred for US-hours overlap.

How to apply

We don't want a cover letter. We want to see you work. When you apply, send us:

• A link to something you've built: an API integration, a bot, an automation, a tool server. Doesn't have to be polished. Has to be real.
• One paragraph on how you use Claude Code or Cursor in your daily workflow. Be specific, not "I use AI to help me code" but how and for what.
• Your hourly rate and timezone.

If your profile looks right, we'll send you a paid test task: build a working MCP server against a real API from our stack. You'll have 30 minutes. That's not a typo. We pay you for your time regardless of outcome.

As part of early screening, we'll also ask for a short 2–3 minute video (phone or webcam is fine) on why you're interested and your key strengths for the role.