First, work on typing more professionally. I received my first paid programming position while I was still in high school working for a collection agency handling data. At the time I was very excited and they informed me that I got the position for a few reasons. First, I was relatively inexpensive. Second, I was very professional in my interview and my resume was light weight but highly polished. Third, I had some of the technical skills they needed, but they felt that with my professionalism and my work ethic I would be able to complete the work. They were right, I did well and I moved on from there.
So, for you, I will go down this list. First, set your salary expectation according to your experience. Have you had other, non-technical positions before? If so, get ready to leverage them appropriately. If not, get ready for a very low salary for your first position. It is highly unlikely you will make $80k on your first position.
Second, work on your professionalism. "U" is not a word. "i", the first-person pronoun we all know and love, should be capitalized. You need to watch your punctuation. You don't need to be perfect, but work on your writing and presentation skills. How you present yourself really does matter.
Where you should be perfect, or as close as possible, is in your resume. Make sure it is polished. Make sure it presents you well. When you go in for interviews look your best. Lately in our business there is an attitude that everyone can come in looking like they are hung over after a long night of coding followed by partying, dressed like a skater, and often riding on a skateboard. You can look like this as long as you have skills to back that image up. If you are really Junior, and you are, you better look like the type of guy who is going to show up on time and get his act together to get some work done.
Third, be ready to show off and discuss your technical skills and most importantly, how you are going to acquire more. They are taking a risk on hiring you. There is a cost to hiring, training, and letting a developer work on your code. You need to show you will provide more value then you take back. From what you write above, I think you will have no problem showing your value.
Finally, getting a job, any job, is a numbers game. Apply to 20 different positions. You will interview at a bunch and you will get the one job you are looking for. After that, learn all you can and then feel free to move on when the time, and your skills, are right. Good luck!
i wrote all of it in good proper english but then had to trim it down a lot to bring it under 2000, and for some reason it still didn't work. So i deleted paragraph or two. Converted "and" to &, You to U...etc.
So, for you, I will go down this list. First, set your salary expectation according to your experience. Have you had other, non-technical positions before? If so, get ready to leverage them appropriately. If not, get ready for a very low salary for your first position. It is highly unlikely you will make $80k on your first position.
Second, work on your professionalism. "U" is not a word. "i", the first-person pronoun we all know and love, should be capitalized. You need to watch your punctuation. You don't need to be perfect, but work on your writing and presentation skills. How you present yourself really does matter.
Where you should be perfect, or as close as possible, is in your resume. Make sure it is polished. Make sure it presents you well. When you go in for interviews look your best. Lately in our business there is an attitude that everyone can come in looking like they are hung over after a long night of coding followed by partying, dressed like a skater, and often riding on a skateboard. You can look like this as long as you have skills to back that image up. If you are really Junior, and you are, you better look like the type of guy who is going to show up on time and get his act together to get some work done.
Third, be ready to show off and discuss your technical skills and most importantly, how you are going to acquire more. They are taking a risk on hiring you. There is a cost to hiring, training, and letting a developer work on your code. You need to show you will provide more value then you take back. From what you write above, I think you will have no problem showing your value.
Finally, getting a job, any job, is a numbers game. Apply to 20 different positions. You will interview at a bunch and you will get the one job you are looking for. After that, learn all you can and then feel free to move on when the time, and your skills, are right. Good luck!