What kind of CV is the best for the job? JOB: Java programer. J2ME platform. Mobile Handsets. Port. IA. and so

I'd look for people with experience with embedded programming. Fresh-out-of-undergrad kids who learned that good Java is a matter of making as many classes as physically possible, and never questioned it, are not going to do well with J2ME. THIS is the sort of job where I'm going to grill applicants about stupid binary tricks... they don't have to know Java, but if they don't, they should be the sort who could pick it up in a day or two. And, as always, a programmer who can't code to design or who can't code with a team is worthless.

I wouldn't insist much on the Java part by itself... because Java programming for mobile ends up looking like many other things except Java mostly because of all the optimization tricks you use. On programming for mobile the first thing you notice is that too many classes = overhead.

You need people with great optimization skills who can quickly understand weird source code even if there is not comments available (So you need people with great logic skills).

Usually those things are not going to be on a CV, I think you'd better select some of the applicants and have something to test for their skills. Ask for questions that need to be solved with logic, some programming questions where you look at the optimization (memory wise and "speed" wise) of their code.

If you're not a programmer yourself maybe get a lead programmer or another programmer to build the test. I'd say that for mobile gaming C++ or J2ME skills are realy good, porting skills is also good and familiarity with Java and mobile handsets is a plus. And make sure they can learn quickly if they don't know the technology you are using.


JFF

thanks for the comments guys.

Question, how can i test their learning skills, or logic skills for example?

Thanks

Quote: Original post by Goguigo
thanks for the comments guys.

Question, how can i test their learning skills, or logic skills for example?

Thanks

There are some (very expensive) companies who do this sort of testing, and it isn't all that useful.

To figure it out with experienced people isn't hard. Question them on the projects they have done, what exactly they did on those projects, the problems they faced on them, and how they handled it. You can keep asking questions until they have difficulty answering so you get a good feel of how and what they thought.

Figuring it out with inexperienced people is harder. There is much more risk involved. You can ask them questions about what they learned, how they learned it, then ask difficult questions to see the depth of their knowledge. Complex questions about real-world problems will help you see their reasoning skills.