DEV Community

Cover image for I failed a coding Interview ๐Ÿ˜ž
Ojay
Ojay

Posted on

I failed a coding Interview ๐Ÿ˜ž

โ€œHi Oj, thanks for meeting Matt today for a second interview. After careful consideration, we decided not to move forward at this momentโ€ฆโ€

This is a response I received from a CTO looking to hire a React Native developer. So, what did I learn?

As a Nigerian living in Nigeria who is trying to switch jobs with an offshore company or start a career with an offshore company, It can be discouraging to hear comments like "So you have to be in the US for this job" or "we assumed you are in the US" despite the remote tag in the job description and even after a series of conversations with recruiters/hiring managers and attempting to pitch yourself and your skills; this could even be after you have scheduled a call or gotten on a brief Introductory call.

But, unlike so many prior interactions with recruiters/hiring managers, this was not the case this time, because this specific company was more concerned with your competency than your location. After an initial introductory call with the CTO, who seemed very cool, I believed this could be a good team to work with because the personality of an organisation's leader can reveal a lot about its working culture. I was already imagining myself working with this amazing team.

I was thrilled to learn more about the technical interview requirements, which turned out to be a React test rather than the more conventional algorithms test. I believe myself to be a proficient React developer and have worked with a few teams.

Fast forward to the feedback after the technical Interview.

โ€œHi Ojonugwa, Thank you for taking the time to interview at XYZ company (intentional omission). Unfortunately, we will not be moving forward at this time. I wish you the best in your future endeavours.โ€

Feedback like this can cause you to go to bed earlier than you intended. Could it be that I was nervous or rusty from attending live-in technical interviews? I thought about it for a while before deciding to contact the CTO once more.

โ€œHello, Apologies for bothering you, but is it possible for me to retake the technical interview?ย  I believe it would only be reasonable to request the opportunity to participate in another technical interview given that I consider myself to be a good developer and have been a part of a few teams that have developed decent products that have scaled. I admit to feeling nervous during my most recent attempt because it had been a year since my last live coding interview, hence the performance. I look forward to your response :).โ€

To my amazement, the CTO agreed to a second interview.

This time, I practiced a little based on my prior experience and concentrated on the nervousness that comes with technical interview time limits.

Fast forward to the feedback after taking the second technical Interview.

โ€œHi Oj, thanks for meeting Matt today for a second interview. After careful consideration, we decided not to move forward at this moment. Feedback was similar, we believe you are a knowledged developer, but the way you structure your components and your problem-solving procedures can be improved. Thanks again for being interested in XYZ company (intentional omission), best of luck!โ€

This time, instead of being hard on myself, I opted to carefully consider the CTO's feedback.

So What did I learn?

  • Technical interviews focusย on your problem-solving approach rather than merely your ability to complete the given tasks.
  • Try to demonstrate your technical prowess in your code rather than applying the quick fix to the task at hand.
  • As much as possible, communicate your steps and intentions aloud.
  • Prior to the interview, enquire as much as you can about the requirements and the other things they expect to see from you outside your ability to do the task at hand.

Importantly, honest and detailed feedback should drive you to continue learning and improving your competence.

Latest comments (41)

Collapse
 
adrianacamarotto profile image
Adriana Camarotto

Good luck in your journey!

Collapse
 
vinsa profile image
Vinod vasava

Keep it up.....keep learning

Collapse
 
camouflagedname profile image
camouflagedName

I appreciate the focus on how humbling the experience can be, even for an experienced programmer.

As someone who has seen plenty of those responses, this brings me some peace of mind. Never stop.

Collapse
 
khuongduybui profile image
Duy K. Bui • Edited

I agreed with everything you said except for this.

Try to demonstrate your technical prowess in your code rather than applying the quick fix to the task at hand.

Do neither. Instead, solve the exercise as if it's a real task you are going to solve on the job. Show your consideration for maintainability, extensibility, security, scalability, performance, etc. If you don't have enough time to take care of something, add an in-code comment or at least say something to the interviewers about it. That is how I usually tell junior developers from the more mature ones: the juniors focus solely on coding while more mature ones consider other aspects of building a system. Senior ones will have to consider even more, like deadlines and business objectives, and are able to make reasonable (and later amendable) compromises when needed.

Collapse
 
oj_redifined profile image
Ojay

I totally agree with you, @khuongduybui... This serves as a more illustrative example of my summary. Thank you

Collapse
 
ayodejii profile image
Isaac Ayodeji Ikusika

keep going bro, you will get there. ๐Ÿ‘๐Ÿฟ๐Ÿš€

Collapse
 
oj_redifined profile image
Ojay

Thank you @ayodejii

Collapse
 
alexkapustin profile image
Oleksandr

As an interviewer, i expect to have some dialogue. Code task is just a subject to have some discussion around it.
The worst thing you can do is look into task and do nothing or write terrible solution.
Instead, you can discuss how would you solve a problem, why would you choose this solution.
Also, it's very important to ask questions, it's better to ask something rather than assume.

Collapse
 
satyaprakshsi11 profile image
SATYA PRAKSH SINGH

Keep going

Collapse
 
jsanta profile image
Jose Ignacio Santa Cruz G.

Remote positions have that catch, of location and language. For example I live in Chile, South America, Spanish speaking country. For some reason the company's job offerings in Spanish, appeared like open world wide. The thing is that even our remote workers are native Spanish speakers, and we still got many applications from Nigeria in English.
Not blaming anyone, but even if you're a great developer, language can easily get you lost in translation (I know it's not your specific case, but had to tell this story).

Collapse
 
dgroyalsteam profile image
DG Royals
Collapse
 
ownlin profile image
ๆ ˆ็ƒŸ

The next one will always be better๏ผAnd ~~ review this interview to understand your weeknessโ€

 
tosey profile image
Tosin Seyi

Ok. I have seen your website but will still need to know more. So how do we get started?

As for the tech stack, can I use python or java for it instead of .Net.

Let me know how I can come in.

Thread Thread
 
tosey profile image
Tosin Seyi

Ok. I have seen your website but will still need to know more. So how do we get started?

As for the tech stack, can I use python or java for it instead of .Net.

Let me know how I can come in

Collapse
 
tuan47th profile image
kEvinEngX

totally aggree with you, i have the same exp for interview like that, how smart your solution to problem is better than task is done

Collapse
 
akselsoft profile image
Andrew MacNeill

Great post. Really valuable for everyone to read and reflect on.

Collapse
 
tosey profile image
Tosin Seyi

Can I be part of this project? Kindly explain to me the tech stack you use for it?

Here is my LinkedIn profile linkedin.com/mwlite/in/tosin-seyi

Collapse
 
adam_gardner_ed9d6a4f26f8 profile image
Adam Gardner

Keep on keeping on man, the hardest part of working...getting the job. As someone who interviews many developers for the company I work at, its all about selling yourself. 90% of the interview I have with each person is all about personality and who the person is. I can teach anyone to code, teaching someone to interact with people that has to be there already. Best of luck to you Ojay.