In this guide
- The Truth About College Pedigree in Tech Hiring India
- 5 Myths That Keep Tier-3 Engineers Stuck
- The Real Barrier: Resume Screening (And How to Bypass It)
- The Three Levers That Replace College Pedigree
- DSA Roadmap: What to Study and in What Order
- Building a GitHub Portfolio That Gets Noticed
- The Referral Playbook: Getting Referred Without Knowing Anyone
- The 12-Month Roadmap (Month by Month)
- Real Engineers Who Made It (And What They Did Differently)
- FAQ
Aniket graduated from a college you've never heard of in Jhansi, UP in 2020. He joined Wipro on a 3.5 LPA package. He spent the next 28 months doing what most service company engineers do — maintaining legacy Java code, attending standups, and watching the years pass.
In November 2022, he made a decision. He blocked 2.5 hours every morning before office — 5:30 AM to 8:00 AM. LeetCode, system design, and note-making. No exceptions.
In March 2024, he received an offer from Amazon India. ₹42 LPA. 12x his Wipro salary.
His college CGPA was 6.8. He didn't have a single hackathon win. He had no IIT, no NIT, no referral from a friend inside Amazon. What he had was 16 months of structured preparation and a system. This guide is that system.
1. The Truth About College Pedigree in Tech Hiring India
Let's separate the two parts of the hiring process where college matters differently.
| Stage | Does college name matter? | What actually matters |
|---|---|---|
| Resume screening | Yes — moderately. Screeners may filter based on college tier at large companies receiving thousands of applications. | Work experience, projects, GitHub, referrals that bypass screening entirely |
| Online assessment / coding test | No. OAs are blind. | DSA problem-solving speed and accuracy |
| Phone screen | No. The interviewer sees your resume but evaluates your code. | Communication clarity, problem-solving approach, coding fluency |
| Onsite interviews | No. Multiple interviewers, all evaluating you on performance. | DSA, system design, behavioral stories, communication |
| Hiring committee | No. The committee sees interview scores — not college name. | Aggregate performance across all rounds |
The college problem is a funnel problem, not a merit problem. Your college affects whether your resume reaches a recruiter. It has nothing to do with whether you perform well in the interview. Engineers from IITs get rejected from Google every week. Engineers from unknown colleges receive Google offers every week. The interview is the great equaliser.
2. Five Myths That Keep Tier-3 Engineers Stuck
"I need to switch to a top product company first before applying to MAANG."
Reality: You can apply to Amazon, Google, or Microsoft directly from Wipro, TCS, or Infosys. Your current company name doesn't matter. Several Prepflix students have gone directly from service companies with 3–5 years of experience to MAANG offers without any intermediate step.
"I need to solve 500+ LeetCode problems."
Reality: Quality beats quantity. Engineers who solve 150–200 curated problems deeply — understanding patterns, multiple approaches, and complexity tradeoffs — consistently outperform engineers who brute-force 500 problems with surface-level understanding. The LeetCode number is a vanity metric.
"MAANG doesn't hire from tier-3 colleges."
Reality: Google, Amazon, and Microsoft have no official policy that excludes colleges by tier. The engineers inside these companies who review resumes and conduct interviews come from a wide range of colleges themselves. There is individual bias — but it's not systemic policy. A strong referral eliminates this variable entirely.
"I should apply after I'm 'ready.'"
Reality: Most engineers wait too long. They prep for 18 months and then still feel unready. Start applying at the 10–12 month mark with a clear target list. Getting rejections with feedback is preparation you can't get from LeetCode. Apply, fail, learn, apply again.
"I can't compete with IIT graduates who've been preparing since college."
Reality: IIT graduates have advantages at the resume screen and early exposure. But by the time someone has 3–5 years of work experience, these advantages shrink dramatically. Interviewers care about depth of understanding, communication quality, and problem-solving approach — none of which are functions of your undergraduate institution.
3. The Real Barrier: Resume Screening (And How to Bypass It)
Most tier-3 engineers who apply online never hear back. This is not because they lack skills — it's because their resume doesn't pass automated screening or junior HR filters before a technical person ever sees it.
Three ways to bypass resume screening entirely
1. Referral (Highest Impact — Covered in full in Section 7)
A referral from a current employee directly submits your profile to a recruiter, bypassing the automated filter. At Amazon, referrals are processed differently from direct applications — they get human review faster. At Google, a referral means a recruiter will call you regardless of your college. This is the single highest-leverage action you can take.
2. Online Assessments (OAs)
Amazon, Microsoft, Google, and most Indian unicorns send OAs through HackerRank or Codility. These are blind — no college name on the screen. Performing in the top 10–15% of OA candidates guarantees a recruiter call. Mass apply to every company sending OAs via campus drives (even if you're off-campus) or job portals like LinkedIn and Instahyre.
3. LinkedIn Recruiter Outreach
Recruiters at top companies use LinkedIn actively. A well-crafted LinkedIn profile with quantified achievements and visible DSA activity (LeetCode stats, GitHub contributions) will attract recruiter InMails. Reach out directly to technical recruiters at target companies — a short, personalised message with a specific ask performs far better than applying through the portal.
4. The Three Levers That Replace College Pedigree
College pedigree is a signal of potential. You replace it with three concrete signals:
| Lever | What it signals | Time to build | Impact |
|---|---|---|---|
| DSA depth | Problem-solving ability, algorithmic thinking | 8–12 months | Passes phone screens and onsite coding rounds |
| GitHub portfolio | Initiative, real engineering skill, technical range | 3–6 months (parallel) | Resume differentiation, LinkedIn visibility, talking points |
| Referral network | Trust from someone inside the company | 2–4 months (parallel) | Bypasses resume screening, fastest path to interview |
5. DSA Roadmap: What to Study and in What Order
Order matters. Most engineers study DSA topics randomly — arrays one day, graphs the next, DP the next. This produces shallow coverage everywhere. The right order builds on foundational intuitions before adding complexity.
Arrays, Strings, Two Pointers, Sliding Window, Hashing, Sorting
- These 6 topics appear in 70%+ of all coding interview questions
- Goal: solve any medium array problem in under 20 minutes with optimal complexity
- Target: 60–70 curated problems, 15 problems per topic
- Resources: NeetCode 150 (first 50), Prepflix DSA Tracker (Arrays section)
Linked Lists, Stacks, Queues, Trees (BFS/DFS), Binary Search Trees, Heaps
- Trees are the most tested topic at Google and Flipkart
- Heaps are tested at Amazon heavily (top-K problems, merge K lists)
- Goal: solve medium tree/graph problems in under 25 minutes
- Target: 50–60 problems across these topics
Graphs (BFS/DFS/Dijkstra/Union-Find), Recursion and Backtracking, Tries
- Graphs are tested at Google more than any other topic after arrays
- Backtracking is essential for permutations, combinations, Sudoku, N-Queens
- Target: 40 graph problems, 20 backtracking problems
Dynamic Programming (all patterns), Advanced Trees (Segment Tree, Fenwick Tree)
- DP is the hardest topic but appears in 1 of every 4 Google interviews
- Learn DP by patterns: 0/1 Knapsack, Unbounded Knapsack, LCS, LIS, Matrix DP, Interval DP
- Target: 40–50 DP problems, one pattern at a time
- Don't move to the next DP pattern until you can solve 5 medium problems from the current one cold
Mock interviews, timed sessions, revision of weak areas
- Do 20+ timed mock interviews (45 minutes each, 2 problems)
- Every mock should include explaining your approach out loud — not just solving silently
- Review company-specific problem lists (LeetCode company tags, Prepflix company PYQs)
6. Building a GitHub Portfolio That Gets Noticed
A strong GitHub portfolio is one of the most powerful tools for a tier-3 engineer. It demonstrates engineering skill independently of your college name or employer.
What makes a portfolio project worth having
- Real users / real scale: A project that 100 people actually use is worth 10 that no one touches. Deploy your projects. Get real traffic, even small.
- Quantified impact in the README: "Handles 500 concurrent users," "reduced query time from 2.1s to 190ms," "10,000 API calls per day." Numbers in READMEs signal engineering maturity.
- Clean code structure: Interviewers who look at your GitHub do read the code. MVC structure, separation of concerns, tests, and clear commits matter.
- At least one backend + one system-level project: A REST API with authentication, database design, and documented endpoints. Shows you can build real software.
Three project types that get engineering recruiters' attention
| Project Type | What it demonstrates | Example |
|---|---|---|
| Backend API with real use case | Database design, REST principles, auth, performance | A job board API with LinkedIn OAuth, search filtering, Redis caching |
| Distributed / scale problem | Systems thinking, async processing, queues | A URL shortener with Redis + PostgreSQL + rate limiting that handles 10K req/s |
| DSA visualiser or tool | Depth on algorithms, teaching ability, passion | A graph algorithm visualiser that animates BFS/DFS/Dijkstra step by step |
7. The Referral Playbook: Getting Referred Without Knowing Anyone
The most common question tier-3 engineers ask is: "How do I get a referral when I don't know anyone at these companies?"
The answer is: you find them, you build a small relationship first, and then you ask specifically. Here's the exact sequence:
Step 1: Find employees at your target company on LinkedIn
- Search: "[Company Name] Software Engineer India" in LinkedIn
- Filter for: current employees, 2nd-degree connections first
- Look for: alumni of your college, engineers from your city, people who've written public articles or posts
Step 2: Send a specific, short connection request message
- Don't ask for a referral in the first message. This fails almost every time.
- Instead: "Hi [Name], I came across your post on [topic] and found it really insightful. I'm preparing for software engineering roles at [Company] and would love to ask you a couple of questions about the engineering culture there when you have 10 minutes."
- You're asking for information, not a favour. People are far more likely to respond.
Step 3: Have a genuine 15-minute conversation
- Ask about their experience at the company, the team they're on, what they enjoy about the role
- Share your background briefly. Let them ask about you.
- Do NOT ask for the referral in this call.
Step 4: Follow up 2–3 days later with the ask
- "Thank you for the chat the other day — it gave me a much clearer picture of what the engineering org is like. I've been preparing seriously for [Company] interviews and I'm confident I can perform well. Would you be comfortable referring me through the employee referral system? Here's my updated resume: [link]."
- Make it easy: have your resume ready, have a clear role in mind, and express confidence without arrogance.
Send 10–15 of these per company. Even a 20% response rate gives you 2–3 potential referrals. One is all you need.
8. The 12-Month Roadmap (Month by Month)
DSA Phase 1 + LinkedIn Setup + College Alumni Outreach
- Arrays, Strings, Two Pointers, Hashing: 60–70 problems
- Optimise LinkedIn: professional photo, quantified experience bullets, featured DSA project
- Identify 3 target companies. Start alumni outreach for those companies.
- Daily commitment: 2 hours minimum. No exceptions on weekdays.
DSA Phase 2 + Start GitHub Portfolio Project
- Trees, Graphs, Heaps, Binary Search: 50 problems
- Start building Portfolio Project 1 (backend API). Aim for production deployment by month 6.
- Apply to OAs: any company sending OAs via LinkedIn or Instahyre. Start practicing under time pressure.
Advanced Graphs, Backtracking + HLD Fundamentals
- Graphs (BFS, DFS, Dijkstra, Topological Sort), Backtracking: 60 problems
- System Design: databases, caching, load balancing, message queues, CAP theorem — 2 hours/week
- Complete portfolio project. Start job applications at tier-2 Indian companies (Juspay, InMobi, Slice, Niyo) to get interview experience with lower stakes.
Dynamic Programming + LLD + Mock Interviews Begin
- DP (all 6 patterns): 40–50 problems
- LLD: Parking Lot, Food Delivery, Library Management, ATM under timed conditions
- System Design: design 8 classic systems (Twitter, URL Shortener, WhatsApp, Amazon)
- Start 2 mock interviews per week — with a peer, mentor, or platform
Apply Aggressively + Referral Conversion + Active Interviews
- Apply to all target companies: Amazon, Google, Microsoft, Flipkart, Razorpay, PhonePe
- Activate your referral network — this is the month to convert those relationships into referrals
- Treat every OA as a live practice. Treat every rejection as data about weak areas.
- Continue 1–2 mocks per week even while in active interview cycles
9. Real Engineers Who Made It (And What They Did Differently)
The common thread: all three worked consistently, not heroically. No 16-hour days. Consistent 2–3 hour daily routines, sustained over 12–18 months. And all three had a specific system — not just "doing LeetCode."
10. FAQ
I have a 5.2 CGPA. Will that block me?
CGPA below 6.0 can filter you out at the resume screen for companies that have explicit CGPA cutoffs (mostly MNCs and larger tech companies in their mass hiring). For Indian product companies and startups, CGPA is generally not a cutoff. A referral bypasses CGPA filters almost entirely. Focus on getting referrals and applying through OA routes rather than the general portal.
Should I do an MS from the US to get a MAANG job?
If your goal is a MAANG job, an MS is not required and is a very expensive detour. Engineers from tier-3 colleges in India get MAANG offers directly without any postgraduate degree. The money you'd spend on an MS (₹50–80L fully loaded) is better invested in 12–18 months of structured prep and one strong job offer. The MS path makes sense if you want to immigrate or if you want research roles — not if your goal is an SWE offer in India.
What's the right approach if I've already been rejected from Amazon twice?
Amazon's cooling-off period after rejection is 6 months. Use that time to genuinely improve the weak area. If you failed the coding round, it means DSA depth. If you failed behavioral, it means lack of STAR preparation. Don't reapply until the specific weakness is addressed — Amazon keeps rejection history and interviewers can see past performance context.
Is it better to target MAANG directly or build up via smaller product companies first?
Both paths work. The "stepping stone" strategy (tier-2 → tier-1 product company → MAANG) is lower risk — you build confidence, interview skills, and a better resume. The direct path is faster but higher rejection rate. My recommendation: target both simultaneously. Apply to Google and Amazon while also applying to Razorpay and PhonePe. If you get the mid-tier offer first, take it. You can continue preparing for MAANG from there — and now with a product company name on your resume.
Pranjal spent 6+ years at Microsoft India and has coached 1,572+ engineers from tier-2 and tier-3 colleges through FAANG and top Indian product company interviews. He founded Prepflix to give every engineer, regardless of college background, the same structured preparation that IIT networks have always provided informally.