Game Career Guide is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Get the latest Education e-news
 
  • Rare's Nick Burton on Getting Into Programming

    [11.02.07]
    - Jill Duffy

  •  Nick's Top CV/Resume Tips

    1. Have good grades and put them on your resume.
    2. List the right skills. You must aim the right kinds of skills you have at the right developer. "If at first you don't succeed, try again and try for the right developer."
    3. Be concise. The person reviewing the resume may be reviewing a stack of them. Highlight your outstanding skills. "This is me; this is what I can do well."
    4. Relevant project work. Tell about the details of one project, and make it the one that's most relevant to the job you're being considered for.

    Nick's Top Application Tips

    1. Target your application.
    2. Be honest.
    3. Provide back-up material (demo reels, portfolios). Highlight these in any applications.
    4. Include demo work. "There's lots of different kinds of demo work, but include your best work, and only a bit of it." As part of that, when showing a group project, identify what you did. "Make sure you include code samples and write a covering letter or FAQ with it."

    Nick's Top Interview Tips

    1. Create a good impression. Show up on time. Turn up clean and tidy, but don't wear a suit. "I say this because people don't."
    2. Relax. "The most important thing -- I can't stress this enough; it should be in flashing neon letters -- try to relax. By the time you get to this interview, everyone wants you to do great in the interview." If you're in a firing squad-type of interview, bear in mind that you can ask yourself whether you really want to work with the kind of people who would put you through a tumultuous experience when they know you're likely to be nervous.
    3. Expect to be tested or given an entrance exam. "It's normal. It's normal for almost all developers to do this now. All we're trying to ascertain is whether what you've said on your CV is true." Brush up on your core skills, and review your math and logic.
    4. Be yourself. "This is of the utmost importance. We're trying to find out who you are. Don't try to be the person you think the interviewer wants you to be." You're not expected to be great right off the bat -- only to have potential.

Comments

comments powered by Disqus