Team Size

There is a wide variety in team size.

Teams can be as small as a single developer or just a few for an Indie title all the way up to over a thousand for the biggest games. Here are some of the pros and cons:

Large team:

Pros:

The game is almost certainly going to be released.

Generally good job security, pay and benefits.

Many people to learn from.

Cons:

Work is split up so easy to get pigeonholed.

Hard to stand out.

Hard to make quick changes to the game. Feels bureaucratic.


Small team:

Pros:

Everybody makes a difference to the game.

Talented & hardworking people move up fast.

Easier to experiment & make changes to the game.

Cons:

Lower pay.

Worse job security. Game more likely to be cancelled.


Personally I prefer teams in the 10-50 range. I would rather be a big part of something small than a small part of something big.

Comments

Post a Comment

Popular posts from this blog

Am I going to enjoy working in games?

This is the big one. Are you the type of person that enjoys making games? Making games is fun because: - Working in a team. - The end product is a cool game. - Interesting challenges and new technology. Not so much fun: - Sometimes projects get cancelled and nothing to show for your work. - Making games can be hard and frustrating. Bugs and working with unfinished tools. - Making games can be monotonous and boring. - You spend loads of time alone. What outsiders often don't realize is that game developers spend 90% of their work time alone. Most of the day you will be sat behind your screen with your headphones on working by yourself. I personally enjoy spending a couple of days solving a particular problem. If you are the bubbly sort of person who prefers small well defined tasks you may not enjoy making games as much. Making games is hard work. There is a real contrast between the glamour of the final product and the hard, boring work that goes into making them. Especially with b...
Read more

How to prepare for the interview?

By far the most important thing interviewers will be looking for is whether you have the initiative and determination to work independently. There is no better way of demonstrating this than having previous work to show. The very best thing is to have worked on game projects before. It's ok for them to be relatively basic and unfinished. This can be a project by yourself or in a small group. As an artists you could show some 3D art. Ideally but not necessarily used in a game. Maybe you have models with different poly counts. Maybe you messed around with shaders. As a coder, show some projects you've worked on. Maybe some fluid physics, editable landscape. Anything really. Experience with Unity or Unreal is super helpful. For you first job. interviewers have nothing to go on. Being able to show some projects you're passionate about really helps. It also gives you something to talk about.
Read more

Getting a job vs starting for yourself

Image
Starting for yourself. It has never been easier to write a game for yourself or with a couple of friends. Unreal & Unity take care of the technical foundation and Steam is a great way to publish. This is a new thing. Up until 2010 it was almost impossible to produce a competitive game with less than a dozen people. So, should you take advantage of this and write your own game? Unfortunately many people are thinking the same thing and competition is stiff. This is a graph of the number of games released on Steam. Clearly there is a lot of competition. How much money can you expect to make? It's complicated but: 68% of titles released on Steam in 2019 have made less than $10k to date. The chances are that your first games on Steam are not going to make anywhere near enough to live off. Here are some interesting videos by CodeMonkey who is experienced and able to eek out a living on Steam. https://www.youtube.com/watch?v=xQMfT_RqBgk https://www.youtube.com/watch?v=gg3Xrv7jUtk Keep...
Read more