Hey guys,
So I am currently In my 4th year at college, which means I have to get off my lazy ass and start looking for a job. My goal is to have a job lined up that I can begin working at right after I get out of college, so I really need to get started yesterday. The problem is that my resume is looking pretty weak, and the more I think about it the more I realize that most of the stuff I do isn't really worth all that much, and definitely not relevant to a lot of the kinds of jobs I'm gonna be looking at, which will probably [I]not[/I] be game development related.
The problem is that basically any project I do [I]is[/I] related is game development in some way. I tend to not have any desire to do projects related to stuff like databases, programs that could be used in business or whatever, etc.
Anyway, here is a list of all of my 'skills':
[B]-Languages:[/B] I know C# and Java well. JavaScript, Visual Basic, SQL, HTML, C++ I'm familiar with but would take a bit of time to really be comfortable with.
[B]-Projects:[/B] I've released several script packages on the asset store: [URL="https://www.assetstore.unity3d.com/#!/content/37650"]PhysSound[/URL], [URL="https://www.assetstore.unity3d.com/#!/content/33148"]EZ Camera Shake[/URL], [URL="https://www.assetstore.unity3d.com/#!/content/28002"]EZ Object Pools[/URL], and [URL="https://www.assetstore.unity3d.com/#!/content/44565"]EZ Effects[/URL]. I also have about 2 dozen other Unity projects of varying sizes, and a few regular C# command line / windows forms programs.
Now for the completely irrelevant stuff that I feel like listing anyway:
-I know how to 3d model using Blender.
-I make music as a hobby (not even close to professionally, I don't even have any kind of hardware).
-I know my way around image editing softwares like GIMP and to a lesser extent Photoshop.
So yeah, other than my GPA being really good (3.965) and having a few items I can put under 'Honors', there isn't much that is relevant in terms of experience and skills. I just would like some advice on how I could put the 'experience' I already have on my resume, as well as what new things I should do.
Thanks a bunch in advance!
Hard to see how you're framing this stuff on your resume without seeing it, but you shouldn't have much of a problem finding a software engineering job with your experience. The company I currently work for (also first job out of uni) asked a few questions about how some real world example could be modelled using OOP (it was basically just some Users with a name, age, etc) and then a few general conceptual questions about databases.
I had no experience with databases, and I ended up working with angular and javascript, both of which are technologies I hadn't used before this job.
Oh, one thing to mention will be your experience in using version control and working in a team. Most of these people are more interested in how you will cooperate in a team, not how many technologies you are acquainted with. If you come across like someone who always wants to do everything yourself then you might have some trouble.
Good luck and hope that helps.
[QUOTE=nos217;48915830]Hard to see how you're framing this stuff on your resume without seeing it, but you shouldn't have much of a problem finding a software engineering job with your experience. The company I currently work for (also first job out of uni) asked a few questions about how some real world example could be modelled using OOP (it was basically just some Users with a name, age, etc) and then a few general conceptual questions about databases.
I had no experience with databases, and I ended up working with angular and javascript, both of which are technologies I hadn't used before this job.
Oh, one thing to mention will be your experience in using version control and working in a team. Most of these people are more interested in how you will cooperate in a team, not how many technologies you are acquainted with. If you come across like someone who always wants to do everything yourself then you might have some trouble.
Good luck and hope that helps.[/QUOTE]
Well, that makes me feel a bit better. I figured having experience with version control and working with a team would be a major point, and I do have experience with the basics of version control. And as much as I hate to say it, I really am the kind of person who likes to do things myself :v:. I think I might just be jaded by the many group projects where I wasn't really happy with the work other group members did.
I think the majority of developers like to do things themselves. It's a big part of the mindset of a developer. It's also why it's so important to probe that aspect of people when hiring them. Think about answers to questions like "tell us about a time when you had to think on your feet to save a project. What did you do and why? What did you learn?" because these are the sorts of things these people like to ask.
A good book on this subject is "Cracking the Coding Interview". He covers all of these things. Again, it's mostly about how you show yourself as a good learner, adaptable, good communication etc.
Sorry, you need to Log In to post a reply to this thread.
