DEV Community

Discussion on: DISCUSS: Technical Interview Horror Stories

Collapse
 
sherribooher profile image
Sherri Booher

I have also been horribly underprepared for a technical interview due to recruiter incompetence. I was told that the company I was interviewing with was not worried if I wasn't 100% comfortable with advanced JavaScript code and/or whiteboarding. When I went into the conference room for the interview, the first thing the interviewer did was write a problem on the whiteboard and then told me to open my text editor and code the answer. He then proceeded to stand behind me/sit beside me, practically breathing down my neck, and watch me. Then, as soon as I started coding, he said to me, "Talk out your thought process." I immediately went blank. It was the most horrible experience of my life...and I had to sit in the parking deck in my car crying for 15 minutes before I could even get myself together enough to drive on the freeway. I'm not spooked and don't know if I even want to try again. I know I shouldn't give up, but how do you get over something like that?

Collapse
 
zacharythomasstone profile image
Zachary Stone

I'm really sorry you had to go through that. That is terrible.

Actually my previous employer didn't even do a technical interview, hired me saying they thought I would be a good culture fit, then expected me to act as a Senior Dev on my team when I only had 1 year of experience.

Throughout some of the worst interviews and job placents even, I've learned that many companies do not understand development. They assume a lot, and have expectations that are outrageous. However, there are companies that do understand hiring a JR Dev is an investment.

For me, I beat myself and blamed myself for failing. In reality, they failed me. They didn't provide a platform for me to thrive, to learn, and to have healthy critique. But even when I left, my experiences left with me. My value wasn't diminished, quite the opposite. These horrible situations would help me to have a much better perspective and I know will be used to encourage and shape the Dev community as a whole.

Your experience sounds like the recruiter was willing to say anything to make you apply so they could get a commission. While the employer interviewing you was expecting to pressure you into performance. Not meeting you at your level, seeing your value and asking how they could benefit from your skills. If anything, chaulk these experiences as being thankful you weren't hired on, and you were spared from working for a company that acts that way.

Thread Thread
 
sherribooher profile image
Sherri Booher

Thank you, Zachary. I really appreciate your kind words. I'm trying to chalk it up as a positive that I now know I don't want to work for a company like that, but it was still just an awful experience and I think a lot of interviewers do enjoy trying to pressure junior developers into high performance. In my experience, however, it leads to just the opposite. The interviewer even had the nerve to ask me on the way out, "What would have made this interview easier for you?" Which I'm sure he took into the next interview with the next candidate, who probably got the job. It just sucks.

Thread Thread
 
zacharythomasstone profile image
Zachary Stone

Yeah, that isn't something someone should have to ask. I have found a lot in our industry has a difficult time with human interaction, not coming off abrasive with their words. My first mentor in my bootcamp would yell "STOP! Why are you writing that! It's terrible!" when I would do a live coding with him. I would freeze up, take it personally, and not be able to process the problem anymore.

I think imposter syndrome is a common buzz word in our industry because of these experiences.

Some practial things I do to help:

  • I am choosey with what companies I apply for.
    What I mean is, I may interview with them, but my thinking isn't if they like me but if I want to work for them. I have a trade, a skill and it's valuable. I can't down myself for my mistakes and throw out that value, it's there. So I can be choosey with the companies I want to work for.

  • I am choosey with the recruiters I work for.
    I have a list of three or four recruiters that I know care about me and my personal development. I actually keep in contact with them often even though I am not looking. I like to send other devs I know that are looking their way occasionally.

  • When I do land that job, I find ways bridge the gap between development and the rest of the departments.
    There is so much misinformation and assumption when it comes to the Dev team and how they work, doing this helps fix peoples expectations.

Some mantras I live by:

  • Assume the best in people.
    So although the intervewee came across as completely abrasive and rude, he most likely didn't mean to. I am sure he wanted to give you a good interview, but just isn't skilled in it. I know I have seen Devs at my first job who struggled with the balance of helping. One would let me squirm all day, and wouldn't throw me a bone.. while the other would over help and write the code for me.

  • Your value and worth isn't dependant upon if others see it or not.
    You are smart! Yes you are. You are creative! Yep... I am talking to you. But you can be your worst critque. Celebrate the small victories. YOU had a ROUGH interview, but you made it through and are still programming, even through you are scared from that experience. You are strong to get through that.

And, even if the interviewer used your advice and the next person got the job, you can still be thankful you didn't. No experience is wasted.