Building an AI Portfolio Without an ML Degree
162 applications per offer, 2026 average.
Advertisement
A degree gets your resume past one filter. A strong portfolio gets you past every other filter. If you do not have an ML degree, your portfolio is your everything.
Here is how to build one that gets you interviews at real AI companies in 2026.
What a Strong AI Portfolio Looks Like#
Three things matter:
- Projects that solve real problems
- Code that is well-organized and documented
- Writing that shows you understand what you built
The portfolios that get hired share these traits. Tutorial clones and demo apps do not.
The 5 Projects That Get You Hired#
You do not need 20 projects. You need 5 strong ones. Here is the optimal mix.
Project 1: A real RAG system
Why: 80% of AI engineering jobs involve RAG. Show you can build one.
Build:
- A "talk to my [thing]" chatbot over a real dataset
- Use OpenAI embeddings + pgvector or Pinecone
- Add chunking, retrieval, and reranking
- Deploy as a real app
Bonus points:
- Hybrid search (semantic + keyword)
- Query rewriting
- Multi-step reasoning
- Source citation
Real-world examples:
- "Talk to my Obsidian notes"
- "Talk to my company wiki"
- "Talk to a specific book or paper set"
- "Talk to a podcast archive"
Project 2: An evaluation framework
Why: This is the bottleneck for production AI. If you can do it, you stand out.
Build:
- An eval set for your RAG system from project 1
- A judge model (Claude or GPT-4) that scores outputs
- A dashboard showing pass rate over time
- Ablation studies (what happens when you change X?)
Show:
- 50 to 200 labeled test cases
- Multiple scoring dimensions (accuracy, helpfulness, safety)
- Pass rate going up as you improve the system
- A blog post explaining what worked
This single project will land more interviews than the next 3 combined.
Advertisement
Project 3: An agent or tool-using LLM
Why: Agents are the next wave. Show you can build one.
Build:
- An LLM that uses tools to accomplish a task
- Examples: a research agent, a code reviewer, an email triager
- Use OpenAI function calling or Anthropic tool use
- Handle errors and edge cases
Bonus points:
- Multi-step planning
- Streaming output
- Memory across conversations
- Production deployment
Real-world examples:
- An agent that searches the web and synthesizes answers
- An agent that takes a PR description and reviews the code
- An agent that takes a meeting transcript and writes action items
Project 4: A fine-tuned model
Why: Shows you understand the spectrum from RAG to fine-tuning.
Build:
- Take an open source model (Llama 3 8B, Qwen, Mistral)
- Fine-tune on a specific task
- Compare to GPT-4 baseline
- Deploy and benchmark
Use:
- Hugging Face transformers
- LoRA for efficient fine-tuning (do not full fine-tune unless you have GPUs)
- A clear comparison methodology
You can do this on a single A100 from Lambda Labs or similar for $30 to $100. Or use a service like Together AI or Modal for managed fine-tuning.
Project 5: Open source contribution
Why: Shows you can work on real production code.
Pick one:
- Contribute to LangChain, LlamaIndex, or another major AI library
- Build and publish your own open source tool (smaller scope)
- Add a feature to an existing project
The contribution does not need to be massive. Even a meaningful bug fix or documentation improvement counts.
What Makes a Project "Strong"#
Five criteria:
1. Real problem
Not "ChatGPT clone." Something useful. Even if useful only to you.
2. Real users
Even 5 to 10 users beats zero. Friends, family, coworkers count.
3. Real iteration
Show evidence you improved the project after launch. Version 1 vs version 3. Changelog matters.
4. Real metrics
How well does it work? You should know. "Achieves 87% retrieval accuracy on test set of 200 queries" beats "It works well."
5. Real documentation
A 1-paragraph README is not enough. Each project needs:
- What it does
- Why it exists
- How to run it
- Architecture overview
- Key technical decisions and why
- Known limitations
Tools You Need#
To build the 5 projects:
Free or cheap
- GitHub for code (free)
- Vercel or Render for deployment (free tier)
- OpenAI API ($5 to $50 credit, then pay as you go)
- Anthropic API (similar)
- pgvector (free, self-hosted)
- Hugging Face (free tier for hosting models)
- Streamlit or Next.js for UI
Slightly more expensive
- Pinecone ($0 to $70/month depending on usage)
- Modal Labs for GPU compute (pay as you go)
- Lambda Labs for GPU rental ($30 to $100 for a fine-tuning run)
- LangSmith for observability ($0 to $50/month)
Total cost for all 5 projects: $200 to $500.
Where to Host the Portfolio#
Your portfolio needs three layers:
1. GitHub
Each project gets its own repo with:
- Clear README
- Architecture diagram (drawn in Excalidraw or similar)
- Demo video or screenshots
- Live demo link if applicable
2. Personal website
Build a simple site at yourname.dev or similar. Sections:
- About (1 paragraph)
- Projects (list of 5 with links)
- Writing (blog posts)
- Contact
Keep it simple. Do not over-design. A Next.js + Vercel site is fine. So is a Notion page.
3. Blog posts
For each project, write a blog post:
- What you built
- Why
- Key technical decisions
- What worked, what did not
- What you learned
These blog posts get you interviews. They show your thinking, not just your code.
Advertisement
Timeline#
Realistic: 4 to 6 months part-time to build all 5 projects.
Aggressive full-time: 2 months.
Suggested schedule (part-time, 10 hours per week):
- Weeks 1 to 6: Project 1 (RAG)
- Weeks 7 to 10: Project 2 (Eval framework)
- Weeks 11 to 16: Project 3 (Agent)
- Weeks 17 to 22: Project 4 (Fine-tuning)
- Weeks 23 to 24: Project 5 (Open source contribution)
Total: 24 weeks. 6 months.
Bonus: write blog posts as you go, not at the end. You will forget details otherwise.
What Recruiters Actually Look For#
When AI recruiters review portfolios in 2026:
- First 10 seconds: do you have ANY shipped projects?
- Next 30 seconds: are they real or tutorial clones?
- Next 60 seconds: do you understand what you built?
- Final check: is the code quality reasonable?
Most candidates fail at step 1. Half of those who pass fail at step 2. By step 3, you are in the top 10%.
If your portfolio passes all 4 steps, you get interviews.
Common Portfolio Mistakes#
Mistake 1: Too many shallow projects
20 toy projects worse than 5 strong ones. Cut ruthlessly.
Mistake 2: ChatGPT clones
Everyone has built one. Yours does not stand out. Skip this project.
Mistake 3: No deployment
A project that only runs on your laptop is worth less. Deploy.
Mistake 4: No evaluation
You built a chatbot. Does it work? You should know. Add evals.
Mistake 5: Bad READMEs
Recruiters spend 30 seconds on your README. Make it count.
Mistake 6: Hiding the code
If your code is in a private repo, you are invisible. Open source.
Mistake 7: No writing
Code without context is hard to evaluate. Write about your projects.
How to Get Your First Users#
You need users to validate projects. Easier than you think.
- Post on Twitter / X explaining your project
- Post on Hacker News (Show HN format)
- Post in relevant subreddits (/r/MachineLearning, /r/LangChain)
- Share in AI Discord communities
- Tell friends in tech
- Show coworkers
- Submit to Product Hunt
Even 20 users is enough to claim "real users" on your resume.
Sample Resume Entries#
How portfolio projects translate to resume bullets:
Bad: "Built a chatbot using OpenAI"
Good: "Built RAG system over 12k engineering docs at [domain] with hybrid retrieval and reranking. Achieved 87% precision@5 on 200-question eval set. Deployed at example.com serving 150 weekly users."
Bad: "Worked on AI agent project"
Good: "Designed and shipped research agent using Claude tool use that searches web sources and synthesizes answers. Open source at github.com/yourname/agent, 340 stars. Handles 3.2 average queries per session in production."
Run your portfolio-emphasized resume through the free ATS checker against AI engineer JDs.
Companies That Hire Self-Taught AI Engineers#
In 2026, these companies have demonstrably hired engineers without formal ML degrees:
- OpenAI (yes, even here)
- Anthropic (some)
- Cohere
- Stability AI
- Replicate
- Most YC AI startups
- Vercel, Supabase, Resend (AI features)
- Most Series A to Series C AI startups
- Many large companies adding AI teams
Do not rule yourself out. Apply.
What to Do This Week#
- Pick project 1 (the RAG system) and a specific dataset
- Set up OpenAI API access
- Build a minimum viable version this week
- Commit to GitHub
- Write a short README
Then next week, start polishing project 1 while planning project 2.
By month 6, you have a portfolio that beats most ML degree holders' portfolios.
The Portfolio Gets You In. You Get You Hired.#
A portfolio is a door opener. Once you have interviews, you need to perform.
Use the free mock interview tool to practice AI engineer interviews. The questions are predictable. Practice answers about your projects until they sound natural.
Use the free cover letter generator to tailor applications to each company, highlighting which of your projects matches their needs.
The path from "no ML degree" to "AI engineer at a great company" is real. Hundreds of people did it in 2024 and 2025. You can too.
Start with project 1 this week. The rest follows.
Advertisement
Advertisement
Send this to whoever has the interview this week.
Keep reading
Australia 482 Visa Jobs for Software Engineers: How It Works
A practical guide to the Australia 482 visa for software engineers, covering sponsorship, occupation lists, and the application timeline.
Backend Developer Jobs in Finland with Visa Sponsorship
Your guide to landing backend developer jobs in Finland with visa sponsorship, covering the market, salaries, and a clear application checklist.
Business Analyst Jobs in Australia with Visa Sponsorship
Find out how to land business analyst jobs in Australia with visa sponsorship, including salary ranges and application tips for 2026.
Advertisement
Advertisement