How to Find and Apply for Unpaid or Stipended Startup Internships
TL;DR - Startup internships (paid, stipended, or unpaid) rarely appear on major job boards. You have to find them through direct outreach and niche platforms. - Before accepting any unpaid internship, evaluate it against three questions: Will you work on real product features? Is there a senior engineer to learn from? Will you leave with something to show? - Direct outreach to founders via LinkedIn or email is often more effective than applying through job listings. - Structure your ask clearly. Founders are busy. A specific, credible pitch gets responses. - If you get the internship, treat it like a job. That's how it becomes a portfolio piece and a reference.
Why Startup Internships Are Different
Large companies run structured internship programs with defined timelines, assigned mentors, and formal evaluation processes. Those programs are visible, competitive, and designed to recruit from specific schools or pipelines.
Startup internships are none of those things. They're informal, often created on the fly, and rarely advertised. A founder at a 12-person company who needs engineering help isn't posting on LinkedIn. They're thinking about whether they can afford to bring someone on, whether they have time to manage an intern, and whether the help is worth the overhead.
Your job is to make the answer to all three questions obviously yes.
The upside of startup internships is real. You're more likely to touch production code, make actual product decisions, and work directly with engineers who have things to teach you. The downside is that some startup internships are disorganized, poorly scoped, and won't produce the experience you need. Evaluating them before you commit is important.
Where to Find Startup Internships
Wellfound (Formerly AngelList Talent)
Wellfound is the first place to look. It's the closest thing to a dedicated job board for startup roles, and many early-stage companies post internship or contractor openings there that don't appear anywhere else.
Search specifically for "internship" filtered to engineering. Filter by stage (seed, Series A) rather than by company size. Startups at seed or Series A are large enough to have a real product but small enough that an intern can contribute meaningfully.
Y Combinator's Job Board
YC posts jobs for its portfolio companies at jobs.ashbyhq.com/ycombinator. These companies tend to be well-funded, well-run, and active. The internship listings here are more likely to be paid or stipended. Competition is higher, but the quality of experience tends to be higher too.
LinkedIn Filtered Searches
LinkedIn's job search has gotten noisier, but you can still filter to startup-stage companies. Look for "internship" combined with "software" or your specific stack, then filter to companies with fewer than 50 employees. The ratio of signal to noise is worse than Wellfound, but some opportunities only get posted here.
Direct Outreach to Founders
This is the highest-effort approach and often the most effective one.
Find startups in industries you're interested in. Crunchbase and the YC company directory are good starting points. Look for companies that have recently raised seed funding. They have money and are in building mode. Find the founder or CTO on LinkedIn. Send a direct, specific message.
The message should be short. Something like:
"Hi [name], I'm a software engineer currently looking for my first role. I specialize in [stack]. I've been following [company] and would love to contribute to the product. I'm available for a part-time or full-time internship, paid or stipended. Would you be open to a 20-minute call to see if there's a fit?"
That's it. Not a cover letter. Not a full background. A specific, low-commitment ask.
Most founders won't respond. That's expected. Send 20 messages. You might get 3 responses and 1 that turns into a conversation.
Warm Introductions
If you know anyone who works at a startup or has connections to startup founders, this is worth pursuing. A warm introduction converts at a much higher rate than cold outreach.
"My friend works at X and thinks you'd be a good fit for what they're doing" gets a very different response than a cold LinkedIn message.
Tell everyone in your network that you're looking for a startup internship. Be specific about what you can do and what you're looking for. People are more likely to make a connection when they can picture the fit.
Startup Communities
Slack groups, Discord servers, and online communities focused on startups sometimes have job boards or channels where founders post informal opportunities. Communities around specific ecosystems (Rails, Python data tools, fintech) often have employers who post roles there before they go to job boards.
How to Evaluate an Unpaid Internship
Taking an unpaid internship is a real cost, measured in time you could spend on other job search activities or paid work. Before you say yes, answer these three questions honestly.
Will You Work on Real Product Features?
The minimum bar for any internship worth taking is real product work. That means writing code for the company's actual product, not internal tools, sandbox projects, or a codebase nobody looks at.
Ask directly in your conversation with the founder or hiring manager: "Can you tell me what I'd be working on specifically?" A good answer sounds like: "We're building out our notifications system and we need someone to implement the email templates and queuing logic." A bad answer sounds vague or noncommittal.
If they can't tell you what you'd be working on, they haven't thought through what they need. That's a sign the internship will be poorly structured.
Is There a Senior Engineer to Learn From?
An internship with no engineering mentorship teaches you to flounder, not to code professionally. You should have access to someone more experienced who will review your code, answer your questions, and help you understand how things work.
This doesn't have to be a formal mentorship program. It can be as simple as a senior engineer who you can pair with a few times a week. But it needs to exist.
Ask: "Who would I be working most closely with on the engineering side? Would they review my pull requests?" If the answer is that you'd be mostly working independently, that's a warning sign.
Will You Leave With Something to Show?
At the end of the internship, you should have at least one thing that goes on your portfolio: a shipped feature, a pull request that merged, a system you built end to end. If the work is likely to be scattered and none of it will be something you can talk about, the time investment is harder to justify.
You can shape this proactively. In your early conversations, mention that you'd like to work on something with a clear scope that you can discuss in future job applications. Most reasonable founders will accommodate that.
How to Structure Your Ask
Whether you're reaching out cold or following up on a job listing, the pitch has to be specific.
Founders are busy. A vague message ("I'd love to intern at your company!") reads as underprepared. A specific message shows that you've done the work.
Explain what you can do. "I know Rails and React. I've built and deployed two production apps. Here's one of them." Link to something real.
Explain what you're asking for. "I'm looking for a 3-month internship, part-time or full-time, paid or stipended." Being explicit about your flexibility makes it easier to say yes.
Show that you've thought about their specific situation. "I see you're building a B2B SaaS product. I have experience with multi-tenant Rails apps." One specific observation beats generic enthusiasm.
Make the ask low-commitment. "Would you have 20 minutes to chat?" Not "I'd love to discuss potentially joining your team at some point when you have the bandwidth." Short and specific.
Here's a more complete example you can adapt:
Hi [Name],
I'm a Rails engineer looking for my first role. I've built [brief description of project]. Here's the GitHub link and the deployed version.
I noticed [company] is building [product area]. I'd be interested in a 3-month internship focused on [specific area]. I'm flexible on hours and open to stipend-based arrangements.
Would you have 20 minutes to see if there's a fit?
[Your name, portfolio/GitHub link]
That's under 100 words. It respects their time and makes it easy to say yes.
What to Do Once You Have the Internship
Getting the internship is the first half of the work. The second half is making sure it produces the outcomes you need: a portfolio piece, a reference, and ideally a job offer or a strong recommendation.
Start With Clarity on What You're Working On
In your first week, make sure you understand your scope. What are you building? Who will review your code? What does success look like at the end of the internship?
If these aren't clear, ask. A good question: "I want to make sure I'm working on the thing that's most useful to you. What would a successful three months look like from your perspective?"
Treat It Like a Job
Show up consistently. Meet your deadlines. Communicate proactively when you're stuck. Ask questions, but work through problems yourself before escalating.
The engineers and founders you're working with are forming an impression of you as a professional. That impression is what becomes a reference letter or a "we should hire this person" conversation.
Document What You Build
Keep notes on what you ship. The features you build, the problems you solve, the code review feedback you received and addressed. This documentation becomes the raw material for your portfolio piece and your interview stories.
Ask for Feedback
Midway through the internship, ask for feedback directly: "I want to make sure I'm improving in the right areas. Is there anything I should be doing differently?"
This signals maturity. It also gives you information you need to improve before the internship ends.
Secure the Reference Before You Leave
Before the internship ends, have a direct conversation about what's next. If a full-time role is possible, ask about it. If not, ask the founder or your engineering lead if they'd be willing to serve as a reference for future roles.
A specific ask works better than an open-ended one: "Would you be willing to take a 10-minute call with hiring managers from companies I'm applying to? I'd like to include you as a reference."
Getting this commitment before you leave is much easier than following up months later when the memory has faded.
What to Do If the Internship Doesn't Work Out
Some startup internships end early or don't produce what you hoped. The company pivots. The founder gets distracted. The "real product work" turns out to be fixing documentation.
If this happens, cut your losses. There's no value in continuing an internship that isn't producing real experience. Thank them for the opportunity and move on.
Don't include it on your resume unless you have something concrete to show for it. One bad internship doesn't define your job search, and an honest evaluation of what wasn't working is itself useful information for choosing better next time.
Getting real experience before your first job is one of the biggest variables in how quickly you land that job. For the full picture of every path available to you, read how to get real software engineering experience before your first job. For what nonprofit engineering work looks like specifically, the nonprofit software internship guide covers that path in depth.
If you want structured support navigating the early stages of your engineering career, here's how the Globally Scoped program works.
Interested in the program?