by mattbettinson on 10/13/16, 10:11 PM with 6 comments
by pbadenski on 10/13/16, 11:31 PM
by viraptor on 10/13/16, 10:27 PM
Apart from this one: "Should I delay applications until I have another resumé piece and I'm a much better dev?" Applications don't cost a lot of time. A year ahead may be too early, but could give you some practice in interviews. Many of the students finishing normal university still don't know how to code anything. Much less actually finish and publish an app. Some are still terrified about the idea of adding a new class to a project. If you completed some actual projects, you're in a better position than many others.
If you apply around the time the semester ends your CV will be in a stack of tens / hundreds probably. Start earlier and don't stop until you find something.
by simantel on 10/13/16, 11:49 PM
As for finding work, I'd suggest choosing a handful of companies you're interested in and getting in touch with them now. You can talk to recruiters about when you should apply, ask about informational interviews, or if they have open-source projects, potentially start contributing to those.
If you live in the locale you'd like to end up in, I'd also suggest going to any meetups that interest you. Meetup.com is a great place to find these.
by shoo on 10/15/16, 5:03 AM
it sounds like you're likely already more capable than a few contractors i've worked with on enterprise software projects. (i'm in australia, things might be different where you are)
if you want to take a break, take a break. but if you want to keep learning how to build software, you're almost certainly already good enough just to get a job somewhere that'll pay you while you continue to learn
i'll second pbadenski's suggestion to reach out and ask a few people who are working in the industry.