Is the software development career really dead after age 35 – 40?

Notice the limit after age 35-40. There is no doubt that this is a great field for young programmers, but is it also suitable for older programmers?

I still haven't reached the age of 35, but will fall into that age in a few years.

So it's no surprise that I think about this question: is software development really a job without a future?

I think that I have been quite successful in my career so far. I started my career as a programmer and currently work as a Software Architect. I have experience as a programmer, architect, Scrum Master, team leader, etc. … Non-technical, I have built many groups from 0, recruiting qualified candidates, and training to improve their weaknesses, etc.

In short, I have skills in many areas of software development. I enjoy participating in many aspects of the system development life cycle and can help the group move forward (both technically and group management, creating the right development processes and a stimulating environment). creativity for programmers).

Does that help me become a good candidate for any job? Are you thinking like this. “That's right, why not? Because you already have all the skills. ”I also think like you.

When I was looking for a job recently, I did not receive any interview from most of the companies I applied for. That's because employers tried to find similarities between their job requirements and my profile.

Employer: Can you work with the Java language?
Me: That's right.
Recruitment: Can you work with Spring, J2EE?
Me: Yes, I can work with Spring. I did J2EE in 2004. Previously, I also worked with JavaEE.
Employer [confused but still asked]: What can you do with Spring?
I: MVC, Data, Security, Spring Boot, and many other things [I list them as a list].
Employer: Do you know about XML?
I [was a bit annoyed because I realized where this question would go]: Yes, yes.
Employer: What version of the Wildfly application server?
Me: I've been working since JBoss, and now I use Wildfly 8.
Employer: Oh, so you haven't used Wildfly 9 yet? Unfortunately, we are only looking for experienced candidates to use Wildfly 9. [Hang up.]

For most jobs, my skills are not exactly the same as the keywords they are looking for, so you can imagine how bad the phone conversation will be. They do not understand that I am much more valuable than the keywords listed in their job requirements.

In the few companies that I get a phone call from, they are looking for someone to work with "just write code" with a small salary.

There are also a few companies that try to test my programming, they asked me to "write a program to print out a ladder of asterisks" and "find duplicate numbers." This investigation is not because of arrogance, but because my skills go far beyond what they think is necessary for that position. Yes, the role here is a Software Architect. However, instead of testing my skills in building architecture and logic, they asked me to print a ladder on the screen.

The remaining companies are too far to go to work and I have to spend 5 hours traveling on trains every day. I have refused to interview calls from these companies, moving home is not an option with the stability of my family in the current city.

I refused when I hadn't interviewed 99% of companies. Of the remaining 1%, I found many reasons to refuse.

Now, when I look back at the period of 10-12 years ago, when I was in my twenties. At that time I was a Junior Developer. I am single and free to go anywhere in the world. I can choose any job. I am also very happy to work "just writing code" with a low salary.

But what will this story tell you? Am I a better Software Engineer in my twenties? Not so!

Now I'm in my thirties, I'm more sophisticated about my work. I am more concerned about the effects I bring to the company. I am also interested in spending time with my family.

Unfortunately, companies do not understand that. They want a person with a certain set of skills, not a person with a lot of experience in many areas. I believe the reason for this is because you are being hired to replace someone who has left that company. You are only expected to do what the previous person did, nothing more. Most of your "other" skills turn out to be pointless for the position you are applying for.

So, in a way, this programming profession is difficult for people in their thirties or older, not because we lack skills, but because we have many things to consider before transitioning. task. Whether it is a job with no future or not, it depends on each person's individual circumstances and flexible handling.

This interest leads us to an important next question: Does programming become a commodity business? That is the content of another future article

ITZone via Techmaster