You would not believe the number of utterly useless resumes that fall into one’s inbasket.   (And that somehow escape the clutches of the spam-filter ... one is constantly “tweaking” those rules, I’m afraid.)

Nevertheless, sometimes someone says something that causes you to pivot on your heels and take notice.   And so, in your third paragraph, I find two things that immediately attract my attention.  

1. ... git ... presentation ...   You know about git?   You presented?   When?   Where?   To how many people?
2. ... 16,000 tests ... perlcritic’s OK ...   “Okay, this is not a tyro.”

Any software engineer is, first and most, an engineer, and such a person’s true job description is to identify a problem, own it, and solve it ... all of this as a means to the end of creating robust, reliable, maintainable business software systems.   Therefore, what you want to do is to briefly describe how you did that.   Who relied upon you, and what references can you give to people who will affirm that you are the greatest thing since sliced bread?

As far as people are concerned, y'know ... you can train them, and they can learn.   If they’re disciplined and reliable and professional, and they don’t know a particular thing, just give ’em a book and a weekend and a $50 Starbucks card.   Everyone is constantly encountering things that they have never encountered before, and dealing with them, and delivering upon their promises.   So, when you are hiring, you are really looking for those qualities.   Reliability.   Resourcefulness.   Discipline.   Honor.

Make that shine.