You've applied to a hundred jobs. You've heard back from three. You start wondering if your projects are bad, your grades weren't good enough, or you're just not cut out for this.
Before you spiral, consider a less personal explanation: your resume might never have reached a human being at all.
1. Meet the Gatekeeper Nobody Warned You About
Most companies, especially bigger ones, don't have a person reading every resume that comes in. They use software called an applicant tracking system, or ATS, that scans, sorts, and often filters resumes automatically before a recruiter ever opens one.
Think of it like airport security. The scanner doesn't care whether you're a good person. It just checks whether your bag's shape matches something it's been trained to flag. Pack it wrong, even with nothing actually dangerous inside, and you get pulled aside anyway. Pack it in a way the scanner understands, and you walk straight through.
Your resume needs to pass the scanner before a recruiter ever gets to judge the person behind it.
2. What the Scanner Actually Checks
Different systems work differently, but most look for a combination of:
- Keywords that match the job description
- Standard section headings, like "Experience," "Education," and "Skills"
- Simple, parseable formatting it can read correctly
- Relevant experience and skills lined up against what the role asks for
It's not trying to be unfair. It's trying to handle hundreds of applications a recruiter simply doesn't have time to read one by one. Your job is to make sure your resume is easy for it, and them, to understand.
3. Formatting Mistakes That Quietly Sink You
Some resume choices look great to a human eye and confuse the system reading it first. Avoid:
- Text inside images, headers, or footers. Many systems can't read these at all.
- Tables and multi-column layouts. They often get scrambled when the system extracts the text.
- Unusual fonts and heavy graphics. Simple and readable beats stylish and unreadable.
- Skills hidden inside a fancy graphic like a skill wheel or bar chart. If it's not plain text, it might not be read.
- Uncommon file formats. Stick to a standard PDF or Word document unless told otherwise, and check that your PDF has selectable, copyable text rather than being a scanned image.
A simple rule: if you can't select and copy the text with your mouse, it's not being read reliably either.
4. Speak the Job Description's Language
This is the single biggest lever you have, and it takes ten extra minutes per application.
Read the job posting closely and notice the exact words it uses. If it says "REST APIs," write "REST APIs," not "web services." If it lists "React," don't only write "frontend frameworks." Systems and recruiters both often search for exact terms, not synonyms.
A simple process:
- Paste the job description into a document
- Highlight the specific skills, tools, and phrases it repeats
- Check which ones genuinely apply to you
- Weave the real ones naturally into your resume, in your actual experience, not as a hidden list
Never claim a skill you don't have just to match a keyword. That backfires hard the moment an interviewer asks a follow-up question.
5. Structure Your Resume the Boring, Reliable Way
Creativity in resume layout usually hurts more than it helps at the filtering stage. Use this structure:
- Contact information at the top: name, email, phone, LinkedIn, GitHub, portfolio
- Summary, two or three lines about who you are and what you're looking for
- Skills, a clear plain-text list
- Experience, including internships, freelance work, and significant projects
- Projects, especially for students without much formal work history
- Education
Use standard headings. "Experience" beats "My Journey." "Skills" beats "What I Bring to the Table." It might feel less creative. It gets read.
6. Write Bullet Points That Actually Say Something
Weak bullet points describe a task. Strong ones show a result.
Weak: "Worked on the login page."
Better: "Built a login page with form validation and error handling, reducing failed sign-up attempts."
Weak: "Used Python for a project."
Better: "Built a Python script that automated a manual weekly report, cutting the process from an hour to under five minutes."
A useful shape: what you did, how you did it, and what changed because of it. Numbers help wherever you honestly have them, but a clear result without a number is still far better than a vague task description.
7. What to Do With No Formal Job Experience
If you're a student, this is probably your biggest worry. It's genuinely fine. Treat these as real experience, because they are:
- Personal and academic projects, especially ones that are finished and deployed
- Freelance work, even one small paid project
- Open-source contributions, including a single merged pull request
- Club or organizational roles, like leading a team or running an event
- Hackathons, which show you can build under pressure
Describe them the same way you'd describe a job: what you built, what tools you used, and what the result was.
8. One Resume Does Not Fit All Jobs
Sending the identical resume to fifty different roles is a common reason for silence. A resume tuned to each posting, even with small changes, performs much better.
You don't need to rewrite everything each time. Keep a master resume with every project, skill, and experience you might ever mention. For each application, copy it and trim it down to what's actually relevant to that specific role, then match the language to that job description.
9. Getting Past the Filter Is Only Step One
Passing the system gets your resume in front of a human. From there, different things matter:
- Clarity over cleverness. A recruiter skims for seconds, not minutes.
- No spelling or grammar mistakes. They're an easy, unforced reason to reject someone.
- A resume that fits on one page as a student, unless you have a genuinely strong reason to go longer.
- A working portfolio and GitHub link, since a recruiter interested in a project will actually click through.
- Consistency with your LinkedIn. Mismatched dates and titles raise unnecessary questions.
10. Using AI to Help, Without Losing Yourself
AI tools can be genuinely useful here: checking grammar, suggesting stronger verbs, or comparing your resume against a job description to spot missing keywords. Use it that way.
Don't let it invent achievements you didn't have or write your whole resume in a generic voice that sounds like everyone else's AI-written resume. Recruiters see a lot of resumes now, and a bland, overly polished one that says nothing specific about you stands out for the wrong reasons.
11. A Quick Self-Check
Before you submit, ask:
- Would this pass if I copy-pasted the whole document into a plain text file? Does it still make sense?
- Does it use the same words as the job posting, honestly?
- Does every bullet point show a result, not just a task?
- Is the formatting simple enough that nothing could get scrambled?
- Have I proofread it, out loud, at least once?
12. Mistakes to Stop Making Today
- One generic resume for every job. Tailor it, even lightly.
- Fancy templates with graphics and columns. Simple wins here.
- Vague bullet points with no result. "Helped with a project" tells nobody anything.
- Keyword stuffing that doesn't reflect reality. It gets caught in the interview.
- Ignoring the job description entirely. It's the closest thing you have to an answer key.
- Typos. Read it backward, sentence by sentence, if you have to. It catches things your eyes glide past.
Fix One Application Tonight
Pick one job posting you actually want. Read it slowly, highlight its real requirements, and rebuild your resume around that specific role using everything above.
One tailored application beats ten generic ones sent into the void.
Let's Connect
I'm Prayush Adhikari, currently grinding through computer engineering, leading an IT club, and building my own company on the side. I write about Linux, productivity, and the honest side of being a developer.
Tell me in the comments if this changes how you write your next application. I'd like to know how it goes.
- LinkedIn: linkedin.com/in/adhikareeprayush
- GitHub: github.com/adhikareeprayush
- Portfolio: prayushadhikari.com.np
What should I write next: a month-by-month plan for your last year before graduating, or how to answer "tell me about yourself" without freezing up?
Top comments (0)