The referral myth and what actually works
Everyone in India's tech job market says the same thing: "Just get a referral." And referrals do work — referred candidates get interviews at significantly higher rates than cold applications. But the advice is useless to most people most of the time, because you either have a contact at the company or you don't.
The good news: cold applications at scale, combined with a strong online presence, can replicate the referral advantage. This guide explains how.
Why most engineering job applications fail before being read
The pipeline from application to interview has multiple filters:
- ATS parsing. Your resume is extracted by software. Complex formatting, tables, or the wrong keywords mean rejection before a human sees it.
- Recruiter shortlisting. The recruiter scans 30–50 resumes per day. You have 15 seconds. A resume that doesn't communicate your level, stack, and relevance immediately gets skipped.
- Hiring manager review. The manager reviews the recruiter's shortlist. This is where technical credibility is assessed from the resume alone.
Most applications fail at stage 1 or 2. Fix those stages first before worrying about interviews.
Resume optimisation for engineering roles
The engineering resume format that clears ATS and passes recruiter review:
Header: Name, email, phone, city, LinkedIn, GitHub, portfolio URL. All plain text.
Summary (3 sentences): Your level (SDE-1/2/3 equivalent), primary stack, years of experience. Example: "Backend engineer with 4 years building distributed systems in Go and Python. Experience with event-driven architectures on AWS, optimising high-throughput APIs, and leading small teams. Looking for SDE-2 roles at product companies in Bangalore or remote."
Experience: For each role, include the tech stack explicitly in your bullet points. Companies, frameworks, scale metrics. "Built a rate-limiting service handling 2M req/day using Redis and Go" is better than "Developed backend services."
Projects: Include 2–3 real projects with GitHub links. For companies that care about actual code, this is your proof of work. A project that solves a real problem, with clean code and a README, is worth more than any certification.
Skills: List every language, framework, database, and tool you've genuinely worked with. ATS systems filter by exact skill matches. Include both common spellings (JavaScript, JS) and framework variants (React, React.js, ReactJS).
Where to apply: beyond Naukri
Most people apply only to Naukri and LinkedIn. The competition is highest there. Diversify:
Company career pages directly. Many mid-size product companies don't actively post on job portals. Check their careers page. Apply directly. Cold applications to careers pages often reach hiring managers faster than portal applications.
AngelList / Wellfound. Strong for startup roles. Startup hiring moves faster than enterprise, and the skills valued are different — generalists do well here.
Instahyre. Tech-focused platform used by companies like Meesho, Razorpay, and Cred. Profile-based, so recruiters come to you once your profile is strong.
HackerEarth and HackerRank. Many companies source through hackathon performance. If you can rank, you generate inbound interest.
Community-based job sharing. Slack communities, Discord servers, and WhatsApp groups for specific tech stacks (React India, Go India, DevRel communities) share job opportunities. Being active in these communities — answering questions, sharing knowledge — creates the informal credibility that referrals normally provide.
Build the profile that makes recruiters come to you
The goal is not just to send applications. It's to build a profile strong enough that recruiters find you.
LinkedIn recruiter searches filter by: location, current/past companies, years of experience, skills, school. The more keyword-rich your profile, the more searches you appear in.
GitHub green squares (consistent commit history) signal active development. A profile with real projects, clean code, and recent commits is taken seriously by technical hiring managers who look.
A portfolio website with your name in the URL (notapdf.com/yourname) means when a recruiter Googles you, the first result is your professional presentation. This is the modern equivalent of a business card — except it shows everything.
The "warm cold application" strategy
A cold application doesn't have to be entirely cold. Before applying:
- Find the hiring manager or team lead on LinkedIn
- Follow them, read their recent posts
- Comment thoughtfully on a relevant post (not "great post!")
- Apply through the official channel
- Send a brief, specific LinkedIn message mentioning the role
This process takes 20 minutes per application and significantly increases the probability that your resume gets read. It doesn't require a referral — it requires effort that most applicants don't make.
Technical preparation: the filter nobody talks enough about
Getting the interview is only half the problem. Once you're in the pipeline:
LeetCode is the standard for DSA interviews at most companies. The pattern: easy problems mastered completely (no "mostly know it"), medium problems at speed, hard problems for target companies (Google, Microsoft, Amazon, Atlassian). Consistent daily practice beats marathon sessions.
System design becomes critical at SDE-2 level and above. The Grokking the System Design Interview course and Alex Xu's "System Design Interview" books are the standard resources. Practice out loud — system design interviews are conversations, not written answers.
Behavioural preparation is underrated in India. STAR method (Situation, Task, Action, Result) for every story you tell. Prepare 8–10 specific stories that demonstrate impact, handling ambiguity, conflict resolution, and technical leadership.
Start your job search assets at notapdf.com — portfolio and ATS resume generated from your existing credentials in under 5 minutes.