Not to sound rude or anything, but theyâll probably ask why you didnât go for a Computer Science degree.
If youâre going off of degrees alone at least. But aside from degree related questions, theyâll ask you what your experience is, if you have no real world experience in this field, you may want to volunteer or work for the cheap on a couple projects just to show you can do it. Because in this field, 9 times out of 10, a Experience trumps a degree any-day.
In fact most jobs donât even require a degree, at least ones Iâve ever seen, theyâd rather you just get in and get it done.
But to answer your question directly:
Theyâll probably ask you stuff such as do you have experience with XYZ Languages,
If you have any experience with Shaders
If you know how to manage memory
If you know how to thread for editing tools and such
If you know how to program AI
If you know how to program procedural stuff
If you know how to create some algorithms to do so and so
If you know how to deal with data security (if doing something that requires server-side, etc) data security, such as encryption, php, asp, etc as a back-end language and if so, do you know how to properly secure the data with todayâs standards on security.
But honestly mate, thereâs really no telling what anybody will ask you,
Iâve had people ask me something, a problem to solve, and they had it wrong, well it was right, but I made it in a more optimized way, and they rejected me because they wanted it done that specific way. Which whatever lol.
I canât imagine a useful scenario where they would ask you specific questions about unity. It would like interviewing and artist and asking them about photoshop. The question isnât whether or you can use unity, everyone can. The question is whether or not you can make games.
Most of the interviews Iâve done are with small indie outfits who donât really have a clue how standardized interview techniques work. The interviewer normally has no idea what they are doing. So you can get a lot of traction by running the interview yourself. Direct the conversation to areas that you are strong in. Sell the unique value you can bring to the company.
Direct questions are ridiculously variable. Iâve had everything from âHow do you program in Unity without relying heavily on IEnumeratorâ to âWhat kind of board games do you like to play?â. Most of the time Iâve tried to take along a laptop so I can show them stuff. I find thatâs much more direct when it comes to questions. âHave you done custom physics?â, âYes, here is a project where I implemented bouncy and waves, and here is how I did it.â And so on. Questions are often directly related to companies current needs for the current project they are working on, rather then pie in the sky tests of your abilities.
Take my advice with a grain of salt. Iâve never actually accepted a job in game development. Normally my interviews end like this âSo do you have any questions for us?â âSure, what kind of salary can I expect?â âWell based on your experience, you could start at [less then you can get in manual labor]. If you work out, you could expect to climb to [less then you are on in your non game job] in just few years.â
Indeed. like online certification basic. Iâm not sure why those would be in an interview, possibly a pre-screen or something. In my experience, basic qualification type inquiries are answered long before an interview (or self-evident based on experience, or irrelevant as they can be learned).
Yea, the last one is either clever or ignorant⌠not enough context to tell. Like asking âWhat is the average size of a GameObject?â The response to the question itself would be more useful than any direct answer.