u/Wild-Measurement7768

Something I have spent a lot of time on lately, sharing here for feedback from other founders who hire.

Post one role and you get hundreds of applications. Inflated resumes, borrowed experience letters, skills listed that nobody can actually back up, and now a wave of AI-written profiles on top. There is no fast, reliable way to tell who can really do the work versus who just wrote that they can. So it becomes hours of screening calls that go nowhere, or hiring on gut and a familiar company name on the resume, and sometimes finding out months later that half the resume was fiction.

The core issue is that hiring still runs on self-declared claims. The burden of proof sits on the employer, one interview at a time, and background checks catch it too late and cost too much.

So I have been building toward a different model, where a candidate's skills, work history and projects come backed by real records and approved evidence instead of self-declaration, so the claims are verified before a profile ever reaches an employer. Verified, not claimed.

What I would really value from this community: does this match what you see when you hire? Where does the unverified-candidate problem hurt you most, screening time, bad hires, background-check cost, something else? And for those who have hired at scale, what actually gave you confidence in a candidate before you committed?

Something I have spent a lot of time on lately, sharing here for feedback from other founders who hire.

Post one role and you get hundreds of applications. Inflated resumes, borrowed experience letters, skills listed that nobody can actually back up, and now a wave of AI-written profiles on top. There is no fast, reliable way to tell who can really do the work versus who just wrote that they can. So it becomes hours of screening calls that go nowhere, or hiring on gut and a familiar company name on the resume, and sometimes finding out months later that half the resume was fiction.

The core issue is that hiring still runs on self-declared claims. The burden of proof sits on the employer, one interview at a time, and background checks catch it too late and cost too much.

So I have been building toward a different model, where a candidate's skills, work history and projects come backed by real records and approved evidence instead of self-declaration, so the claims are verified before a profile ever reaches an employer. Verified, not claimed.

What I would really value from this community: does this match what you see when you hire? Where does the unverified-candidate problem hurt you most, screening time, bad hires, background-check cost, something else? And for those who have hired at scale, what actually gave you confidence in a candidate before you committed?

The most expensive mistake Indian freshers make is accepting the first number a company gives them without saying anything. Not because they're greedy but because nobody ever taught them that the first offer is almost never the final offer.

Here's what actually happens on the other side of that table.

Most companies budget a range for every role. If the range is 6 to 9 LPA they will open at 6. Not because you deserve 6 but because that's how negotiation works. If you say nothing they pay 6. If you push back professionally they move. It's that straightforward.

The reason freshers don't push back is because they're scared of losing the offer. In reality companies almost never withdraw offers because a candidate negotiated. What they're actually thinking when you negotiate is that this person knows their worth, which is a green flag not a red one.

The script that works is simple. After receiving an offer say something like "Thank you so much, I'm genuinely excited about this role. Based on my research and the skills I'm bringing I was expecting something closer to X. Is there any flexibility there?" That's it. No aggression, no ultimatums. Just a calm ask. The worst they can say is no and you're back to exactly where you started.

A few things that help your position before negotiating: have at least one other offer or interview in progress, know the market rate for the role on Glassdoor and AmbitionBox, and never give your salary expectation first if you can avoid it.

The Indian job market is hard enough without leaving money on the table because nobody told you this was allowed.

What's the best or worst negotiation experience you've had?

Over the last several months I have been collecting and analysing job rejection stories from Indian graduates across engineering, commerce, and management.

200+ stories. Different colleges. Different cities. Different roles.

The pattern that emerged was not what I expected.

Almost none of them were failing because they lacked skills.

Here is what was actually happening.

---

**PATTERN 1: The vocabulary problem**

This one shocked me the most.

The same skill described with different words gets completely different outcomes.

"Cross-functional collaboration" and "stakeholder management" are the same skill.

But ATS software — the applicant tracking system that screens your resume before any human reads it — does not know that. It counts text strings. Not meaning.

So a candidate who wrote "cross-functional collaboration" on their resume for a role that said "stakeholder management" in the JD got filtered out automatically. The hiring manager never saw their name.

This was happening across almost every rejection story I looked at.

**The fix:** Read the job description carefully. Find every phrase that appears more than once. Use those exact words in your resume. Not synonyms. The exact words.

---

**PATTERN 2: One resume for every job**

75% of resumes are filtered by ATS before a human reads them. *(Source: LinkedIn Talent Insights 2024)*

ATS scores your resume against the specific job description you are applying to. A generic resume scores low for every single role.

Most candidates I spoke to were sending the same PDF to 50 to 100 companies. Each application scored low. Each one got filtered. None of them got a callback.

The same candidate with a tailored resume for each role would have cleared ATS and reached a human recruiter significantly more often.

The problem is not their qualification. It is the infrastructure they are using to apply.

---

**PATTERN 3: Responsibilities not results**

"Managed a team of 5."

Every manager writes this. It means nothing to a recruiter reading application number 247.

"Led a team of 5 to deliver a product feature that increased retention by 32% in Q2, two weeks ahead of schedule."

This is a story. Stories get remembered. Claims get skipped.

Almost every resume I looked at was full of responsibilities. Almost none had results with numbers.

**The fix:** For every bullet point on your resume ask — what was the outcome and can I attach a number to it? There is almost always a number somewhere.

---

**PATTERN 4: Format that destroys ATS parsing**

Beautiful resumes. Invisible to software.

Tables, columns, graphics, icons, text boxes — ATS reads linearly. When it hits a table or a two-column layout it scrambles the text completely.

The candidates using Canva templates, designed CVs, or two-column formats were getting filtered at a dramatically higher rate.

Plain text. Single column. No graphics. No icons. This is what passes ATS every time.

It looks less impressive to the human eye. It gets through every time.

---

**PATTERN 5: Applying broadly instead of precisely**

200 applications. 198 silences.

This was the most common situation I heard. And almost every time the candidate was applying to roles with wildly different requirements using the same resume.

20 well-matched, vocabulary-aligned, tailored applications outperform 200 generic ones every single time.

The job search is not a numbers game. It is a quality per application game.

---

**Run your resume against these 5 right now:**

1. Are you using the exact vocabulary from the JD or your own words?

2. Are you tailoring your resume for each specific role?

3. Does every bullet have a result with a number attached?

4. Is your resume plain text, single column, no graphics?

5. Are you applying to roles that genuinely match your background?

If any of these is a no, that is where your callbacks are going.

Happy to answer any questions in the comments. This took a while to put together so I hope it helps someone.

Over the past few months I've been obsessively reading through rejection stories from Indian candidates. Not just scrolling actually noting down what went wrong and where.

Here's what I found.

The problem is almost never the candidate.

1. The ATS Black Hole - Most applications die before a human sees them. ATS systems filter resumes by exact keyword matching not skills, not potential, not experience. A candidate with 5 years of relevant work gets rejected because they wrote "led a team" instead of "team leadership." That's it.

2. The One CV Mistake - The single most common pattern: sending the same resume to 100 different jobs. Every job description is slightly different. Every ATS is calibrated differently. One resume cannot win everywhere. The candidates who get callbacks are spending 20 minutes tailoring each application - not blasting the same PDF everywhere.

3. The Interview Breakdown - For people who do get interviews, rejections cluster around one thing: vague answers. "I'm a hard worker" kills more offers than anything else. Interviewers are trained to probe for specifics. Candidates who answer with numbers, situations, and outcomes move forward. Candidates who answer with adjectives don't.

4. The Silence Trap - Most Indian candidates apply and wait. The ones who get hired apply AND follow up on LinkedIn within 48 hours. A short, direct message to the hiring manager - not HR - after applying increases response rates significantly. Most candidates never do this because it feels awkward. That awkwardness is your competitive advantage.

5. The Confidence Drain is Real - After 50+ rejections with zero feedback, candidates start applying for roles below their level, accepting worse terms, and second-guessing skills they actually have. The system produces this outcome deliberately - it's not your failure, it's a design flaw.

The job market in India right now is genuinely hard. But most of the rejections I read were fixable not fundamental. Happy to answer questions or go deeper on any of these points.

What's the biggest wall you've hit in your search?