Make.com Automation Engineer

About this role

You’ll design and ship integration scenarios on Make.com for client engagements. Most of them are mid-market companies with somewhere between 5 and 30 SaaS tools that need to talk to each other in ways that off-the-shelf integrations don’t handle.

This is not a “build automations from a backlog” job. The work is consultative: you’ll spend time understanding what should actually happen at each handoff, then design the scenario that does it reliably. You’ll own the scenarios you build, meaning you’ll be on the hook for them not breaking silently in production.

What you’ll do

• Build production-grade Make.com scenarios across a range of integrations: APIs, webhooks, CRMs, ERPs, messaging platforms, data warehouses
• Diagnose integration problems in client environments, often in systems someone else built
• Write the documentation that lets clients run their own scenarios after you hand them off. This is non-negotiable; we don’t ship undocumented work
• Build error-handling and observability into every scenario you ship. We run automations as production systems, not landmines
• Occasionally lead the technical conversation in a discovery meeting with a client

Who this is for

You’ve built real Make.com scenarios in production, not just for personal projects. You can read API documentation without a hand-hold. You’ve debugged something at 11pm because production was down and the on-call person didn’t know what to do.

You probably have experience with at least one of: Zapier, n8n, Workato, Tray, or another iPaaS-style platform. Make.com specifically is a strong plus.

You write clearly. You explain technical decisions to non-technical people without being condescending. You don’t hide problems from clients. You tell them what’s wrong and what you’re going to do about it.

What you won’t do

• Sit through 10am stand-ups about velocity
• Build automations from a JIRA ticket without knowing why they exist
• Pretend something is working when it isn’t

Compensation

Competitive. We discuss the range early in the process, not after three rounds.