0
\$\begingroup\$

As someone involved in the hiring of engineers that must have experience using NDK (I work for Unity and support the VR/graphics groups), I see quite a few resumes of people who claim to be using NDK and c++ but at the same time reference the use of JNI. I thought JNI basically made it possible to use NDK using java without using c++. Any thoughts? ( I know I am a recruiter but I am not using stack overflow to recruit, rather, better understand the very technologies I am working around every day. I appreciate your help in advance )

\$\endgroup\$
  • \$\begingroup\$ If you're looking for a C++ developer, why would you even consider hiring Java developers? They aren't inferchangeable \$\endgroup\$ – Bálint Mar 1 '18 at 7:40
  • \$\begingroup\$ If you're asking for details beyond the Java JNI vs. Android NDK post SO, please clarify. Might disagree with @Bálint - knowing JNI doesn't preclude experience with NDK. That being said, if NDK experience is 'must have' advertise accordingly. Some of job seekers fear aggressive keyword filters & tend toward over inclusion; then again, some get real loose with the truth in an attempt to get in the door. Hiring is difficult. \$\endgroup\$ – Pikalek Mar 1 '18 at 14:47
  • \$\begingroup\$ we arent considering hiring java developers. My questions wasnt if the two languages are interchangeable. Pikalek- Hiring is difficult but you answered my question...much thanks :) \$\endgroup\$ – AnimErin Mar 2 '18 at 20:55
  • \$\begingroup\$ @AnimErin Glad it helped. I hadn't meant to answer per say in comments (which is less than good form), so I've provided a proper answer. \$\endgroup\$ – Pikalek Mar 7 '18 at 16:46
1
\$\begingroup\$

Hiring is difficult. I commend that you are taking the extra step to familiarize yourself with these sorts of software engineering details.

As you observed, the two languages aren't interchangeable. However, knowing JNI doesn't preclude experience with NDK, or vice-versa. In fact, it might be preferable to note applicants that are familiar with both. For instance, most high level language programmers don't strictly need knowledge of assembly level programming, but those who do may be more versatile. Having some awareness of what happens outside your required knowledge domain can give you insight toward performing better inside your knowledge domain.

Ultimately, if NDK experience is 'must have' requirement, advertise accordingly. Some of job seekers fear aggressive keyword filters & tend toward over inclusion in an attempt to avoid being screened out. On the other hand, some applicants get real loose with the truth in an attempt to get in the door. Clearly signalling the job requirements (I.E. 'must have NDK experience') is probably the best way to avoid losing qualified candidates. After that, advertising time/space/$ permits, stating that 'JNI by itself is not sufficient' may help focus your candidate pool.

.

| improve this answer | |
\$\endgroup\$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.