December 23rd, 2008, 9:43 pm
It is the case that most developers in a bank are not even remotely "quant".IT career paths are often not great, and I do not see that changing soon. In HK I think it is even worse since it is not as big as NY/London but with wage costs not much less.But in any IT career, a good knowledge of the business area helps a a lot, quant finance is just one way of doing it.Part of the difference is that there are no "Masters in Settlements", or in exchange connectivity, etc.So many people head in the quant drection simply for lack of a better opton. I think demand for QDs will be more stable than may types of work in banks.You do need decent maths to be a QD, and many IT grads also face the problem that the maths they have done are not the right kind.I have said that C# is reasonably useful in this line of work, more so than Java and represents a plausible trade off for those who ar not sure if their future wll be in quant work or mainstream IT.Java is of course more common than C#, but I forecast that over the next 5 years C# will pay better than Java, since the supply/demand for Java does not look as attractive if you are selling the skill.Excel is great a defence against your career going bad.Demand will be there for >10 years, and is much easier to get to a level where people will pay you money than C++, Java, SQL, etc.That's more important than you might think. This is your first recession, it will not be the last, I guess there are anywhere between 4 and 12 recessions between you and retirement.Also, all skills age and die.C++ has seen off many other languages, and C/C++ are still very strong, but everything dies.Java is showing signs of early aging, and it's quite possible that C/C++ overtakes it again in a few years.Or not...I have made bad forecasts on this stuff before, and surely wiill do again. No one on this forum is even close to me in ability to forecastwhich technologies will prosper, and even I don't know how to call it well enough to tell you what to do.You stand no chance.Even if you guess right, it will die anyway.If you look back (say) 15 years at the s/w dev skills that banks were hiring the only major survivors are C++ and SQL. Clipper, OS/2, Powerbuilder, and many others are words that I guess you don't even recogniise.I guess 80% of the buzzwords in demand then have faded to background noise.Even C++ is quite unlike the language used in the early 1990s, many people thought MFC were really cool, on the CQF I now use it as a nexample of shit class design.At 37 you may well find that Java (or C# or F# or Perl) simply do not convince anyone to hire you.It may happen quicker than that. Skills can die in a year flat, or version changes erode you away to obsolete.As a techie you have to keep gambling that the skill you learn next will have a demand, and that cycle will happen several times.
Last edited by
DominicConnor on December 22nd, 2008, 11:00 pm, edited 1 time in total.