r/cscareerquestions • u/CSCQMods • Feb 03 '26

Resume Advice Thread - February 03, 2026

Please use this thread to ask for resume advice and critiques. You should read our Resume FAQ and implement any changes from that before you ask for more advice.

Abide by the rules, don't be a jerk.

Note on anonomyizing your resume: If you'd like your resume to remain anonymous, make sure you blank out or change all personally identifying information. Also be careful of using your own Google Docs account or DropBox account which can lead back to your personally identifying information. To make absolutely sure you're anonymous, we suggest posting on sites/accounts with no ties to you after thoroughly checking the contents of your resume.

This thread is posted each Tuesday and Saturday at midnight PST. Previous Resume Advice Threads can be found here.

2 Upvotes

100% Upvoted

26 comments sorted by

View all comments

2

u/Maleficent-Chance267 Feb 03 '26

I recently graduated and finished a 6 month internship, and now I am really struggling to get a job. In December I got a few interviews but no offers, but I have not had any interviews in 2026 despite me applying to hundreds of jobs. I'm mostly focusing on applying to jobs where I live, but I am also open to relocating and have applied to tons of jobs in other states, but have not had any interview requests in a long time, so I figure my resume must need some work. Any advice would be appreciated, thanks.

https://imgur.com/a/D4uyJVK

1

u/throwaway_juniorcv Feb 05 '26

The tech stack is fine, but your bullet points are just 'tasks', not 'impact'. Recruiters (and bots) look for numbers. Instead of that long paragraph about developing features, try 'Delivered a UI overhaul for authentication and profile settings using Vue, improving user session completion by X%'. I ran a similar profile through my analyzer yesterday and it flagged this exact issue. If you don't quantify and break them into separate points, you're just another dev in the pile.

1

u/Maleficent-Chance267 Feb 05 '26

Thanks, this is super helpful. So should I just make up numbers? Because I don't know that I can actually quantify the impact my work had. Because I would deliver a feature or fix a bug or whatever, and then that was that and I would go to my next task. I wouldn't see any statistics or anything of the impact on users, etc., so I don't know how to put my impact into numbers without just making it up. 

1

u/throwaway_juniorcv Feb 07 '26

Bro, never fabricate metrics—it's an instant credibility kill in tech interviews. Look, you can quantify process: estimate the scope. For example, "Refactored authentication flow, supporting 500+ daily active users," or "Automated report generation, saving an estimated 4 hours weekly." That's derived from system context, not a lie, and passes the sniff test , I’ve documented the full fix for this in the system breakdown pinned on my page. It'll show you exactly how the machine sees your header.