> What should they include? What are your expertise areas. Such as specific framework and languages. Detailed experience of recent work places. > What are the

> What should they include? What are your expertise areas. Such as specific framework and languages. Detailed experience of recent work places. > What are the most common mistakes developers make when talking about themselves ? They think 1 person will read the resume and decide. It usually goes through at least 2 levels: - HR, they usually focus on keywords and filter the bulk - Developers, they usually are interested in more details to see if you can fit technologically > What do you look for? Proven track record of delivering projects. Whether be professionally or as a side project. > Are there things that can influence you favorably? Rare achievements that you don't see on every resume. Something you consider personal or even a team win. Random example: Our team managed to improve the initial load time from 10s to 0.5s which also improved our bounce rate. My greatest tip would be that you make your resume specifically for the 2 types of people I mentioned above: HR and Devs. Since HR are first and get more resumes, make the first page keyword heavy `X language - Y years of experience`. On the second page go into details of specific jobs and tech decisions.