I will work for free ...
swombat: I don't think this is a good approach.As an employer, I wouldn't want to invest the time in getting someone up to speed with my systems if they have no "lock-in" that means they'll stay with me until they've paid off for that initial ramp-up period (which would cost me time). I particularly wouldn't want to do so for someone who already has a job at a software company - I'd clearly be a distant second (if not third or fourth) priority in that person's life.Next, about the profile - I suggest you pick a narrow specialty that you really want to work on (e.g. Ruby on Rails), and focus on that. I don't think many people, particularly start-ups, are interested in hiring a "C#, Java, RoR, Silverlight, Ajax" guy. That long list makes you look unfocused and implies that you probably suck at a lot of technologies rather than being very good at a few.My suggestion to you would be: pick one technology with a thriving OS community (e.g. RoR), and contribute open-source software. That's one way to work for free that will greatly enhance your value to potential employers. Start a blog, talk about your experiences with Rails, promote your open-source projects, etc. You'll soon find paid work coming your way.