So I now have 20 credits towards my computer science degree, and starting my next semester next Monday, taking 14 credits. At this point I don't feel anywhere close to being qualified for any type of good job in the field, but at around what point should I start thinking about that? Some possibly relevant information:
- I have a degree already, but it's liberal arts.
- I'm 31 and have varied work experience, but nothing special.
- I'm at this point more concerned with starting to get relevant experience than looking for the highest paid job I can find.
- I know the very basics of Java and C++, and like to think I'm a little more proficient than that at Python. I'm taking a more advanced C++ class this semester.
- I have not taken any sort of database design class yet, but am enrolled in one for this coming semester.
- I'm fairly proficient if a bit rusty with Office software.

What should I be looking for? I don't expect to get a job coding at this point, but does anyone have any recommendations for types of jobs I should be looking for to help get my foot in the door? I'm in Metro Detroit if by some lucky chance anyone knows of anything specific. Thanks!

You should be looking to get a coding job. There's no other job that will allow you to hone your skills more. If you're not thinking about and writing code you're just falling behind.

Sent from my SM-G900R4 using Tapatalk

Do you think that's realistic given my current skill set, or should I wait until I have some more classes under my belt?

I don't know what the coding job market is like in your area, but yea I'm sure you could get a job if you demonstrate reasonable proficiency to a company. My advice was more in general don't do something that's not coding unless you absolutely have to because if you're not writing and thinking about code on a regular basis you will lose proficiency. Getting a job in coding is even better because you may learn about building, maintaining, and coding in a production environment which is difficult to learn just banging out coding challenges or the like in your spare time to stay fresh.

Do codecademy's sql course to get a very rough idea of how db queries are written and how dbs are structured. It's better than nothing.

If you can't find any internships or entry level/junior positions, look for beginner testing jobs in the languages you know.

Also, go to meet ups. Networking is so vital.

+1 on looking for internships asap.

and +1 on learning sql. its super easy.

I would guess your entry level courses have taught you object oriented? if not, learn that ldo.

learn mvc too.

I'm taking database design and implementation with SQL and XML this coming semester, so looks like I'm on the right track there. Thanks for the meetups idea, I've already found some decent looking options for that in my area.

I really appreciate the feedback. I have few people in my life who know anything about this stuff and it makes it kind of hard for me to gauge where I'm at.

Don't wait to learn sql. Learn it now and let the class expand that knowledge! Nothing wrong with starting out ahead of other people.

Think Stanford has a good online class for sql too, which is part of Odin project's sql section

The Stanford SQL class is decent for the theory, but the SQL implementation from how to build a database, writing queries, to writing triggers, is plain horrible. I'd immediately reject anyone's opinion that is solely based on that class.

OP, just start applying now. No pain in testing the waters and seeing how far you can get. Getting over the fear of looking like a moron is a major step.

Use your university's resources to find a job now. I find that you will get a higher response rate through that.

Also start looking for summer internships now.

Like others said start applying now because you want the experience and the daily emersion of programming. Companies will look favorably at the fact that you are working towards a degree (they may even help pay for it), because it shows commitment, that you're a "doer" not just a "thinker", and "continuing education" that they themselves may lack.

As others said networking is key, join user groups, go to a SQL Saturday event, SAS has lots of stuff especially if you're near a major metropolis. Good luck!


Sent from my iPhone using Tapatalk

An observation I've had as I'm learning SQL and about databases generally: it seems like there is a large overlap between relational databases and OOP. As in, the related tables are like objects and the data therein is similar to the attributes of an object. Just something I've found interesting that I wasn't sure where to post. Thanks again everyone for your help, I've found a lot of stuff here extremely valuable this past year.

You were supposed to start applying a few months ago...

Go to career services and find all the on campus recruiting events ASAP.

It doesn't hurt to apply to places as long as you don't get too demoralized and as long as you don't make a poor long term choice just to get a job. Example of getting demoralized would be I started applying to places after taking my first 2 courses, and I didn't get a single interview for my first year. Example of how getting demoralized leads to poor choices: I started applying to QA positions, Project Manager positions, and Business System Analyst positions bc those were the only ones that would talk to me. Luckily I didn't end up taking any of those jobs.

Eventually things start to click with programming and systems concepts, so don't worry. It took me about 1.5 years for things to click.

As an aside, I would stay away from C++. There are a lot of nuances to that language, and it will be difficult for you to have an advantage over the kids using that language since they were 12.

My boss was traveling to campuses in my area recruiting this week. A lot of the people I am working with got hired through campus recruiting. If there is on campus recruiting, go! In addition apply to paid internships. If you are still early in your degree you are likely most suited to these. Also apply outside your metro area.

do you have to be a student to go to campus recruiting?