Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Honestly, if you yourself aren't a flash developer, I'd caution against interviewing a potential Flash developer, unless you're only doing it to get a sense of their character (as opposed to their skill level). Experience in working with the technology is going to give you a much more realistic perspective - blindly asking questions that other people told you are good ones to ask will get you into trouble.</p> <p>That said, if you can find someone you know to sit in on the interview with you and provide evaluation from a technical standpoint, here's a few things I'd remind them to ask:</p> <ul> <li>object oriented programming</li> <li>loading external media</li> <li>audio &amp; video playback (also maybe volume control / mixing)</li> <li>event listeners</li> <li>transitions / animation</li> <li>filter / sort algorithms</li> <li>common UI elements: scrollbar, form elements, drop-down menu, rollover states, drag-and-drop, etc.</li> </ul> <p>Those are sort of generally useful areas of knowlege, but the true test of profficiency is a practical test - "write a class that meets these requirements", or "this code isn't working, find out why and fix it" are good ways to immediately gain insight into the candidate's work (and thought) process.</p> <p><strong>Most importantly:</strong> even if the interviewee is short on specific knowlege or experience of the subjects you settle on, it's better to get someone who is a fast learner and will easily comprehend new concepts then to get someone who might know a lot now, but will resist learning new stuff.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload