Preparing for the future

A complete random mess

Technical interviews suck. Even companies that have extensively studied and refined their process agree: there is no real correlation between interview performance and job performance.

Years ago, we did a study to determine whether anyone at Google is particularly good at hiring. We looked at tens of thousands of interviews, and everyone who had done the interviews and what they scored the candidate, and how that person ultimately performed in their job. We found zero relationship. It’s a complete random mess, except for one guy who was highly predictive because he only interviewed people for a very specialized area, where he happened to be the world’s leading expert.

This shouldn’t be surprising. The requirements of a typical coding interview demand an ability to think quickly, verbalise one’s entire thought process, find an optimal solution within a few minutes, and write and debug code without the aid of a compiler. The real world technical demands of an engineering position require an ability to think slowly, build prototypes, test, refine and iterate. It should be clear just from this that interviewing at a tech company is a skill in and of itself.

I’ve conducted many hundreds of technical interviews. Even with that experience, my own career success rate — interview panels which led to me receiving an offer — is only something like 70%. And not all those failures were early on in my career.

Still, it’s a very hard ask for tech companies to hire an engineer without knowing if they can write code. And so, almost every tech company requires at least one coding interview for an engineering position, and many place a technical phone screen as the first hurdle before even getting to an on-site panel. This is the case even at Medium, where we’re constantly trying to improve our interview process.

Fortunately, these interview skills are learnable. Unfortunately, most people don’t have many opportunities to practise, except when under the pressure of interviewing for a real job that they really want. I failed my first two technical interviews in the Bay Area many years ago. Students applying for internships or first positions have a particularly hard time of it.


The diversification imperative

As has been stated and re-stated many times over the past few months, our industry is still overwhelmingly white and male. There are significant structural and societal hurdles that make it harder for people who are not cisgendered white men to get into, and then succeed at, a career in engineering. If you aren’t convinced of this yet, I’d like to suggest you read more from smart people like Ashe Dryden and Marco Rogers.

I’m convinced. I really believe this hurts our industry, and impedes our collective ability to innovate. As Carvell Wallace said recently at AlterConf:

People are only good at solving the problems they have.

How are we to create products that address the needs of, for example, young black women, if we don’t have any in the industry? If you’re not convinced by the moral or social justice imperative, you can at least be convinced, I’m sure, by the economic one. Besides, homogeneity is boring.


Making a start

There are many fine organisations working to address this imbalance, including Black Girls Code, Women Who Code, Tech Superwomen, and CODE2040, with whom I’m proud to say that Medium is partnering this summer as a host company for three fellows.

But outside of these organisations, what can we do individually to address this issue? Something, at least.

A recent mock interview arranged by CODE2040 between myself and a young candidate convinced me that I can help by preparing students for their first technical interviews.

So, starting next week, I’m going to be blocking out an hour of my time each day at 12pm PST to offer free mock engineering interviews to current Black and Latino/Latina CS students who want to pursue a career in engineering.

The mock interview will take place over Google Hangouts and will last an hour, during which time I’ll walk you through an example format of a technical phone screen. I’ll ask a coding question and try to help you get comfortable with thinking out loud, narrowing in on a solution, and writing code in a shared coding environment. I’ll tell you the kind of things I look for in a candidate, and how you can make it easier for the interviewer to say “yes”. There should also be time to answer any other questions you have.

This will obviously be drawn from my personal experience on both sides of interviewing, but hopefully much of it should be transferrable to the general case.

There will be no charge.


Caveat emptor

Medium wholeheartedly endorses the mission of greater diversity in the workplace, but this mock interview program is a personal endeavour. In line with the distributed authority we enjoy here, I haven’t asked anyone here for permission to do this (though knowing our team, I’m sure they are going to be supportive). Suffice it to say, though calendar invites might come from a Medium email address, and I might call you from a Medium laptop, this is not an official Medium program.

A mock interview with me is not an interview for an internship or full-time position at Medium. Applications for Medium’s Summer 2015 intern program are closed. We are hiring for full-time positions, but to avoid a conflict, you should not take a mock interview from me if you are planning to apply to Medium soon — I do a significant amount of the first round technical phone screens here.

Though I’m pretty well-calibrated on what makes for a good interview, a private endorsement from me that you did well in a mock interview should not be construed as a guarantee that you’ll succeed elsewhere. I hope I can help, but your mileage might vary. If there was an Apache license for this kind of thing, that would probably cover it.

Also, it’ll be lunch time, I might be eating.


Let’s do this

With all that said, if you qualify, you’re ready, and you’re interested, you can request a time here:

www.meetme.so/majelbstoat

I look forward to speaking with you soon!