Get to Know Eric Elliott
Take the time to check out the resources available online to determine whether or not Eric’s technical skills are a good fit for your project prior to scheduling interviews. There is plenty of material available online to make this determination. During the actual interview process, the most efficient use of time is to talk about real life problems you are tackling right now.
Line up a series of technical whiteboard / brain-teaser screening interviews with your company’s brightest engineers. Please read “The Technical Interview is Dead, and Nobody Should Mourn.” It doesn’t matter if that’s your company’s standard procedure. Broken processes should be fixed. Consider this Eric’s first contribution to your company culture: The right way to evaluate an engineer is to collaborate on a real world problem. Do some pair programming. Please read “How to Conduct a Better Coding Interview.”
Recruiters: Please Read
Here’s the honest truth: Tech recruiting is an industry desperately in need of disrupting. All seasoned developers with a sizable online footprint and publicly available contact information have to wade through giant pools of recruiter spam to find any real opportunities. If it’s obvious that you don’t know who you’re talking to, your copy-and-pasted job post won’t ever reach Eric’s inbox. He prefers to communicate with top decision makers at a company and tackle the company’s biggest tech challenges to maximize his contribution. Finding the mission is a process, not a job post.
Working with Eric’s Agent:
Some people pride themselves on answering their own email, and Eric has a very profound respect for them, but chooses to work differently. When you contact Eric, you’ll actually be contacting his agent first. She’s amazing at spotting great mutual opportunities, and manages all of Eric’s meetings and bookings. Eric is freed up to do more of the things he is passionate about, like tackling the world’s hardest problems or teaching people how to code.