I love this, but it could go even further:

Blaine Cook was "rejected" from Twitter after years of hard work. But he faced an insane scaling problem, and most of us would look bad if we faced the same set of problems.

Steve Jobs was "rejected" by Apple after years of hard work.

Or my all time favorite:

John Lasseter was fired from Disney because he was too enthusiastic about cutting edge digital animation (rather than the traditional animation techniques for which Disney was famous), then he became head of Pixar, which got bought by Disney, and which took over Disney's animation, and so now he is head of animation at Disney. They fired him, but now he is back, and now he is in charge, because he was right.

Lots of great people do great work and then get fired. Getting fired doesn't mean they were wrong. Sometimes it simply means they were too right, and nobody wanted to hear it.

I was rejected by Adobe, Apple, Google, Microsoft, Twitter, Facebook, Amazon, Netflix, Skype and many more companies. I got rejected by Apple 3 times and two times with Facebook and Google.

I'm now working for Google.

One thing I can tell for sure, specially after interviewing others. It's all random. Most of interviewers make their mind about the candidate in seconds. If you are a charming person you have a good chance. If you are not a very likable person you have a very small chance.

This reminds me of an old zen tale:

>There is a Taoist story of an old farmer who had worked his crops for many years. One day his horse ran away. Upon hearing the news, his neighbors came to visit. “Such bad luck,” they said sympathetically. “Maybe,” the farmer replied. The next morning the horse returned, bringing with it three other wild horses. “How wonderful,” the neighbors exclaimed. “May be,” replied the old man. The following day, his son tried to ride one of the untamed horses, was thrown, and broke his leg. The neighbors again came to offer their sympathy on his misfortune. “Maybe,” answered the farmer. The day after, military officials came to the village to draft young men into the army. Seeing that the son’s leg was broken, they passed him by. The neighbors congratulated the farmer on how well things had turned out. “Maybe,” said the farmer.

The point being that when you become so upset with being turned down for a certain job you are setting yourself up to be let down by missing the big picture. The reality of the big picture is you have no idea how something that might seem like a great success might lead to great failure, or great failure might lead to great success.

Eventually these folks got accepted though. I guess that's the moral we're supposed to take away from this: If you get rejected a lot, but you keep trying, you'll eventually be accepted?

If so, that's bullshit. The only reason we don't see any examples here of people who never get accepted is because they're invisible to the industry. Many of them probably ended up committing suicide or switching careers. (I've contemplated both more than I care to admit in polite company.)

We can't all be winners.

(But by that logic, we can't all be losers all the time either. You're probably somewhere in between both extremes.)

I recently interviewed at very hot container startup. I had 1 phone screen, 6 on-sites, and 2 follow up phone calls. I did well in the phone screen to be invited onsite. Apparently, I did great on the 6 interviews onsite and then they wanted to have a follow up phone call with a manager (30 mins). That was positive too. But, the last phone call was set up with the SVP who determined that I was not a good "culture fit" after 30 mins on the phone. This in spite of me having had wonderful technical conversations and interviews (including coding) - which I apparently rocked- with 6 engineers and 2 managers, and having very highly relevant experience working in the cloud (orchestration and networking). The SVP just swooped in and decided I was not a good fit.

I simply don't get interviews these days. Sigh! On to a better company.

Interview processes are more about social skills than technical skill (even in engineering interviews). There is a huge amount of randomness involved - Maybe the HR person just didn't like your face!

It's mostly about understanding the company culture, reading the interviewer's face and trying to figure out what they want to hear as you go along (of course technical skills are a prerequisite).

The only time I didn't get an offer was because I asked for too much money. I think asking for more money is a good idea though; it weeds out all the frugal companies.

I think that if your success rate is 90%, it means you're not charging enough. You need to bring the price up and allow the success rate to drop - Then the average quality of offers will go up.

Companies keep files on candidates, which generally makes sense for tracking purposes, but they can be counter-productive at the big companies.

I go in and apply. I meet with 6 people out of thousands, representing 1-3 teams out of hundreds. It doesn't work out, for any of <n> reasons, some of them just luck of the draw. But now my interview is in the system and will be forever referenced. I'm given a polite but non-informational "it's not a fit" and sent off to a competitor.

Idea: Big companies shift to lighter-weight interviews which aren't considered final. If you're good enough to make it to on-site and it doesn't work out (but there was lots of reasons to think it would have), then you get happily scheduled for another round in a few weeks or whenever, and Company tries to not leave you with a stigma of rejection.

This frequently happens with executive recruiting, but not at lower levels. At least, I haven't seen it. Instead we get so many stories like on this website, where it should have been obvious just by CV/portfolio alone that they were awesome developers.

I have to say, after inheriting a code base from Max(@mxcl), its sad that anyone would reject him. Hes pretty much the guy that gave me the first sane introduction to cacoa programming. - That being said, I was rejected from a company because I hadn't used binutil in python. - I find I can pass any interview with a confident low voice more consistently than by showing my technical expertise. - People are interested in how well you assimilate into the culture of the workplace. Sometimes, that workplace culture needs to evoluve to include a more eclectic dev-background, or they risk alienating talented people. Alas, sometimes that evolution is not nessicary or its just to early for the company. - I've seen this happen to good devs and I've been on the receiving end of it. - Hiring isn't fun; you have to find someone who understands who you are. Inheriting trust is a lot faster then building trust and I find most companies don't have the time (sometimes ability ) to build that trust.

It's interesting how in our current time, if you work at Twitter, facebook, google, or a famous start up, it is synonymous to "I made it".

It happens the other way around also.

In an interview for a CTO type position a while ago, the only technical member of the interview panel was visibly aghast that I had never made a bootstrap theme - which, despite me explaining where that sort of task fits into the webapp ecosystem to the others, had already rubbed off on the rest of the panel. The extensive team/project building portfolio presented was irrelevant.

I thanked them for their time and didn't call back as I've had my fill of toxic work environments out there.

Being rejected from the top tier of technology companies and then landing in another top tier company doesn't seem so much like a genuine expression of angst over rejection but rather a bitter leer. But sure, the way work rejection is delivered is typically insensitive, and getting rejected sucks-- companies have no compassion for assets they don't want to use, and it's dehumanizing to realize you are utterly replaceable and plentiful as far as they are concerned.

The reason why there are so many rejections is because companies are trying to minimse the false positives instead of minimising the false negatives.

I'm a recruiter and I sometimes say that "recruiting is the business of rejection".

At any given moment I might have between 5 to 20 possible jobs that I'm searching for people for. In a given week I might receive 1,000 applicants.

It is incredibly hard to get anyone into a job and often great people are rejected for various reasons.

The Business of Rejection - that's recruiting.

I live in Zurich and I used to code for a living. Now, I hire engineers for different startups in Switzerland.

As I got deeper into IT-recruiting, I realised that candidate filtering at the top of the funnel is fundamentally broken. Especially in Europe companies expect a CS degree and don't appreciate self-taught skills as much as in the US.

I am trying to change this. If you look for a tech-job in the most liveable city in the world, check out my story "8 reasons why I moved to Switzerland to work in IT" on http://medium.com/@iwaninzurich/eight-reasons-why-i-moved-to... or send me a mail to the mail-address in my HN-profile.

Being rejected a few times this week, this makes me feel a bit better. For one interview ... my brain decided to take the day off ... nerves I guess ... it was not pretty. Any who (sic) ... the show must go on ... back at it tomorrow morning wish me the best.

Twitter - where most of these rejected people ended up?..

Someone I know at Facebook said that they have something called "Overheard at Campus" or something like that, where people post funny things they hear on campus. They said that recently one of the posts was: "I am going into an interview. I am pissed. It's gonna be a reject from me." Which pretty much underscores how interviewing appears to be these days, especially at a company like Facebook.

Thank you for this site! I am going through the interview process now and there are times where I feel like a fraud. Some call this impostor syndrome. It's encouraging to read others who have travelled the same path I've been on.

> I was rejected at Amazon and other companies with no technical interviews because I wasn't a Java engineer.

That one seems pretty legit to me.

It's interesting how all these top companies insist on JS expertise, I didn't know that it was so important for an interview and that's something I need to work on.

I love how Facebook HR rejected one of my acquaintances and then after he asked "Why?", the recruiter sent an email that was something along these lines: "Ok, may I schedule a technical interview in a week?".

Eventually he ended up being an engineer there.

My experience and rejection also indicated there's something arbitrary random going on in the interview process. Once a recruiter from Google commented my grades with a serious attidute, saying I should keep them as high (I was still a student) and I immediately realised that grades weren't even checked because my grades were horrible (GPA<3, ridiculous bible theology social classes ruined it for me) and if they cared I should get them higher.

It seems to me like that best predictor of whether you'll get the thumbs up is social cues, rather than anything technical.

I went to an on-site at a major company, and there was a guy who just wouldn't smile. He also led me down the wrong way on the tech part, which is easy when you make zero facial gestures and talk like a robot. I figured it out eventually, it wasn't hard, but he dinged me.

With the other people it was just a breeze. We chatted about various low level performance things, about how the work environment is, and so on. The tech parts were easy, because you could tell whether you'd actually understood the problem correctly.

I was rejected for grad school after submitting half-hearted applications and now work as a fullstack Haskell developer. I didn't even know I would find it as satisfying as research.

I just want to confirm the sentiment about how subjective interviewing is. I recently switched to using a coding challenge instead of a traditional interview loop. I would take candidates out for coffee pitch them the team and position, ask them some questions about themselves and then explain how the challenge would work. The first time I did this I decided to give everyone the challenge, even people I was sure were going to eat it, just to give myself some good data about how tough the challenge was and if it needed to be tuned. I was shocked by how bad my tech-radar really was. Not so much on the upper end, I can spot the winners still. However some of the people who I thought would eat it did a lot better than I thought they would. It made me realize how subjective interview loops really are, with little to no chance of the interviewer to be shaken out of their biases if they don't want to be. Not that coding challenges are perfect, but I'm never going back. I will refuse to participate in interview loops now - on either end.

I'd guess that over my nearly 20 year career, I've been rejected from more companies than most HNers have even applied to. I've listened to tons of employers tell me what they think I'm not capable of, and that was back when you would actually get personalized feedback from a failed interview. My grades, my lack of a "prestigious" education, my technical skills, my people skills, my background, my previous employment history, my potential, and, of course, the catch-all "cultural fit" have all been used as reasons that Company X was sure I'm an idiot. I don't let interview rejections bother me for even a millisecond anymore--it doesn't mean anything whatsoever, and I'm convinced getting hired at any given company is more of a dice roll than anything else.

I don't think it's bullshit. I also don't define people as "winners" or "losers" depending on whether they get cool jobs.

I think it's true you'll eventually get accepted in a nice job if you work in IT/software development, have a decent level of competency, and keep at it without getting too discouraged. It's easy to feel crushed when you get rejected twice in a row, so I think this is valuable lesson: you can have decent skills and you'll still get rejected (sometimes arbitrarily, sometimes because it just wasn't your best day), and you shouldn't feel crushed because interviews are -- sadly -- highly random, and even great developers get rejected. That's the point of the website: your skills are likely not the reason you got rejected, so don't get too discouraged.

This isn't some feel good bullshit philosophy. It's true. Getting a job isn't about being a winner. If you have decent skills -- say, you have some experience and fizzbuzz isn't a stumbling block for you -- you are already marketable. You just need to have the combination of luck/being prepared/being in one of your best days.

Exactly. These people are all from the first-world countries, they have plenty of opportunities to get hired so eventually they do. I was rejected by dozens of "cool" companies, almost never even getting to the technical interview, because they'd rather not hire a foreigner. I had to find a local job which pays me a wage most people here would consider laughable.

The takeaway (I believe) is that the process is _Random_

I take the odds as dating or finding a friend; in a large co., some times you may find the fit other times you may not.

Yep.

I had a two-year unemployment spell from 2010 to 2012. I applied to tons of jobs, and I got a bunch of interviews, but all of them rejected me until that very last interview at the end. And when I did get a job at the very end, it ended up being with a very young startup that never stopped having serious problems until I left them at the end of 2014 [0].

I was... not in a good state. Halfway through those two years, I had a nervous breakdown where I alienated a lot of people and lost some friends. It set my gender transition back by three years (I didn't even start thinking about it again until a year and a half after I was employed again). I thought about ending it multiple times. In fact, when I finally got my job after two years of unemployment... the day after I accepted the offer (the day of my in-person interview, I was given the offer and immediately accepted it) was the day I found out that my extended unemployment benefits had reached their end. If I didn't get that job, I wouldn't have been able to make rent at the end of the month, and I can guarantee that I would've killed myself rather than become homeless.

It also fucked up my emotional state so much that I stuck with my next job longer than I should have, that I made myself accept the downright abusive way my employer treated me, because my two years of unemployment made me feel so worthless that I felt like I didn't deserve a better job than the one I had. In fact, I believed I was truly stuck with that job, that it would never be possible to get something better. It took years for me to break out of that and actually find something better. It wasn't until after I left that I realized I was in the same mental state as a victim in an abusive relationship.

[0] Moving this to the end because it's long and ranty, but I need to get this off my chest. These serious problems include: being paid barely enough to stay afloat, no health insurance, no equity even for early employees, a verbally abusive boss who handled stress by taking it out on his employees, technical managers who made awful decisions because they had no management experience, a non-technical owner/CEO who refused to seek VC because he wanted to keep control so he had us constantly demo our product to rinky-dink angel investors over and over, an office in a building run by utterly terrible property managers (I have horror stories...), and management too cowardly to stand up for me when the property managers decided to discriminate against me for being transgender (I had to get the city involved, I did all the legwork myself, and I won despite our bumbling CEO almost accidentally sabotaging my case). I lived with all of this for almost three years because I honestly believed I was so broken that I didn't deserve a job at a company that wasn't abusive.

> I recently interviewed at very hot container startup. I had 1 phone screen, 6 on-sites, and 2 follow up phone calls.

Seems to me like you dodged a bullet.

> But, the last phone call was set up with the SVP who determined that I was not a good "culture fit" after 30 mins on the phone.

Why is an SVP spending 30 minutes on the phone with candidates that have already done eight interviews with the troops on the ground? You definitely dodged a bullet.

> 6 on-sites

I don't understand the point of multiple (or very long) interviews. If they can't decide after the first 30 minutes if the candidate is hirarable, they probably won't.

It's an illusion to think that interview environments relate directly to workplace performance. Interviews are mostly useful for the subjective parts than for grilling candidates in hopes of avoiding a bad hire. Going through all the hoops and knowing all the things doesn't make for a good employee. Not unless you're being hired as a robot worked in some factory floor.

Also, unlike what seems to be the general idea elsewhere on this thread, soft skills are very important, I argue even more important than hard skills. If you have any ability to learn (which may be considered a soft skill) you can pick up almost any technology and implement almost any algorithm. Not so if you lack the ability to relate to you coworkers, work effectively as a team, or clearly communicate your ideas.

You can learn tools, but you either have the right attitude or you don't.

Maybe you legitimately weren't a good fit? I'm not being facetious, but "the SVP was an idiot and made a terrible call despite all the evidence" is possible but not the most likely scenario.

Maybe someone with exactly your skillset and experience was hired, hated it, and quit after 6 months. Maybe one of the other people you interviewed with mentioned an offhand comment you made and it soured the SVP's expectation. Maybe they just got served divorce papers and were shitting on everyone that day?

It's so random that I don't even try to second-guess or deconstruct the non-technical side anymore. It happens or it doesn't.

starts with D, btw.

Are you sure?

At my previous company (a relatively small startup, admittedly), one of the indisputably best engineers (a 10xer if I've ever worked with one) was hired after such a "second shot". A few weeks is probably too rapid a turn around, given that a "failed" interview is a negative signal (or at least, should be That's the point, after all). But say, a year later for engineers in that wide fuzzy area between "Hire!" and "Oh god no!"? I think plenty of companies do do that.

Further anecdata: Friends who've been rejected from Google have told me that they were explicitly encouraged by their Google recruiter to re-apply in ~a year.

This happens at the developer level too. Of course, occasionally there may be a candidate who is just not there yet. So companies ask you to wait, some for X months other for X years and then reapply. An engineering position is sometimes about the skill sets; my team looks for ML and Data folks. But sometimes it is also about solid engineering chops and some people just need to work more on those. That is not a bad thing; it is just a thing.

I've never had a job where I was required to code in JS. However, I have had one interview where I went headfirst into SCSS when the job actually only required C/C++ skills (it was work on a computer vision system).

The thing is, I think most interviewers ask for what they are most comfortable with, so they can evaluate. Which is why questions related to JS are probably so common for companies like Google, Facebook, Twitter, etc. even if you don't actually need it or use it.

However, I would also point out that JS is pretty easy, if you know any of the standard languages you'll be fine. Although, I do find it humorous because JS is basically one of the worst constructed languages I know of (even though I use it daily...).

Dude you'll always have to do something with HTML/CSS/JS. Even if its not your main gig. Luckily all three are fairly simple. Just go make a simple webapp without any libraries and from that you'll pick up 99% of what you'd need to know.

Author of project is part of JS community on Twitter.

If you have no JavaScript these days then largely you can forget job hunting.

If you have awesome, expert, deep, deep JavaScript then firstly you might as well be a unicorn but secondly, you will get a job.