If this is the wrong place to be asking this - please let me know and I'll happily ask it somewhere else!

I am completing a C++ Proficiency test for a "Junior Engine Programmer" role at a game studio in the UK. The test involves creating a pathfinding demo and rendering it to the screen. I won't go too into the details of the test, but the brief doesn't mention any documentation or unit testing etc.

I've been told by a lecturer I should definitely include both of those, despite not being asked, and by another that I should use my time more wisely to make a great implementation. What is the done thing here? The only thing close that the brief mentions is making clear where I've used other libraries.

Is there anything else I should consider submitting with the implementation as well? Thinking of technical specification such as class diagrams etc, or anything really.



1 Answer 1


I'm sorry, but we can not answer this question for the general case, because interviewers are not all the same. People who make hiring decisions are all individuals who apply their own personal judgment systems and expect very different things. While one person might be impressed by the extra length you went to, another might wonder why you are wasting your and their time by adding stuff they never asked for.

What you can try, is to do some research to find out what they are likely looking for:

  • Read the job offering description, test instructions and other information provided to applicants very carefully. Read between the lines to find out what kind of person they are looking for. Do they want someone who can follow instructions? Or someone with the initiative to do their own thing?
  • Try to find out how they are working internally. Do they have any development blogs describing their development processes? Did people from that company talk about them at conventions like GDC? (by the way, if you do get to the personal interview stage, then showing you did your homework about the company you applied to will almost always earn you a couple extra points)
  • Are they a large or a small company? Large companies tend to have very standardized application processes with very formalized rating systems. These simply don't leave room to take any additional work into account, so it's often futile to try to score that way. Smaller companies often tend to look at applications a lot more subjectively and might be impressed by applicants who do things which set them apart from the rest. But this is not a hard rule either.
  • Just ask them back whether or not they would want to see supplemental material like that together with your test submission.

If this doesn't give you any pointers, then the best thing you can do is think about what course of action does best represent you and the way you want to work.

  • \$\begingroup\$ And by the way: Almost none of this advise is specific to the game development industry. \$\endgroup\$
    – Philipp
    Jan 18, 2020 at 11:55
  • \$\begingroup\$ Seems like good advice. Thank you :) \$\endgroup\$
    – Figwig
    Jan 18, 2020 at 12:27

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .