This week, Honeypot.io published a short video where I gave “5 Tips For Junior Developers | How To Break Into The Industry.”
One of the first comments that appeared said “‘How to break into the industry’ should be about how to get that job at IBM, and not what you did after you got it. Or am I missing something?”
After a bit of reflection, I realized that Stefan was completely right! I had skipped over a vital time in the developer’s journey: how to land your first developer job.
Today I want to address this gap and give you five tips on landing your first developer job.
I want to preface this post with the caveat that I was very privileged in my job search. I completed an internship at IBM and from there was offered a role internally at IBM. I did not have to apply for a multitude of jobs to land my first developer job.
Prior to landing a job with LogMeIn (my second role) and subsequently at Spotify, I applied for as many jobs as I possibly could. I did not hear back from nine-out-of-ten companies that I applied for and I struggled to determine why. I had landed my first job without much effort, why was I having so much trouble landing a second job?
The following tips have come out of my struggle to land a role and I hope they help any developer out there struggling to find their first or second role.
Let’s be honest: landing a job interview is difficult in-and-of-itself. We always discuss how anxiety-inducing the technical interview process is but we don’t often discuss how difficult it is to even get an interview in the first place.
When applying for your first role it can be intimidating to know which roles to apply for. Do you apply for a junior developer role? Do you apply for an entry-level developer role? Often the job requirements don’t perfectly align with what you deem your skillset to be, so you have two options: apply only to roles which you feel tightly align with your skillset or apply to all roles you think you generally fit into.
Regardless of which option you choose one thing is certain: you must have a stand-out resume to get noticed. Recruiters see hundreds of resumes and only spend about 7.4 seconds on average reviewing resumes.
A few tips for having a notable resume include:
- Use a fun resume design to stand out from the other candidates
- Prioritize the most important information at the top
- List your contact information at the top
- Don’t include a photo
- List what direct impact you had on the success of a project in your work experience bullet points
- Include quantitative data points to back up your work experience “so what” statements
- I won’t be diving into the nuances for creating a technical resume, but I did create a full course with LinkedIn Learning that you can check out for more details!
Here’s what my resume looks like! Remember, we’re in a creative industry so you have a bit of freedom when designing your resume!
When companies are looking to hire an entry-level developer they want someone who is motivated to learn. As a developer, we’re expected to stay up-to-date and learn continuously, thus it’s imperative to highlight your willingness to learn during the interview process.
If you have the time and ability to take a few online courses I highly recommend it. FreeCodeCamp, LinkedIn Learning, and Coursera are a few online learning platforms that offer certificates upon completing a course. You can add these to your resume and your LinkedIn profile.
Additionally, if you’re asked in an interview if you have experience with X technology, you can state “I haven’t worked with X before but I would be eager to learn it!” This shows that you’re excited to grow as a developer and from the company’s perspective this translates into a candidate who will be a great investment.
Straight out of college I had the biggest ego you can probably imagine (especially with an IBM internship behind me). “I deserve a great job and I won’t have any trouble getting an offer.”
There is a massive difference between having confidence and having an ego. I had a massive ego and it hindered my growth as a developer (and a human) for several years. I’ve seen many new developers also fall into the ego trap. The longer you work in the tech industry the more you realize how much there is to learn.
When hiring managers are making their decision they want to bring on a team member with humility. They want someone who is a team player and is not afraid to admit when they don’t know the answer to something.
Some of you reading this may not have fallen into the ego trap but I certainly did. Take some time to reflect on how you present yourself to interviewers but also how you view your own skillset. If you’re riding the border between confidence and ego it might be time to do some self-reflection. It will positively impact your success at landing your first developer job.
If you completed a college degree in software engineering or computer science you have an advantage over other applicants who did not complete a technical degree. If you completed a boot camp you likely have one or two projects that showcase your skills. But if you’re self-taught or are switching industries you likely don't have a large backlog of projects.
While it’s becoming more commonplace to hire candidates without formal education, I would be remiss if I didn’t acknowledge the privilege that comes with a relevant college degree. If you don’t have relevant formal education, I highly encourage you to have two or three coding projects on GitHub that showcase your work. It will be time-consuming but having these projects will increase your chances of landing your first job.
Technical interviews are hard, it’s why I’m currently in the process of creating a full course on how to be successful in your technical interviews. A good technical interviewer will want to see how you approach complex problems, they won’t necessarily expect you to find the correct solution.
I never learned how to effectively solve problems and it put me at a massive deficit during technical interviews. A few tips for demonstrating good problem-solving skills during technical interviews include:
- Clarify the question (they’re left with a few missing pieces to see if you can deduce them)
- Write down the functional requirements (what are the things your solution absolutely must include)
- List possible solutions as well as benefits & drawbacks
- Speak your thoughts out loud
- Admit when you don’t know something
- Optimize your solution
- Test your solution
- Explain areas for improvement
I’m not an expert on how to solve problems so I encourage you to take time to learn how to solve complex problems. But by following the guidelines above you’ll improve your technical interviewing skills.
Landing your first developer role is exhausting and frightening. Keep in mind that everyone in the industry has gone through the same process. The reality of it is that it may take time to land a job interview and it will likely take you several tries to land a job offer.
I won’t tell you not to get discouraged: you will. Let yourself experience your emotions. Take a break from applying and interviewing and focus on your mental health, and come back to the process once you’re ready. You can do this.