<< QCon London 2008 - day 3 | Home | It's my data >>
Twitter RSS feed for Simon Brown [Twitter] simonbrown: it's friday and I have a camera @chinposin update

Coding the Architecture RSS feed for Simon Brown [Coding the Architecture] Just a short note to plug a handful of sessions that Kevin and I are presenting at the upcoming Software Architect 2008 conference, 3rd-5th June, London. 1. Coding the Architecture : From Developer to Architect The first is a re-run of our ...

The 3 types of city developers

Or how business knowledge is deemed more important than technical knowledge

Despite the impending doom and gloom of a city recession (or just a few months of uncertainty, depending on your point of view), the recruitment agents are out in force at the moment. Most people I've spoken to recently have had a ton of cold calls and there's a worrying trend. But before I dive into that, let me summarise what I think are the three types of city developers.

  1. Those with a passion for business knowledge : This set of developers have a real passion for understanding the business area in which they are working and is particularly common within the investment banking industry. The people in this group (and I know a lot of them) genuinely want to learn more about credit derivatives, equity derivatives, FX, quantitative analysis, etc.
  2. Those with a passion for IT as a craft : This is the set of developers with a genuine interest in technology, who would be happy to use new and cool technologies regardless of the business context. I know a lot of people in this group too, and typically they aren't that fussed whether they work in FX, equities, etc or even in investment banking.
  3. The 9-5'ers : There are undoubtedly developers in the city that are in IT because it pays well and they aren't necessary interested in either of the above. This is fine, everybody has the right to earn a living doing what they want.

It's probably fairly obvious that I fall into category 2; my interests are in technology, software development and solving business problems with technology. Most of my investment banking work has been in the middle/back office, which means that I've not been exposed to the "shop window", where all of the real business stuff happens. By the time business information makes it's way down to middle/back office systems, it's all just flat files and messages. For all I know, the front office could be selling fruit and veg. Okay, I'm exaggerating. Systems in the middle/back office *do* deal with business concepts, so you have to understand them. For somebody like myself in category 2, I'm typically brought into a project because of my technical skills and my view is that the people around me already have the business domain knowledge. It's rare to find people with a passion for both the business *and* technology, but they do exist (Evolution did a good job hiring a number of them in the past).

With this in mind, let me paraphrase a couple of recent conversations I've had from agents cold-calling me.

  • [Agent] Hi, I understand that you're an experienced Java developer/architect.
  • [Me] Yes.
  • [Agent] Fantastic, we have some excellent senior roles available at the moment. What's your [equity derivatives|credit derivatives|algo trading] knowledge like?
  • [Me] (explain that I'm in category 2 with a strong technology focus).
  • [Agent] Not too worry, we could pitch you in with a reduced rate/salary with a view to increasing that after 6 months. How does that sound?

I've worked in the city for the best part of 10 years and I don't understand this one-sided view that recruitment agents seem to have. If you don't know "the business" then you're effectively a second class citizen. The implication of all this, of course, is that business knowledge is deemed more important than technical knowledge. I find this attitude quite disturbing.

Many city organisations *do* value technical know-how. I've helped some of my customers hire developers (often to replace me when I roll-off the project) and even the permanent employees aren't always expected to have a deep understanding of the business domain. I've seen many permies hired from into investment banks from outside of the industry because of the technical skills they bring to the table, and I know of one large bank that is currently trying to explicitly hire people from outside of IB because they want to evolve the way that they think about technology.

What are your thoughts on this? Should I forget about learning how to build scalable systems, sell my tech books and study the financial markets instead? ;-)



Re: The 3 types of city developers

In my view a skill that is often underestimated is the ability of the tech boys (especially consultants) to acquire the relevant business knowledge in a short time frame. To me this seems more important than specific knowledge in certain areas.

Re: The 3 types of city developers

I agree ... particularly if you are working across a bunch of different business areas and you have to start making an impact ASAP.

Re: The 3 types of city developers

Same thing in the mobile space. "Do you have experience in mobile" can almost be completely summed up in knowing WML and XHTML. That's 90% of it for most jobs (unless you're doing j2me / brew work) but recruiters keep on asking it.

Re: The 3 types of city developers

As developers we have to be both knowledgeable and constantly reeducated. What I was working with 4 years ago is almost completely gone. I try to learn a new tool or API every month and a new programming language every few months. Given this, it shouldn't be too hard for us to pick up new business knowledge. Personally I've jumped into and picked up: publishing, institutional investment, medical devices, health insurance and now banking.

Re: The 3 types of city developers

Sorry to say, but the recruiters (and Brady, above) are right to an extent. Not only should a developer know his own craft, he should have some in-depth knowledge of the business he codes for. If that sounds hard, it's because it is. It's harder than learning to code, and possibly harder than learning to code _well_. But it's worth it. My company has made a career out of programming not because we're the world's best programmers (we're pretty darn good, but I'm sure there are better and/or cheaper), but because we can get into clients' heads and know what they really want based on our "insider" knowledge of their business. Once you mesh the knowledge of the client's business with your coding skills, you will remove a large amount of "friction" between your software model and their business model. If you're any good, you probably have an inkling of how to build a scalable system already. So set the tech books aside and figure out what your client is in the business of doing. Then apply your developer skills to the problem. (Note: YMMV, and you may have to talk to further layers such as data designers, requirements people, etc depending on the team size -- my company works with small business and doesn't have to deal with that as much. If you do, make those people your best friends. They have the final say on what you write -- you don't go around them, and it's a good idea to ask them questions right and left.)

Re: The 3 types of city developers

My experince is recruitment agents are generally wankers. Most of the time though these guys just seem to work off buzzwords and talk crap. They don't know the business very well and they don't know the technology. It's all mind games with these guys.

Once you meet the actual hirers you can find out if you are the person for the job and how important those business skills really are...

I consider the ability to learn the business quickly combined with strong technical skills as the best developer/architect traits. Especially in todays market when people are changing jobs every couple of years! Sure you need business experts, but not everyone should be one.

Re: The 3 types of city developers

Core techies are like sculptors but the figure/shape to be sculpted is determined by the business. Right?
Well...My manager is a so-called business guy knows nothing about technology. He once told me, "...Technical skills are pretty useless. I can get any 10th grader to complete an Enterprise system, provided he understands how the business works..."!
To which I asked,"...then why don't we use the clerks in the front office to design the system, as they have the best understanding of the business?".

Re: The 3 types of city developers

Perhaps the recruiters should build the systems. ;-)

Add a comment Send a TrackBack