Skip to story
DevGlan After Hours

✍ STORY 6 min read ·
Dhiraj RaySoftware Engineer · 1 years · India

One Backdoor Entry That Ruined a Startup

Sometimes, a startup doesn't fail because of a lack of funding, customers, or a good product. Sometimes, the people running it make decisions that slowly destroy everything they've built.

This is a real incident when I was working at a small startup in HSR Layout, Bengaluru.

I had joined the company as a Java developer intern. There was a small team. There were three senior employees, and I was among the interns working under their guidance.

The startup was building a product, and things were progressing reasonably well. We had a client, a delivery timeline, and a product that was almost 80–90% complete.

But then something happened that changed the entire direction of the company.

It Started With a Salary Hike

To give you some context, salaries at this startup were extremely low. After completing an internship, developers were being offered around ₹9,000 per month. I don't know exactly how much the seniors were earning, but compensation was certainly not generous.

Two of the senior-most employees requested salary hikes.

The co-founders were willing to offer an increase, but not anywhere close to what the employees expected. Eventually, both senior developers resigned. Now imagine this situation.

Your product is 80–90% complete. A client delivery deadline is approaching. And two of the people who built most of it have just resigned.

For any startup, this should have been a serious warning. But our co-founders seemed confident.

After all, this was Bengaluru. Finding another Java developer shouldn't be that difficult, right?

They accepted the resignations. And then came the decision that, in my opinion, changed everything.

A New Developer Appeared Out of Nowhere

Instead of conducting a proper hiring process, one of the co-founders suddenly brought in a new employee.

There was no interview that we knew about. No technical discussion involving the existing team. One day, this person simply joined the company.

The new employee introduced himself as someone with around three years of experience in manual testing in Mumbai and had completed trainings on Java and related backend technologies.

Given that two experienced developers had just resigned, we naturally expected him to take responsibility for the remaining development work.

Initially, everything seemed normal.

But after a month or two, we started noticing some unusual things.

Something Wasn't Right

Our startup had two co-founders.

Interestingly, both were also employed at other companies. They were managing this startup alongside their regular jobs and would generally visit our office on weekends.

During weekdays, most of the work happened without their physical presence.

We used to discuss project issues, workplace concerns, and other matters among ourselves. But after this new employee joined, we began feeling that even our internal conversations were somehow reaching the co-founders.

It became difficult to speak openly. Over time, the working environment became increasingly uncomfortable. Then we discovered something interesting.

The new employee apparently had a family connection with one of the co-founders.

From what we understood, they belonged to the same village, and there was some uncle-nephew kind of relationship between them.

I don't know whether he had undergone any technical interview or what exactly was discussed during his hiring.

And because of his personal connection with the management, questioning anything became even more difficult.

The Product Was Delivered. Then the Real Problems Started.

Remember, the product was already around 80–90% complete when the senior developers resigned. The new employee took responsibility for the remaining work. Eventually, the product was delivered to the client.

The application was full of bugs.

Issues started coming in. The client was unhappy. The co-founders were frustrated. The pressure inside the company increased dramatically.

I cannot say that every bug was introduced by the new employee. Software projects can have problems for many reasons.

But what was clear to us was that the project had not been delivered at the expected quality. And the person who had taken responsibility for completing it was struggling to handle the situation.

Then came another surprise.

The Responsibility Suddenly Fell on Me

There were two of us who had joined the startup as interns and now working as software engineer after completing 6 months of Internship.

We had not been responsible for building that particular project.

Yet, when the delivery went wrong, much of the responsibility for fixing the bugs started falling on us.

Imagine being a fresher, earning a very small salary, and suddenly being expected to fix production issues in a project you had barely worked on.

Instead of addressing what had gone wrong with the hiring and project handover, the focus shifted toward getting the remaining employees to somehow fix everything.

The work environment kept deteriorating.

Eventually, We Both Resigned

But we found ourselves dealing with problems that were far beyond what two inexperienced developers should have been expected to handle without proper guidance.

The trust within the team was gone. The work environment was no longer healthy.

I had survived only around nine months at that startup.

But the story didn't end there.

What Happened to the Startup After We Left?

I remained in touch with one of my former seniors, Yogesh, who had been a mentor to me during those early days. He was someone I respected and had learned a lot from.

Through our conversations, I heard more about what happened after we left.

The company apparently continued struggling with project delivery and responsibilities. I also heard that the company had hired a few more interns.

Later, the startup moved to another location.

And within roughly six months of our departure, I learned that the startup had shut down.

I don't know every detail of what happened during those final months.

I also cannot say with certainty that one employee or one hiring decision was solely responsible for the company's closure.

But having witnessed what happened inside that office, I strongly believe that the decision to replace experienced developers with someone whose suitability for the role was unclear played a significant part in the company's decline.

Instead of ensuring a proper technical replacement and a smooth handover, they brought in someone with a personal connection to management, without any hiring process visible to the team.

Hiring someone you know is not necessarily wrong. Hiring someone without properly evaluating whether they can do the job is where the real problem begins.

This is one part of my experience working at my first startup in Bengaluru. I've shared two other incidents from the same period:

Why I Could Survive Only Nine Months at My First Startup

How a Failed Background Verification Cost Me My Next Job

Frustrated Workplace DramaRant

Now, What's Your Story?

You've heard their side. Maybe it's time someone heard yours.

Tell your story ↗

Conversation (0)

Strong opinions welcome. Personal attacks aren't.

Oldest first · Replies grouped

Loading replies…

No one's spoken up yet. Be the first.

What's Your Take?

Use @ Mention beside a reply to tag that participant. You can mention up to five people. You can write now. Sign in a new window before posting.

Don't Keep This One to Yourself.

Good stories deserve more than one audience.

Report this story