Skip to content
loading...
markdown guide
 

Pre-interview:

  • Evaluate your realistic chances of landing the job. Some factors to consider: experience with relevant technologies, your understanding of their business, product etc, past interview/coding test results, how desperate they are to fill the position. This might help cushion the blow afterwards.

  • Think rigorously and ask yourself if you're a good fit as per the JD and whether you even want the job.

Post-interview:

  • Insist on them (politely) to give you meaningful, constructive feedback.

  • Follow their advice and don't rush to applying for other similar openings until you know you've covered some ground.

In general: contemplate, look at the bigger picture and consider the billions of people who don't enjoy a fraction of the privilege, opportunity or wealth that most of us do. Didn't get a callback from Morgan Stanley because Bjarne Stroustrup thinks you don't know jack about the C++ STL? Compare that to the basic living conditions of the vast majority of the world.
You'll be fine and your life will most likely improve, not decay. Perspective always helps.

 

Perspective always helps.

Thanks! Will try to look at the bigger picture and improve.

 
 

As you unfortunately always get some sort of generic rejection email without any specific feedback, I try to document everything I remember from the interview / application process that might have contributed to a rejection - e.g.

  • what went wrong during the interview itself
  • specific questions I couldn't answer (well)
  • typo on resume

And then I try to move on as fast as possible. I try to remember that there are a lot of other awesome opportunities out there that I might not even know of yet and that I am already improving myself by having taken notes what went wrong this time. But of course this is easier said then done.

 

The worst if you don't even get a rejection email not even a generic one.

 
 

Facebook rejected me last summer. I took all of the questions they asked me and worked through them on my Medium account. I was able to monetize the articles and get paid to help others succeed where I failed.

Just patch the holes, share what you've learned, try to make a buck, and move on to the next thing

Classic DEV Post from Nov 30 '19

Does your background make your work unique?

What's the skill, hobby or weird habit that makes your work unique?

Bence Hornyak profile image