To learn Documentum or to learn something else- That is the question

I received a few e-mails from junior level JAVA developers last week, each of them wanted to know if they should pursue opportunities that would allow them to get hands-on experience with   Documentum. All of them had completed Documentum training, one even said that he had passed the certification exam, but not a single one of their employers had a project or assignment that would give them the opportunity to exercise their new skills. It seems that they were trained so that they'd be ready to go "when the need arises" and that that moment hasn't arrived quite yet. Here's what one of them said:

My employer told me that Documentum is a hot technology, that my salary will rise quickly if I learn it. So I learned it, but I have not been given an assignment where I could use it. I am still coding in Java, like before.  I thought to change employers so I could work with Documentum, but all of the jobs require 5 years of experience. How can I get 5 years of experience if I can't even get one? Should I forget about Documentum and stick with Java? Is it true, do Documentum developers get paid more than Java?

Now the first part of this fellow's question is classic, entry level workers who want to move-up or move-on have been asking variations of it for ages. How will I ever get a job that requires a certain kind of experience if I can't get a job that allows me to gain that kind of experience?

The answer isn't too hard to figure out. You either ask your employer to put you on a project that will allow you to gain the skills you want to acquire OR you find an employer who will.

In the Documentum space, this isn't going to be easy because the demand for Documentum developers is relatively flat. Chances are that you will either have to wait for someone to move out of the job market to get hired or be in the right place when a Documentum professional moves on to a new role.

There may be an exception to this in countries to which a lot of software development and support is outsourced; in those regions salaries should continue to rise in both Documentum and Java alike. It might be worth noting that job mobility is greater in those places too. I recently conducted a search for a global 50 firm whose IT development center in India and the average tenure among the candidates I interviewed was 32 months.

On the question as to whether Documentum developers earn more than Java developers, in the most general terms, the answer seems to be yes. According to Indeed.com the average Documentum developer makes 100k while the average Java developer makes 94k. It might be worth noting, however, that job security might be greater for Java developers than for Documentum developers because the number of Java jobs has increased 42% since January 2009 while the number of Documentum jobs increased only 7% (and that the number of Java positions, overall, is quite a bit greater.)

And though no one asked, it might be worthwhile for a Java developer to consider if he should move on to a newer technology. There is a huge demand for Java developers who know PIG, Java developers who have worked with HADOOP, Java developers who know Alfresco and many, many other Java + combinations. Entry into rapidly growing, emerging  job markets is easier because there are often more jobs that there are experienced developers' therefore employers are more open to training high-potential individuals.

So while I don't mean to rain on anyone's dream of becoming a highly-paid Documentum developer, it would be irresponsible not to mention that market conditions may not be in your favor. I wouldn't say that experience Documentum professionals are in the same boat, especially if they can function as technical business analysts.

Finally, while there's probably no need to say it, I could be totally wrong. But, that being said, since you have so little invested in a Documentum career at present, why not consider trying to use your Java as the ticket for entry into an emerging technology space?

Comments

[ukdavo]

..and once you're a Documentum developer there's no escape. "Documentum people don't know Java, they know Documentum JAVA". :-)

[Virginia]

Thanks for the comment. Any idea on how we can help Documentum developers escape?

[Spoonix Net]

Three years ago I started working for Documentum Analyst position. At the same time I first heard the word "Documentum". At that time I already was a programmer who did not care about what language to develop. I can not say that it was easy, but I have mastered the Documentum DFC/WDK and Administration/Configuration, without any training courses, myself only. During these three years I saved enough money for the employer.
All I want to say. Make me an offer which I could not refuse. And I'll do what you need. Even stubborn Java programmers for a certain amount can become convinced of, let's say - .NET programmers:)

[Doquent.wordpress.com]

I feel that these challenges will keep on popping up as long as the question is technology-centric. The question sounds like "Which technology should I be a slave of?" rather than "Which technology should I master?"

The focus probably needs to be on building a track record of successful delivery and the ability to pick up whatever is needed to deliver successfully. I do understand that many employers look for expertise in specific skills. However, I have also seen employers choosing a well-rounded candidate over a candidate with very specific skills but lacking general abilities beyond those skills. For example, having Documentum WDK experience but not having a clue about Documentum architecture or not having good analysis/design skills.

The candidate needs to present himself/herself as the product rather than a specific skill as the product. At the same time one needs to prepare the specific skills and offer to be tested on those skills in the interview process. Yes, some employers might skip over your resume but that is not in your control anyway.

A point-of-view on a topic like this could fill pages so I would try to summarize my perspective. Strengthen the core technical skills (analysis, design, etc.), build good employee skills (team player, communication, etc.), keep an eye open in the space beyond the technology (e.g. content management in addition to Documentum), and create a track record of successful delivery and of picking up new skills.