Career Advice
How to Apply to a Startup When You Have No Experience
What founders actually read in an application, why a proof-of-work project beats a longer CV, and a step-by-step process for applying to startups with little or no experience.
Ceeve Team · 2026-08-30 · 8 min
Startups do not hire the way large companies hire. If you apply to a twelve-person team the way you apply to a graduate scheme, you will lose to someone with less experience and a better application.
At a glance
- At an early-stage startup, a founder or hiring manager usually reads your application personally. There is often no ATS to beat.
- They are answering one question: can this person reduce my workload in the next month?
- Evidence of something you built or shipped outweighs an extra line of experience.
- Ten adapted applications beat a hundred generic ones.
Who reads your application
At a company of 5,000 people, your CV is screened by software, then by a recruiter who has never done the job, then by the hiring manager. Keyword coverage matters because a machine gates you.
At a company of twelve, the person reading your CV is often the person you would report to, sometimes a founder, and they are reading it between two other things. They will spend twenty seconds deciding whether to read the rest. Formatting for a machine is wasted effort here. Formatting for a distracted, specific human is not.
What they are actually looking for
Not credentials. Evidence of self-direction. Early-stage teams have no capacity to hand out tasks, so they hire for the ability to see a problem and move on it without being asked.
That is why a small, finished thing you made carries more weight than a longer list of responsibilities. A teardown of their onboarding flow, a script that automates something tedious in their domain, a landing page you rebuilt, a short analysis of their market with three specific recommendations — any of these prove more than a bullet point ever will.
It does not need to be impressive in absolute terms. It needs to be relevant, finished, and yours.
A process that works
1. Narrow before you apply. Pick a city and a role family and shortlist ten companies whose product you can explain in one sentence. If you cannot explain what they sell, you cannot write a convincing application.
2. Read the posting like a brief. Early-stage job descriptions are usually written by the hiring manager and describe real, current pain. The first three responsibilities listed are the ones that matter. Everything below is a wish list.
3. Adapt the CV to the role, not the company. Reorder your bullet points so the experience closest to those first three responsibilities appears at the top. Use their words for the same concept — if they say "growth," do not say "marketing." Cut anything irrelevant, even if you are proud of it. A one-page CV that maps to the role beats two pages that cover everything.
4. Quantify with what you actually have. No work experience does not mean no numbers. Society events you organised, users of a side project, coursework with a measurable result, a freelance client's outcome — all of these are legitimate. Never invent a figure; a founder who probes an inflated number in an interview will end the process there.
5. Send proof, not promises. Attach or link one small artefact relevant to their problem. Say in two lines what you looked at, what you found, and what you would try first.
6. Write to a person. Find the hiring manager or a team member. Four sentences: what you noticed about their product, the thing you made, what you want, and nothing else. No paragraph about being a passionate self-starter.
7. Follow up once, after a week. One short message that adds something new — a further thought, a second piece of work. Then stop.
What to avoid
A generic cover letter about your passion for innovation. Applying to fifty roles in a day. Claiming familiarity with tools you have opened once. Long emails. Asking for "any available opportunity" instead of a specific role — at a small company, that reads as someone who has not thought about what they would do there.
If you get no replies
Small teams are inconsistent at responding, and silence is usually a capacity problem rather than a verdict on you. But if twenty adapted applications produce nothing, the problem is likely one of three things: you are applying to roles that need experience you do not have, your CV is not making the first three responsibilities obvious in the top third, or you are not sending any evidence of work.
Fix the third one first. It is the fastest to change and the one that most reliably makes a founder reply.