Silence usually means a pipeline problem, not a talent problem. Too many untargeted portal applications, a CV that does not match the role, projects that do not work when opened, and almost no referrals or direct outreach. Fix those four and measure each stage.
What people tell me
I graduated in computer science or a related field and did not get placed on campus, or my internship ended without a full-time offer. I have applied to fifty or more companies through job portals and LinkedIn, sent cold emails and asked for referrals, but I get rejections or no reply at all. Money is tight and I feel numb. I do not want to settle, but I no longer know what is going wrong.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- Count your funnel: applications sent, replies, first rounds, final rounds. The weakest stage tells you what to fix.
- Forty tailored applications with outreach beat four hundred one-click ones.
- Referrals and direct messages to engineers and hiring managers convert far better than portals alone.
- Open every project link on your CV. A broken demo quietly ends many applications.
- Keep a daily routine that mixes applying, building and practising, so the search does not become your whole identity.
Silence is data, not a verdict
When dozens of applications go unanswered, it is natural to conclude you are not good enough. In most cases I review, that is not what the evidence says. What it says is that the applications are not reaching a human, or they are reaching one and failing a thirty-second scan. Both are fixable, and neither is a judgement on your ability as an engineer.
The entry-level market is genuinely harder than it was a few years ago, with more applicants per role and fewer openings labelled junior. That is exactly why a scattershot approach stops working and a deliberate one still does.
Treat the search as a funnel
Open a spreadsheet and track every application: company, role, date, how you applied (portal, referral, direct message), and how far it got. After three or four weeks, the pattern shows you where to spend effort.
| Where it breaks | What it usually means | What to fix |
|---|---|---|
| No replies at all | CV not matching roles, applying too broadly, only using portals | Tailor the CV per role type, add referrals and outreach |
| Replies from HR but no technical round | Weak projects, unclear skills, location or availability mismatch | Strengthen two projects, make stack and availability obvious |
| Technical rounds but no final | Problem solving or communication under pressure | Structured practice and mock rounds |
| Finals but no offers | Behavioural answers, salary expectations, team fit | Prepare stories, research pay, ask for feedback |
Most fresh graduates who write to me are stuck on the first row.
Five fixes that change the first row
- Pick one or two target role types. "Frontend developer" and "backend developer" need different CVs. A single generic CV sent to both is weaker for each.
- Tailor the top third of your CV. Your headline, skills and first project should mirror the language of the listing. This takes ten minutes per role type, not per application.
- Make your projects bulletproof. Open every link. Features described on the CV must work. Remove anything half built. A recruiter who clicks a broken demo does not come back.
- Get referrals properly. Find engineers at the company on LinkedIn, send a short, specific message mentioning the role and one relevant project, and ask whether they would be comfortable referring you. Many will say yes to a polite, prepared request.
- Apply early. Listings get most of their serious attention in the first few days. Set job alerts and apply within forty-eight hours where you can.
A referral message that gets answered
Keep it short, specific and easy to say yes to:
Hi, I saw the junior backend role on your team's careers page. I recently graduated and built a deployed booking API with Node.js, PostgreSQL and automated tests (link). If you think I would be a reasonable fit, would you be comfortable referring me? Happy to send my CV. Thank you either way.
No long life story, no attached CV in the first message, and no follow-up more than once a week later.
A weekly rhythm that keeps you moving
| Activity | Weekly target |
|---|---|
| Tailored applications | 10 to 15 |
| Personal outreach messages (referrals, hiring managers, alumni) | 10 |
| Problem-solving practice | 5 to 7 hours |
| Improving one portfolio project | 4 to 6 hours |
| Reviewing your funnel and adjusting | 30 minutes |
This keeps applications steady without letting them eat every hour, and it means that by the time replies come, your skills are sharper than when you applied.
Look beyond the obvious companies
Everyone applies to the same well-known names. Widen the net deliberately:
- Startups and mid-sized product companies, which often move faster and read applications themselves.
- Local companies with small engineering teams that post only on their own careers pages. The Sefism company directory lists many that hire in Pakistan, with their careers links.
- Contract, internship or apprenticeship roles that convert to full-time.
- Remote roles for junior engineers, knowing competition is higher.
When the internship did not convert
If you performed well in an internship but did not get an offer because of headcount or company decisions, that experience is still valuable. Ask your manager for a written recommendation on LinkedIn, list concrete outcomes from the internship on your CV, and mention in outreach that the offer was affected by company-wide constraints. Recruiters understand this happens.
Protect your head as well as your pipeline
Financial pressure and weeks of silence wear people down. Set working hours for the search and stop at the end of them. Keep building something you enjoy so there is visible progress each week even when inboxes are quiet. If the pressure is severe, a short-term job or freelance work that pays the bills is not failure; it buys you time to search properly.
Do not settle, but do stay honest
Holding out for a good role is reasonable. Set a timeframe, for example three months of the rhythm above, and review the funnel data at the end. If nothing has moved at the first stage despite real changes, widen the role types or locations rather than repeating the same approach.
If you are still stuck
Read A job search is a pipeline, not a performance and How to apply for software engineering jobs, then the full graduate plan in From CSE graduate to your first software engineering job. If you want an honest outside look at your profile and approach, book a free 1:1 session.
Was this answer helpful?
Read next
- A Job Search Is a Pipeline, Not a PerformanceMost people run a job search as a series of hopeful individual events, which fails for a structural reason: the response rate on cold applications is low enough that any single one is close to noise. The people who find work reliably are running a pipeline instead. Thirteen heuristics for the mechanics, which are the part you actually control.
- How to Apply for Software Engineering JobsA job search is often a hundred applications, and knowing that before you start changes how you run it. How to write a resume where every line says what changed, why referrals outperform everything else, how many applications to keep live, what to track so you know whether the problem is the resume or the interview, and what to do in the ten minutes after an offer arrives.
- From CSE Graduate to Your First Software Engineering JobJob, timing and learning are one loop that traps graduates. How to run learning, applications and interview practice in parallel, what to stop learning, how junior technical interviews are structured, how to practise patterns and speak your thinking aloud, plus a twelve week plan and a reflection template.
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open to X and Instagram followers and university students. Prefer to talk? A free call works too.