AI Automation Engineer

AI automation engineer roadmap

Before week 1 — an honest fit check

This roadmap assumes you can already use a computer fluently and are comfortable reading documentation that was not written for beginners. The sixteen-week figure assumes roughly ten focused hours a week; double the calendar if you have five. What it does not assume is a CS degree — the hiring signal in this field is a working system with error handling, not a credential. If you finish stage 2 and find you dislike debugging other people's APIs, stop there: that activity is most of the job.

Stage 1 — foundations (weeks 1–4)

  1. Learn HTTP basics: GET/POST, headers, JSON, status codes.
  2. Build a 3-step workflow: form → spreadsheet → email notification.
  3. Write a short Python or TypeScript script that calls a public API.

Stage 2 — integrations (weeks 5–10)

  1. Connect a CRM or support tool via OAuth or API key.
  2. Add branching, filters, and scheduled triggers.
  3. Implement retries and dead-letter handling for failed runs.

Stage 3 — LLM workflows (weeks 11–16)

  1. Call an LLM API with structured output (JSON schema or tool use).
  2. Build a human-in-the-loop review step for high-stakes outputs.
  3. Track token cost and latency per workflow run.

Stage 4 — production (ongoing)

Portfolio projects that interview well

Inbound lead enricher (clear business metric), support ticket classifier with escalation rules, or document intake pipeline with extraction plus human QA. Each should show diagrams, sample logs, and what you would improve next.

What to build as your portfolio piece

One system, boringly reliable, beats five demos. The strongest cheap signal is an automation that has run unattended for weeks and failed gracefully at least once: a lead-intake flow that survived a CRM outage and queued its retries, with a README that names the failure and the fix. Hiring managers in this niche read post-mortems the way designers read portfolios — the incident narrative is the credential. Keep run logs; they are your proof the thing actually ran.

Roadmap FAQ

How long does the roadmap take?

Most people need 3–6 months of focused part-time work to reach hireable mid-level projects. Faster if you already script and have touched APIs; slower if you are starting from zero programming experience.

Should I learn n8n or Make first?

Either works. n8n suits self-hosting and developer-heavy teams; Make has a gentler UI for business users. Pick one, finish two portfolio projects, then sample the other.

When do I add LLMs?

After you can build reliable non-LLM automations. LLMs add nondeterminism— you need logging, fallbacks, and human review patterns before production use.