This post is inspired by Jaseem Abid’s original post (Thanks to him). I found it helpful and motivating. Hence I am doing my version of it. Alright, so here is the idea.

Why do we not talk about our failures?

Jaseem’s original post was about a few companies that rejected him outright without even an interview. But my version would be slightly different. It will include outright rejections, ghosted rejections, and rejection after interviewing.

Also, quoting Jaseem one more time to state the purpose of this blog post:

This might be the motivation someone needs to keep trying and hence I believe is worth sharing

I hope that reading this helps you a little bit in your job search! I want you to know that job search might be stressful (at times), but you got this! Prepare yourself and go out there; Don’t get hurt by rejection.

No challenges are roadblocks. They are just speed bumps.

– Devin’s mom (The Kicks S1E01)

Ok, let me start the show!


The year was 2015. I was fresh out of college! Never applied/attended an interview before because I was not allowed to attend the campus interviews happening in college due to low marks.

So, there I was browsing through Hasjob (one of my favorite job portals) every day. I then noticed this job listing saying that Paytm is hiring for software engineers who do node.js.

I got very excited. I had started using Paytm (a digital money wallet) sometime back and was amazed by this new way of handling money.

So, I went on and just applied for it. I think this was my first ever job application.

Luckily, I got back a response. They wanted to do a phone call. I didn’t even think about what they would ask on the phone. I was so happy that I was even considered for a phone call. haha :D

Then the phone call came. It was so fast - we said hi and maybe a very little intro. Then this happened

interviewer: do you have a paper and pen right now?

me: no

interviewer: Ok, take those and get ready?

me: (running around to get a paper and pen) ok, got it.

interviewer: which language are you comfortable in?

me: JavaScript

interviewer: Ok, write a program to reverse a linked list.

me: (stunned, because the last time I wrote a linked list was years ago for data structure exam) ummmm, (tried so hard to think of a solution)

(after a few mins)

interviewer: Did you write it?

me: I just wrote the linked list structure and function signature

interviewer: never mind, just read out what you had written in the paper.

(me, reading in breaking voice)

interviewer: Kbye

[Ghosted && Rejected]

Short while, I called my friend who had been preparing for interviews and he introduced me to the fact that asking data structure questions is normal. That’s when I got the taste of how the interviewing world is :D


It was the same year and just after the Paytm rejection, I came across DoSelect. It is a coding assessment platform like Hackerrank. Those kind of sites were gaining a lot of traction at that time. Remotely executing your code and evaluating solutions from a website is pretty cool.

Earlier as a student, I released one of my successful projects called compilex which is a library useful for building such kind of sites. So I was so much interested in working on such a product. Hence I applied.

The first round was using the DoSelect platform itself. Simple algorithm and data structure style questions (I think I answered 2 out of 3 correctly; the other one partially accepting solution). They asked for a Google hangout video chat. But I had a very poor internet connection at that time and openly mailed them about it and asked if it is ok to do an in-person interview instead.

They said ok! At that time, they were based out of InMobi office. I took a “500D” BMTC to arrive at their office (used google map to track the right bus stop, but got down early in the previous bus stop. haha). Thankfully, there are a lot of 500D buses and so I hopped on the next one and arrived at the right spot. This was the first time I entered a tech park and a big office. I was WOWed!

I was nervous and thinking about what they will be asking me. There was a technical discussion. The thing that went wrong there was “I wasn’t confident while telling my answer”. They asked me something like “how to get realtime updates in the browser?”, I knew that WebSockets are used for them but I didn’ confidently put that in front of them. I said about long polling and was a bit reluctant about starting the conversation about web sockets. Because I wasn’t sure if WebSockets were a proper standard. So the conversation went a little bit weird.

After that, I spoke with the founders. I was so naive throughout the entire conversation both in-person and mail. I was so new to a lot of things - tech, speaking with people, etc. I am sure that I looked like a fool at some point in time. haha. The conversation ended in a good note. I very much appreciate their time.

Got back home. I was very happy and even naively told my grand-mother that I might be getting an offer anytime soon. We waited for their email (lol, she still keeps a check on me whenever I start a job search - even after 5 years). Waited and waited…. haha. Even mailed them back 10 days after to follow up. (I read through that mail to get the feel of nostalgia and how naive I was - it felt like I was so desperate for the job)

[Ghosted && Rejected]

At this point, I already learned a couple of things about job search

  1. Don’t be desperate. Just accept who you are and try to find people who are willing to accept who you are and help you improve.
  2. Never say that you are getting an offer to others before receiving the actual offer letter. That way we avoid embarrassment in front of family and friends. hahahaha.


I think this was 2 years after that. I was so interested in open source communities, side projects, etc. Mozilla was doing cool stuff like rust. Also, it’s presence in India was increasing more and more.

I think I loved Mozilla as a company because of these reasons:

Firefox was one of the coolest browsers back when I was in school. It was amazing to notice all the improvements Mozilla bring in after every new update. Those days Opera and Firefox were two of my favorite browsers (until Chrome came along).

The second reason is MDN Web Docs - Mozilla Developer Network documentation for JavaScript. I love these docs and these have huge respect from me even now.

I saw a really different role on their career page. It wasn’t particular about any tech stack, but it was more like a research/prototyping engineer. I also think that it was a remote role. I just applied away to see if they would even consider me for such a role.

Then I received this nicely written rejection email. I am copying and pasting the full email because I love the way they used the word “Web” in there!

~ ~ ~ ~

Hi Vishnu,

Thank you for your time and interest in Mozilla and our Staff Experiments Integration Full Stack Developer position. We have looked at your resume and, although we appreciate your background and experience, we are choosing not to move forward at this time.

This isn’t necessarily the end! We know that people are always learning and growing and we have new jobs opening all the time. We do keep you in mind and will contact you if we think we have an opening here that you would be well-suited to. Also, every position we open is posted to our twitter feed, so follow us at @mozilla to keep an eye out for other positions that would be a good fit for you!

We’re sorry that we were unable to make it work this time, but we hope that we see you around the Web.

Thank you!

The Mozilla Recruiting Team

~ ~ ~ ~

I wrote back happily saying,

~ ~ ~ ~

Thanks for taking the time to look into my application and giving notification on the status of it. I hope to see you around!

~ ~ ~ ~



These were the times when I was having questions like “What do I want to focus and specialize on? Do I want to concentrate on frontend, backend, or DevOps?” - kind of like adolescence. I think a recruiter from Cohesity reached out to me. They said that there was a position open for Frontend engineer. I thought of trying out for it (just to know if people trust me for a frontend role) - I had been mostly doing full-stack stuff for a while.

There was an on-site interview. I went in super-delayed for that - who knew there will be that much traffic on outer ring road of Bangalore and also I was the first rider for the Uber driver that I had got that day (I mean like the first-ever rider in his uber driver career). Spend quite some time helping him out with Google maps, Uber driver-partner app, and what not, android and phones in general!

When I arrived, I was introduced to the interviewers. I think there were 2 technical rounds - needed to write JavaScript in both of them. Questions like implement a debounce function were asked. I think I did it well. But I might have troubled a bit while speaking with one of the interviewers.

Then in the afternoon, one of the interviewers took me to their team lunch and introduced me to a bunch of team members. I had lunch with them. For the most part, they were all speaking in Hindi (a language that I don’t know). Then I said that I am sorry and I don’t understand Hindi. Then they also said it’s ok (and sorry).

I was notified that the recruiter would contact me for the results. The recruiter reached out to me over the phone and said, “we were looking for people who are already very specialized in frontend and you are more aligned towards the backend. So it didn’t work out, but we will let you know once those positions open up.”


When discussing this interview experience with one of my friends, he said that the part where I went in for lunch with the team was also part of the interview to evaluate culture fit. haha :D


This was one of the turning points for me. I never interviewed with big co. at that point and this was the first time. A recruiter reached out to me via LinkedIn and I sent my resume back showing interest.

Why was I interested? AWS was the main reason. After that is Kindle, haha :D Apart from those, I felt good about Amazon’s growth inside India. I was interested in how these big co. operate (spent most of the time working at startups at that point in time). I was in the hiring drive for their newly established Amazon Pay team. After a few rounds, I met with someone who said that I might be part of an internal team. Not sure, if those two were the same roles :D

The interview experience was so much energy-consuming. I first took a few weeks preparing Data Structure and Algorithms. I think I just went through the list of data structures. At this point, I didn’t do much puzzle questions and my point of view was if I am just good at knowing these data structures and coding basic operations in them, I might be able to answer whatever was thrown at me!

The first day was fully data structure and algorithm puzzle questions. There was a written round. After that, there were two more rounds with Amazon Engineers. I enjoyed the conversation I had with both of the engineers.

The next rounds were about system design. This is where things went wrong with me. I think I was over-confident and didn’t prepare well. The over-confidence is mostly due to me thinking like “system design, right? I already do a good job at work while designing stuff. So it should be easy peasy.”

They asked me some pretty common design questions in multiple rounds - I was told to draw the class diagram and stuff. They were checking on the Object-oriented design skills. They probably expected me to be writing Singletons and Abstract Factories there, haha. At that time, I was working with JavaScript at work and wasn’t ready for it!

Also one of the rounds was about testing knowledge on concurrent programming. I was expected to write code involving 2 threads etc. I tried answering that thing in Go but it didn’t go well. I should have just told them upfront that I work mostly with Node.js and it is single-threaded.


The HR called me over the phone and shared that I wasn’t strong enough in my system design skills and apply back in 6 months. Some good things here: they didn’t ghost. They shared the feedback and encouraged to reapply. Also, I didn’t have to pay for cabs and food during these interviews :D haha.

Jokes apart, I think I learned a few things in here:

  • If you don’t know something, accept that you don’t know and come clean with the interviewer.
  • Don’t be over-confident.
  • Go in prepared!
  • Choose the right tech while preparing for interviews. If not choose the interview where they ask you about the tech you know of. For example: probably choosing some Object-Oriented Language like Java or C++ might have been more suitable for answering the design part of the interview here or I should have tried out for roles like Web developer or something that deals with JavaScript.


A recruiter reached out via LinkedIn and I sent back the resume showing interest. They called for a hiring fair - 100s of people were there.

We were asked to dress formally I think (I went in wearing a white shirt, black pants, and formal shoes). First-round was written (write programs on a paper). Followed by an in-person round.

interviewer: Are you experienced in python?

me: No. I am experienced in JavaScript and Node.js

interviewer: (looking confused) but the role we are interviewing for is for someone who is experienced in python

me: oh, ok.

interviewer: asked a question just for the sake of it (but hugely confused about how they allowed me in there)

me: (answered the question)

It was so short. Then I was asked to wait and the HR spoke to me asking “did you tell that you were in for node.js to the interviewer?”. I said yes. Then they were like “oops, sorry, we are looking for python and the node.js role might open up afterward”

hmmmmm, ok!

I regret most part of doing this. But there is a good thing. I discovered a good milkshake shop near their office. The milkshake that I had there was so awesome and I made it a habit to drop by that shop whenever I was nearby. haha, sweet!


Schneider Electric

Felt very similar to IBM type interview. Both of these were optimized for filtering out from a large number of people.

First-round was written MCQ or fill in the blanks style questions. Forgot exactly. But I had noted down that I got 23 out of 30 in that. haha!

Two rounds with engineers.

One round was a discussion regarding previous work experience.

In another round, I was asked a puzzle SQL question - couldn’t answer it.


Preparation and a little luck of getting asked what you know in play here!


Got a referral for this! (thanks to the friend who referred me)

Initially there was a small phone call with the HR and showed up on-site.

Two rounds:

  1. Whiteboard an algorithm question
  2. Design question - picked up from an actual work problem that they had solved.

I wrote a sub-optimal solution for the coding question. Also didn’t do the design round well.


But I got the chance to meet up with the friend who referred me at the end of the interviews and felt encouraged in the job search process :)


I was using Uber almost every day around that time. This was when ride-sharing apps were booming!

Also, I like reading through their engineering blog etc. So I was excited to apply for a position there.

I applied via their careers portal on a weekend and received this mail first thing on a Monday morning!

~ ~ ~ ~

Hi Vishnu,

Thank you so much for giving us the opportunity to consider you for the Software Engineer II role. We know it takes a lot to submit an application, and we want you to know how much we truly appreciate your interest in Uber! We’ve carefully reviewed your application, and unfortunately it isn’t a match for what we’re looking for this time around.

Please do not hesitate to keep in touch and reach out if we have another role you think could be a fit in the future. We wish you all the best.


The Uber Recruiting Team

~ ~ ~ ~



I was interested in building a slack bot and read through the entire of slack’s documentation. I was amazed by all the slack bots out there.

One such slack bot is Donut. So I applied to them.

~ ~ ~ ~

Hi Vishnu,

Thank you for your application to Donut. We recently filled the role you applied for and are no longer actively recruiting for this position. That being said, we’d love to keep your resume on file as our team continues to grow and stay in touch about future opportunities that may be a good fit.

We appreciate your interest in Donut and wish you success in your job search.

The Donut Team

~ ~ ~



Startup in initial stages. The small team focused on an interesting problem space (observability) - also remote first.

Almost got ghosted, but I messaged them asking if I was still being considered; if not at least a simple feedback.

They were generous enough to spend some time over a call to give me feedback. I wrote an entire blog post about this.



I love Juspay while making payments on mobile. I spoke with their founders back in 2015 in a JavaScript conference.

The founder started an email conversation with someone in the company CCing me and their careers email - asking to co-ordinate a coding test. That person never got back and ghosted.

While that was in 2015, I happened to apply back again after 5 years. They posted in “Ask HN: Who is hiring?” thread.

HR spoke with me and told me that they will send a coding test.

Never got the coding test.

[ (Ghosted && Rejected) x2 ]


I tried reaching out to a recruiter on LinkedIn (after seeing their LinkedIn posts), but they never responded back with a message.

It felt like writing to /dev/null.

[Ghosted && Rejected]


Already missed the UPI wave and didn’t want to miss out on the Neo bank wave in India.

Applied via their careers page. Got back this email.

~ ~ ~ ~

Hi Vishnu,

Thank you for your interest in epiFI Technologies! We wanted to let you know we received your application for DevOps Engineer, and we are delighted that you would consider joining our team.

Our team will review your application and will be in touch if your qualifications match our needs for the role. If you are not selected for this position, keep an eye on our jobs page as we’re growing and adding openings.

The epiFI Technologies Team

~ ~ ~ ~

Never got back a review.

[Ghosted && Rejected]


Raksul is a Japanese company that was trying to hire for building a fresh development center in India. A recruiter reached out to me regarding the opportunity. First was a general webinar kind of session where the CTO spoke about the culture etc. They seemed cool. The idea of building a fresh team from scratch kind of attracted me. So, I decided to interview further. Also, they were hiring for Go Engineers - so it kind of aligned with me.

The first round was 1 day take-home assignment. It went well. Next was a 1hr chat with leadership. It went good as well. Then there was a coding assignment for which 7 days time was given. I was busy with other commitments around that time and couldn’t complete it properly - barely spent 2 days on the assignment.

I enjoyed the conversation and coding assignments. They helped me in honing my Go skills. I even got a thorough code-review on the assignments. Thanks for that! But unfortunately, I never received an official mail intimation from them about the rejection. So I will have to consider this ghosting.

[Ghosted && Rejected]

Walmart labs

Received a call from HR saying that they are interested in the profile. They said the first round will be data structure and algorithms. They asked if I am prepared for it. I should have just said yes, but I said “prepared but not sure if I am at the level to crack Walmart labs”. lol, rookie mistake!

They said that they will send the ds and algo online round to email. But never received one.

[Ghosted && Rejected]


Applied via their job portal. Received an email:

~ ~ ~ ~

Hi Vishnu Bharathi P,

Thank you for your application to our Web DevOps Engineer position. We appreciate the time you took to consider opportunities at Zoom Video Communications. At this time, we are not seeing exact alignment with the current team needs.


~ ~ ~ ~



I hope that this post helped you a little bit or at least served as relaxation in your job search :D Sometimes you get a job and sometimes you get an adventure - like in my case of discovering a good milkshake shop in the worst possible interview experience.

Focus on preparation and getting better! That’s probably something in our control.

Also, note how common ghosting is! I wish that we get better at not ghosting people as an Industry.

Just in case if you are searching for a job: Stay cool, search strong!