Google Engineer Rejected by Startup Over Low College CGPA

When Salary and Experience Aren't Enough

In a striking reminder of how hiring practices vary across the Indian tech industry, a Google engineer drawing a salary of ₹80 lakh per annum found themselves rejected by an Indian startup—not for lack of skills or experience, but because their college CGPA fell below the company's screening threshold. The incident, which gained traction on social media, has reignited conversation about whether academic metrics remain relevant when evaluating seasoned tech professionals.

The engineer, currently employed at one of the world's largest tech companies, applied to the Indian startup expecting their Google credentials and substantial salary package to outweigh any concerns about undergraduate performance. Instead, they encountered a rigid hiring gate that refused to look beyond college grades accumulated years earlier.

The CGPA Question: Relevance vs. Reality

College CGPA is a blunt instrument for assessing professional capability. By the time an engineer reaches Google—a company notorious for its rigorous hiring process—their academic transcript should be historical context, not a disqualifying factor. Yet many Indian startups continue to use minimum CGPA thresholds as automated filters, sometimes screening out candidates before human recruiters ever see their profiles.

The irony is particularly sharp here. Google's own hiring process emphasizes coding ability, problem-solving, system design, and behavioral fit over academic credentials. An engineer who has passed Google's gauntlet and spent months or years succeeding there has already proven their technical mettle in ways that matter. A college CGPA from years past is a poor predictor of current performance.

Why Startups Still Lean on CGPA

Several factors explain why Indian startups—especially early-stage ones—continue relying on CGPA cutoffs:

• Screening at scale: For startups receiving hundreds of applications, CGPA filters reduce initial candidate pools quickly and cheaply.
• Perceived quality signal: Many hiring managers mistakenly believe CGPA correlates with long-term job performance, though research suggests otherwise.
• Risk aversion: Founders and HR teams may feel justified using "objective" metrics, even when they're outdated or irrelevant.
• Lack of better alternatives: Building robust skill-assessment frameworks takes time and resources that early-stage startups often lack.

The Startup Hiring Crisis

This incident highlights a broader challenge facing Indian startups: talent acquisition. The sector has grown dramatically over the past decade, with thousands of startups competing for engineering talent. Yet many still employ hiring practices borrowed from the 1990s, when limited information about candidates made proxies like academic pedigree seem reasonable.

A software engineer at Google represents the opposite of hiring risk. They have demonstrated the ability to:

• Solve complex algorithmic problems at scale
• Collaborate in a world-class engineering environment
• Deliver shipping code used by millions globally
• Navigate career growth at a top-tier tech company

None of these achievements are reliably predicted by a college grade point average. If anything, the engineer's ₹80 lakh package—substantially above typical startup compensation—signals confidence from a heavyweight employer about their market value.

What This Means for Indian Startups

Startups that reject experienced engineers on the basis of college CGPA risk missing transformative hires. These candidates bring not just technical skills but domain knowledge, processes, and perspectives from leading global companies. For a startup trying to scale beyond early product-market fit, such talent can accelerate growth dramatically.

More fundamentally, these rigid screening practices suggest that the startup in question may lack confidence in its own recruiting capability. Rather than invest in better interviews, coding assessments, or reference checks, they outsource hiring judgment to an academic metric from five or ten years prior.

Industry Response and Changing Norms

The incident sparked discussions among Indian tech leaders about whether CGPA cutoffs have a place in modern hiring. Several high-growth startups and tech leaders have publicly moved away from such requirements, arguing that demonstrated work experience provides far better signal.

Some platforms and startup accelerators now explicitly discourage CGPA-based filtering, encouraging hiring teams to focus on recent work samples, portfolio projects, and structured interviews instead. The logic is straightforward: college performance is a historical artifact, while a Google tenure is a current and proven indicator of capability.

For the engineer in this story, the rejection likely stings more because of its arbitrariness than its impact. Candidates with Google on their resume are rarely unemployed for long. But the incident serves as a cautionary tale for startups: exclusionary hiring criteria, applied mechanically without judgment, can cost you access to exactly the talent you need to compete.

Key Takeaway

As Indian startups mature and compete harder for engineering talent, abandoning outdated filters like CGPA cutoffs isn't just fair—it's smart business. The engineer rejected for their college grades may have been exactly who that startup needed to build its next product or scale its platform. Instead, a rule book cost them that opportunity.