As a hiring manager I see a lot of resumes and I am frequently shocked at how poorly many candidates come across on their resume. There may actually be nothing wrong with your skillset or experience, but many can&#x27;t make it show on their resume.<p>If for every position you did:<p>1. Feature enhancements in HTML, CSS and JS
2. Bug fixes and debugging
3. Wrote scripts, created new layouts etc etc<p>...then sorry, I am not even interviewing you because you don&#x27;t seem to be thinking very critically about your job and what you are really here to do for the company.<p>Always express your resume in terms of accomplishments and what change you produced that affected the ultimate goal of the business.<p>So no, you didn&#x27;t do &quot;feature enhancements&#x27;, you &quot;Increased conversion rate by 5% after acting upon A&#x2F;B test results.  Streamlined the customer on-boarding experience by reducing clutter, pre filling forms, and cutting page latency.&quot;<p>After 8 yeas of experience and a brief listing of technologies you frequently work with somewhere on your resume, I don&#x27;t really care what technology you used to accomplish the above. The fact that this is how you think about your role at the company is what matters to me. Any deficiencies or strengths will come out during the interview but I&#x27;ll definitely invite you for a conversation.<p>And I agree, interviewing front end devs using algorithm puzzles are bullshit. A clear sign the company hiring doesn&#x27;t know what it actually needs in a person but just do it because it&#x27;s what Google does (or did).