Member-only story

Why Startups Hiring Senior Developers Can Be a Huge Mistake

Experience is valuable. But for startups? I don’t think so

Mohammad Faisal
3 min readMay 25, 2021
Interview
Photo by Sora Shimazaki from Pexels.

Running a startup is exciting. You are part of a journey where the destination moves constantly.

Hiring and managing people is even more challenging. A well-organized team is the most important asset for a startup.

In my experience as a founding member of a startup — and after working for multiple startups in the last 3-4 years — I have noticed that the outcome of a team depends more on chemistry than technical strength.

Today, I will share my experience with older programmers and why I think startups should avoid hiring them.

They Have More To Lose

Younger programmers are eager to take risks. They have nothing to lose. They can bet on a promising technology or change to a different tech stack.

But the case is different for older programmers. They have spent their career working on a specific technology. Maybe they are very good at it, but it’s not guaranteed that technology will solve every problem.

In these scenarios, they oppose adopting a new technology because they suddenly go from experts to newbies!

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Mohammad Faisal
Mohammad Faisal

Responses (51)

Write a response

This is nothing but straight up ageism with zero basis in fact or reality. It sounds like you've had some specific bad experiences with individuals and are eager to stereotype others based on them.

As you are drawing from your personal experience, you may want to retitle this article “How I made a huge mistake hiring the developers I hired.”
I’m a front-end developer in a startup using React. Between me and 2 other developers, we have a…

Mohammad, you should keep this article in your archives for a few years, then -- when you are a senior developer -- and the whole developer community finally realizes that React is "legacy code" (and needs to be completely rewritten) you can write…