Link Details

Link 891277 thumbnail
User 448255 avatar

By dotCore
via java.dzone.com
Published: Dec 14 2012 / 01:27

I’ve always heard that it was difficult to move from QA into development (game design/programming/art/production). I thought this was smart- QA people should be there to be QA people, not doing a job only because they hope it would lead to something else.
  • 5
  • 0
  • 536
  • 517

Comments

Add your comment
User 226303 avatar

devdanke replied ago:

1 votes Vote down Vote up Reply

The answer to this question may vary by company and country. In the USA, if a company needs a developer and you can pass the technical interview, and seem like you can work with the dev team, then you'll get the job. Most USA businesses do not care whether you've been in QA or don't have a Computer Science degree. They care whether or not you can do the job. And your level of interest/passion for development work. But it's worth noting that, the insights gained from being in QA could make you a better developer. If you can convey that during the interview, that will help you. It also helps, when you are entry-level or moving into a new development area, to show code or projects you've worked on, that prove you can write the kind of software the company needs. When there's a high demand for developers and not enough talent out there (such as now, for mobile and big-data developers), then companies will give even unqualified applicants a try. So, when the market is strong for developers, that's the time to make your move.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (5)



Voters Against This Link (0)



    Node.js
    Written by: Bert Belder
    Featured Refcardz: Top Refcardz:
    1. Design Patterns
    2. OO JS
    3. Cont. Delivery
    4. Java EE7
    5. HTML5 Mobile
    1. Debugging JavaScript
    2. OO JS
    3. JSON
    4. Ajax
    5. REST