Full Stack Developer. 👩💻 realtoughcandy groupie. In love with music. Although I've been known to listen to GnR (Guns n' Roses), I'm a bigger JNR fan...JavaScript, Node, React.
Location
Atlanta, GA
Education
Bachelor of Science: Information Technology (Kennesaw State University)
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.
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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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.
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.