I have six years experience as a developer and development lead, followed by another six of development management, project management, performance management, scrum mastery and technology strategy but was made redundant in July when my former employer practically shut down their in-house technology department.

Over the years, I allowed them to move me further and further away from the code in return for better and better pay, but now I find that I can't get a job anywhere near my old salary, nor can I persuade recruiters that I'd be a great dev lead, senior developer or contract developer because all I've been able to do hands-on for the past couple of years is a few cheeky proof-of-concept projects rather than 75% or more of my time cutting code and I don't have the current "sexies" which seem to be J2EE for java or BDD, TDD, mocking and MVC3 for c#. I've managed teams doing those things, but not done them myself.

What strategies can I adopt to a) brush up the hands-on skills that are certainly not as good as they were and b) persuade prospective employers that all the rest of my experience adds up to a really good hiring opportunity?

  • 1
    What is driving you back to programming? Just the money? And how are you seeking work? There are a lot of software jobs going in London right now, most of which don't really require the "current sexies".
    – pdr
    Commented Sep 26, 2012 at 10:17
  • 3
    Interest, mainly. I found that the further I got away from the code, the less I enjoyed my job. Seeking work by scouring cwjobs, itjobboard, monster, totaljobs for everything that looks like I might be able to do it and applying - if there's a better way please share! :-)
    – Xav
    Commented Sep 26, 2012 at 10:55
  • 12
    @Xav I don't mean to be discouraging, but if you are still referring to it as J2EE and think it is a sexy then you are further out of touch than you might think. It hasn't been called J2EE in several years. Commented Sep 26, 2012 at 12:18
  • 2
    I'd probably keep doing what you are doing professionally and if you like programming so much, do it on the weekend as a hobby. That way you're writing code for yourself.
    – sashang
    Commented Sep 26, 2012 at 14:33
  • 2
    @sashang: That doesn't make any sense. The OP is unemployed. If he "kept doing what he has been doing", he'd starve!
    – Jim G.
    Commented Jan 12, 2013 at 18:43

2 Answers 2


I have been in a similar situation, but I had kept my skills up-to-date (always do that!) and I had contacts who recommended me, so I found it easier.

You do need to brush up your skills. First of all, focus. Don't look at Java and .NET -- your problem is already that you are a jack-of-all-trades -- pick one and mold yourself.

If you go .NET, pick a personal project and use the full MS stack (SQL Server, MVC for ASP.NET, Entity Framework, MSUnit, Moq, Unity). It's not necessarily the best set of frameworks for .NET, but it is the stack you'll find at a lot of .NET shops. Other places will be happy that you know an ORM, a unit-test framework, and an IoC framework.

While you're at it, brush up your interview skills. Learn by rote the basic, standard phone-interview questions for your chosen technology. You'll be surprised how far that gets you.

Now some bad news: I don't know what you've been earning but, if you're struggling to find work, you may well have been overvalued. And you've let your skills degenerate in the line you want to be in -- so even if you were worth that much as a manager, you may not be worth it as a programmer any more. You might have to be a bit flexible on wages, unless you can afford to wait while you brush up your skills again.

Onto some better news, how to find a job in London:

The best way is to have contacts. If you don't have them now, that's unfortunate, but you can still get them. Google around for user groups and meetups for your chosen technology in London. Also, get involved with non-technical development groups, like the eXtreme Tuesday Club.

Your very presence at one of these groups indicates that you're more dedicated to your craft than your average developer. Network well and you will find people who work at companies who are always looking for people.

Another fast but deeply time-consuming method is to make your CV public on a job site heavily accessed by agents -- jobserve is always my go-to site, but some of the ones you mentioned also apply. This will get you two days of phone-calls from agents trying to convince you to go for all sorts of jobs. But take some advice from someone who's been down this road.

  1. Buy a throwaway phone SIM so that, when you find a job, they can't keep contacting you.
  2. Be very sure what you want BEFORE you upload that CV. Tailor the CV accordingly.
  3. Don't even bother applying for jobs on those sites. Let the agents come to you.
  4. Be confident when explaining what you want to agents. Try to make yourself sound perfect for your perfect job, rather than suitable for any job.
  5. Make it clear to agents that if they try to push something other than what you're looking for, you won't work with them again.
  6. Stick to that, cause they'll do it anyway (I had one that sounded perfect, til I got to the bottom of the description and found it was in Bristol), but there are plenty of agents.
  7. Make it clear that they mustn't put you forward for a job without talking to you first. Being sent to the same job by multiple agents is a big no-no.
  8. That said, don't let them talk you into giving up information on other jobs you're going for, no matter how hard they insist. As soon as they know a company is looking for people, they'll start harassing them. Just ask "would you want me to tell other agents about jobs you're sending me for?"
  9. Know that, no matter how hard you play the agents, you will end up at some dead-end interviews. But it shouldn't take too long to find a job.

Finally, while the agents in London are still very powerful, the economy is such that a lot of companies are trying to bypass them and save their 15%. StackOverflow careers is a pretty good way of doing that, so put your CV up there and browse it for jobs.

This will be a slower process but not so overwhelming and will probably lead you to a better job.

  • 2
    +1: For the recommendation to focus on only one framework, the reality check about being "overvalued", and the networking advice.
    – Jim G.
    Commented Sep 27, 2012 at 0:33

...because all I've been able to do hands-on for the past couple of years is a few cheeky proof-of-concept projects rather than 75% or more of my time cutting code and I don't have the current "sexies"

Why not:

  1. Learn one of the current "sexies".
  2. Develop something that solves a real problem.
    1. (No matter how small that problem may be.)
  3. In advance of an interview, prepare yourself to demonstrate that you can build something significant with one of the current "sexies".

... I've managed teams doing those things, but not done them myself.

I know it's water under the bridge, but why weren't you keeping up? How could you possibly manage a team using these technologies if you didn't know go things worked under the hood? Also, as a former developer, weren't you curious?

In the future, regardless of your rank, I urge you to stay curious. Without question, all of the best tech professionals are curious.

  • I want to say that I was curious but got into trouble with the boss for getting too close to the "under the hood" stuff. Of course, that's just a lazy excuse...
    – Xav
    Commented Sep 26, 2012 at 14:10
  • @Xav: I could see a manager not wanting his under-manager to be too close to the metal. Often a good manager is measured by his ability to delegate. However, especially in the tech world, an over-reliance on underlings can be a career-limiting-move (CLM).
    – Jim G.
    Commented Sep 26, 2012 at 14:43
  • 1
    @Xav/Jim G: For the role of Team Lead/Manager, coding is priority 5; bitquabit.com/post/coding-is-priority-number-five Staying curious is one thing. Indulging that curiosity at the expense of the job that's in front of you? Different thing.
    – deworde
    Commented Sep 26, 2012 at 14:49
  • @deworde: I agree with you. Of course, even if coding is priority 5, a team lead/manager must remained "dialed in" to what his/her direct reports are developing.
    – Jim G.
    Commented Sep 26, 2012 at 14:54

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .