Real problems
Work on problems Zuddl actually has.
Skip to what the internship is
01
02
03
04
Engineering
Design
Marketing
Revenue
People
Finance
IT
Any team, really
01
02
03
04
01
02
Paid AI Builder Internship · Zuddl
Build AI tools that drive real business impact.
- 3 months, extendable to 6
- Remote, anywhere in India
- 2nd year to recent grad
You build for
Engineering
Design
Marketing
Revenue
People
Finance
IT
… and any other Zuddl team with a real problem
The internship
Not a side project. Not a toy.
Zuddl is an AI-native events platform. This role sits one layer behind it — you build the AI-powered internal tools and automation that Zuddl's own teams run on every day.
Your own project
You own a project from week one — not after weeks of onboarding.
Real users
Build tools that Zuddlers actually use.
Direct impact
Your work improves how the business operates.
What you'll build
Find a real problem. Build the thing that fixes it.
Internal tools and automation for whichever Zuddl team has the problem. Manual work removed, workflows that stop getting in the way, tools the people around you open every day — and notice when they're gone.
Tooling for the people who build and ship the product.
Automation around the work that turns ideas into interfaces.
Tools for the team that takes Zuddl to market.
Automation for the people who sell and support Zuddl.
Tools for the team that hires and looks after Zuddlers.
Automation for the work that keeps the numbers straight.
Tooling for the people who keep everyone running.
These aren't the boundaries. Find a problem anywhere at Zuddl and make the case for it.
What you get
The terms, in plain language.
Your own project
From week one.
Named mentor
Someone you can learn from.
Remote
Anywhere in India.
3 months
Extendable to 6 by mutual agreement.
Hours
Flexible.
Stipend
₹50,000 per month. Confirmed in the offer.
What we're looking for
A short list, and an honest one.
You'll have a coding agent for the rest. What we can't give you is the judgement to know whether what it produced is right.
Databases
Model data, query it, and explain your choices.
APIs
Consume one and build one.
Debugging
Figure out why something broke — instead of re-prompting until the error goes away.
AI judgement
Use AI aggressively, but know when it is wrong.
AI-native by default
Using Claude Code, Cursor, Codex or similar is expected, not a confession.
We care less about which one you picked than whether you understand it, can say why you picked it, and can point at where it gets things wrong.
Claude Code
Cursor
Codex
or similar
A CS background, ideally
Not required. Understanding a working stack counts for more than where you learned it.
Recent work
The tooling moved a long way in the last few months. Show us work done on the current version of it.
Things you run yourself
Agents, workflows or assistants you've wired up beyond a chat window. Hands-on only; we'll ask about whatever you mention.
And four things we read for
- A real problem, and the people who had it.
- Judgement about where AI belongs.
- Taste in how you built it.
- Fundamentals under the hood — a data model that fits, code someone else could read, a README that runs, no secrets in the repo.
×
No aptitude tests
×
No puzzle rounds
×
No formal degree required
×
No events experience needed Any stack, any domain.
The builder philosophy
Small is fine.
Ugly is fine.
One user is fine.
Just make something useful.
Someone should be thankful it exists — and the someone can be you. That's the whole test.
We want to see
- ✓ Scripts that automate real work. Something that was done by hand, and now isn't.
- ✓ A tool that solves a real problem. A friend, a teacher, a shop, or you. A command-line tool counts.
- ✓ Something actually used by someone — or that would be, if they knew it existed.
Don't send
- × YouTube tutorial projects. They tell us nothing about you.
- × Non-functional clones. If it doesn't work, it isn't a product.
- × To-do lists , or anything of that kind.
Before you apply
This isn't for you if…
Two things we'd rather say here than in a rejection email.
- − You want to work on the product customers see.
- − You'd rather stay quiet until you're sure you're right.
About the second one. Say your ideas out loud, even the half-formed ones. Staying quiet until you're sure doesn't work here.
How we hire
Two steps. That's the whole process.
Show us something you've built
Plus a short form about the project and how you work.
- Resume — PDF. One page is plenty.
- Public GitHub repo — built recently, using AI. The README should say how to run it.
- 3–6 minute demo video — you showing it working and how it's built. A screen recording with your voice is fine. Not a slide deck.
Allow about half an hour, plus the video.
Build with us
If you're shortlisted, you work alongside the person who has the problem.
- A few days
- A real Zuddl problem — unsolved, and one we actually have.
- A demo and a conversation about how you built it.
Details come with the invitation.
No aptitude test. No puzzle round.
FAQ
Things people ask.
What counts as "built with AI"?
Either or both: the product uses a model at runtime, or you used AI tools to build it. Tell us which. Using Cursor, Claude Code, Copilot or similar is expected, not a mark against you.
Can I submit a team or college project?
Yes, if you tell us clearly which parts were yours. We'll ask about those parts.
What about the internship itself?
Three months, paid, remote within India, extendable to six by mutual agreement. Hours are flexible. You get a named mentor and a project of your own from week one. The stipend is confirmed in the offer.
Apply
Show us what you built.
Five short pages: basic information, education, the project, what it does and how you built it, and when you can start. Allow about half an hour, plus the video.