18:30 Doors open
19:00 Talk by Yervant Kulbashian

"Describe what a Content Provider does, then never use one again for the remainder of your career."

Developer interviews are notoriously bad predictors of job performance. Companies regularly employ an ad-hoc cocktail of irrelevant quizzes, burdensome assignments, and inapplicable whiteboard problems to screen potential candidates, hoping to separate the code ninjas from the amateurs.

But how much of this actually works? How well do whiteboard tasks correlate with on-the-job productivity? How can you ensure you don’t reject great candidates based on little more than a - possibly biased - intuition? How can you show declined candidates the path to improvement, and help them to succeed in the future?

“We’ve decided not to go ahead with your application at this time.”
“Why?”
“I don’t know. I’m the hiring manager.”

The goal of this talk is threefold:

• To help you clarify what you are trying to discover from an interview,
• To define best practices that surface promising candidates,
• To leave all candidates feeling fairly treated, regardless of the outcome.

Based on a decade of corporate research, as well as my own, and my peers' experience hiring Android devs across three companies, this talk presents a practical approach to hiring your next Android dev, one that ensures even rejected candidates hold your company in high regard.