I really hope that I have chose the right section to post this, and if I didn't, I am really sorry and a moderator may move/close/delete my topic.

Ok, so I have C++ experience, more accurately one year in the embedded programming field ( still working there ), plus the experience from university, and some personal projects ( nothing mighty tough ). I love playing games, and also love writing code, therefore I would like a lot to write code for games.

The question is: What should a simple mortal like me do to get a job as a game programmer, be it gameplay programmer, graphics, AI, or whatever ( I am sure that I would fit in one of those fields ). How could I convince a possible interviewer that I am the right person for the task, when there are 5 more persons waiting to attend the interview, with more relevant experience? Please keep in mind that I am aiming for more complex games ( PC, Console ), and not mobile games, or browser games. ( I am aware that this might be a mistake, and I am willing to take any kind of feedback positively )

Should I temper myself and start developing small games on my own? Would this prove anything to a reviewer? I guess that yes, but the effort required to learn something about this industry from the inside is much smaller than the effort required to to it on my own ( I have read a few books on game development, but I really don't fine this helpfull, if they are not paired with some real experience ), and I would not expect the experience earned this way to be very helpfull.

Is there actually a place for newcommers too? All the serious studios seem to ask for a great experience, of a few years, in nothing else than game development, some of them asking even for at least one AAA title shipped, and this is rather scary, because it makes it seem as there is no place for beginners in this industry.

Should I just try my luck and send some CV's to some game development studios, with a nice cover letter, hoping that some of them might appreciate the enthusiasm more that the actual field experience?

I have played with some toys, including directX and OpenGL, but I really, really, wouldn't mention this ( especially in the context of an interview ) because in my opinion the only real experience is the one earned on the battlefield, not on the playground ( I.E: at home ).

Yes, demonstrating your ability to finish a product, and/or show off your technical prowess with a finished game, or at least a demo, will very much assist you. There are a literally a few hundred people lining up from your position, and most studios try to hire people with prior industry experience, so any distinguishing factor you can grasp, GRASP IT.


That said, I don't know why you would really want to... the indie market is BOOMing, if you've got the talent, create your own game. Having gone from the game industry to just the programming industry ( to now self employment ), no friggin way I would go back. Horrifically run/managed, at the time, horrible pay ( at least compared ), stupid hours ( crunch time as a result of the horrible management ), a legion of doe-eyed kids lining up to replace you because they believe making games must be as fun as playing them ( again, putting a crunch on wages, at least initially ), oh and then there is job security... like, there is none. Almost every studio out there is two seconds away from being purchased by an EA or THQ and shut down 3 months later... Not to mention many game companies, hire on a boom/bust cycle anyways, knowing full well once a game is released, they will do a large round of lay-offs.

That said, it's been well over a decade, things may have improved... but from some of my friends I coorespond with that are still in the industry, it sure doesn't sound like it. Just opening the paper and seeing the number of successful studios getting shut down on a daily basis at least proves the business side of things hasn't changed much.


/ Ok, i'm done being a downer.

[color=#282828][font=helvetica, arial, verdana, tahoma, sans-serif]

[background=rgb(250, 251, 252)]I have played with some toys, including directX and OpenGL, but I really, really, wouldn't mention this ( especially in the context of an interview ) because in my opinion the only real experience is the one earned on the battlefield, not on the playground ( I.E: at home ). [/quote][/background]

[/font]

[color=#282828][font=helvetica, arial, verdana, tahoma, sans-serif]

[background=rgb(250, 251, 252)]Oh, and lose this mindset... short of outright lying, list as much relevant gaming experiences, regardless to how you got them.[/background]

[/font]


[color=#282828][font=helvetica, arial, verdana, tahoma, sans-serif]

[background=rgb(250, 251, 252)]In the end though, the easiest way to get into the gaming industry ( or frankly, almost any industry ), when you are one generic face in a sea of resumes is to make personal relationships. It's not entirely a matter of "who you know", but let's just say, knowing people sure does help![/background]

[/font]

Having gone from the game industry to just the programming industry ( to now self employment ), no friggin way I would go back. Horrifically run/managed, at the time, horrible pay ( at least compared ), stupid hours ( crunch time as a result of the horrible management ), a legion of doe-eyed kids lining up to replace you because they believe making games must be as fun as playing them ( again, putting a crunch on wages, at least initially ), oh and then there is job security... like, there is none. Almost every studio out there is two seconds away from being purchased by an EA or THQ and shut down 3 months later... Not to mention many game companies, hire on a boom/bust cycle anyways, knowing full well once a game is released, they will do a large round of lay-offs.

x2. The game industry really isn't all it's cracked up to be .. I just read all these posts on 'how to break into the game industry' from these youngsters, when the sad truth is most people in it are trying to break out lol.

One of the few things working for a company tends to have over doing indie stuff though, is they take the risk. I.e. whatever happens, you take home a salary. You might / probably will get laid off when the company has financial troubles etc, but you are compensated for your time working. When you work as an indie, you take the financial risk.

And the fact is most games don't make money. By far the majority lose money, often spectacularly, which is why so many game companies spring up and go under. If you've been paid your salary, the loser is the investors (seriously, who invests in game companies???). If you are an indie, and it doesn't make money, you make nothing. Conversely, in the unlikely event it does do alright you can take a bigger slice of the profit, but that's so unlikely as to be considered a pleasant surprise rather than an expectation.

I really hope that I have chose the right section to post this, and if I didn't, I am really sorry and a moderator may move/close/delete my topic.

Ok, so I have C++ experience, more accurately one year in the embedded programming field ( still working there ), plus the experience from university, and some personal projects ( nothing mighty tough ). I love playing games, and also love writing code, therefore I would like a lot to write code for games.

The question is: What should a simple mortal like me do to get a job as a game programmer, be it gameplay programmer, graphics, AI, or whatever ( I am sure that I would fit in one of those fields ). How could I convince a possible interviewer that I am the right person for the task, when there are 5 more persons waiting to attend the interview, with more relevant experience? Please keep in mind that I am aiming for more complex games ( PC, Console ), and not mobile games, or browser games. ( I am aware that this might be a mistake, and I am willing to take any kind of feedback positively )

Should I temper myself and start developing small games on my own? Would this prove anything to a reviewer? I guess that yes, but the effort required to learn something about this industry from the inside is much smaller than the effort required to to it on my own ( I have read a few books on game development, but I really don't fine this helpfull, if they are not paired with some real experience ), and I would not expect the experience earned this way to be very helpfull.

Is there actually a place for newcommers too? All the serious studios seem to ask for a great experience, of a few years, in nothing else than game development, some of them asking even for at least one AAA title shipped, and this is rather scary, because it makes it seem as there is no place for beginners in this industry.

Should I just try my luck and send some CV's to some game development studios, with a nice cover letter, hoping that some of them might appreciate the enthusiasm more that the actual field experience?

I have played with some toys, including directX and OpenGL, but I really, really, wouldn't mention this ( especially in the context of an interview ) because in my opinion the only real experience is the one earned on the battlefield, not on the playground ( I.E: at home ).

As serapth pointed out, that last paragraph couldn't be further from the truth. Doesn't matter where you learned your kung fu, playground or battlefield. It's easier to learn most types of kung fu in the playground (but some is easier in the battleground).

You don't have to be working at a company to learn stuff. Far from it, it's often harder to learn / experiment when you are working for someone else because you'll be following a task list, and not getting to work on what you want.

So in short, if you really want to get a job, as a coder (or level designer / artist), do some research, find out how different types of games work, the techniques involved. If you are an artist, make levels / characters for existing games. If you are a programmer, make little games, learn techniques, make some demos. You've got a huge amount of resources and info out there to learn from on the net.

Then when you are s*it hot, you can get some self respect, and you won't need to worry about getting a job, because companies will be gagging to hire you. You'll have to beat them off with a stick.

1. Ok, so I have C++ experience, more accurately one year in the embedded programming field ( still working there ), plus the experience from university, and some personal projects ( nothing mighty tough ).
2. What should a simple mortal like me do to get a job as a game programmer... How could I convince a possible interviewer that I am the right person for the task, when there are 5 more persons waiting to attend the interview, with more relevant experience?
3. Should I ... start developing small games on my own? Would this prove anything to a reviewer? ... I would not expect the experience earned this way to be very helpfull.
4. Is there actually a place for newcommers too?
5. it seem as there is no place for beginners in this industry.
6. All the serious studios seem to ask for a great experience, of a few years, in nothing else than game development, some of them asking even for at least one AAA title shipped
7. Should I just try my luck and send some CV's to some game development studios, with a nice cover letter, hoping that some of them might appreciate the enthusiasm more that the actual field experience?

1. That is NOT "experience." Read http://www.igda.org/games-game-october-2006
2. Build a portfolio so you are NOT outshone by all the other entry-level applicants.
3. Yes. Write code. Write small programs that solve some game problem. Collaborate with others too. You don't need (necessarily) a complete game. But you do need demos. You need a portfolio.
4. Yes.
5. That's a false perception.
6. You're reading the wrong job ads. Stop reading ads for experienced programmers, and look for ads for entry-level people. And just send in applications. Read this forum's FAQ 24 and FAQ 27. Back out to the Breaking In forum main page and click Getting Started to read the FAQs.
7. No. I mean, it's POSSIBLE that might work, but only in the sense that ANYTHING is "possible." You need to make yourself a more desirable applicant. Build a portfolio.

8. I don't know why you would really want to... the indie market is BOOMing, if you've got the talent, create your own game. Having gone from the game industry to just the programming industry ( to now self employment ), no friggin way I would go back.
9. Horrifically run/managed, at the time, horrible pay ( at least compared ), stupid hours ( crunch time as a result of the horrible management ),
10. Almost every studio out there is two seconds away from being purchased by an EA or THQ and shut down 3 months later...
11. Just opening the paper and seeing the number of successful studios getting shut down on a daily basis...

8. Not everybody has that talent or ability, even after several years in a game job. I think it's important to go the job route first, because it's a valuable learning experience, and earns money, while building oneself up to the point of going independent afterwards.
9. Not every company is horrifically run/managed. The pay is a lot better than not being paid while trying to level oneself up to the necessary experience level to go independent. Not every company crunches constantly.
10. That is a bit of an exaggeration.
11. Yes, times are tough. I still recommend that a raw graduate strive for the job route first, before trying to go independent.

Ok, so what I did understand so far:

1. Theoretical experience is nothing. This is something I was quite aware of. I have seen how true this sentence is when I got employed for the first time ( also last time ), and I realized that I actually knew nothing ( I might exagerate a bit )

2. Field experience is nothing unless is related to games. Somehow, I did not expect this. As I said, I work for a year as an embedded software developer, which I find related to games somehow, at least in the sense that both of them have real-time constraints, and the project I have been working on for the last year might be considered by many persons quite interesting. I thought that this experience might help me somehow and give me some sort of advantage. It's heart breaking

3. Doing little programs and demos at home helps a lot. I have a hard time accepting this, and while I do such thing quite often, I do them just for fun, and I never thought that they could actually mean something for an employer. In fact, most of the projects made at home have been deleted from my hard drive for a long time. I never actually considered them real projects.

4. A little bit of self confidence never hurts.

5. The game industry is not the best industry to work within. While this might be real, the desire to be there is too strong, at least in my case. Anyway, I got a lot of time ahead to convince myself if this holds true or not.

Bottom line: I should hold my horses for now, and improve myself for a while, before attempting to enter the industry. Thank you for sharing your opinions.

8. Not everybody has that talent or ability, even after several years in a game job. I think it's important to go the job route first, because it's a valuable learning experience, and earns money, while building oneself up to the point of going independent afterwards.
9. Not every company is horrifically run/managed. The pay is a lot better than not being paid while trying to level oneself up to the necessary experience level to go independent. Not every company crunches constantly.
10. That is a bit of an exaggeration.
11. Yes, times are tough. I still recommend that a raw graduate strive for the job route first, before trying to go independent.

All fair points. A small rebutal though.

8. I wasn't necessarily suggesting going indie full time. Merely that you can, in this day and age, get involved in game development without going to work at a [big] company.
9. Of course not. Also, I was dealing with experiences > a decade old, I hope things have improved. I do still hear *many* horror stories about crunch/death march development still being very common. Of course, these things do exist in other fields as well, just seemingly nowhere near as common.
10. Yes, it was a huge exaggeration, but that doesn't take away from it's "truthiness." Just look at all the "successful" studios that have been shuttered recently, especially by THQ chasing a better share price in an attempt to not be delisted, but Activision and earlier Atari are no less guilty, and to a degree, neither is EA.
11. I generally recommend a raw graduate get a more lucrative programming job, and work on games as a hobby or indie developer. Want to know the most disturbing part... times are tough, but profits in the gaming segment haven't taken a hit, so what's with all the job insecurity, hmm?

As Tom is explaining, times are tough, but it all depends on many factors and changes from situation to situation.

There's less job for more applicants but in many fields, not in videogaming only. By the way, contacts are important. More important than ever in such tough times.

11. I generally recommend a raw graduate get a more lucrative programming job, and work on games as a hobby or indie developer.

A perfectly good approach, but again -- not necessarily for everyone. Not working in games professionally means it'll be hard to make contacts. When the programmer is not a Renaissance man, he'll need artists, audio, businesspeople, marketing help. Working in games means the individual (upon going indie) will at least know some of the right people he can call on.

[quote name='Serapth' timestamp='1334610089' post='4931877']
11. I generally recommend a raw graduate get a more lucrative programming job, and work on games as a hobby or indie developer.

A perfectly good approach, but again -- not necessarily for everyone. Not working in games professionally means it'll be hard to make contacts. When the programmer is not a Renaissance man, he'll need artists, audio, businesspeople, marketing help. Working in games means the individual (upon going indie) will at least know some of the right people he can call on.
[/quote]

Fair point, and frankly indicative of how I went about things over all. The contacts I made were (are) very important to me for a variety of reasons.