DEV Community: Mahesh

I Thought Applying to More Jobs Was the Solution. I Was Wrong.

Mahesh — Tue, 12 May 2026 22:42:51 +0000

A few months ago, one of my friends showed me a spreadsheet where he tracked all his job applications.

There were over 150 entries.

The strange part was that the problem wasn’t effort.

He was applying consistently.
He had decent projects.
He practiced DSA regularly.
He even had internship experience.

But the response rate was terrible.

Most applications ended in:

no response
rejection
application viewed but ignored

At first, we blamed the market.

Then competition.

Then bad luck.

But after reviewing his resume carefully, I realized something important:

The issue wasn’t necessarily his skills.

The issue was that his resume wasn’t communicating those skills properly.

And honestly, once I started looking deeper into resumes and hiring systems, I realized this problem is extremely common.

The part most people underestimate

A lot of people still imagine hiring as:

recruiter opens resume
recruiter reads carefully
recruiter decides

But modern hiring usually doesn’t work like that anymore.

In many companies, resumes go through ATS systems before a recruiter ever sees them.

ATS (Applicant Tracking Systems) are basically filtering systems that scan resumes for:

keywords
role relevance
formatting
skills
experience alignment

If the resume performs poorly during that stage, it may never reach a human reviewer.

That realization completely changed how I looked at resumes.

Because suddenly, a lot of confusing things started making sense.

Why some skilled people struggle to get interviews.
Why generic resumes often fail.
Why visually attractive resumes sometimes perform badly.

The “same resume everywhere” problem

One of the biggest mistakes I kept noticing was this:

People send the exact same resume to every company.

Honestly, this includes me too at one point.

It feels efficient because rewriting resumes repeatedly is exhausting.

But companies are searching for very specific signals.

A frontend-focused role might prioritize:

React
UI architecture
accessibility
performance optimization

A backend-focused role might prioritize:

APIs
databases
scalability
distributed systems

If your resume stays too generic, important signals become weak.

For example:

A job description says:

Node.js
MongoDB
REST APIs
Redis

Your resume says:

Built backend systems

Technically true.
But weak.

The ATS and recruiter don’t automatically assume all the underlying details.

Once I started tailoring resumes more carefully based on the role, the difference became noticeable.

Not instantly.
But definitely noticeable.

Weak bullet points silently destroy resumes

This is another issue I kept seeing repeatedly.

A lot of resumes describe work without describing impact.

For example:

Worked on authentication module

This tells almost nothing.

Now compare it with:

Built JWT-based authentication system supporting 4,000+ users and improved login reliability

Suddenly:

ownership feels clearer
scale becomes visible
impact becomes measurable

The work feels real.

And recruiters skim resumes extremely fast.

If nothing stands out immediately, they move on.

One thing I realized while reviewing resumes is that measurable outcomes create credibility instantly.

Even small numbers help:

reduced load time by 20%
improved response speed
handled 5k+ requests/day
increased engagement
automated manual workflows

Without impact, many resumes feel generic even when the work itself was good.

Fancy templates are often harmful

This surprised me more than anything else.

Some of the worst-performing resumes I tested were visually beautiful.

Clean colors.
Fancy icons.
Complex layouts.
Canva templates.

To humans, they looked modern.

To ATS systems, many of them looked confusing.

I tested resumes where:

skills sections disappeared
experience blocks broke
keywords were skipped entirely
formatting collapsed during parsing

That means applicants were unknowingly damaging their own visibility.

After seeing this repeatedly, I started preferring simpler resume structures much more.

Not because simple resumes look prettier.

Because they communicate more reliably.

Another thing people ignore: clarity

Sometimes resumes contain too much information without clarity.

Especially skills sections.

I’ve seen resumes listing:

25 frameworks
15 databases
multiple languages
cloud platforms
AI tools
design tools

all together.

The result?
Nothing stands out.

A focused resume often performs better than an overloaded one.

Recruiters usually want clear signals:
“What is this person actually strong at?”

Not:
“This person has touched everything once.”

Why I started building FitCheck

After repeatedly reviewing resumes and experimenting with ATS-style analysis, I realized how repetitive the process was becoming.

Every application involved:

checking ATS compatibility
matching job descriptions
rewriting bullet points
improving wording
identifying missing keywords

So I started building a tool mainly for myself.

That eventually became FitCheck [https://fit-check.in].

The original goal was very simple:

Help people understand why resumes get ignored.

Over time I started expanding it into:

ATS analysis
resume vs job description matching
cover letter generation
study plan generation
interview preparation workflows

Because honestly, resumes are only one part of the process.

Getting shortlisted is one challenge.
Clearing interviews is another.

The biggest thing I learned

The most surprising realization for me was this:

A lot of talented people are bad at presenting themselves on paper.

Not because they are incapable.

But because nobody really teaches resume communication properly.

Most people learn through:

trial and error
random online advice
copying templates

And modern hiring systems are far more structured than most people realize.

Small improvements in:

clarity
impact
formatting
alignment

can completely change how a resume performs.

Final thoughts

If you’re applying to jobs and hearing nothing back, don’t immediately assume you’re underqualified.

Sometimes the issue is:

weak presentation
ATS incompatibility
generic descriptions
poor role alignment

And the frustrating part is that many people never realize this.

They just keep applying more.

Honestly, I used to think volume was the answer too.

Now I think quality and alignment matter much more.

While building FitCheck and learning more about hiring workflows, that’s probably the biggest lesson I’ve taken away from all of this.

How I Realized Most Resume Rejections Happen Before a Recruiter Even Sees Your Resume

Mahesh — Fri, 08 May 2026 04:50:44 +0000

A few months ago, one of my friends showed me his job application tracker.

It had around 120 applications.

The painful part wasn’t the number.

It was the response column.

Almost every entry said the same thing:

No response
Rejected
Application not selected

At first, we blamed the market.
Then competition.
Then luck.

But after reviewing his resume carefully, I realized something that completely changed the way I looked at job applications.

The resume wasn’t bad.

It was just invisible.

The problem most people don’t notice

A lot of people think resumes are rejected by recruiters.

In reality, many resumes never even reach a recruiter.

Before a human sees your application, it usually goes through an ATS (Applicant Tracking System).

The ATS scans your resume and checks things like:

Keywords
Skills
Formatting
Experience relevance
Alignment with the job description

If your resume doesn’t match well enough, it can get filtered automatically.

That means even qualified candidates sometimes get rejected before anyone actually reads their resume.

Once I understood this, a lot of things suddenly started making sense.

The “same resume everywhere” mistake

One of the biggest mistakes I see people make is sending the exact same resume to every company.

It feels efficient.

But it usually reduces your chances.

Let’s say a company is looking for:

React
REST APIs
MongoDB
Performance optimization

And your resume says:

Frontend development
Backend systems
Full-stack projects

Even if you’ve done all the required work, the ATS may not understand the connection clearly.

This is why job description alignment matters so much.

A lot of people have the right skills.
They just don’t present them in a way the system understands.

Another issue: weak bullet points

I used to write resume points like this:

Worked on a web application using React and Node.js

Technically true.

But completely forgettable.

Now compare it with:

Built a MERN application used by 5,000+ users and reduced page load time by 38%

Same project.
Same work.
Completely different impact.

Numbers instantly make work feel more real.

Recruiters skim resumes quickly.
If nothing stands out, they move on.

Formatting can silently hurt your resume

This surprised me the most.

Some resumes looked visually amazing.
But when tested through ATS systems:

Sections were skipped
Skills were not detected
Bullet points broke
Entire experience blocks disappeared

Most of the issues came from:

Tables
Multi-column layouts
Fancy templates
Icons
Complex formatting

A resume can look impressive to humans but still fail automated screening.

That’s why simple formatting usually works better.

What started working better for me

Instead of mass applying, I started changing my process.

Before applying, I now:

Read the job description carefully
Match important keywords naturally
Rewrite weak bullet points
Check if the resume is ATS-friendly
Tailor projects based on the role

It takes more effort.

But the quality of applications becomes much better.

And honestly, it feels more productive than sending 50 random applications.

Why I ended up building FitCheck

After repeating this process again and again, I realized how manual and repetitive it was becoming.

So I started building a tool for myself.

That tool slowly became FitCheck.

The idea was simple:

Help people understand:

Why their resume gets rejected
How well it matches a job description
Which keywords are missing
How to improve bullet points
How to generate better cover letters

I also started adding study plans and interview-related features because resume optimization alone isn’t enough.

A good resume might get you shortlisted.
But preparation is what helps you clear interviews.

Something I learned while building this

A lot of people applying for jobs are actually skilled.

The issue usually isn’t intelligence.

It’s communication.

Your resume is basically a compressed version of your work.

If it doesn’t clearly communicate your impact, systems and recruiters may never realize what you’re capable of.

That realization changed the way I approach applications.

Final thoughts

If you’re applying to jobs and not getting responses, don’t immediately assume you’re underqualified.

Sometimes the issue is:

Resume structure
ATS compatibility
Weak presentation
Poor alignment with the role

Small improvements in those areas can completely change outcomes.

And honestly, most people never get told that.

If you’re curious, you can try FitCheck here:

https://fit-check.in

It’s still evolving, but it already helps with:

ATS analysis
Resume vs Job Description matching
Cover letter generation
Study plan generation
Interview preparation workflows

I’m continuously improving it based on real feedback and real resume problems people face.

I Stopped Applying to 100 Jobs… and Things Started Changing

Mahesh — Tue, 05 May 2026 18:25:57 +0000

A few months ago, I was doing what most people do.

Open LinkedIn → search jobs → apply.

Repeat.

Some days I would apply to 20–30 jobs.

And at the end of the week?

Nothing.

No replies. No interviews. Just silence.

The part that frustrated me the most

It wasn’t just the rejections.

It was not knowing why.

Was my resume bad?
Was I applying to the wrong roles?
Was the market just bad?

When you don’t get feedback, you start guessing.

And most of the time, you guess wrong.

What I changed

At some point, I stopped.

Not completely — but I stopped applying blindly.

Instead of focusing on quantity, I tried something different:

I read the job description properly
I compared it with my resume
I noticed what was missing
I tweaked my resume for that specific role

It felt slower.

Almost like I was doing less work.

But something interesting happened.

The shift

I didn’t suddenly start getting 10 interviews.

But I started getting responses.

Even small things like:

“We’ll review your profile”
“Shortlisted for next round”

These didn’t happen before.

That’s when I realized:

It’s not about how many jobs you apply to.
It’s about how relevant your application is.

What most people (including me) get wrong

We treat job applications like a numbers game.

Apply more → get more chances.

But the system doesn’t work like that.

Every job has its own requirements.

And if your resume doesn’t reflect those requirements clearly, you’re invisible.

The small things that made a big difference

These are not complicated, but they matter:

1. Matching keywords

If the job says:
Node.js, REST APIs, MongoDB

Your resume should say the same.

Not:
“Backend development”

2. Rewriting bullet points

Instead of:
“Worked on a project”

I started writing:
“Built a MERN application serving 3,000+ users and reduced API response time by 35%”

3. Removing unnecessary stuff

I had things in my resume that weren’t helping.

Once I removed them, the resume became more focused.

Why I’m sharing this

Because I wish someone had told me this earlier.

Applying more doesn’t fix the problem.

Alignment does.

What I’m doing now

After repeating this process multiple times, I realized how time-consuming it is.

So I started building something for myself to speed it up:

Check how well a resume matches a job description
Highlight missing keywords
Suggest improvements

I’ve been using it personally, and it has helped me stay consistent.

If you want to try it:
👉 https://fit-check.in

Final thought

If you’re applying to a lot of jobs and not hearing back, don’t just increase the number.

Pause.

Look at what you’re sending.

And ask:

“Does this actually match what the job is asking for?”

That question alone can change everything.

Why You’re Not Getting Interviews Even After Applying to 100+ Jobs

Mahesh — Mon, 04 May 2026 15:04:03 +0000

I kept noticing the same pattern everywhere.

People applying to 50, 100, even 200 jobs… and getting nothing back.

No interview calls. No responses. Just silence.

At first, I thought it was just the job market.

But after going through a lot of resumes (friends, classmates, people online), I realized something:

Most resumes don’t even reach a human.

The part no one talks about

Before a recruiter sees your resume, it usually goes through an ATS (Applicant Tracking System).

This system filters resumes based on how well they match the job description.

If your resume doesn’t match → it gets rejected automatically.

The biggest mistake

Sending the same resume everywhere.

Example:

Job description:

Node.js
REST APIs
MongoDB

Your resume:

Backend development
Built scalable systems

Even if you’ve done the work, the ATS might not recognize it.

Weak bullet points = missed opportunity

A lot of resumes say:

“Worked on a web app”

Instead of:

“Developed a MERN application serving 5,000+ users and improved performance by 40%”

Same work. Different impact.

Formatting issues

Things like:

Tables
Fancy templates
Complex layouts

can break ATS parsing.

What actually works

From what I’ve seen, these make the biggest difference:

Matching resume with job description
Using relevant keywords
Writing measurable achievements
Keeping formatting simple

What I started doing

Instead of blindly applying, I started:

Tweaking my resume for each job
Checking keyword alignment
Improving bullet points

It’s slower, but way more effective.

Why I built something for this

After doing this repeatedly, it became time-consuming.

So I built a tool for myself that:

Checks ATS compatibility
Matches resume with job description
Highlights missing keywords
Helps improve bullet points & cover letters

If you want to try it:

👉 https://fit-check.in

Final thought

If you’re applying a lot and not getting responses, don’t just apply more.

Fix alignment.

That’s where the real difference is.