AI automation internship, open worldwide
Agents are only as good as the plumbing underneath them. You will build the sites, dashboards and automations that carry real customer work, every day. Open worldwide, and you can apply from anywhere.
- Location
- Fully remote
- Open to
- Worldwide
- Length
- 3 months minimum
- After that
- Job offer for the right person
Last updated 2026-09-03. This role is open until 2027-08-09.
Who we are looking for
This is for you if
We are not filtering on qualifications, and there is no minimum grade or age. What we are looking for is someone who has already made something, can talk about it honestly including the parts that went wrong, and would rather find out they were mistaken than be left thinking they were right. Every internship here works on live systems from the first fortnight, so the trait that matters most is being comfortable with real consequences and quick, direct feedback about them.
- You have built and shipped something on the web, even if it was small. A live URL beats a tutorial certificate every time.
- You would rather fix the root cause than patch the symptom, and you get uncomfortable when you cannot explain why something works.
- You want to see your work used. Everything here goes to a live site or a live account within days, not into a folder.
The work itself
What you will actually do
This is the real job, not a summary of it. Each of these lands in your first weeks rather than being held back until you have proved yourself on something artificial. You will be paired with someone senior, every job arrives with a written brief and a clear definition of done, and everything is reviewed by a human before it reaches a client. That is how we can put an intern on live work safely: the rails are strict, so the work does not have to be small.
- Build and improve real pages on live client websites, then check them yourself at phone, tablet and desktop widths before anyone else does
- Wire systems together so data moves without a human copying it, a form to a CRM, a CRM to a dashboard, a dashboard to a report
- Write the automated checks that stop a broken build reaching a customer
- Chase down bugs in live systems using the evidence, the logs, the payload, the actual record, rather than guessing
- Deploy your own work and prove it landed, because committed is not the same as live
What you take away
What you will learn
These are the things that transfer. Tools change and frameworks come and go, but the habits below hold on any stack, at any company, for the rest of your career. They are also the things almost nobody is taught explicitly, which is why we teach them deliberately rather than hoping you absorb them.
- How to debug systematically instead of trying three random fixes, which is a skill most developers never get taught properly
- How modern sites are built for both people and AI search engines, including the schema and structure that decide whether anyone ever finds the page
- How to work safely on live systems, with branches, reviews and rollbacks, so that moving fast and breaking a client's business are not the same thing
Tools you will use
- Astro, React and Tailwind
- Node and TypeScript
- Git, GitHub and Netlify
- Claude Code
- Playwright for browser testing
The detail
What the job is really like
The unglamorous half of AI, and why it decides everything
Everyone wants to build the agent. Far fewer people want to build the thing the agent stands on, and that is exactly why this role matters. An AI sales agent that cannot read the calendar cannot book a call. A dashboard that shows a client a number nobody can trace is worse than showing nothing at all.
The systems work is where AI stops being a demo and starts being a product. You will spend your time on the parts that have to be right: the page that loads on a phone, the form that reaches the CRM, the deploy that actually went live rather than merely committed, the number on screen that traces back to a real record. None of it is glamorous. All of it is the difference between a client who renews and a client who quietly stops replying to emails.
What you will actually be building
Our clients get a website, a CRM, a set of agents, and one dashboard to run it all from. That is a lot of surface, and interns work across it rather than being parked on one corner of it for three months.
In a typical month you might build new pages on a live client site, add a section to a dashboard, wire a new data source into a report, write the checks that guard a build, or track down why a form stopped reaching the CRM. The work is varied because a small company cannot afford narrow specialists, and that variety is the fastest education available anywhere. You will touch front end, back end, data and deployment in the same week, which is unusual and is the reason people leave here able to build a whole thing rather than one layer of it.
Debugging is the skill we care most about
Most developers, when something breaks, try three things they half remember and hope one works. We do the opposite, and we will teach you how, because it is the single most transferable skill in this job.
You will learn to read the actual payload before theorising, to reproduce a fault with real inputs rather than a simplified version that quietly removes the cause, and to stop after two failed attempts and reconsider instead of pushing a broken approach for another hour. You will learn that ruling something out is a hypothesis, not proof, and that the only way to know a cause is to read every line in the path. This one habit will make you better than plenty of people with five years of experience, and it works on any stack you ever touch afterwards.
Working on live systems without breaking them
Interns here touch production, which surprises people. It works because the rules around it are strict, simple, and never bent for convenience or deadlines.
Everything happens on a branch. Nothing reaches a client without a human reviewing it. Every deploy is checked by loading the real page, not by trusting that the build passed, because a build passing only proves the code compiled. If a change is hard to reverse, it waits for an explicit yes from someone who can give one. You will learn to work quickly inside those rails, which is a far more useful skill than being fast in a sandbox where nothing matters. Employers do not need people who can move fast, they need people who can move fast without costing them a client.
Who this suits, honestly
This suits someone who is genuinely curious about how things work and slightly allergic to hand waving. If you enjoy the moment where a confusing bug suddenly makes sense, and you would rather understand the cause than apply a fix you found online, you will enjoy this a great deal.
It does not suit someone who wants a narrow, well defined ticket queue with every decision already made. The briefs are clear about the objective and the boundary, but you will often have to work out the middle yourself, with help available the moment you ask for it. Asking early is encouraged and never held against you. What is held against you is spending a day stuck in silence, because that costs the team far more than the question would have.
What you leave with
Three months in, people who have done well have shipped live work they can point at, learned to verify their own claims with evidence, and built at least one system end to end from empty folder to live URL. That is a portfolio that proves something, rather than a list of technologies.
The habits are worth more than the code. Reading before guessing, reproducing before theorising, checking the real page before saying it works, stopping and re-planning after two failures. Those transfer to every job you will ever have and to stacks that do not exist yet. We have been building with AI since 2019 and deployed 500+ AI agents, and the clients you build for are real businesses with real customers, from martial arts schools to regulatory consultancies.
What we actually read
We are looking for a specific shape of answer: what you expected, what actually happened, what you checked, and the moment you realised your assumption was wrong. Vague answers about “trying a few things until it worked” tell us the fix was luck. Shortlisted applicants get a short practical task, which is a problem we have already solved so we can compare your approach to ours. It is not unpaid work for us and it will not take your whole weekend.
Applying
Six fields, then it is with us
No CV template, no covering letter, no application theatre. A person reads every one.
Questions people ask about the AI Automation Developer Intern role
What level of coding do I need before applying?
You should be able to build a small web page or script on your own and read an error message without panicking. We will teach you the rest inside the three months. Send us something you have actually built and finished.
Which languages and frameworks do you use?
Mostly JavaScript and TypeScript, with Astro, React and Tailwind on the front end and Node behind it. If you know a different stack well, that transfers faster than you think, because the thinking matters more than the syntax.
Is the internship remote?
Yes, fully remote, and we accept applications from anywhere. The job listing names the countries we can currently contract through, so if you are outside them say so in your email and we will tell you honestly whether we can make it work.
How long does it run and what happens at the end?
Minimum three months, and if you are good there is a job offer at the end. We run this programme to find people we want to keep, not for cheap short-term help, and we say so plainly for that reason.
Will I get real work or side projects?
Real work, from the first fortnight, on live sites and live accounts. Every change is reviewed before it reaches a client, so you learn on the real thing without carrying the risk of breaking someone's business.
Do you help me learn or am I on my own?
You are paired with someone senior and every job comes with a written brief and a definition of done. Feedback is direct and fast, and it is about the work rather than about you. Asking early is encouraged, never penalised.
Think you would be good at this?
We would rather see one real thing you made than a perfect CV. Send it over with a paragraph about what broke and how you worked it out.