Donald and Brunleyy give some suggestions on what they look for when hiring new developers and how you can optimize your resume to get more responses while job searching.

Have suggestions and want to discuss these topics more? Join our Discord.

Interested in Software Development? Check out Donald's blog and videos.

You can interact with Brunleey live on Twitch or enjoy his other content here.

Hosts:

• Donald Feury
• Brunleyy

Show Notes:

- Most important information first
1. Name /w mission statement (if any)
2. Skill list
3. Job Experience
4. Projects
5. Education
- Remove personally identifiable information
- Location
- Anything indicating age
- Personal information like sex, religion, probably phone number unless you want it to end up in random call lists
- Information like this, while I may prompt to see you in a positive light, is also just as likely, even more so I would say, to see you in a negative light.
- Remove any information that is ambiguous
- Skill ratings
- You will interpret this information in a completely different way than someone else will. Saying you're 3 / 5 or whatever in a skill doesn't actually tell me how well you know it. Someone could interpret that is you not knowing enough and chuck your resume in the trash
- Certificates are completely unnecessary except for jobs that involve government work or certain positions. If the job you're applying for needs certifications, place them after skills.
- Phase your job descriptions in the form of In order to solve X problem, I solved it by using Y, which lead to Z result
- It's not always possible to quantify a result but being able to part hard numbers like a 20% increase is very effective
- Example: Integrated our existing tooling with TestRail by creating a custom webdriverio reporter using Typescript, enabling more clarity into our automated testing results.