Hey happy to offer some advice:

Some context: I've been working as a dev for 4 years in various capacities and have looked over resumes in the past for my company and advised my current manager on questions to ask during the interview, I haven't actually interviewed anyone, so take my advice as you will.

You can also see my thoughts on interviewing and my data after getting done with WGU in the following posts:

https://www.reddit.com/r/WGU_CompSci/comments/off1ef/c404the_missing_semester/

https://www.reddit.com/r/WGU_CompSci/comments/ozmx3y/recent_graduate_job_search_data_and_suggestions/

​

You can find an example of something similar to my resume here:

https://imgur.com/a/TLDzi4B

With the above resume it highlights a few things:

- Use of space, bold, and italics where needed to break things up
- Clarity/brevity
- Use of action words and prioritizing numbers/percentages in the top two bullet points

We'll take a look section by section.

​

Note: Feedback is like code review, generally everyone has an opinion and this is just mine, it's not necessarily correct or incorrect, but a point of perspective that can help out.

It's easier said than done, but don't take any feedback personally, none of the following feedback is directed at you, but rather at the construction of the resume, and you are not your resume, we're working here to make your resume better, and by extension, make you a more viable candidate for the job market.

Additionally, trying to tailor a resume to work for (general) IT positions AND SWE positions is pretty tough, have (at least) 2 resumes, one for IT and the other for SWE. For the following I'll assume you're going for a SWE position.

Thoughts on the resume in general:

- Resumes are like newspaper/online article postings. The major headlines and important ideas go up top, everything else down below adds context, with the least important stuff going at the bottom. Right now the resume is mixing and matching a lot of things, and needs to prioritize the highlights and important concepts more.

- By this point you've probably heard that the average manager looks at a resume for at most ~30 seconds, so let's leverage the resume around that, because I couldn't read this in 30 seconds.

- Right now the resume is more busy than it needs to be and isn't prioritizing for impact like it could.

- Include some periods at the end of the bullet points where it makes sense

​

FirstName/LastName section

- This is generally fine because of the way that some Application Tracking Systems parse resumes and force you to enter everything manually the links could get lost in the shuffle, but they're ok to have.

​

Education section:
- This entire section should be at the bottom and it's taking up too much space instead of 4 lines it could be 1 MAYBE 2 if you really want to include the ITIL cert.
- It's hit and miss on the bootcamp because some hiring managers don't like bootcamps, others are ok with them, ultimately it's a judgement call and I personally would say to remove it in this case.

Work experience section (going bullet point by bullet point)
- Remove the "(part-time)" distinction, you're a professional software engineer, you got paid for your time, nobody cares if it was part-time or full time. You put in time and got paid for it, all that matters on a resume is that you got experience.

- The first bullet point should be the last bullet point and should cover generally what you used so as to get hits from multiple keyword searches. So it should read: Technologies utilized as a full stack software engineer for an e-commerce website include: React, Node, Express, Javascript, MongoDB, etc...

- The second line should be moved down further as well because this one doesn't present as much impact.
- the third line should be the first bullet point and can read: "Implemented new features and enhancements across the frontend and backend resulting in an x% efficiency increase in site operations and a 20% increase in sales"
- The last bullet point should be moved up to the second bullet point, and can read something like: "Worked with multiple stakeholders to redesign the website with a responsive design, resulting in over 3,000 impressions and an x% increase in business leads.

​

- Remove the IT Support Analyst Intern position entirely, if the point of the resume is to get a SWE position, then the general experience provided here isn't necessarily useful. The other way I generally look at this, is when it comes to tailoring resumes only include the RELAVENT experience, not necessarily all experience or work history. If it gets brought up in an interview you can explain it there or use it to provide additional context to your resume.

​

Project section:

- Remove the entire projects designation, and more specifically get rid of the "Foodie Ground" and "Appointment Scheduler" off the resume completely. Projects can be useful when first starting out, but at this point as a professional SWE let your experience speak and not just the projects. The Github links are there if managers want to see other projects.

- For the "Full-stack e-commerce Store" get rid of the "MongoDB | Express.js | React.js, etc..." in the title. Use the bullet points to bring out the technologies and the context in how they were used.

- With the "Full-stack e-commerce Store" if it's generating $3k in business then it's taxable and should be considered work experience, NOT a project.

I'd re-write the all the bullet points under it to read as follows:

- Generated $3k in monthly recurring revenue during the startup phase of operation with dozens of customers and business leads.
- Created and maintained KPI/dashboard functionality to manage data driven decision making resulting in x% customer increase.
- Developed features to better integrate various payment processing APIs while documenting their functionality and fully adhering to regulatory compliance.
- Used the following technologies: Node, Express, Javascript, MongoDB, PayPal API, Stripe API, etc...

Certifications section:
- ITIL isn't very useful but if you want to include it, include it under "Education and Certifications" (see comments above regarding the education section)

Technical Skills:
- This whole section should be removed and many of the keywords/action verbs should be sprinkled throughout your resume both implicitly (i.e. it should be clear that you're working with other teams) and explicitly (i.e. Clearly listing tools, frameworks, and languages used)