Suggestions for soon to be graduate

ITstudent1213

Just looking for some thoughts on this:

I am finishing up a 17 month IT Conversion course (see here) next month which has kept me very busy. I am applying for jobs, but I am thinking ahead in case I am not successful.

I have done quite well in the course (1.1 - majority A`s, otherwise B`s) so I think I have what it takes long term. In the new year (if I have not found a job) I was thinking of getting Oracle Java Certification:

http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=458&get_params=p_track_id:OCPJSE7

As well that I would work on building up my portfolio, perhaps by developing more Android Apps (have done a few basic apps as part of the course). I was also thinking of completing ITSQB Certification (Software Testing), as a testing job is a another possible route into employment.

What do you think of this plan?

I could go down the other route (IT Support, virtualization, networks etc) although I have chosen all my Final Semester modules with development in mind (Java, Android and Ruby).

John_Mc

If you like Development, don't even consider doing a course in Testing as you'll hate it if you ever go down that route.

t's a very good market for developers at the moment, but all look for experience. I'd keep working on your portfolio and skill set - maybe look at developing a few websites as these require a wide variety of skills that you'll need even if you don't get a web dev role.

You could also focus on scripting for batch and ETL.

You'll be a good graduate candidate if you can go into an interview and discuss or demonstrate, and will have no problem finding a good role if you're willing to move where the jobs are.

jester77

meh, I wouldn't be getting too bothered with certs especially the ISTQB unless you want to get into testing. Get your github account in shape with the projects you've been working on and get your android apps onto the marketplace. This in itself is worth more than any qualification.

There are lots of ruby and java projects out there, have a look at some of the ones that you are interested in and are familiar with from using, fork the project, play around and maybe even contribute back. I think your time invested in such things is better than time invested in the study for a certification.

angryInch

jester77 wrote: »

meh, I wouldn't be getting too bothered with certs especially the ISTQB unless you want to get into testing. Get your github account in shape with the projects you've been working on and get your android apps onto the marketplace. This in itself is worth more than any qualification.

There are lots of ruby and java projects out there, have a look at some of the ones that you are interested in and are familiar with from using, fork the project, play around and maybe even contribute back. I think your time invested in such things is better than time invested in the study for a certification.

This is about the best advice a new graduate can get.
There are so many ways out there to differentiate yourself from the competition.
Write an App (iphone or android), write a WebApp, get involved with a open source project (may be harder for a beginner), and keep informed on new trends in the industry (www.theregister.co.uk and www.dzone.com are a good start).

Reference the App, WebApp, Website, Open Source project you worked on in your LinkedIn profile and on your CV.
Most perspective employers will have a look at any on-line content or app that you link to, and if it look good in most places it will be enough to get you an interview.

All of the above also have the added benefit of getting you actually working on real software, a big advantage when doing an interview, as you can detail real problems that you encountered and how you figured a solution to them.

bpmurray

Be aware of the need to show your soft skills. You should be volunteering in CoderDojo or Silver Surfers, and contributing to an OpenSource project is a very good scalp for your CV.

You should also be learning new generic skills that will give you an edge. The skills that new graduates almost never have are:

A knowledge of Continuous Deployment with an understanding of the process. Set up a Jenkins server with a simple project, and automate it end-to-end, with unit tests, test coverage metrics, etc. Read up on JUnit, Copertura, Mockito for Java and Jasmine, Karma for

JavaScript.

Globalization requirements, with resourcing of strings, an understanding of character sets and Unicode, locale-specific collation & calendars, BiDi, etc.

Accessibility (US section 508 of the ADA or W3C WAI/Aria)

mad turnip

If you havent already start using a unix system and learn how to use it compared to windows through a command line.

Learn the basics and practise version control with any past projects you may have done.

angryInch

While learning all the skills above may be useful, what you really need to concentrate on is having something to show.
Its all very well saying that you have learned unix/linux (a very useful skill), Continuous Deployment (if you are writing something, you should try to use it), Unit testing (again, if you are writing something, you should try to add some) etc. but really, its just going to be a line on the CV, and will not have any great impact on someone reading it.
The best bang for you buck, is to have something tangible they can look at, it will give the perspective employer a real feel for your capabilities and will make you memorable.
Plus, it will show them you are capable of taking an idea and following it though to a completed product (a surprisingly rare skill).

fergalr

Big problem for employers, if you don't have experience, is figuring out whether you actually know the absolute basics of being able to code; many grads, even with good degrees, don't.

So that's the first hurdle to jump - make sure you are reasonable at coding, and make sure you can walk someone through a basic interview question that shows your coding skill (e.g. 'fizzbuzz'). If you haven't done this before, practice it.

Then, what angryInch said:
Build a project - such as a mobile app, or website, ideally in the area you want to work (eg. if you want to be a mobile developer, make a mobile app, etc.).
Make it modest (much more modest than you think. Seriously. Think 'lotto number picker', not 'e-mail client'.), but make it fairly finished (doesn't crash when it starts, looks reasonable). Be able to talk about it in an interview. Practice talking about it.

Be able to send someone a link to it, in your CV or cover letter, that doesn't look crap, and that they can quickly see it.


If its an app that they can't see until they install, maybe have a 1 minute video/screencast that demos the main functionality, that you can include a URL to in your cover letter or CV.


'Candidate has actually built something themselves, that I can see actually works' is a big differentiator.

Fussgangerzone

Well, you have a good attitude anyway, and keeping your options open. Although your good attitude might fade away if you go into testing! The only happy testers I've met are the bonkers ones.

I'd humbly suggest building things in collaboration with people like yourself. You can build something that's bigger, take on a more specialised role, and hopefully have something more impressive to show for it, as well build on your experience in collaborating with others.

You're probably quite personable, but putting yourself across well is massively important, too. At the extreme end, I've seen people with great work not make it past the phone interview because the interviewer thought they were insane. (These weren't testing jobs)