Banking experience is overpriced by many places. Once you get that banking job, even if you're mediocre, you're going to be overpaid compared to your skills and ability as long as you stay in the industry.
Many people in banking IT become less valuable over time. They see projects buckling under the pressure from the trading desk to deliver, and think that somehow practices such as unit and other testing, daily builds, and the like don't apply to banks. They get lazy and used to delivering low quality stuff for a high reward.
People coming from outside IB have often got better quality development experience than peers who have spent all their time in the IB sector. They're the ones who are more likely to be able to make a good business case for decent development practices.
The best thing to do if you're in a bank and recruiting is to actively seek people with no banking experience. Telecommunications. Games. Image Processing. Air Traffic Control. There's plenty of people out there who are great value. Many agencies will assume you want prior banking experience unless you explictly tell them otherwise. Do so.
If you're in banking IT, learn the maths and the business. Hardly anyone does, and that lack of a wider understanding is partly why it's so hard for people in IT to push good practice to the business. Learn the language and frames that everyone else is using rather than being stuck in a ghetto.
But conversely, if you're in banking IT, find a trading desk that understands technology. Otherwise you'll always be having to make the business case for good practices rather than meeting the business half-way. You need to be able to make the case, sure, but it's a waste of time and energy to have to do so continually. Many teams get tired of doing this, and end up hustled into too many short term fixes, as a result of which the whole development needs to be restarted every 4 or 5 years.
And finally, here are three reasons why banking IT systems aren't what they should be:
- the yearly bonus. The pressure is always on to deliver in time for the compensation round. Stuff is rushed out before it's ready, and without the testing in place to allow refactoring. Much of the following year is spent clearing up the resulting mess.
- turnover. People move between banks with great frequency. Average times in jobs depend on who you ask, but if you're in the same area for more than 2 years, you'll be starting to be an authority. The knowledge of a system's "theory", the metaphors and assumptions that underly its structure, degrades quickly.
- high entry cost. It takes a lot of money to set up as a bank. So banks can be inefficient everywhere in the organisation and still be OK. This is getting eroded by the hedge funds, but is still important.
No comments:
Post a Comment