DEV Community

Anushka Shinde
Anushka Shinde

Posted on

How I Built a Resume That Actually Gets Shortlisted - The Honest Messy Journey

My First Resume Was Embarrassing

I'll be honest.

My first resume was someone else's resume with my name on it.

I found a template on Overleaf.
Replaced the person's name with mine.Added my basic education details.Added some skills I barely knew.No projects. No certifications. No experience. Nothing real.

That was it.That was my first resume.

And I sent it out thinking it was fine.

How It Started Getting Better

I made a LinkedIn account.

And suddenly I was seeing resumes
that made mine look like a rough draft.

People were talking about ATS scores. About what Google prefers .What Microsoft looks for.
What gets shortlisted vs what gets ignored.

I started paying attention.

And slowly one project at a time,
one certificate at a time,one skill at a time my resume started filling up with real things.

Not borrowed things.
Mine.

The Fake Instagram Account Nobody Knows About

Okay. Here's something I've never told anyone.

I made a fake Instagram account.

Not for anything weird.To follow tech people without mixing it
with my personal life.

Recruiters who had hired people.
Developers who worked at big companies.Career coaches who guided freshers for free.

I used to comment on their posts.
Ask questions. Take notes.Learn from people who had actually
been on the other side of hiring.

One day a woman caught me.She noticed my Instagram ID and my resume didn't match at all.

I was honest with her.She was completely fine with it.

And she guided me more than
any YouTube tutorial ever did.

Here's what I learned from that experience

Tech people who have established careers genuinely want freshers to succeed.They are not trying to pull you down.They share knowledge freely because someone once helped them too.

Don't be afraid to reach out.
Even with a fake account. 😅

What I Actually Did to Build My Resume

Step 1 - I built things first
You cannot have a good resume
with nothing to put in it.

I built 8 to 9 projects over time.Then I selected the best 4 to showcase.Not all of them. The ones that told the strongest story.

Step 2- I was ruthless with certifications
I had 10 to 15 certifications.
I asked Claude and ChatGPT "Out of these, which ones actually
matter to recruiters right now?"

Both gave similar answers.I kept only those.The rest dropped.

No point cluttering your resume
with certifications nobody recognizes.

Step 3 — I only added skills I could answer for
This was the most important rule.

I took ChatGPT's suggestions to Claude.Took Claude's suggestions back to ChatGPT.Cross referenced both.

And then added only the skills
I could genuinely answer questions about in an interview.

Because a skill on your resume
is an invitation for the interviewer to ask you about it.

Don't invite questions you can't answer.

Step 4 — I humanized everything
AI suggestions are a starting point.Not the final version.

Everything AI helped me write I rewrote in my own words.My own tone. My own voice.Something that sounded like me not like a template.

Step 5 — I showed it to real people
My brother. LinkedIn connections.
Instagram recruiters. College workshops.

Every set of eyes caught something the previous ones missed.

The Moment I Knew I Was on the Right Track

My college had a CV writing workshop.

I saw BTech students' resumes.
Computer engineering students' resumes.

And I realized my resume was actually better.

Not because I'm smarter.Because I had been learning from the updated world not waiting for someone to make a YouTube video about it.

I talked to real recruiters.Real developers. Real people.And I kept updating. Keep improving.

What Your Resume Actually Is

Your resume is not a document.

It is evidence.

Evidence that you built real things.Evidence that you learned real skills.Evidence that you are worth 30 minutes of someone's time.

A weak resume doesn't mean you're a weak developer.It means your evidence isn't showing yet.

Start building the evidence.
Then let your resume tell that story.

What I'd Tell My Past Self

  • Start with any template. Just start.
  • Build projects even when nobody asks you to.
  • Add only what you can defend in an interview.
  • Ask real people not just AI, not just YouTube.
  • Update it every single semester.
  • Compare it to others not to feel bad but to know where to improve.
  • Your resume will never be perfect .But it can always be better than yesterday.

Final Thought

I went from copying someone else's name off an Overleaf template to having a resume that got shortlisted when better coders didn't.

Not because I'm the most talented person in the room.

Because I treated my resume like a project.I iterated. I improved. I asked for help.I kept building the evidence.

That's all it takes. 😊


What's the biggest resume mistake
you made as a fresher?

Drop it below 👇
Let's help each other avoid the same ones!

Top comments (0)