Announcing the interviewing.io Technical Interview Practice Fellowship

By / September 16, 2021

I started interviewing.io because I was frustrated with how inefficient and unfair hiring was and how much emphasis employers placed on resumes. But the problem is bigger than resumes. We’ve come to learn that interview practice matters just as much. The resume gets you in the door, and your interview performance is what gets you the offer. But, even though technical interviews are hard and scary for everyone — many of our users are senior engineers from FAANG who are terrified of getting back out there and code up the kinds of problems they don’t usually see at work while someone breathes down their neck — interview prep isn’t equitably distributed. This inequity never really …

Announcing the interviewing.io Technical Interview Practice Fellowship Read more »

interviewing.io is finally out of beta. Anonymous technical interview practice for all!

By / September 16, 2021

I started interviewing.io 5 years ago. After working as both an engineer and a recruiter, my frustration with how inefficient and unfair hiring had reached a boiling point. What made me especially angry was that despite mounting evidence that resumes are poor predictors of aptitude, employers were obsessed with where people had gone to school and worked previously. In my mind, any great engineer, regardless of how they look on paper, should have the opportunity to get their foot in the door wherever they choose. So, we set out to build a better system. On interviewing.io, software engineers can book anonymous mock interviews with senior engineers from companies like Facebook, Google, and others, and if …

interviewing.io is finally out of beta. Anonymous technical interview practice for all! Read more »

The Eng Hiring Bar: What the hell is it?

By / January 14, 2021

Recursive Cactus has been working as a full-stack engineer at a well-known tech company for the past 5 years, but he’s now considering a career move. Over the past 6 months, Recursive Cactus (that’s his anonymous handle on interviewing.io) has been preparing himself to succeed in future interviews, dedicating as much as 20-30 hours/week plowing through LeetCode exercises, digesting algorithms textbooks, and of course, practicing interviews on our platform to benchmark his progress. Recursive Cactus’s typical weekday schedule Time Activity 6:30am – 7:00am Wake up 7:00am – 7:30am Meditate 7:30am – 9:30am Practice algorithmic questions 9:30am – 10:00am Commute to work 10:00am – 6:30pm Work 6:30pm – 7:00pm Commute from work 7:00pm – 7:30pm Hang …

The Eng Hiring Bar: What the hell is it? Read more »

No engineer has ever sued a company because of constructive post-interview feedback. So why don’t employers do it?

By / February 16, 2021

One of the things that sucks most about technical interviews is that they’re a black box—candidates (usually) get told whether they made it to the next round, but they’re rarely told why they got the outcome that they did. Lack of feedback, or feedback that doesn’t come right away, isn’t just frustrating to candidates. It’s bad for business. We did a whole study on this. It turns out that candidates chronically underrate and overrate their technical interview performance, like so: Where this finding starts to get actionable is that there’s a statistically significant relationship between whether people think they did well in an interview and whether they’d want to work with you. In other words, …

No engineer has ever sued a company because of constructive post-interview feedback. So why don’t employers do it? Read more »

We ran the numbers, and there really is a pipeline problem in eng hiring.

By / February 25, 2021

If you say the words “there’s a pipeline problem” to explain why we’ve failed to make meaningful progress toward gender parity in software engineering, you probably won’t make many friends (or many hires). The pipeline problem argument goes something like this: “There aren’t enough qualified women out there, so it’s not our fault if we don’t hire them.” Many people don’t like this reductive line of thinking because it ignores the growing body of research that points to unwelcoming environments that drive underrepresented talent out of tech: STEM in early education being unfriendly to children from underrepresented backgrounds, lack of a level playing field and unequal access to quality STEM education (see this study on …

We ran the numbers, and there really is a pipeline problem in eng hiring. Read more »

3 exercises to craft the kind of employer brand that actually makes engineers want to work for you

By / January 14, 2021

If I’m honest, I’ve wanted to write something about employer brand for a long time. One of the things that really gets my goat is when companies build employer brand by over-indexing on banalities (“look we have a ping pong table!”, “look we’re a startup so you’ll have a huge impact”, etc.) instead of focusing on the narratives that make them special. Hiring engineers is really hard. It’s hard for tech giants, and it’s hard for small companies… but it’s especially hard for small companies people haven’t quite heard of, and they can use all the help they can get because talking about impact and ping pong tables just doesn’t cut it anymore. At interviewing.io, …

3 exercises to craft the kind of employer brand that actually makes engineers want to work for you Read more »

You probably don’t factor in engineering time when calculating cost per hire. Here’s why you really should.

By / January 14, 2021

Whether you’re a recruiter yourself or an engineer who’s involved in hiring, you’ve probably heard of the following two recruiting-related metrics: time to hire and cost per hire. Indeed, these are THE two metrics that any self-respecting recruiting team will track. Time to hire is important because it lets you plan — if a given role has historically taken 3 months to fill, you’re going to act differently when you need to fill it again than if it takes 2 weeks. And, traditionally, cost per hire has been a planning tool as well — if you’re setting recruiting budgets for next year and have a headcount in mind, seeing what recruiting spent last year is …

You probably don’t factor in engineering time when calculating cost per hire. Here’s why you really should. Read more »

Scroll to Top