Advice on Applying for a Job

Over the years I have reviewed a lot of dev job applications and resumes and done a ton of interviews with dev candidates. Looking back on all of it, here is the advice I have for those who are applying for a dev job. Please NOTE this advice is based on the fact that a human will be reading your resume. Thankfully, I have never had to interface with bots when applying for a job so I don't have any advice to offer on that front.

Don't try to know it all

Often a job listing will list ALL of the technologies a company works with from the frontend framework to the backend server operating system. Most of the time they are not actually looking for someone who knows ALL of that. They usually want someone who knows some of their tech stack. For this reason, don't pretend to know anything you don't.

If it's on your resume be ready to talk about it. I can't tell you how many times I have asked someone about a skill on their resume and they reply, "Well, I have only ever read a blog post on that" or "I worked with that once 5 years ago." To me, that looks deceitful. I would rather you not have it on your resume, to begin with. Furthermore, if you are asked about a technology you are not familiar with I would rather you admit you are not familiar with it than trying to pretend you are.

Make your resume stand out

When you are reading a lot of resumes it doesn't take long before they all start to blend together. A couple of things that always help a resume stand out to me are:

1. Color
2. Two Columns
3. Font variations (Bold, underline, italic)

Color: Almost any pop of color makes a resume easy to remember because 99% of the resumes you see are black and white. Obviously, if everyone uses color this advantage goes away but I don't see that happening anytime soon. Consider adding a pop of thoughtful color to your resume either in the font or a light tint for the background. However, when you do make sure it is still readable and not hard on the eyes. For example, maybe stay away from bright lime green. 😉

Two Columns: For whatever reason, EVERY resume I have ever seen with two columns is extremely well organized and easy to read. I think the columns force you to up your game on organization and to keep descriptions short because you have less page width to work with. All of this leads to an easier to read and digest resume.

Font variations: Using font weights is a great way to draw attention to things on your resume. When looking at a resume the first thing I do is always skim it. This is where font-weight comes in handy. If you bold your skills or maybe a big project those are going to jump out at me first. Sometimes, people may not even have time for a thorough read so this is going to ensure you get your key points across quickly

Convey that you want it

When I look at applicants applying for a job one of the top things I look for is How much do they want it? I know this is going to get some debate because some people just want a job that earns a paycheck and that is totally fine! However, for me personally, I want to work with happy enthusiastic people who enjoy their work. I find that those people make great coworkers and boost the morale of the team.

Answer the questions 

This may seem obvious, but you wouldn't believe how many times I have asked a question and the candidate skirts around it or answers in a very noncommital way. If someone asks you a question in an application or interview make sure you are directly answering it. We honestly want to know your thoughts and opinions on the matter!

For example, let's say you are asked: "What kind of testing strategies do you use and which ones do you think are the most important?"

GOOD: "I use X and Y testing strategies this way and that when I code. In my opinion, testing strategy Y is the most important because of all these important things."

BAD: "There are a couple of different ways to test code. One way is X and it does this. Another way is Y and it does that."

The problem with the second response is that it doesn't give me any insight into what YOU use or what YOUR approaches or opinions are when it comes to testing. The biggest thing I look for when I ask an opinion question is, does the candidate have a reason to back their opinion up? Most of the time I don't actually care about the opinion, I'm more interested in your justification and reasoning behind your opinion.

Nothing is a bigger turn off to me than an opinion without a reason. "X is the best testing strategy and everyone should use it!" Ok great, tell me why otherwise, I don't believe you. Yes, I was THAT kid always asking "But why?!" growing up 😅

Now some people will argue that at least the second response proves the person knows about testing. Knowing about testing is great BUT that is not what I am trying to determine with the question. I'm expecting the person will know something about testing, but what I want to see is have they thought critically enough about it to form an opinion. This is how you can separate out those going through the motions vs those who are taking the time to really understand what they are doing.

Explain links

If you put a link in your resume or application, explain what the link is, don't expect the reviewer to do all the work! You have to at least give some context. One example might be:

Here is a link to my blog: dev.to/person_1. I tend to blog about accessibility and frontend frameworks.

If I have time, I can click the link and explore. But if I don't, then I still get the gist of what you like to blog about. Also consider that sometimes people will get printed versions of your resume and might not be able to click the link. For these cases, the explanation helps provide context about what the link is. Also, make sure the link is short and easy to type. Then, if the person reading your resume wants to type it by hand into a browser they can. In short, make sure your resume as accessible as possible for everyone and every medium.

That's All Folks!

This is far from a complete list of all the things you should keep in mind when you are applying for a job but hopefully, you found these few tips useful. Good luck finding your next dev gig!