The Entry-Level Software Engineering Resume

What could be missing?

Leslie G.
5 min readDec 16, 2021

I have a diverse work history. I have seen and fielded many resumes. Among the many things I do is provide resume critique.

I’ve seen an increasing number of resumes for full stack web development and software engineering. The secret was too good to last — With many thousands emerging from coding bootcamps, what was once an open field for talent has become grossly competitive with several thousand applying for a single SWE opening. This is where you need to shine.

I have seen hundreds of software engineering jobs every week, only because I was still a bootcamp student and not yet ready to apply. Life can be ironic. For those feeling discouraged, please hang in there.

In addition to sharing job openings, I am also sharing my experiences with anyone searching for an entry-level SWE job. This article was fueled by actual conversations on LinkedIn. Here is honest feedback based on resumes I see actively circulated:

  1. You’re applying to job postings. Well, duh. Of course you are. But that’s a surefire way to be up against several thousand applicants. For perspective, I was up against 3,000 applicants, then 960 applicants, respectively, for the last 2 full-time jobs I have held. Not all companies advertise their job openings. These sit quietly for you to find them.
  2. Is the job listing on Indeed? CareerBuilder? Glassdoor? When you see a job opening, go to the employer’s website and apply directly unless they (the company hiring) expressly instructs you to do something else.
  3. I am not a fan of industry job feeds, association-related job boards, gated websites, or email-based job listings that tease information and require you to jump through hoops to apply. By the time marketers publish these announcements, many are 6–18 months old.
  4. Never pay for access to job listings. The practice is 15–20 years old, and many such outlets are connected to improper handling of data.
  5. Life is too short and unexpected. Follow the organizations where business is connected to something you like, or aligns with your personality. It’s popular to chase FAANG companies, but you do you. If you‘re good at HTML, CSS, and JavaScript then you can make a decent living as a web developer. Everything else is fluff.
  6. Scrutinize your resume. For the remainder of this article, I will focus on some of the more serious problems that I am seeing on resumes. Let me begin by saying resume critique is one of the most subjective topics I’ve ever seen. One person will tell you to do something, and another will advise just the opposite. What we all agree on: Run spell check AND a grammar check on your resume, every time you make a change.
  7. Seriously, I am seeing spelling/grammar errors in 90% of resumes belonging to people that complain they aren’t getting responses. (Aside: My writing style is deliberately conversational, from television.) Resume inconsistencies are another problem, such as spelling JavaScript and Javascript in one document. Don’t think interviewers won’t notice. Or, the appearance of acronyms without first being spelled out when your resume is being intercepted and interpreted by non-tech staff.
  8. Do not have your name and contact information as an image or graphic. So many creatives do this. I see it everywhere. This strips your contact information from Applicant Tracking Software (ATS) and Automated Resume Screening (ARS) systems. Until recently this would end your candidacy. An exception is if you’re applying to a creative agency where they’re prepared and expecting your infographic-style resume.
  9. Expanding on the above, double check your resume can be automated easily and that your details are in text and easy to grab. A simple way to double check is to use text selection, copy the text of your resume, then paste it into any kind of new document. The result should not be awkward or scrambled. I’ve received some criticism about this from people who prefer to submit their resumes in .pdf form. I’m also one of these .pdf users, but my point here is to keep things readable and relatively simple because who knows what human resources is using for office technology.
  10. Have both a mentor in your industry AND a professional proofreader or college educator eyeball your resume. A 2nd set of eyes will spot errors that you may not notice. Take a short break and return if you’ve been working with a document for a while.
  11. That 2nd or 3rd pair of eyes on your resume may also begin looking out for you. They might see an opportunity, a job opening at work, or meet the CEO of a growing company. With your blessing, they can spread the word that you’re actively looking for work and that may help you get an interview.
  12. “It’s all about who you know…” That’s an old saying that can be infuriating in cases of nepotism, but it’s very true that meet ups and making new connections will reveal more opportunities to you. LinkedIn is the #1 platform for presenting yourself professionally to businesses. If you don’t have an account, get started. You do not need a paid account.
  13. You do not need a profile picture. It leaves you open to all kinds of discrimination and vulnerabilities that I will not discuss here.
  14. Social media. If your public profile has 2 raised middle fingers and your photos document your molotov cocktail collection (unless it’s Ukraine), maybe it’s time for some clean up.
  15. Google search your name and titles. Go more than just a few pages deep. See and know what’s out there. Do this on a quarterly basis. Do not correct anything, but you may want sensitive data removed.
  16. I’ve seen resumes by fresh bootcamp grads selling themselves seriously short. This upsets me because no pricey bootcamp should be sending people off without any kind of resume review. Make sure your resume spells out the programming languages that you learned and the frameworks used. If anything was a multi-chapter aspect of your curriculum, then it should be listed on your resume. Describe your capstone projects in detail and by requirements. These are valuable keywords for ATS/ARS systems and hiring managers to notice you.
  17. If you are using underscored, hyperlinked words to connect to your website or capstone projects… What if your resume ends up as a scan or photocopy and active links are disabled? Would it be better to spell out the complete hyperlink?
  18. Remove “Aspiring” and “Junior” from your resume and profiles. You can aspire to be anything you want. But those phrases scream beginner. (Exception: If it’s an actual title held at a previous job.)
  19. Do not erase your entire work history. I don’t care what the bootcamp rep told you. Most reputable employers run an employment or background check. Your capstones are your software projects, and your prior employment is your work experience. Everything from teaching or local government to flipping burgers or barista of the month is translatable. You never know. Your employment background can be an advantage.
  20. Be open and receptive to feedback about your resume. People frequently ask for help on public forums. Professionals may stop to read a resume, notice something glaring or missing and respond with important feedback. Don’t be the asker that gets defensive. We want to see you hired.

In conclusion, think through every aspect of your day from start to finish. We are bombarded all day, every day by all kinds of products, services, and businesses. Look into them. Send a quick Thank You note after each interview. And Blessed Be the interviewer who takes time to respond post-interview with constructive feedback rather than ghosting candidates.

--

--

Leslie G.

Strategic Communications | Media Relations | Multimedia | Web Development // IAPWE. Conversational writing. Learn something new everyday.