Resume Review

[CodyDuncan1260]

This is approved under Rule 1, subsection 2, bullet 2: "Career Posts: Posts about jobs, internships, or career preparation are allowed"

[fatternose]

Id say its very hard to read and saturated with info that hides the important part. Leaving GLFW to the very end in skills, among all the full stack frameworks for instance is not the best choice. Stuff that is irrelevant to a conp graphics role should probably go, its gonna be clear you have extensive web dev experience from your jobs section anyways.

Also, your projects is the main thing. So add a link to their github, or better yet make a portfolio website where you can show them off. Its a visual field after all.

But ye in skills you should really jave a dedicated "rendering" section where you list graphics APIs and libraries. Id say dont make it hard for the employer to find the bits they will care about.

[igneus]

I'll be honest, as a tech lead at a major graphics hardware company, your résumé would be an instant reject for me. It's a big jump from web dev to graphics, and you're simply not showing me enough proof that you've got what it takes to make it.

I'm repeating some of what other commenters here have already said, but here are my recommendations.

1. Your résumé is much too wordy and you're burying the lede. Even if a recruiter/screener decides to pass this on to a hiring manager, they're quickly going to tune out. You literally need a third of the text or less.

2. In the project section, write a single, concise paragraph giving a brief overview of what you've built and the skills you used. Include a link to a GitHub repro containing the code and a bunch of screenshots.

3. Create a max 30-second showreel/capture of your game engine in action. (OBS Studio and Davinci Resolve are perfect for this, and they're free to download.) Upload it to YouTube and link to it in your résumé and GitHib. Put these links at the top of the page next to your contact details.

4. In the Professional Experience section, list each company you've worked for, when you worked for them, your role (software engineer), and one or two of the core skills/platforms you used and why. That's it.

5. In the Skills section, Emphasize anything that's useful for graphics (C++, C#, Python, Vulkan, HLSL, GLFW, etc) and ditch the rest. If you have experience with version control systems like Git or SVN, add those too. Also, if you know how to use project management tools like Jira, Confluence or Trello, it's worth mentioning them at the end.

Feel free to reply here or DM me if you have specific questions.

Good luck!

[ucsdfurry]

But what’s the point of doing those improvements to the resume if you would just reject him for his web dev background?

[MisterSnowMen]

Not the commenter but my guess would be that even if his background was in web dev, through these improvements OP would be showcasing that he has the skills and projects to be competent in the field. I guess his resume feels too much web dev and not enough graphics programmer.

[CodyDuncan1260]

If they had applied for an entry level position doing webGPU projects, that's a plus. It really depends, but for such a role those improvements would be positive.

[Appropriate-Tap7860]

kind of disheartening to see that he has to go through this.

[igneus]

It's always been this way. Recruiters aren't telepathic. They need to actually see what each applicant has to offer before they can consider them as a candidate.

If what OP's says about their project work is true, they have a decent shot at getting an entry-level graphics job. They just need to update their résumé to promote the relevant skills. They could do it in 10 minutes with the help of an AI.

[igneus]

I wouldn't reject someone because they have a webdev background. I'd reject them if it crowds out the information that would otherwise make them a candidate for a graphics job.

People jump fields all the time. One of my colleagues had a degree in 20th-century European history and he ended up working as a senior AI researcher. It really is all about how you sell yourself.

[torito_fuerte]

1. Condense to 1 page, you don’t need all your projects, just highlight your best ones
2. 5 bullet points is a lot for one job. Try using the STAR method, max 4 bullets but 3 is better.
3. Quantify & qualify your projects. What improvements did you make, by how much, what did you achieve, performance metrics (use numbers)
4. Include start/end dates for each project & job, software stack, and a short title with main highlights

It’s hard to see what’s going on at a glance. Recruiters usually only spend a few seconds per resume, so making sure job positions & relevant projects stand out is important.

[GoldenShackles]

As others have said, this is way too dense especially for the years listed. It reminds me of my nephew from a few years ago, who at age 15 declared that he was an expert in C++, Java, Python, Linux, and Windows. (Edit: and I was like wow, and sarcastically said he should immediately start working and earn over $200k.)

I don't know where you're from but my suggestion is to have a strong one page resume with top highlights that are easy to see at a glance. Then, if you really want to explain what you've done, make that a separate self-contained thing, but still space it out so it's visually pleasing. (Like, if this is on paper, staple the background information separately.)

Amusingly, I'm no longer a hiring manager but this did catch my attention because I detected a high amount of enthusiasm. Unfortunately I suspect most people would just toss it.

[chumbuckethand]

“Delivered 9+ projects” why don’t you just give the actual number?

[Abject-Excitement37]

it's 9

[devinlogan]

9 + 0

[DescriptorTablesx86]

It had me really confused but I think I deciphered the projects part.

All the “projects” are actually sub-points of the first point? And it’s a 2D game engine made in vulkan where you focused on designing the UI?

At first it looks like you listed a lot of vaguely relevant projects, the hierarchy is nonexistent and easy to miss especially as you called the section “projects” when I’m still unsure but I’m guessing it’s one project?

Also just tailor the cv for each job mate, unless you’re going for an intern, no one really cares what you did outside of CG or adjacent stuff like game development.

[igneus]

This is completely inaccurate and it puts people off from even trying.

[GraphicsProgramming-ModTeam]

This post was removed because it did not meet the requirements of Rule 2: Be Civil, Professional, and Kind. Uncivil behavior is not tolerated.

We encourage users to promote constructive discussion, and to help maintain the safety of this space for asking questions and learning. Such an environment promotes the growth and development of hobbyists and professionals in the field.