Applying to a job: What to show in code I send?
Hi guys,
first some background info:
I'm currently finishing my second year of a 3-year bachelor degree in gameprogramming. A few days ago I visited the developers I wanted to work with once I'd finished my degree. To my surprise though, the ones I talked with while there encouraged me to apply now, even though I'm not finished with my degree. The point of this degree is to get into the industry, so if I can do this a year early then I'm all for it.
I meet all the requirements (mainly C++), and they've set no previous experience in the industry as a requirement for the job I'm after (Game Programmer, could also go under the name of Junior Programmer I believe).
I called and spoke with them, asking what they'd like to see in the source code I sent with the application, but it was not very specific.
I'm currently working on a semesterlong project written in C++ with OpenGL, a generic spaceshooter game. It is this I plan to use as an example of my work. The project is meant to be about OpenGL though, not C++, and as such my focus has thus far been on the graphics part. The job I want to apply for on the other hand, is only about C++, and I believe showcasing my OpenGL-knowledge wouldn't help much.
And so I ask you:
Looking at the application of someone who is potentially underexperienced, and still a student, what specifically would you have to see in the C++ sourcecode to consider taking him in for an interview?
Or:
What specifically would have to be missing/poorly written for you to turn him down?
Thank you for your time. :)
Student at NITH, Norway2nd year of Gameprogramming BachelordegreeC++ enthusiast
[caution] CAUTION! [caution] CUIDADO! [caution] ACHTUNG! [caution]
It is a common practice (of bad companies) to employ people before they graduate on terms that make it difficult to complete their degree. They won't pay as much, and they know you can't move to another company as easily without a degree.
Don't quit your degree program just because you found a job.
Finish your degree.
If that means putting off your game job until after getting your degree, then so be it. You will not regret that decision a decade from now.
You will earn more over your entire career, you will be more employable, you can move more easily up the career ladder, and you will not regret it.
It is a common practice (of bad companies) to employ people before they graduate on terms that make it difficult to complete their degree. They won't pay as much, and they know you can't move to another company as easily without a degree.
Don't quit your degree program just because you found a job.
Finish your degree.
If that means putting off your game job until after getting your degree, then so be it. You will not regret that decision a decade from now.
You will earn more over your entire career, you will be more employable, you can move more easily up the career ladder, and you will not regret it.
What my salary is comes second, actually getting a job in the industry comes first.
To me, it seems nigh impossible to actually get a job as a developer in this country, and I wasn't even sure I'd ever be given the opporunity in the first place.
Getting a new job, if I should for some reason stop working there, would be much easier than if I'd just finished my education. "You need experience to get experience."
Finishing my degree at a later time wouldn't be a techical issue, although leaving a paid job to go back to school would probably be a tough decision.
Still, thank you for the advice Frob, I'll take some time to reconsider, though I'm quite sure I'll apply either way, and instead take the decision when I know more about the actual difference.
To me, it seems nigh impossible to actually get a job as a developer in this country, and I wasn't even sure I'd ever be given the opporunity in the first place.
Getting a new job, if I should for some reason stop working there, would be much easier than if I'd just finished my education. "You need experience to get experience."
Finishing my degree at a later time wouldn't be a techical issue, although leaving a paid job to go back to school would probably be a tough decision.
Still, thank you for the advice Frob, I'll take some time to reconsider, though I'm quite sure I'll apply either way, and instead take the decision when I know more about the actual difference.
Student at NITH, Norway2nd year of Gameprogramming BachelordegreeC++ enthusiast
Writing bad code "because you're focusing on the graphics part" definitely won't earn you any points... The code will ultimately reflect your C++ skills, even if it's very simple.
And I agree with frob... This is extremely shady.
Though what would happen if you did go work there, and then went back to finish your degree later? It could end up being a great educational experience.
And I agree with frob... This is extremely shady.
Though what would happen if you did go work there, and then went back to finish your degree later? It could end up being a great educational experience.
Like kiwibonga said finish you degree first! I was just in the same position sorta. I got a job for a game company programming and was worried about not being able to finish my degree, well during the interview I brought this up and they were willing to work around my school schedule and have encouraged me to stay enrolled. So you might want to bring up the fact that you are in school and want to finish with them and see if they are willing to work around it, if they are not willing then trying to get night classes for your course work will be a nightmare having to work and then go to school. I wish you the best of luck.
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music." - Kristian Wilson, Nintendo, Inc, 1989
Quote: Original post by frob
[caution] CAUTION! [caution] CUIDADO! [caution] ACHTUNG! [caution]
It is a common practice (of bad companies) to employ people before they graduate on terms that make it difficult to complete their degree. They won't pay as much, and they know you can't move to another company as easily without a degree.
Don't quit your degree program just because you found a job.
Finish your degree.
If that means putting off your game job until after getting your degree, then so be it. You will not regret that decision a decade from now.
You will earn more over your entire career, you will be more employable, you can move more easily up the career ladder, and you will not regret it.
very good advice !
Quote: Original post by CodeLuggage
To me, it seems nigh impossible to actually get a job as a developer in this country, and I wasn't even sure I'd ever be given the opporunity in the first place.
Don't be shy to move in another city/country.
Definitely finish the degree. Anything else would be folly. If they want to hire you now, they'll want to hire you later. If nothing else, have the confidence in yourself to say "If they want me now, they'll want me later when I'm even better."
Its no good to jump at the first scrap they throw under the table. I've never once hesitated to turn down an offer when I knew I deserved better and there's not a snowball's chance in hell that I'd have ever cut short my degree program to jump into the industry. As Frob pointed out, taking them up on the offer would likely be short-sighted and leave you at a disadvantage for the future. If nothing else, having a degree gets you taken as a serious contender, even if that just means getting past the HR drones.
As for your code, show only what you're proud of, and only what you are confident of your understanding of, because it's likely to become a topic for a future interview. You should be able to explain in detail how it works, acknowledge shortcomings, defend your design decisions and, ideally, speak intelligently about alternative approaches to the problems you've solved. Avoid "generic" code such as Matrix/Vector libraries, thin DirectX wrappers and similar things. The best conversation will come from problems that you really had to twist your mind around to solve (provided you ended up with a "good" solution, of course).
Its no good to jump at the first scrap they throw under the table. I've never once hesitated to turn down an offer when I knew I deserved better and there's not a snowball's chance in hell that I'd have ever cut short my degree program to jump into the industry. As Frob pointed out, taking them up on the offer would likely be short-sighted and leave you at a disadvantage for the future. If nothing else, having a degree gets you taken as a serious contender, even if that just means getting past the HR drones.
As for your code, show only what you're proud of, and only what you are confident of your understanding of, because it's likely to become a topic for a future interview. You should be able to explain in detail how it works, acknowledge shortcomings, defend your design decisions and, ideally, speak intelligently about alternative approaches to the problems you've solved. Avoid "generic" code such as Matrix/Vector libraries, thin DirectX wrappers and similar things. The best conversation will come from problems that you really had to twist your mind around to solve (provided you ended up with a "good" solution, of course).
throw table_exception("(? ???)? ? ???");
Quote: Original post by kiwibonga
Writing bad code "because you're focusing on the graphics part" definitely won't earn you any points... The code will ultimately reflect your C++ skills, even if it's very simple.
And I agree with frob... This is extremely shady.
Though what would happen if you did go work there, and then went back to finish your degree later? It could end up being a great educational experience.
Ah, no, I did not mean that I wrote poor C++ code, or anything of the kind. I merely pointed out that during this particular project I've focused on OpenGL and graphics, rather than trying to show everything I know of C++.
For example: I haven't used templates extensively, nor much polymorphism. This, in my opinion, has not lead to my code being less effective or wellwritten, I've just chosen another solution and path.
I see many of you offering the same advice; finish my degree.
Up to this point I were leaning towards applying for the job, and quite possibly take it were it offered, but you are all making convincing arguments.
Perhaps I've been too hasty in assuming I'd probably never get a chance at a gamedev-job. That's the real issue, I'm afraid I won't get this chance again (that when I finish my degree, there will be no jobs avaliable here).
I have, and I am strongly considering moving out of the country, or to another part of the country, but I've family and friend which ties I'm reluctant to break. Still, it is an option which I'd consider when the time came to find a job, and there were none.
Thank you all for your replies, they were not what I wanted to hear, but that's not a bad thing. I'll keep thinking on this.
Student at NITH, Norway2nd year of Gameprogramming BachelordegreeC++ enthusiast
Quote: Original post by CodeLuggage
I have, and I am strongly considering moving out of the country, or to another part of the country, but I've family and friend which ties I'm reluctant to break.
Uhm, will your friends pay for your monthly living costs. Do you want your family to pay ? Some of your friends may be just pure lucky and get a great job few months after they`re finished with uni, but not all of you will.
So, the sooner you understand, that life changes radically after uni, the better for you. Don`t ever think of not accepting the job offer outside your current place, just beecause of friends. Chances are, that after the uni, when they start living real life, having daily job/household duties, they won`t have enough time for you anyway. That`s the way life is.
If I were you I would try the job, make sure they understand the days off you need for school during the term and during exam period. The worst that can happen is , that you`ll simply quit the job if the education would be in risk.
Just finish the degree. It`s going to be extremely tough to do that while going to daily job later, should you choose not to finish it now. Especially with your own family. There are lots of jobs for programmers everywhere. You can start doing any DB job, and try your luck with gamedev companies.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement