I have seen thousands of resumes in my life. Some were nice, while others were awful. In some cases, the resume truly reflected the person behind it, in others, it failed to.
My first touchpoint when looking for new software engineers is this document.
There has been much discussion about what to include in a resume and what format to use.
Today, I want to address three resume issues I consider old myths:
Let's dive in.
There are so many software engineering degrees out there, but the truth is, you don't need one to become a successful software engineer.
When I see a resume without a bachelor's degree, it doesn't raise any red flags. On the contrary, it piques my curiosity.
I want to know more about the reasons that led this software engineer to go down that route. As long as they have a coherent answer, I'm comfortable working with them.
At Supportful, we've removed education requirements from our job descriptions entirely.
I believe that in our current era where information is abundantly available and often free, formal education isn't the only path to knowledge and skills.
Many software engineers have made it through self-study, early work experience, or intensive coding bootcamps.
Some of the finest engineers I've worked with either skipped college altogether or were career shifters, coming from completely different backgrounds.
I used to be obsessed with resume continuity: each position had to follow the previous without any gaps. It's no longer the case.
I came to realize that this expectation is unrealistic and potentially harmful to both candidates and employers
Sometimes, finding the right job can take time, especially in tough job markets.
Some software engineers prefer to wait or work on side projects until they find the right fit in terms of role responsibilities or career goals.
Also, life happens, and people sometimes need breaks to rediscover themselves or attend to family matters and personal situations.
Remote work does not equate to laziness or a lack of productivity. It's work, but in a different setup.
Software engineers working remotely still have to collaborate effectively with a team. They might even have better time and task management skills than their in-office colleagues - having to manage life and work in the same environment.
Some of the world's most successful software companies, like HubSpot, GitLab, and Zapier, have embraced remote work as a core part of their culture.
Many engineers seek out remote opportunities for valid personal reasons, such as life-work balance or family commitments.
On the other hand, companies looking to grow should leverage remote work to attract top talent from around the world.
When you're building your engineering team, focus more on the traits that make up a successful software engineer and less on the engineer's degrees, resume gaps, or work arrangements.
What are other myths do you think tech leaders should discard when reviewing a software engineer's resume?
I wish you happy growth!
Book a call and get matched with engineers in 24–72h.
