Yeah, I wouldn't want to be a tester. Testers, normally, do not get paid very well and they are morally abused. :) Hours on end just sitting at a couch, playing the same level, over and over and over. Which, might not sound too bad, but I rather work on the intellectual/creative side of my brain than becoming a monkey.

Quote: Original post by evanrogers
1. What is the probable amount of time I will have to wait before I can begin working somewhere. I'm willing to move almost anywhere and I will be applying to as many game-related programming jobs as possible.

I wouldn't expect it typically takes too long. Once you have an offer, it shouldn't be more than a month that you can actually start, and I would guess it's probably closer to 'immediately'.

Quote: 2. Should I consider applying as a tester instead? Should I state on an application that I would consider a job in Q/A?

No. If you are a programmer, and want to be a programmer, then apply to be a programmer. Don't state that you would "consider doing something else, just to get a job" - that's not the attitude you should have, and it's not the one you should give off. If you're a good programmer, then you're a good programmer - don't sell yourself short because you think that any job is good, as long as it's related to games. Reach for your goals, and don't accept anything unless you're truly satisfied.

Quote: 3. How much should I expect to get paid?

*shrug* it really depends on your abilities, where you work, etc... I think a typical starting salary for a programmer is somewhere in the 60-80k range, again it depends on where you work (geographically). If you respect the company that you're applying to, then trust that they will probably give you a fair offer.

Quote: 4. Should I avoid companies with bad reputations like Midway and EA. Will these companies be my only choice? Don't get me wrong, I'm ready to work as much overtime as needed, but I want a job that will help me move towards becomming a lead programmer.

There are hundreds and hundreds of game companies out there. If you already have a bad impression of some companies, that could be reason enough not to work there. It's really up to you, but I wouldn't turn down any phone interviews - it will give you the chance to talk to one of the developers there, and see how good you feel after the conversation. I don't feel that it's inappropriate, for instance, to bring up the "reputation problems" if you're at an interview at EA. They know there's some bad rap out there, and I think they would be more than happy to try and clear the air with you - at least listen, and you can make your own judgement call. Know the right time to bring it up, though.

Thanks for all the advice. I feel I have a better understanding of the situation now. I have one last question:

Is it necessary that I live near the job location before I apply? I live in upstate New York right now and I haven't seen more than a couple dozen companies in the whole northeast. I am considering moving to an area with a high concentration of game companies, like northern california/southern washington. As an alternative, I suppose I could apply to several places out of town, wait until I have some intervies lined up, and fly or drive around the country. Is this a good idea?

Evan wrote:

>Is it necessary that I live near the job location before I apply?

I already told you that it is. I already told you you have to live near the company before you apply. I guess you didn't like that answer (or are just looking for a 2nd opinion).

LOCATION, LOCATION, LOCATION.

Quote: Original post by tsloper
Evan wrote:

>Is it necessary that I live near the job location before I apply?

I already told you that it is. I already told you you have to live near the company before you apply. I guess you didn't like that answer (or are just looking for a 2nd opinion).

LOCATION, LOCATION, LOCATION.

No, it's not necessary. Many companies relocate new employees. That shouldn't stop you from applying, for sure - there are many companies spread across the country, it would be silly to move before even applying, and moving reduces your options.

Many companies should also fly you out for in-person interviews, if you make it that far. At least, that has been my experience. Maybe I'm just good [wink]

I guess I don't understand why it matters to a company where I live if I am willing to relocate anyways. I'm willing to drive or fly to conduct an interview. And when I find a job I want, I'll just get an apartment ASAP. I'm not picky about where I live and I don't have a lot of belongings. Is this plan too strange?

Quote: Original post by evanrogers
I guess I don't understand why it matters to a company where I live if I am willing to relocate anyways. I'm willing to drive or fly to conduct an interview. And when I find a job I want, I'll just get an apartment ASAP. I'm not picky about where I live and I don't have a lot of belongings. Is this plan too strange?

Doesn't sound strange at all. In any event, discuss how moving works with the interviews you get. Good luck!

Rdragon wrote:

>No, it's not necessary. Many companies relocate new employees.

Fresh out of college? Unlikely.

>it would be silly to move before even applying

It is risky. Best to move to a hotbed - an area like Seattle/Redmond or SF Bay Area or Los Angeles - where there are lots of companies within commuting distance.

>Many companies should also fly you out for in-person interviews, if you make it that far. At least, that has been my experience. Maybe I'm just good

It's been my experience too (I've even been flown to Europe for an interview), but I'm not fresh out of college. Did you get an airline ticket right after graduating? If so, do you really think that's typical and reliable advice for fresh grads?

> discuss how moving works with the interviews you get.

Of course. For experienced people, they'll usually pay moving expenses. For entry-level people, they usually have tons of local applicants and no budget for moving expenses.

Evan wrote:

>I guess I don't understand why it matters to a company where I live

I explained this in the Barrier-Busting FAQ and in the Stupid Wannabe Tricks FAQ (http://www.sloperama.com/advice.html). The distance injects too much time into the process. Imagine: Employer has tons of local applicants and some long-distance applicants. The local applicants can show up and interview the very next day, whereas the long-distance applicants will take a week. For entry-level positions, they wanna fill'em now, not a month from now. And they can fill'em now because there's a ton of local applicants.

For experienced people, they've got the luxury of time and money - can afford to fly'em in for an interview in a week or two, wait while candidate gives notice to his old job and settles living arrangements, then pay for candidate's moving expenses. But not for entry-level people with wet ink on their diplomas.

Every company I've worked at has flown people out for interviews and paid moving expenses. This includes companies from giant developer/publishers to small 'indie' (in terms of publisher association) companies. And yes, this includes college freshies.

If the company has any kind of success/revenue, it should not be an issue for them to handle these costs. The cost of employing someone is far higher, and it pays to get the right person, no matter where they are from.

Okay, thanks, I understand now. I will probably try my luck in the northeast and if that fails, move in with a friend in san fransisco for a while.

- Evan