1. Avoid saying things that apply to everyone. Example, "I love building products that delight my users." Who wouldn't say that when applying for a job? This, "help create positive social change" is more interesting and should be the focus of your intro.
2. Avoid useless phrases. Example, "This has manifested itself in many ways during my career." Boring filler.
Overall, you could cut the length of this by 30-50% just by removing cliches and filler phrases. It would immediately become much more readable and emphasize your technical skills.
I guess the next step is to write a blog post to assimilate everything I learned today about setting up a 'dev' resume.
"Most recently, I been the de facto architect of NBC News’s four iOS and tvOS applications."
(It's also worth noting that I have ~12.5 years of experience in the software industry, Seattle—the city where I live—has a hot tech market, and I have focused mainly on iOS software development for the past six years. Relatedly, I never apply for jobs through websites, only through people, meaning that I manage to skip buzzword-skimming front-line recruiters. So YMMV.)
https://www.dropbox.com/s/0tntyr8isf2l47k/Aaron%20Brethorst%...
Coming at this from the other side of the table, my first reaction to reading most resumes is "so what?" Tell me why I should care that you increased Flibbet production by 22%, or that you decreased bug volume by 19%. What does that translate into in terms that someone who doesn't work at that company would care about?