Why Your Resume Is Not Getting Shortlisted, and How to Fix It

Strong grades, no shortlist

A student in the final year of a master's in computing reached out asking for mentorship. Their grades were excellent, top of the classification scale. Their goal was clear: a role at one of the big tech companies. And their challenge, in their own words, was simple and painful: "Can't get resume shortlisted."

I hear some version of this every week. From graduates with high CGPAs, from developers with a year or three of experience, from people who relocated to a new country and suddenly hear nothing back. The common thread is confusion. They know they are capable, yet the applications disappear into silence, and they cannot tell whether the problem is the resume, their skills, or the market.

So let me explain how screening actually works, why strong candidates get filtered, and exactly what to change.

My honest read

Grades get you into consideration for some graduate programmes. They almost never get you shortlisted on their own. For software roles, a resume is judged on one question: does this person look like they can already do a version of this job?

A first class degree says you are good at learning. A resume that gets shortlisted says you have built things, solved real problems and made an impact. When a strong student is not getting shortlisted, the problem is rarely ability. It is almost always one of three things: the resume does not show evidence, it does not match the role, or it is only ever being sent through the most crowded channel.

How screening actually works

A human skims, fast

Recruiters handle large volumes, especially for well known companies. When the job site Ladders ran an eye tracking study with professional recruiters in 2018, the average initial screen lasted about 7.4 seconds. In that skim, eyes jump to titles, company or project names, dates, education and whatever stands out visually. Resumes with simple layouts and clear headings did better; cluttered layouts with multiple columns and long sentences did worse.

That means the first few lines of each section matter far more than the details at the bottom.

ATS: myth versus reality

You have probably seen the claim that "75 percent of resumes are rejected by ATS before a human sees them". That figure circulates widely without a credible source. When the resume company Enhancv asked 25 recruiters how their applicant tracking systems behave, the large majority said the system does not automatically reject resumes for formatting or keywords.

Here is what is closer to the truth:

The real enemy is volume. A popular role can attract hundreds or thousands of applicants within days. A recruiter searches, reviews the best matches, builds a shortlist, and stops. Your job is to be in that first cluster and to be obviously relevant within seconds.

Why strong students still get filtered

Generic bullets. "Worked on a web application using React and Node.js." This describes a technology, not a contribution. Every applicant has a line like this.

No impact. Nothing tells the reader what changed because of your work: faster, more users, fewer errors, less manual effort, a grade, a competition result.

Projects that look like tutorials. A weather app, a to do list, a clone following a popular video. These are fine for learning but signal "beginner" to a big tech recruiter. I often find another problem when I click through: the live demo is broken, the repository has node_modules committed, or the features described on the resume are not actually implemented. That mismatch hurts credibility more than having fewer projects.

Poor structure. Skills buried at the bottom, education in the wrong place, inconsistent dates and styling, two pages of dense text for a graduate.

Unclear visa or location signals. If you are an international student or recently relocated, recruiters may be unsure whether you can work there. If you have the right to work, say so plainly. If you will need sponsorship, target companies and programmes that sponsor, rather than hoping nobody asks.

Only applying cold. Sending the same resume through job portals for the most popular companies in the world is the most crowded channel there is.

Rewrite your bullets around evidence

A useful structure is the one Google's former head of people operations, Laszlo Bock, popularised: accomplished X, as measured by Y, by doing Z. You will not always have a number, but you can nearly always describe scope, scale or outcome.

Use numbers you can defend in an interview. If you do not have a real metric, describe scope honestly rather than inventing one. Interviewers will ask.

Make your projects prove depth

For big tech and product companies, one or two deep projects beat six shallow ones. A project that proves depth has:

• A real problem, ideally one you or someone you know actually had
• Non trivial engineering: authentication, data modelling, background jobs, caching, testing, deployment, or handling failure
• A live demo that works and a clean repository with a README explaining what it does, how to run it, and the decisions you made
• Consistency: every feature on the resume exists in the project

Each project entry on the resume should include one line on what it is, two or three bullets on what you built and why it was hard, and links to both the code and the live version. If you need inspiration for substantial ideas, the FYP ideas library has briefs scoped around real deliverables.

Structure: one page, in the right order

For a graduate or early career engineer, keep it to one page. A clean order that works:

1. Header: name, email, phone, LinkedIn, GitHub, portfolio. Use full, readable URLs or clear usernames rather than hidden hyperlinks.
2. Education: near the top when you are a recent graduate. Include the degree, institution, dates and classification if strong.
3. Technical skills: grouped as Languages, Frameworks and Libraries, Databases, Tools and Cloud. Keep it honest and relevant.
4. Experience: internships, part time roles, research, teaching assistant work.
5. Projects: your strongest two or three.
6. Achievements: competitions, publications, scholarships, open source contributions.

Small things that matter:

• Use one naming convention: React or React.js, not both
• Consistent date formats and heading styles throughout
• A single column, standard fonts, enough white space
• Export to PDF and check that the text can be selected and copied, which is a quick sign it will parse cleanly

Tailor for every role that matters

You do not need a new resume for every application, but you do need a version per role type: backend, frontend, full stack, data or machine learning. For each important application:

• Read the job description and highlight the skills and responsibilities mentioned repeatedly
• Make sure those words appear in your skills and bullets where they are genuinely true
• Reorder projects so the most relevant one is first
• Adjust the summary line if you have one, so it names the role

Align LinkedIn with your resume

Recruiters often check LinkedIn after the resume, and sometimes find you there first. Mismatches raise doubts: a role listed as an internship on LinkedIn but full time on the resume, different dates, or a company with no presence anywhere. Make them agree.

Then make LinkedIn work for you: a clear headline naming your target role and main skills, an About section with two or three short paragraphs, projects added with links, and a profile photo. I cover what actually helps in LinkedIn for Engineers: What Actually Works.

Referrals and warm outreach

For big tech, a referral does not guarantee an interview, but it usually gets your resume read by a human with more attention. Here is how to ask without being awkward.

Find people: alumni from your university working at the company, people from your programme who graduated earlier, speakers at meetups, and engineers who post about their work.

First message template:

Hi [name], I am a final year MSc computing student focusing on backend systems. I saw you work on [team or product] at [company] and read your post about [topic]. I am applying for the graduate software engineer role there and would really value ten minutes of your perspective on what the team looks for. Totally understand if you are busy.

After a conversation, or if they offer:

Thank you again for your time. If you are comfortable referring me for [role, job ID], here is my resume and a two line summary: [summary]. No pressure at all if not.

Keep it short, specific and respectful. Send five to ten of these a week rather than fifty identical ones.

Graduate programmes and internships at big tech

Large technology companies usually run structured early career hiring: internships, new graduate roles and sometimes apprenticeships or graduate schemes. A few general patterns are worth knowing, though you should always check each company's own careers page for the current cycle:

• Many companies open graduate and internship applications months before the start date, often in the autumn for roles starting the following year
• Popular programmes can close early once they have enough applicants, even if no deadline is listed
• Some roles are filled on a rolling basis, so applying early helps
• Student careers pages and university career services are the most reliable sources for exact dates

Set up job alerts on each target company's careers site, and keep a spreadsheet of openings, deadlines and contacts.

A four week fix plan

Then repeat weeks three and four continuously, and improve the resume whenever interviews reveal a gap.

A quick checklist before you send it

• One page, single column, readable fonts, consistent styling
• Education near the top, skills grouped and easy to find
• Every bullet shows what you did and what changed
• At least one project with real engineering depth
• All links work, demos load, repositories are clean
• Every claimed feature actually exists
• Keywords from the job description included where genuinely true
• LinkedIn matches the resume
• Work authorisation stated clearly if relevant
• Sent through a referral or warm contact wherever possible

If you remember one thing

A resume that gets shortlisted is not a list of what you studied. It is a short, evidence based argument that you can already do a version of the job, sent through a channel where a human will actually read it. Fix the evidence, fix the structure, and stop relying only on cold applications.

For more on the application side, read How to Apply for Software Engineering Jobs and A Job Search Is a Pipeline, Not a Performance.

Ask your own question

Resume shortlisting is one of the questions people ask me most, so I have collected the common ones, anonymised, with detailed answers in the career questions library.

If you want honest feedback on your profile and positioning for the roles you are targeting, you can book a free 1:1 session with me.

Student or want early access to the Sefism member area? Join the waitlist.

Stay in touch

• LinkedIn: where I post about careers, job searching and lessons from mentoring engineers.
• X (Twitter): short, daily notes on software engineering.
• Instagram: a more personal look at the work behind the posts.
• Topmate: book a free 1:1 session for career guidance on your situation.
• Sefism Discord: share your progress and get unstuck with other developers.
• Sefism YouTube: walkthroughs and talks on careers and engineering.

Cover photo by Resume Genius on Unsplash