4 ms·
I've worked in gamedeve since 2007 and interviewed a lot of people. Small games portfolio doesn't matter, because small games, just like beginner tutorials from
by golergka 5y ago
I've worked in gamedeve since 2007 and interviewed a lot of people. Small games portfolio doesn't matter, because small games, just like beginner tutorials from Unity, don't teach you skills necessary to work on a large-scale project with multiple developers. When you're working on small-scale projects, you can follow bad practices and don't hit their limitations.
However, if I would be interviewing a game designer and not an engineer, this portfolio would have been incredibly relevant.
- ImprobableTruth 5y agoDoes this also apply to junior roles? I would expect a portfolio of small games or some tech demos is the best you could expect there.
- aloner 5y agoNo, small side projects will definitely help you stand out when you're applying for a junior position since you don't have a lot of experience yet.
- GuB-42 5y agoSure, but neither do binary searches and balancing trees. If writing a 10000 line game is not like working on a million line project, writing a 100 line algorithm is even less so. And yet, some recruiters value coding tests more. In fact, practices in competitive coding are almost the opposite of what you need in large projects. You need to get a result as fast as possible, and the code is thrown away in the end. Readability, robustness, reusability, none of these matter, descriptive names are a waste of time, so is freeing up resources. Competitive coders are usually good coders in general, simply because they care, but so are people with side projects.