|had a professor help out with it|
If you have graduated from a University, then probably the only part of the course that would be of interest would be your final project. Thinking around that, what skills did you learn/show around that - report, presentation, group, research, communication etc etc What did you major in and any minors?
Also, what extra activities did you undertake? What holiday time jobs/internships did you have? Hobbies? Travelling, different languages?
You mention soduku console game. Why console and not graphical would be my question. Can this person only program for the console and not GUI?
As this is a C++ forum, I'm assuming you're looking for junior C++ programming jobs. Almost certainly your first hurdle will be the 'C++ interview' - probably on-line. You need to practice these type of questions as it's easy to trip up on some if you're not experienced in doing them - especially when you're not using a compiler to tell you of syntax errors etc. I knew of at least one company that tested every applicant - and then only looked at the CVs for the top scorers.
Also, if you're replying to specific job adverts don't just send you 'standard' CV. Look at the advert, see what they are looking for and how you might have something they would be interested in - and tailor your CV accordingly. How does what you know/done fit with what they are looking for? What can you bring the company, how would you be an asset to them etc etc.
Note that many 'first pass' CV scrutiny is now done by computers (ai etc). They are probably looking for specific words/phrases - and if it doesn't find them it rejects the CV. So again looking at the job advert try to incorporate as much as possible into your CV - whilst obviously not telling out-right lies!
If you are lucky to get an interview, note that you will almost certainly be asked about what you have stated on your CV - so make sure you can talk intelligently about all of it - and your University course parts that weren't C++ related. Also be ready to be given a problem to solve with no notice - and be expected to explain your thinking as you go along to forming a solution. Being able to think through a solution (even if you don't fully solve it) with explanation is more important than knowing the particular arguments of an STL algorithm function (although knowing what are available is important) as these can be looked-up.