#Worst Graphics Programming CV ever? (hundreds of rejections without any technical testing)
60 messages · Page 1 of 1 (latest)
you are just listing random keywords and "skills" you supposedly have
but how do you prove them? you have ubisoft in there, what did you do
do you have projects, do you have things you can mention you have done
the whole "basic understanding" section should gets nuked. Just say you know that
problem is. i can go and do a similar CV just listing a bunch of keywords, but there is no proof behind them. And there is no info on yourself either
anyone can claim they know math by putting random keywords under a math section.
the problem is that a cv like that, where its just listing random things, just doesnt have any weight behind it
you have the stuff on vmware and ubisoft. try to expand those sections, and explain what you did
that would give weight to the other part
here's mine for reference
notice the projects section
with a lil explanation of what I did there
also notice the link to a portfolio
and yeah vblanco is right in every way here
remove the parts where you sell yourself short
a CV is boastful, it's fine
also ask yourself, what do the recruiters/interviewers want to see
and aim for that
your github doesn't have that much polish either
this could be fairly impressive if you gave the readme some love
as i see it, the goal of the CV is to brag as much as possible in the shortest amount of space, and to offer proof of said bragging somehow
you appear to have some fun stuff in the github, if you add more READMES to the projects and link to those, it will be a massive win
as always with poor CVs, it's mostly about framing
one sentence per project is enough in the CV
you wanna frame yourself as someone who'd excel at the job, not as someone who's kinda alright
as reference from my linkedin (where i build my CVs from)
also one tip is to make your CV spell out a "story"
each project just has link plus short explanation of what it is
as in, you started off as an engine/graphics programmer, then you went to VMWare, and now you're applying for that job; how does each step lead to the next?
for example when I was applying for my current job as an engine programmer my "story" was that I wanted to make games, studied game design and learned programming, fell in love with the more programming-oriented aspects and wanted to do more of that, did a bunch of projects for that and got a job at a studio as a gameplay programmer, and now I want to go even more into the programming side as an engine developer
and the CV kinda reflected that, as did the portfolio
so that the job I applied for was essentially just the natural, logical next step forward
ofc that's a bit advanced and you can't always do that
related to it, you can choose what to prioritize in the CV depending on target work
(and it often helps in the interviewing stages more than in the cv filtering stage)
so for example if i was going to apply for an unreal project, i would put the projects about unreal and the psvr game. but if i was going for a graphics programming engine dev, i would put the low level stuff and graphics
yeah, this especially applies to stuff like, in your skills you have proof theory & lambda calculus, ZFC set theory, measure theory, computability theory etc - how does that make you a better graphics programmer?
if the answer is that it doesn't, then you can remove it (or put it much lower down)
btw, how do you talk to recruiters/HR?
you can keep it as "advanced math knowledge like : x y z
stuffing keywords still helps somewhat
fully remote is a bit tricky, but feasible
I wrote a little post about this a while back, mostly aimed towards juniors but it might help you
password is GGC2023
btw, in case you've fallen for that trap, it's completely fine to apply for a different job at the same company after being rejected
anywhoo the post goes over a lot of that kind of stuff, should hopefully be helpful
ye it's not, if anything it shows you have an interest in the company
if they ask for a cover letter, you can even mention it and what you've improved on since your last application
mention which game engine at ubisoft if possible
and instead of "some work on", just say "improvements of engine tooling and build system" (again you don't want to be humble hehe)
other than that, it's a good WIP 👍
i would say merge the first two sections
no projects and companies, but have them be the same
yea that's a good point