I've been studying computer science on my own for a few years, but I don't personally know anyone who programs.
I was wondering how you know when you're ready to start looking for a job? Does lack of formal education get in the way?
|
I've been studying computer science on my own for a few years, but I don't personally know anyone who programs. I was wondering how you know when you're ready to start looking for a job? Does lack of formal education get in the way? |
|||||||||||||||||||||
|
|
There isn't a specific checklist programmers check before saying, "Yep! I think I can work now." Most of us gauge our knowledge by helping out on forums/boards/in person meetings. If you can help people with programming problems, you consolidate what you know and you demonstrate your knowledge. Look around job boards online and see what the common requirements are for your given language. Python, for instance. What is generally asked for a python job listing? Google App Engine knowledge? Pygame? TKinter? Find that out and you will see how 'marketable' you are for a job. Having said that you are a programmer - many programmers don't even know what an interpreter is, let alone create one. |
|||||||
|
|
You're ready. Get out there and meet people. Join a local user group. Talk to people. Listen for opportunities. Don't focus too much on big companies. Instead, start with a small company that is willing to take a chance without the paper credentials. Consider an internship. Make yourself indispensable. In the meantime, build something useful for a stranger while you hone your skills on your own projects. Solve someone's problem and then showcase it when you apply for jobs, "See, I can solve your problems. I've done it before." |
|||
|
|
|
You might be interested in 'The Programmer Competency Matrix' found here: http://www.indiangeek.net/wp-content/uploads/Programmer%20competency%20matrix.htm There you can find some really useful information to check your skills systematically. The matrix lists 32 competency aspects in five categories, giving examples in four levels. |
|||
|
|
|
Go and do something for someone or yourself, perhaps start on guru.com until you're sick of it or craigslist.org looking for web gigs or stuff, you'll be fine if you can code, just go make things, that's the best resume, things, things are the best. But really, my best suggestion is to get involved in something open source, contribute a bunch, learn a bunch more, and be off to the races :) |
||||
|
|
|
You won't know until you start looking. But I do think that no education and experience will tend to get your resume filtered (I know it would at the handful of places I've worked at least). One idea is to take some interesting CS courses at a junior college. A lot of times the professors work in industry (especially if you take a night or saturday class). And if you're a stand-out, and you directly express interest to the professor, you might just find an opportunity. |
|||
|
|
|
You sound like you're ready. You will have a difficult time getting through the HR filter at large companies, but it is not impossible. In the current economy it will be tougher though. The biggest problem for you will be no proven history of developing and delivering projects. I have done many technical interviews. Once a resume got to me I didn't really care about where they went to school. I only cared about what they could do and if they could do the work. I would just throw your resume out there and go for it. Worst they can say is no... at least I think that's the worst... |
|||
|
|
|
You are ready when you can start teaching others. I started coding BASIC in my spare time at 13 in 1981 and got my first job a year later, teaching. However, it might have been easier back in the days. |
|||
|
|