Jump to content
GameDev.net Posting Guidelines (please read before posting)
The Game Job Advice FAQs (please read before posting)
So you want to break into the video game industry (you want a game biz job). First, you have to know which type of job you want -- if you don't know which you want, you need to read about the game industry and the types of jobs in it. Then you might need to make a decision. Third, you need to be qualified for the job. Fourth, you need to know how to find information and how to ask good questions (you need to not ask bad questions). Finally, we have tips for getting the job.
Do not post Help Wanted or Position Wanted or team-building posts in any of the discussion forums. Click Careers atop this page.
Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.
Posted 15 March 2014 - 11:49 AM
Posted 17 March 2014 - 11:53 PM
My first job (I still work at the same company but have changed teams/roles a lot) was building menu screens for a game. I was actually hired with no experience in the tools required for the job, but Flash and ActionScript are fairly easy to learn if you have a solid programming background. I was never given menial tasks (unless you count building menu screens as menial! Ha!)
I always had lots of mentoring (both in the areas I was working and in areas I wanted to work in), and was expected to mentor new hires as well. I obviously didn't want to be building menu screens as my entire life, and I was able to find an opening on another team in my company that let me get into other domains. A lot of my original teammates had trouble finding opportunities outside of front end programming and ended up leaving for opportunities at other companies out of frustration.
While I would say junior engineers would never be touching engine code, it doesn't mean that people fresh out of university would never touch engine code. However, they would likely not be hired on as a junior developer and would need to prove that they know what they're doing (likely having built their own engine in the past).
Posted 18 March 2014 - 04:10 AM
So...how did you find it, I assume most people started as a junior programmer. Did you ever feel out-of-your-depth, what kind of tasks were your set, I read that a junior programmer will generally never see any engine code, were you given menial tasks to do, did you get much mentoring and did you feel like you were learning and progressing in your skills or was it more a case of staying static.
My first job (in 2005-6) was the best I was working with - It had some romantic feeling when everything was new
I got weak skills (I knew the language but any of the api used) I usualy didnt understand much of the code i was supposed to 'extend', learned much, got very weak salary, fine pals to work with, ..and i was 10 years younger
It was all very fine..[sadly later it become worse,, i can do more but this energy usually was mostly gone] (probably depends on
the team and thw freedom and partying/academia energy if
present or muffled
Posted 18 March 2014 - 08:20 PM
Posted 19 March 2014 - 01:33 AM
I was always the strongest programmer in all of my companies until my current one, and as a result I feel my growth has been hampered. I have learned half as much in the last 2 years as I did in the previous 8 years (IE 2× as fast).
It is best to always try to find a company where people are better than you, if you can.
I was usually the weaker (or among the weakers) and I also felt that my growth was hampered by this fact; And i can say othervise: It is good (better?) to find acompany where people are not much better than you.
(In my first work all were juniors and it was great energy) <--
Form me usually unexperienced programmers were much better to talk with becouse they shared some romantic view on programming where experienced programmers I knew were more silent and not social
and not so fun (at all) to work with (there were also men in the middle state (half-seniors?) also less social-energetic then juniors)
Edited by fir, 19 March 2014 - 01:45 AM.
Posted 19 March 2014 - 10:31 PM
I agree with L. Spiro. I usually take this approach in every walk of life (be it academic, work, social). Thing is work with the best, because you can learn from them.
where experienced programmers I knew were more silent and not social
If experienced programmers are very anti-social, I guess it could be a problem. Though showing them that you are eager to learn generally helps. I had this superior once who was always easily angered, wanted to do things very quickly, and was very unpopular with the juniors (but not the superiors). Once I showed him that I was willing to learn, he softened up, and I learned buttsload of stuff from him.
These experienced ones generally have even more 'romantic view' as you say - they love what they do so much that they actually want to work with them all the time. What I do is show that I have the common interest in the field and they usually also get excited once I show I have the same viewpoint as them. At least, this works for me
GameDev.net™, the GameDev.net logo, and GDNet™ are trademarks of GameDev.net, LLC.