what were your major(s) in college;
I majored in Film Studies with a minor in Managment
which major(s) or minors would you recommend, which are recommended across the industry;
Honestly talent is more important than formal education, although the education tends to refine ones skills. But if your goal is to get into the business, then it depends on what field within the industry you are interested in.
what made you want to become a game designer, what did you do to ensure that you achieved that goal;
I decided early on in college that I would get a job that I had fun doing because I just wouldn't be able to stand "putting up" with something just for a steady paycheck. I saw this as a fun job and since I love games and had enjoyed previously working in a project-based industry, I decided this is where I wanted to go. I made the decision and just stuck with it. As I said above, it took me nine solid months of actively looking for a job before I found one in the industry, but I stuck with it.
did you play a lot of video games before you were hired (and do you now), or just really appreciate the few you play;
I played an excessive amount of games before I even thought about getting into this industry. I do appreciate what I see in games nowadays more since joinning the ranks even though some might say that some of the magic is ruined And to be honest, I had more time to play games before I started working here...
what other jobs did you consider applying for, game industry or otherwise;
I was originally a Information and Computer Science major in college and was expecting to work for the government. After I decided to go into games, I held an IT job while I was looking for work in this industry.
how did you present your skill to your interviewers (portfolio, design documents, working demo?)
It really depends on what job you are applying for. I originally had interviewed with Obsidian for a design internship. Then, months later, they contacted me wondering if I'd still be interested in something along those lines as they were going to do a trial run of internships. It happened so fast that they didn't make me take the design test and basically just drilled me for a few hours. I guess the best way I presented my skill was through my resume and my answers to their questions. Most of it comes down to the face-to-face, regardless of your qualifications on paper. I think I just made a good impression.
what is the most important thing to know/keep in mind/do going into an interview in such a coveted position, what are the worst things to do;
From my experience interviewing with companies in this industry, the worst things you can do are:
-Be over-eager. Now, this is not the same thing as having passion or excitment about the industry, those are pluses people look for.
-Be casual about the process. It might be an informal setting or conversation, yet the person on the other end of the table is still there to figure out if you are right for the job. People will send in stuff that I wouldn't even call first-draft highschool English class material. Don't be sloppy with your work or their tests. Put in the effort.
-Insult the comapny you are interviewing with. You would not believe how many trolls from the boards apply for jobs here after clearly stating that they think our company is run by monkeys and we make crap games. Constructive criticism is one thing, but being an **** will not get you hired
The best advice I have is:
-Make a list of say, twenty companies you would like to work at and rank them in order of your preference. Then, try to get interviews with the companies at the bottom of the list and work your way up. Look, you are going to make mistakes in the interviews and such (everyone does) so it's best to make those mistakes with companies you are less interested in working for. That way, when you get to the top of your list, you will be a seasoned interviewee and be more comfortable with the whole thing, which will only help your chances.
-Create assests. If you want to be an artist, have a kick-ass portfolio. If you want to be a gameplay scripter or designer, have some way of demonstrating to them what you can do (Mods are a fantastic way to do this). It's just a matter of conveying to them in a timely fashion what you are capable of.
why do you think they picked you out of everyone (because of strengths, mindset, experience, perhaps very convincing?);
That is certainly a question for one of the fellas who interviewed me.
how did they test your skills;
In a very sink-or-swim manner. I would be given a meager task and if I completed it well, they would give me something a little more challenging and important. Eventually I just worked my way to a place where they regarded me as a pier (an inexperienced one, but one nonetheless)
what tasks or jobs have you had to do as a designer that you weren't told about in the interview;
I'd say just about everything I did. I was in a position where I was supposed to help out the design team any way I could to the best of my ability. They gave me vague posibilities as to what I might be doing, but nothing prepared me for the scope and breadth of tasks I was given. This included anything from doing mundane excel spreadsheet work to actually designing certain levels and quests.
did they take note of where you went to college and what you majored in, or were they more interested in the skills you were able to present;
Again, more of a question for them. But I assume that both were a factor. The fact that I completed a degree at a four-year university probably didn't hurt me any
what made you better than others applying to obsidian(what made you more desireable and/or stand out in a crowd?);
Again, for the interviewers to answer if they so wish.
about how many rejections abroad did you get before you were seriously considered, and what did you learn from them;
Several. I had been casually persuing a position for years and been turned down by lots of companies. Most of them had legitimate reasons, but they were excellent learning experiences. My do's and dont's above came from those experiences and the first-hand knowledge helped me in the end.
what design or gaming experience did you have going into the industry;
I was a writer for one thing. Scripts, novels, papers... it's all about the creativity you can call on when you need to. Honestly my experiences in college were probably the best way to hone my skills. As for gaming experience, I think I was able to demonstrate that I didn't just "play" games, but I understood them. I could go further than just saying a game was good or bad, I could tell them why with at least some insight.
what expectations did you have going in to the industry, and how have they changed;
I have had friends in the industry so I was probably more prepared that the average person coming in fresh. I think the biggest wake-up call was the fact that "**** happens!" and it's not always someone's (or some company's) fault. I used to tear into companies when a game fell short or content had to be cut or I found a bug. But looking at it from the inside, I now understand that there are so many factors and variables that go into making a game that you can never account for everything no matter how much experience you have around the table. I think the hardest thing for some people to get used to is to have their work on the game get cut or not make it in (that's assuming the entire project doesn't get scrapped). It can mean that months of work would have essentially been for nothing and some people can find that hard to take. There are many good reasons it happens, but people can still take it personally and be hurt or offended by it. You just have to grow a pretty thick skin.
what path would you recommend to a person wanting to become a designer, (and even if you strongly recommend it) and is a college degree necessary;
Designer is a hard one. I would suggest keeping your creative talents sharp, be it through writing, mod making, world creation for a pen-and-paper game... anything that keeps your imagination going, because that will be your primary tool. The other stuff is incidental... there isn't any one major in college that I would suggest... we have designers with degrees in law and environmental engineering!
what would a typical day at obsidian consist of for you;
That depends on where we are in the project cycle. A medium Monday well-into the project would be:
-Stagger in sometime around 9:30
-Catch up on emails and begin getting the latest build
-Design meeting at 10
-Company meeting at 1030
-Get some small tasks out of the way before lunch
-Lunch at around 1130
-Begin hacking away at larger issues and try to make a dent in your tasklist
-Walk around the complex with some fellow employees to chat and grab a snack around 400
-Finish up tasks and be out the door by 7
Again, this can differ GREATLY depending on where we are in the project cycle
describe, if you can, a non-typical day you had at obsidian;
During crunch time, it would be more like the list above except at the end you would need to add
-Dinner around 630
-Back to start second round of tasks.
-Get as much as humanly possible done before 100am when the nightly build process would start grabbing assets for the next day.
-Work after the build went through until you can't keep your eyes open (I'd say around 400am)
how much contact did you have with programmers and artists working on KOTR2, do you see them often;
I came on late in the project when a good chunk of the art assests were done so I really only had to go to an artist when there was a problem, but that is much different early on in the project. I saw programmers almost once-an-hour either to help fix something or figure out how to do something new. The office environment is very open and everyone is very accessable.
what do you feel was your best contribution to KOTR2, what do you wish you had done differently or had a hand in;
I think my best contribution was the small problem of having to fit a game like that on a platform that only has 64megs of RAM I was given the task to make sure all of the levels we had fit, which almost none did at the time. I really feel that was a test to see if I was ready to start on the producer track since it was a very producer thing to do. But after everyone's hard work, we got it all nice and squared away.
As for what I would like to have done differently, there were several times at the end of the project where I couldn't jump in on certain tasks because I just didn't have the knowledge of the system we were working with. If I had taken more time out to sit down and learn that stuff, I would have been able to contribute even more... but honestly I think I'd say that no matter how much I had :D
what are your likes and dislikes of your job (the position itself, not being at obsidian);
I loved my job. I was given a variety of tasks that challenged several of my skills. The job itself was a fantastic learning experience. As for dislikes, I think the only thing would be that there was no one for me to delagate to. I was the bottom of the design totem pole. But that was my job and that's what I signed up for.
typically, how many hours a day do you work? does that differ from hours said during your interview;
I'd say once we are in full swing, it's about 12hours from the time I get there to the time I leave... sometimes more and sometimes less. That's honestly about what I expected.
what is the atmosphere like? casual? team-oriented? stressful?;
One of the things I always mention when telling someone about Obsidian is the interesting duality of the atmosphere. Obsidian itself is a very casual company where it is not uncommon to hear jokes and laughter somewhere in the office almost all the time. However, I have never met so many skilled and productive people in all my life. It's a wonderful example how being casual does not mean you have to sacrifice productivity. When it's time to work, people work. We get our **** done.
On top of that, there is no one at the office (from the CEO down) that isn't approachable. The lowliest intern can walk into Feargus' office and bring something up and he would give him the same attention he would a lead designer. The management here has surrounded themselves with competent and talented people and in doing so, rarely ever have to "pull rank" on someone (and even then, it's never really ugly).
what advice would you give a designer about to start his/her job (on his first day);
For the love of Jeff, don't be afraid to ask questions. You won't bother anyone by asking a legitiment question about something you would have no way of knowing your first day on the job. And get to know the people around you. They are going to be invaluable in the coming months (not to mention you're going to be seeing lots of them )
do you have any programming or artistic skill;
I have some programming knowledge left over from my ICS days in college... as for skill, I'm going to go ahead and say no As an artist... well, let's just say there's a reason I'm a designer and not an artist! That being said, it does help to have an eye for both and at least enough competence to not be afraid of the other areas of the industry... at least in my case.
have you held any positions at wizards of the coast;
A few characters in Living Greyhawk but that's about it!
is there anything else you can say about your job and what it consists of, how to become a designer, experience every person applying for a design position or any other position should have, what to expect working at a game studio, in a team, or as a designer in general, or anything you wish you would've done differently or known in how to become a designer?
I think you pretty much covered it. But I'd like to think that my well of knowledge hasn't been tapped dry just yet, I'm sure something else will come to mind later on.