By Cyril KimbiGraduates apply for months and hear nothing, and conclude that the market is closed or that connections decide everything. Connections do help. But a large share of rejections happen for reasons that are visible on the application itself, and those are fixable.
What is actually being compared
When a manager has forty applications and four interview slots, the qualification is a filter, not a decision. It removes people who do not meet the line. Everyone left is compared on other things:
- Proof of doing, not just studying. An internship, a project, freelance work, a role in an organisation — anything where you produced a result rather than attended a course.
- Communication. Whether your application is clear. It is treated, fairly or not, as a sample of your work.
- Reliability signals. Finishing what you start. Gaps and abandoned programmes raise questions you should answer before they are asked.
- Fit with the actual job. Whether you appear to understand what the role involves day to day.
The evidence problem, and how to fix it in one year
Most graduates have no evidence because nobody told them to collect any. The good news is that this is buildable from a standing start, and faster than people expect.
Anything that produced a result counts, provided you can describe it concretely: an internship, a small piece of paid work, a project built for a real user, a association or church role where you organised something, a documented volunteer contribution. What does not count is a list of skills with no instance attached.
The test is whether you can complete this sentence: “I did X, which produced Y.” If you cannot, it is not yet evidence. Our guides on internships and work experience and on building a student CV cover how to find and present these.
Why applications are rejected before anyone reads them properly
Four recurring, entirely avoidable reasons:
- The same letter sent everywhere. Visible immediately, and it signals that you are not interested in this job specifically.
- Length. A CV that runs to several pages for a first job suggests you cannot identify what matters.
- Errors. When the job involves writing anything, mistakes in the application are treated as a work sample.
- Duties instead of results. “Responsible for customer service” says nothing. What changed because you were there?
None of these require talent to fix. They require an hour per application instead of five minutes across twenty.
Fewer applications, better ones
The instinct when nothing is working is to send more. It is usually the wrong direction.
Ten applications genuinely adapted to the role — naming the organisation, addressing the stated requirements in order, showing you know what the work involves — consistently outperform a hundred identical ones. The identical hundred also teach you nothing, because rejections without feedback tell you only that something is wrong.
Adapt the first third of the CV and the whole letter to each role. The rest can stay stable.
The soft requirements nobody writes down
Two things employers weigh heavily and rarely state.
Bilingual capability. In a two-language country, a graduate who works in both is useful across the whole organisation. This is often decisive between otherwise similar candidates — see the bilingual advantage.
Whether you will stay. Training a new graduate is expensive. Anything suggesting you will leave in six months — an application that looks like a placeholder, no interest in the sector — counts against you quietly.
Starting smaller than you planned
A first role slightly below your target is not a defeat; it is where the evidence comes from. A year of real work makes the second application far stronger than the first, because you stop arguing that you could do the job and start showing that you have.
What matters is that the role is real and that you can describe what you achieved in it. That is worth more, twelve months later, than having held out for a title.
Frequently Asked Questions
Does the class of degree matter?
It helps pass the filter. Beyond that, evidence of doing the work matters more.
How do I get experience with no experience?
Projects, volunteering, small paid work, organisational roles. Anything with a describable result.
How many applications should I send?
Fewer, adapted properly. Ten targeted beat a hundred identical.
Do connections decide everything?
They help, but most rejections come from avoidable faults in the application itself.
Should I take a job below my target?
Often yes. Real work is what turns a weak application into a strong one.
