This time we discuss things on the other side of the interviewing table with things to look out for when interviewing candidates to get that high-performing team you've been looking for.

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

Today we discuss some important to do and NOT do during an interview to maximize your chance of getting through. We talk about non-technical and technical interviews.

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: (Sorry these are incomplete this time)

Non-technical Interview

- Do not speak ill of your previous/current employer. It is frowned upon, even if they did objectively bad and stupid shit

- If asked why you left/are leaving, give a neutral answer that is oriented towards growth. Something like `Looking for new opportunities`

- Do a little bit of research about the company if you are accepting an interview. They will ask what you know about them and showing them you've spent time learning about them looks good.

- If possible, always try to answer a question in a way that demonstrates how you will provide value to the company

Donald and Brunleyy talk about how they weed out bad job listings from one's that are actually worth applying for, as well as their general strategy when it comes to 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: 

- Decide what type of responsibilities and/or tech stack you are looking for

- Look for positions that match keywords that are in line with those responsibilities and/or tech

- Check any and all major job boards

- Indeed

- Special Note about Indeed: Some listing will prompt you with a few questions when you go to apply, usually in the form of `Do you have X years with Y skill?`. You must answer yes to these questions or your resume will **NEVER** make in front of anyone.

- JustRemote

- RemoteOK

- Monster

- Many others

- If you see a position that might work out, just send the resume. Do not bother researching the company unless they actually respond back looking to do an interview. Ultimately, this a numbers game. Especially if you're just trying to get your foot in the door.

- If you want, before sending the resume, you can tweak what keywords are in your job descriptions and skill section to match up with what they're looking for. Don't put anything that can't carry a conversation about though.

- Red flags to watch out for:

- When you're looking over the responsibilities and it sounds like 2 or 3 jobs in one. I prefer to stay away from these because the situation tends to get worse, not better, in terms of responsibility creep. This may also mean they don't really know what the fuck they are even looking for and are casting a wide net.

- I *prefer* listings that list the salary expectations. I will still apply if the position sounds decent enough but I will bring up salary expectations early if they don't

- Formatting and just general spelling errors. If they can't even take the time to proofread the damn listing, I don't expect much out of that company.

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.