Many engineers are not designers, and should not be judged as such. Constructive criticism is more helpful here than lambasting them for not adhering to your personal standards of UX.
While I agree with your second statement, your first is misplaced. There is a huge difference between "I'm an engineer, can't design, here's my resume(even my HTML5 resume)" and using oddly timed fade-ins, slides, text reflection, etc. etc.
If you try to put that much design in a resume, you get judged as a designer.
2 days late; not sure if you'll still get a chance to read this. But, I'll bite.
As someone who's hired (good and bad) engineers in both UI/UX and back-end disciplines, my first impression of it was "Yeah, it's not pretty, but he does not allege to be a designer." At that point, I checked out the source code. It was not spectacular, but he did communicate an working grasp of the technology he professed to understand.
If this resume was judged in a biased lean towards UI/UX, my opinion is that you'd be passing up a potentially hard-working and dedicated employee. With a little help from a designer, this guy could possibly do great things.
I'd argue that engineers should only "design" so much as they feel comfortable. If you have a decent sense of laying things out, stick to a nice minimalist grid. If you feel you have a decent idea of what fonts look great together, contrast serif and sans-serif fonts, sizes, weights, etc... and there ya go.
If you're just throwing a gradient here, a border there, a glow there, etc... then you're just shooting blind.
If you try to put that much design in a resume, you get judged as a designer.