Ask HN: 10 years experience, 200 resumes, almost zero responses. Do I give up?

Okay, thanks for taking a look. I'll send it tonight when I get home.

Mostly C# web development. I've done some Xamarin too but I prefer web development. I live in Cincinnati. I've done very little hackerrank stuff because nobody here seems to care about it.

He will probably be better off in https://old.reddit.com/r/experienceddevs

Hi there,

You're correct to make a note as to why one of your last jobs lasted a few months. However, it might be better to say "Unfortunately this company went out of business". That's all someone screening your resume needs to know for now.

When you mention "mismanaged" it could be misconstrued that you're kissing and telling, and companies interested in reputation-management may pass you by.

The tech breakdown of each role is good, but maybe in delivering the features you talked about you ended up working with a Product/Design/QA department? Worth calling out if so, shows you can work productively with others.

Personally I'd skip the video intro, but that's a personal preference.

I linked this to a manager friend in SF:

> DeVry (for-profit school drowning in legal issues w/r/t quality and fraud) + non-CS "IT?" degree -- a public state uni would rate higher in general

> probably can drop the helpdesk job, it's a decade ago and has no bearing on CS/SWE/SDE

> can rephrase certain terms like "Used browserstack to check CSS." => "Cross browser + platform testing of CSS and responsiveness with Browserstack"

> seeing requirejs as a skill is very odd. I would not say good or bad, but just "odd", like it feels as if they are just looking for more things to list unnecessarily; in this regard you would want "webpack" or "rollup" in 2013-2014+ as a replacement

> drop the video resume, especially if the majority of it contains pauses and fillers like "uhh, um"

> for the automation developer role, I would be more interested in what CI/CD systems you were using rather than "multiple build steps" - were you running automated browser e2e in gitlab ci?

> your font wildly changes on the helpdesk job - missed copy/paste?

The skills section seems poorly laid out, lots of old tech, no .net core. If you've not used .net core, go through the few hours of basic tutorials so you can at least answer basic questions about the differences and then add it any way. It's basically the same stuff you've already been doing.

The logical order of your skills makes no sense, why mention patterns like MVVM? Valuable skills such as React should be near the front, not the rear.

Try a skill matrix in a table, a bit like this (but better, I'm typing this on a mobile):

    C#, .Net, .Net Core. 7 years
    JavaScript (inc. React, Knockout, jQuery)  6 years
    SQL, EF   8 years
    Node.js   3 years
    SQL Lite  2 years

Drop all the unimpressive noise like MVVM, REST, IIS. Or add them at the bottom of the skills matrix in a catch-all other skills category. Might be worth it just to catch the right buzzword.

None of the jobs list the tech used or what you actually did, so it's not clear you have actual experience programming. Some of them make you sound like you are an amateur (and I stress sound, not saying you are):

Repaired and upgraded first-tier applications

Collaborated on agile team to successfully add features to the company's website

That's all you've said about several years worth of work. Nothing you've built, nothing you achieved. What features. What did you upgrade. What test beds did you implement as the automation tester?

Those are just general, extremely fuzzy, descriptions. You mention tutoring and teaching so much too, it sounds odd, especially because you're listing so little actual work. Also, you focus on some odd things. Used browserstack to check CSS. How is that relevant on a CV?

Have you tried something more descriptive, like:

Random Company LLC - Senior Software Developer

Working on our internal monitoring tools written in ASP.Net MVC with EF and SQL. Features implemented included:

- Built a BI performance tool allowing management at-a-glance overview of client-facing systems

- Built a quick report tool, allowing team members to add simple SQL files and have them automatically turned into a sortable table with CSV download

- Overhauled performance for 3 key pages struggling with large datasets, reducing avg TTFB times for pages with more than 1000 records from 15 secs to 0.5 seconds

- Part of the team responsible for migrating, championing and training the migration of SVN to git

- Regularly maintained a top 3 bug fix rate within the team

- Mentored the 2 junior developers on the team

That makes it clear the tech, shows what kind of programming you were doing, and still makes it clear you did some mentoring.

With the gaps you have I'd also be tempted to drop the months part of each date, just list 2018-2020. Not 100% on this, maybe some recruiters could explain whether this looks dodgy or not.

Including a video resume seems like a bad idea. Remember, the purpose of a resume is to get a face-to-face interview (or COVID-19 equivalent). Your video, IMHO, only allows people to form superficial opinions about you without the time commitment or interaction of an interview. They can think "That guy seems hesitant/cocky or older/younger than I expected" and form judgements without any chance for you to react and prove otherwise. I've interviewed plenty of developers who come off unsure of themselves or full of themselves at first impression until you probe them a bit. You're letting people stereotype you (with whatever personal biases they have) without any chance to get passed those biases. Also, you aren't a professional performer (probably, few people are) so what are the chances that your "performance" is an accurate representation of who you really are? Yet, you're being judged by that.

I agree with others that your resume needs to be more accomplishment driven with lots of action verbs and results statements. You want to include a sample (but not a laundry list) of interesting problems you solved and value you delivered. Employers are far more interested in that than who you are and what bag of skills you have. Granted, you need to include buzzwords to be seen by resume filters but your resume should scream "Here's the kind of great stuff I can do for you" in the first few bullet points or so rather than a technical checklist.