can you put a failed startup on your resume
Yes, and you should. A failed startup is not a gap to hide but proof you shipped something, made decisions with consequences, and learned what does not work, while the only failure that hurts you is pretending it never happened.
- Resume use among employers fell to 67% in 2025, down from 73%, as hiring shifts toward proof of skill over credential listing.
- Internship experience cuts new-grad underemployment odds by 48.5%, but entrepreneurial work with real outputs functions similarly when framed with specifics.
- Big tech new-grad hiring is down more than 50% from 2019 peaks, making differentiated proof of execution more critical than pedigree.
- 53% of employers have dropped degree requirements, per TestGorilla 2025, yet most still lack structured ways to evaluate non-traditional experience. Your job is to make it easy.
why recruiters secretly prefer failed founders to blank resumes
A recruiter staring at two fresh graduates sees the same problem either way: no proof anyone trusted you with real responsibility. The one with "Founder, [Startup Name]" has at least crossed the threshold of building something, hiring someone, spending money, and facing the market. The other has only crossed the threshold of attending class.
The recruiter's real question is not "did this succeed?" It is "what did this person actually do, and can they do it for me?" Success is not the only signal. A failed startup with specifics beats a prestigious internship with generics. "Grew to 2,000 users, churned at 40%, learned distribution before product-market fit" tells a story. "Marketing intern at [Brand]" tells almost nothing.
The fear that failure marks you as damaged is mostly in your head. In a market where new grads are roughly 7% of hires at major tech employers, down dramatically from prior years, recruiters are scraping for signals of self-sufficiency. Someone who incorporated, built, pitched, and wound down a company has operated with more ambiguity than most entry-level hires ever face.
The catch: you must frame it as work, not as a story about your dreams. Recruiters are not therapists. They do not care that you "learned so much" unless you specify what, how much, and what it cost you.
how to write the entry so it reads as proof, not confession
The difference between a compelling failed-startup entry and a cringe one is specificity about outputs and ownership. Never write "Founder, attempted to build a social app." That is a confession. Write "Founder, [Name]: built MVP in React/Firebase, acquired 1,200 users via TikTok organic, shut down after 8 months due to unit economics; $14K revenue, $22K costs."
Lead with what you built, not what you intended. Use numbers even when they are small or negative. "Spent $8K of savings" is more credible than "raised funding" when the funding was zero. "Interviewed 47 potential customers" beats "conducted market research."
Own the failure in one line, then move to what you would do differently. "Shut down after identifying CAC exceeded LTV by 3x; revised pricing model in final month" shows analytical recovery. "Unfortunately did not succeed" shows you have not processed what happened.
Group your bullets by skill area if the startup touched multiple domains: product decisions, growth experiments, financial management, hiring or vendor negotiation. This lets a recruiter scanning for "product sense" or "growth" find their keyword without forgiving the failure.
what to do if the startup never launched or never made money
Not every startup fails after shipping. Some die in prototype, some in conversation, some in your own hesitation. The rule still applies: specificity saves you. If you built a prototype, describe the prototype. "Designed and built a functional prototype for a restaurant reservation tool; tested with 3 local businesses; shelved after feedback showed incumbents had locked distribution channels."
If you never built anything, be honest about what you did do. "Spent 6 months evaluating market opportunity, conducted 23 customer interviews, determined addressable market was too small for venture-scale" is valid work. It shows judgment, not just execution. The danger is inflating this into "Founder, stealth-mode startup" or implying revenue that did not exist.
The worst version is the one where you hide behind jargon to obscure that nothing happened. Recruiters who have screened hundreds of resumes can smell "strategic planning for B2C platform" as code for "thought about it." Replace that with the actual activity, however modest.
where this fits in the bigger picture of replacing credentials with proof
The university filter operates on a simple promise: survive the program, get the signal, hope someone notices. Entrepreneurship is the opposite. There is no program. There is only the work and whether anyone can see it. A failed startup is raw material that the filter system has no category for, which is exactly why it can differentiate you.
But raw material needs shaping. The reason most founders underutilize their startup experience is they never translated it into language a hiring manager recognizes. "I did everything" is not a role. "I owned user acquisition and reduced CAC by 34% through referral experiments" is a role with proof.
This is where the old system and the new one diverge, since a degree attempts to pre-certify you for everything while proof-based hiring asks you to demonstrate something specific for the role at hand. A failed startup, properly framed, is a dense concentration of specific demonstrations. You just have to excavate them from the narrative of failure you have been telling yourself.
when to leave it off entirely
There are two valid reasons to omit a failed startup. First, if it lasted less than three months and produced no tangible output, not even a prototype or documented learning. At that point it reads as an idea, not as work. Second, if you cannot answer detailed questions about it without blaming cofounders, investors, or "the market." Interviewers will probe, and defensiveness undoes whatever credibility the entry earned you.
Everything else belongs on the resume. Six months of real effort with nothing to show is still six months of operating in uncertainty, making decisions, and living with consequences. That is the job. Most entry-level roles are not hiring for success rate. They are hiring for tolerance of ambiguity and willingness to own outcomes.
frequently asked questions
Should I say "failed" or use softer language like "wound down"?
Use neutral precision. "Wound down," "shut down," "pivoted and discontinued" are all fine. Avoid "failed" as a self-descriptor and avoid "sunsetted" or "paused" if you never resumed. The goal is clarity, not emotional distance.
What if I was a solo founder, not a "real" startup?
Solo is real. The question is whether you shipped, sold, or served anyone. If yes, list it. If you only researched and never tested, call it "independent project" rather than "founder" and describe the research scope.
Do I include revenue if it was tiny?
Yes, especially if tiny. "$3,200 in revenue" is more credible than "monetized" or "generated revenue." Small real numbers beat vague upward language every time. They also give interviewers something concrete to ask about.
How do I handle questions about why it failed in interviews?
Prepare a 30-second version that owns your decisions, names one specific misjudgment, and closes with what you would test next time. Practice until you can say it without rushing or apologizing. The interviewer is evaluating your self-awareness, not your business acumen.
Does this replace internships, or supplement them?
Supplement, unless the startup produced comparable scope. Internship-to-full-time conversion runs 63.1% because structured programs provide referenceable supervision and known skill benchmarks. A startup can match that if you make the benchmarks visible. Do not assume equivalence; demonstrate it.