I'm a current PM, previously a developer for a number of years. Here's what I would do:
Create a portfolio of side projects / sample applications in whatever language /framework you'd like to work with. You'll learn something, and have something to talk about in interviews. Then the interview process for a developer position is easy: show them what you've done and talk about how you built it. If your skills and approach are a good fit with the company, they'll hire you.
Another idea: create a profile on oDesk / equivalent and take small paying programming jobs. They may only pay $20, but you can gain experience, contacts, and credibility.
I do the same, but I like to have an external backup as well. What if Linode disappears and you need to rebuild on another hosting provider? Small chance I know, but multiple backups never hurt.
In my experience, most Canadian businesses won't consider you without the correct visa. I haven't really heard of too many companies sponsoring someone.
Have you considered doing some contract work through oDesk or similar? If you establish some contacts with American / Canadian companies and prove your value, they may be more inclined to help you come over.
I've hired a number of people. I'm usually not too picky about knowing a specific technology. I'm more interested in the soft skills, as well as proof they'd be able to pick things up quickly.
My reasons for NOT hiring someone:
- can't communicate well. I always ask them to draw something (like an ER diagram) and explain it.
- doesn't show examples of initiative
- doesn't seem passionate about career choice
- no examples of previous work
- (for recent CS graduates) can't explain something that should be part of standard CS study: eg NP completeness, what Big O notation means, etc.
I work at a consulting shop and manage the web app development team. This is a question we struggle with as well. We've called it "custom business applications", "web applications", or simply "business applications".
Sometimes, it helps to focus less on the technology and more on the process of how you'd help your clients and the value you provide. Don't bother mentioning that you do "web" apps (as opposed to mobile or desktop). Describe the process and how you do what you do. That gets the conversation going, after which you can start discussing technology.
That's just it. There are no "good ideas". Every idea may or may not work. You don't know until you try it. And execution is 90%.
Good execution of a marginal idea will likely succeed. Poor execution of a good idea will certainly fail.