4 ms·
If you can't find work as a developer, seek out development adjacent work and see if you can move into it. Things like (hands on) technical support/IT, quality
by toast0 5y ago
If you can't find work as a developer, seek out development adjacent work and see if you can move into it.
Things like (hands on) technical support/IT, quality assurance/testing, some customer service roles, etc.
Unfinished projects aren't too big of a deal, but make sure you highlight the relevant ones for the company you're applying for. As an interviewer, if I'm asking you about your project, I'm looking for some area where you have deep understanding, so I can confirm you know stuff and can explain things. It's ok for it to be unfinished, as long as you can talk about why you did x or y, how did this part work, what was missing, what would you do differently.
When you get those kinds of questions, you want to be able to have an answer, and not just blurt out; oh i stopped working on that pretty quickly. It's like when people put a group project on their resume but they didn't do much of the work and didn't understand it. Not a lot to talk about then.
I don't know if Ottowa has a junior/community college system, but it's possible to take some classes for not much money, you might want to consider it. It sounds like you've seen how hard it is to get your foot in the door without a credential, so you may be motivated to get one. Working something IT or something during the day and taking a class or two at night isn't easy and doesn't get you a degree very fast, but it puts you on a path.
- WheelsAtLarge 5y agoThis is a very good way to get the job you want. I've known a few people that could not get the position they wanted so they "snuck in" by getting a job, any job, at the company they wanted to work at and then talking their way into the position they wanted. If you show that you are a good worker then managers are more likely to take a chance on you.
- drakonka 5y agoJust chiming in to agree. I started working in embedded QA in 2008 and have made a couple of hops in those first years into more and more programming-heavy roles. Time-wise, I think the amount of time it took me to get into a full time programming role from QA was about the same as or a little less than the time it'd have taken to get a degree. So not necessarily a time saver, but that wasn't really my focus anyway.