I recommend a Summary of Qualifications that talks about what you are able to do. It's the "executive summary" that makes the HR screener want to read more. I c

I recommend a Summary of Qualifications that talks about what you are able to do. It's the "executive summary" that makes the HR screener want to read more. I can tailor this to the job if I need to do so. Then I recommend listing work experience focused on acheivements. Recruiters want to see how your past experience will translate to future success so don't list job duties. List accomplishments at the job. How much revenue did the apps you wrote bring in? How many active users did the app you built support? Did you mentor other people and were they successful? Did you contribute to an open-source initiative? "Built and maintained web applications using Ruby on Rails and React with over 200,000 active users per month." I do list skills both in context and in a skills section. My résumé has gotten me an interview every place I've sent it for the last 15 years. These things will never hurt you to do on yours. They will only help you. I've heard that objectives hurt, and I know that work experience that reads like a job description hurts too. My wife is in HR and I've asked these questions of her network of people and that's the general consensus. So I hope that helps.