When doing hiring I want to see evidence that you are a web developer. Acronym soups on a resume are irrelevant by themselves since everyone does that. Quite simply you need to have a portfolio that substantiates your list of acronyms. You can bet I will do a view source and view network traffic on it.

What is important to me is also that developers communicate well. In an interview I put them in front of the whiteboard to explain something they claim to know well from their resume, looking at the communication.

You could do that sort of thing in advance by writing a series of blog postings, for example showing how you came up with the top level design and implemented one of your portfolio items.

Attention to detail also matters and is a strong signalling mechanism. For example your text above has a spelling error that is picked up in Firefox and Chrome.