Thread Truncated (Cap Enforced)
Only the first 20 tweets are unrolled into slides to ensure reliable PDF exporting and high server performance.
Canvas & Ratio
Choose your destination platform format
Layout Template
Choose a content structure for your slides
Preset Themes
Typography & Sizing
Brand Kit Customization
AGENCYConfigure brand assets for headers & footers
Outro Slide CTA
Customize your closing call-to-action slide
Background Pattern
Build Your Carousel
Drag and drop any post card below onto a slide, or use the quick buttons to insert content/images instantly!
Most people think you need a computer science degree to work in AI.
Save this :)
A small group of people figured out that the highest-paid building role in tech right now doesn't care what your diploma says. It cares what you've shipped.
The difference between those two groups is not credentials.
It is a portfolio.
An AI engineer is the person who builds the systems that connect large language models to real products. The support bot that actually resolves the ticket. The internal search that finds the answer buried in ten thousand documents. The agent that runs a multi-step workflow without a human babysitting it. This is not research. It is not training models from scratch. It is building production software with AI at the core, and it is one of the most in-demand jobs in the entire market.
Here is the part nobody told you. For the majority of these roles, a portfolio of shipped projects carries more weight than a degree. Hiring managers will tell you plainly that they've watched self-taught engineers run circles around PhD holders, because shipping is a different skill than studying. The credential gate is mostly an illusion, and the people who realize it early get years ahead of the people still waiting for permission.
This is the path. No degree required. Here's exactly what it looks like.
## First, Understand What This Job Actually Is
Before you learn anything, get the role clear in your head, because most people aim at the wrong target.
There are two roles people confuse. The <b>machine learning researcher</b> invents new models and trains them. That work genuinely benefits from advanced degrees and heavy math, and it's a small slice of the market. The <b>AI engineer</b> takes models that already exist and builds useful things with them. That work rewards software skill, product sense, and shipping discipline far more than academic credentials. The vast majority of open roles and the ones you can break into without a degree are the second kind.
You're aiming to become the engineer who builds with AI, not the scientist who builds the AI. That distinction will save you from wasting months on math you don't need yet.
The role sits at the intersection of three things: software engineering, a working understanding of how language models behave, and product thinking. You don't need to be elite at all three on day one. You need to be competent and improving, and you need proof.
## Phase 1 (Months 1–3): Learn to Code Properly
This is the step you cannot skip, and the step most people try to skip.
You must be able to write real, working code before anything else makes sense. Python is the language. Almost every AI library, framework, and tool is built for Python first, so this is not a preference, it's the standard.
Spend these months getting genuinely comfortable. Not "I watched a tutorial" comfortable. "I can build a small program from a blank file without looking up basic syntax" comfortable. Variables, data types, control flow, functions, working with files, calling APIs, handling errors, and reading other people's code. Learn how to use Git and put everything on GitHub from day one, because your GitHub is the first half of your portfolio.
If the math worry is nagging at you, set it down. You need comfort with basic statistics and a feel for how numbers behave. You do not need to master linear algebra and calculus to start building with LLMs. The deep math matters for research; you're building. Pick it up later if a specific project demands it.
<b>What to Do This Phase</b>
• Complete a structured Python course and write code every single day, even thirty minutes