Ever feel like you've been thrown to the wolves when it comes to assessing and sourcing candidates? Hiring for
technologies you've never heard of, being expected to master tools you've never used, and tying in marketing skills in your job posts and sales skills in your phone screens? It's a great deal to keep up with. Sometimes, you may identify with the classic Abraham Lincoln quote: "Better to remain silent and be thought a fool than to speak out and remove all doubt."
To help out, we've compiled a list of some questions you may be afraid to ask, but still need answered, so you neither have to remain silent or be thought a fool.
What's the difference between Java and Javascript?
These are two distinctly different languages, and just because a candidate knows one doesn't mean they're fluent in the other. Essentially, their similarities end after the name--like ham and hamster. Java is a programming language used to build web-based applications. Many consider it overkill for smaller apps, so Java is most useful for larger applications on high volume, high security sites.
Javascript, on the other hand, is code written for the front end of sites, used to affect display and interactivity with various areas on the page. Finely written Javascript allows you to interact with the page without reloading, for example, posting a comment on someone's Facebook status.
An experienced Java developer gave a much more technical description of the difference over on Quora: Read Quote of Joshua Engel's answer to What is the difference between Java and JavaScript? on Quora
What does full stack really mean?
A true full stack developer may be the rarest of all tech talent. This essentially means an individual who can see a process through all the way from network and server set up, data analysis, a business-minded sense of product value and use cases, product building, testing, user interface, and user experience. This is an extreme example of an all-powerful type of engineer, but put most simply a full stack engineer is someone who can tackle any tech problem, even if it's traditionally a bit outside their comfort zone.
What's the difference between UI and UX?
When recruiting Designers, it's important to know a bit about their specialty for two reasons. First, without an appropriate understanding of their abilities, you'll never be able to accurately assess them for your roles. Second, the fastest way to turn off talent is to have no true understanding about what it is they actually do. Here's a slide from an Entelo webinar explaining the difference between UI (User Interface) and UX (User Experience):
What's an X-Ray search and how do I build it?
Boolean search, a process sometimes called X-Raying, is a huge weapon in a recruiter's arsenal. Essentially, it allows you to create extremely precise searches of sites like LinkedIn, Github, or StackOverflow, and use the pages Google has indexed to locate candidates you might not normally surface. Building a search like this from scratch can be confusing and time consuming, so your best bet may be to use an existing string and edit it to include a specific location or title that's most relevant to your open role. This eBook can get you started with Boolean Search, and this blog post has X-Rays for a few sites that you can tailor to your own needs.
Are there any other tech recruiting questions you're itching to ask? Leave a comment or tweet @EnteloRob!
