How do I break into AI work without a CS degree?
You don't need one. Much of AI automation work is connecting tools a business already uses so repeat tasks run on their own, with an AI model handling steps like sorting, summarizing, or drafting. The harder part is knowing which work is worth automating, and people from ops, sales, support, project management, and marketing already know that. Learn one tool like n8n or Make, build one small automation that fixes a real problem, show it, and apply to roles that value business sense.
What the work looks like
Take a team that copies every new lead from a web form into a spreadsheet, then into their CRM, then writes each follow-up email by hand. An automation can do the copying. An AI step can read each lead, tag it, and draft the follow-up for someone to check before it goes out.
The job is finding a process like that, mapping how it really works today, building the automation, and keeping it running as the business changes. Some roles are mostly building. Others sit on the people side, like helping customers get results from what was built, running the operations around it, or selling it.
Titles on the board right now include automation builder, AI ops, member success, voice AI, and forward deployed engineer. They're different jobs around the same kind of work.
Skills that transfer
Ops. You know where work gets stuck. Every automation project starts with that question.
Sales. You know how a lead moves from first contact to a closed deal and where it drops off. Lots of automations are built around that path.
Project management. Scoping, timelines, and keeping people aligned on what's being built. Automation projects need all three.
Support. You've seen every way a customer gets confused, which helps you build things people can use. It also lines up with member success and customer success roles.
Marketing. Lists, campaigns, follow-up sequences, and reporting are common things businesses want automated.
The tools are new to you. The business side is what you've been doing for years.
Getting your first role or gig
1. Pick one tool. n8n, Make, and Zapier are all good places to start. If you want to work with agencies, look at GoHighLevel too. Go deep on one before trying others.
2. Build something small that's real. Use a problem from your own job or from someone you know. Sending new form leads to a sheet and a Slack channel is a fine first build. So is drafting answers to common support emails for a person to approve.
3. Show it. Record a short screen video of it running and explain what problem it solves. Write a few lines on what you built and what you'd do differently. That's the start of a portfolio.
4. Apply to roles on the board. Read each post closely. Many name the exact tools the team uses, which tells you what to learn and build next. Put your build at the top of your application.
5. Build the next one. Each one gives you something new to show and fills a gap the last one didn't.
What not to waste time on
Stacking courses. Take one to learn the basics of your tool, then switch to building.
Learning to code before anything else. Some roles need it and you can add it later if you head that way. It shouldn't hold up your first build.
Trying every new AI tool. New ones show up all the time. Get good with one setup and add tools when a real problem needs them.
Waiting to feel ready. Apply once you have one real build you can walk someone through.